To the best of my knowledge, those particular pages are not currently maintained. They would be old versions compared to the current state of things.
Could I ask what you are trying to accomplish and perhaps we can help you out?
Since the core framework is evolving, many plug-ins need to be recompiled against it so depending on what version of the core you have, you need to make sure you have the plug-ins that were compiled against it. Mix-and-matching does not work well.
Have you tried downloading the last release (v0.8) and install plug-ins via the installer utility?
The only other option at this time is to wait just a bit longer for the devs to commit the interim (test) release. I really wish I could be more help on this.
Well, time for another update. We know how folks don't like extended periods of silence. I know I don't. So we want to list changes that have been made since returning to active development.
You can expect these (and a couple more) when the test release is posted. With several of these changes, major hurdles to Multi-Zone have been overcome:
- OMLabel: BUGFIX: Corrected a small bug with text not being rendered at the correct width
- OMPanel: CHANGE: Named access marked as Obsolete
- NEW: Added support for direct access of panels controls (same as screenmanager but directly from the panel), Usage: PanelName[screen, ControlName]
- NEW: Added missing decrease and increase z order methods
- NEW: Added direct panel events: Loaded, Entering, Leaving and Unloaded
- OMTextBox: NEW: Added support for autofit of text, Usage: TextBox.AutoFitText = true;
- PluginSettings: CHANGE: PluginSettings now creates the database and tables if missing at first access of settings
- OMDialog: NEW: Support for more icons in dialog added ("OM logo" and "Work in progress")
- HelperFunctions: CHANGE: class eventMonitor marked as obsolete, use direct panel events instead.
- NEW: Control helper functions class added (HelperFunctions.Controls) which supports certain grouping of controls like an Up/Down control group
- OSSpecific: NEW: Added method for getting OS and App environment info (32 and 64 bit) (also added in Platform.Windows)
- AssembleyInfo: CHANGE: Last part of version number is now autoincrementing.
- SafeThread: NEW: Added additional methods that removes the need for passing a pluginhost reference along as a parameter.
- ScreenManager: NEW: Added code to support new OMPanel functionality
- GameWindow: CHANGE: property Keyboard and Mouse renamed to DefaultKeyboard and DefaultMouse
- KeyboardDevice: CHANGE: ToString now returns the proper string for usage in InputRouter
- MouseDevice: CHANGE/NEW: Modefied to properly support direct mapping of touch screens
- OImage: BUGFIX: Added additional locks to prevent access problems
- Windows.API: NEW: Added additional api calls to support more OS functions
- WinGLNative: CHANGE: Modefied to properly support direct mapping of touch screens
- WinRawMouse: CHANGE: Modefied to properly support direct mapping of touch screens
- Graphics.Structs: NEW: Added StyleToFormat method
- CHANGE: Added support for setting fontsize directly in font data
- Core: BUGFIX: Change the IBasePlugin cast to properly support VB plugins
- InputRouter: BUGFIX: Completely rewritten to better support touchscreens and unit mappings.
- PluginHost: NEW: Added StartupScreen property
- NEW: Added support for grabbing data from inputRouter for usage on skins (eGetData)
- NEW: Added support for trigging showIdentity from other classes.
- RenderingWindow: BUGFIX: Multiple changes to better support touch screen input
- MainMenu: NEW: Additional errorhandling
- OMDebug: NEW: Even more debug info added
- OMDialog: BUFIX: Fixed autosize of dialog form
- OMDir: BUGFIX: Fixed directory structure data from not showing in certain cases
- OMSettings: CHANGE: MultiZone skin rewritten (plugin needs further clean up of code)
Quite an impressive list. The test will be released after internal testing and verification. As mentioned previously, we need to ensure that even the test version will be stable enough for folks to play with. Default plug-ins will be included. Optional plug-ins would not be included in the test release. They would need to be updated by their respective authors anyway using the updated framework.
Last edited by jmullan99; 08-30-2011 at 08:53 AM. Reason: Spelling
Ooo... nice list of updates here. Although, as a dev myself I gotta pick it apart a little if I may, to see a little more of the specifics that might be useful.
Can we still use screenmanager, or is that obsolete now? Aka, I'm guessing this new method would take over (OMControl)manager[screen,"optionalpanelname"]["controlname"]?•NEW: Added support for direct access of panels controls (same as screenmanager but directly from the panel), Usage: PanelName[screen, ControlName]
Does this include wordwrap formatting if text is too long for the line, but the textbox has enough of a height to include more lines?•OMTextBox: NEW: Added support for autofit of text, Usage: TextBox.AutoFitText = true;
Up/Down of groups specific, or groups in general? Meaning you can add a group for whatever controls you like and, for example, moving the group would move all the controls in that group at the same time?•NEW: Control helper functions class added (HelperFunctions.Controls) which supports certain grouping of controls like an Up/Down control group
Are current SafeThreads with the pluginhost param needing to be changed? IE: Current way of coding them obsolete?•SafeThread: NEW: Added additional methods that removes the need for passing a pluginhost reference along as a parameter
And finally, are these changes commited already/going to be? Or, will they not be available until the actual testing/release phase?
instead of going trough the screenmanager. This does however mean that you have to keep a reference to you panel in you plugin rather than the screenmanager so I guess it's a matter of personal preference.Code:((OMLabel)panelZone[screen, "Zone_TextBoxAudioUnit"]).Text
Failure is not an option...
The only full multizone / multiscreen cross platform open source Front End -> OpenMobile
I'm a little late with an update. Been away to British Columbia to attend my daughters wedding and visit with family.
Work continues. Mostly tracking down a few bugs. The latest commit to SourceForge is #652. Again, as mentioned before, there is no guarantee that the latest code is stable and wont be changed/broken. A stable release for testing will be announced separately.
Have a great weekend!
Sounds like it was a good trip!I'm a little late with an update. Been away to British Columbia to attend my daughters wedding and visit with family.
My dev'ng slowed a little since I've been having touch troubles in the car that's been taken up a lot of time. I'll have to grab a 'newer' commitment soon and see how the changes are for the dev's!
EDIT: Just played around with revision #652 for a minute... ControlDemo plugin crashes when clicking the Toggle Buffer :wink:... I'll check out the dev'ng stuff later today while watching football .
Below - snippet of Debug.txt
It was an excellent trip!
I hear you on the hardware things. In testing, I actually find different things between my desk setup and the car. Hardware is definitely 1/2 the challenge and can be a nuisance for sure. I have not bothered to try the controldemo. Not yet.
Anyway, best of luck with your touch screen issue.
Well, it's been a slow week-and-a-half on the development front
Real life has kept the devs occupied with long days and even weekends. One has had some hardware malfunctions which doesn't help either.
At the risk of sounding like a broken record, minor progress has been made. Some pre-existing bugs, from several versions back, have become "visible" with the correction of other bugs. For instance the improper audio device assignment to zones in multi-zone use. Also now my install is crashing when adjusting the volume slider control.
Nobody more than the devs themselves want to see a test release made available. But none of us wants to see an unstable and/or unusable app for folks to test. Including myself. Before I jump to adding my third zone. Releasing a test version also requires modifying the default plugins to match the changes in OM. But that step should not take very long.
So, I know the reaction: "ya, ya, more delays". Even I feel that way sometimes. But the loyal followers will be rewarded with an excellent front end.