Alright guys, I've got the basic elements of the GUI done up in processing, including the core objects to handle screen display, display of the keypad (absolutely essential for hardware w/o keypads - a little annoying for PC users, I know =), and the general workflow for handling input.
The Processing-based GUI uses the excellent ControlP5 library from Andreas Schlegel, who has been very communicative and fast to add some new features we needed to the library distribution.
Some notes about the intent of this GUI:
* It should run on any Mac, PC, or Linux-based computer
* It should run, as is, on any Linux-based PDA
* It should run, as is, on any Linux ARM platform
* Windows PDAs/Phones are a hope, but not direct target
* Iphone is not a target for this GUI
* Android is an eventual target, but dependent upon the Android Processing port
* It should enable all functionality without the use of a physical keyboard
* It should expose all functionality of the engine
* It should provide both quick and easy means of shooting a video, along with the ability to easily define the more advanced capabilities of keyframing and action scripting
* It should enable a first-time user to create their first video in under ten minutes
* It should enable experienced users to create simple videos (no AS/KF's) in under 1 minute
* It should abstract the user from the engine's complexity
** allow naming of axes, input by relative distance (inches or degrees instead of steps)
** allow manual control of axes using simple directional buttons
** abstract user from complex keyframe activities, instead provide options of "run action here, etc."
* Allow for both real-time interaction (changing of parameters on the fly) w/ engine, and 'scripted' style activity, where a user first inputs and checks all individual settings before uploading to engine
Included in the svn repo is a PDF of the latest worfklow document, I'll start working on getting more of the known conversations about the UI documented here in the forum.
For new developers: those who haven't yet contributed to the source code or design are very much welcome to suggest or make changes, no matter your programming abilities. However, until we've established a working communication channel between us and you, we will need you to submit them to us for inclusion, rather than letting you commit to svn directly. After a couple of submissions have been made successfully, at this point will grant access to commit to subversion. All we'll ask then is that you work in your own branch until everyone can agree that the changes be included - at which point in time we'll merge the code.
Please keep any discussion about the OM GUI development to this forum, that way everyone knows where to look. =)
The SVN repository for the code as it stands can be found here:
Some notes about this version (correct as of my posting this message):
* The only screens that are working so far are the movie menu->easy movie setup, and then the camera sub-menu there.
* There is no communication with the engine yet, we are simply laying out the UI presently
* There are still a lot of efficiencies to be gained and modularity to be added. Nothing is set in stone yet
* There is a known issue where left-navigation panel buttons are not retaining their clicked state. I broke this in some recent changes and will track it down and fix it in the next couple of days.
I look forward to your feedback and suggestions!