My new BuildOS interface...EXE attached!!!
 

Sup Folks,

Here's a new screenshot of new version and I attached a zip file for testing.

NOTE: Backup your current BuildOS.exe

Features:

1. OEM Size on the fly
2. Live monitoring of any folder change, or option.xml file change and auto reload.
3. Live monitoring can be enable/disable on demand.

TODO:

1. Save/Open/Save As
2. Complete the build ROM action

TESTING:

1. Live monitoring: you can edit any option.xml inside of OEM folder and the specific package will get reloaded and have light blue color. If you add a whole new folder into OEM folder, the program will auto reload the whole setup. I might put it as a single item reload just like the option.xml in future.


Let me know.

I refer the old way, that way i can see more. It is quick and convenience. If there is room for improvement, I would like it able to save the last selection choice, so next time open, you'll see the last pick

That's a good start vboyz. Can't wait to see the results.

I think gguru's has ya on the attractiveness factor. And quite a few more features as well.

Now if you're writing this in Java or planning on making a linux version... :P

- DogGuy

I like how yours has the file sizes at the bottom, very helpful!

thnx guys, in order to develop further, could someone please help me with all the command to build the temp/dump folder just like the current BuildOS is doing?

I would like to get everything I need first so that I can go ahead and do a full round of development and testing before going public testing.

Thanks.

It might be easier to build up on an already existing build os. Take a look at a couple and take the best parts from each. That way your already getting some feedback.

I welcome any work that advances what we do, but have to ask if you're re-inventing the wheel. GGuru's version of Bepe's app has already been well developed for what we do and he is continuing to tweak it. Perhaps work with him, but it seems redundant to spend time doing the work that has already been done. Just my opinion.

Bumps for updates...

verizonguy - do you mean that gguru's buildos (the one he did for the apache), works for the mogul?

Is source code available?

No, source isn't available. Why? Because there's magical code I didn't write in it and the owners asked me not to disclose it.

Does BuildOS (v.9.5) work for Titan/Mogul: no. Support for Titan/Mogul and Touch/Vogue will be available soon, however. [I only offer pre-releases to donators, so please don't clutter this thread or my inbox with requests]

so is there any new news on the new BuildOS that will be compatible with the vogue?
thanks, Jim.

Check PPCkitchen.org for any updates. There's nothing much new there right now - I got hung up on some massive internal changes for .nbf devices (Apache). On the plus side, after being broken for nearly a week, at least it isn't crashing anymore.

Vboyz - got your PM; I'm responding here becuase there are probably other's who want to know the same thing. In a nutshell, all BuildOS does is copy the OEM files to dump, resolve any conflicts, and build the registry. As usual, resolving the conflicts is a devil of a task. The later stages of inserting the files into the rom, encoding, and flashing can all be handled by existing external tools.

You asked about multi device at one time too...yes, you can do it. The front end (the BuildOS part) doesn't have to be any different, but the rest is device dependent.

BTW - We've added a host of tags to the option.xml file - you might want to take a look at some of them for display purposes (there are more being added with the next release)