just tried this.
When I copied a built dll across, it did not appear in the list for the buttons (sample1 did fine).
So I copied the new openmobile.framework.dll to the openmobile folder and now openmobile crashes as soon as it starts.
Ok sample 2 attached...
I actually found a small bug in the framework so theres a new version included in the zip which fixes it and adds support for numosk (as soon as theres a skin for it).
It should give decent examples of using a list, the osk, and handling events.
I haven't done vb .net in awhile so there may be an easier way to hook events but I couldn't think of it and I know the code I used for the sample works.
openMobile - An open source C# Front End (why choose openMobile?)
- Always Recruiting Developers -
Like what you see? Donations are always welcome
just tried this.
When I copied a built dll across, it did not appear in the list for the buttons (sample1 did fine).
So I copied the new openmobile.framework.dll to the openmobile folder and now openmobile crashes as soon as it starts.
just wanted to say, good idea for getting developers to contribute.
works better than berating them......![]()
![]()
EWF, HORM, MinLogon on XP.
Zotac ION Atom N330, 2GB low-profile RAM, M3-ATX
Win Embedded Std 2011 RC
OCZ Vertex Turbo 30GB SSD
Lilliput 629 Transflective, WRX Screen Mount
BlueSoleil BT, i-Blue GM-2 GPS, DirectedHD Radio, Andrea Mic
VoomPC 2
signing the framework was supposed to make it easier but it seems to be too picky so heres everything unsigned. This should all work together just make sure to use the framework dll in this zip for compiling. Future changes should work just by swapping out the one dll.
Well hopefully it goes both ways... they get a better development experience (except for poor enforcer being the first to take the plunge) and a platform they know will last...and we get their help
openMobile - An open source C# Front End (why choose openMobile?)
- Always Recruiting Developers -
Like what you see? Donations are always welcome
I'll give that a go tonight.
OK, got that example working.
I now have a question/observation.
From what I can see at the moment the size and position of the controls seems to be determined by the plugin developer, is it planned to have this determined by the skin designer, otherwise the only difference between skins is going to be the colours and design of the buttons not the placement.
Well yes and no.
One of the biggest differences is that we separate plugins from skins. A skin (aka high level plugin) should really only be displaying data, where as the real work is being done by the various "low level plugins". For example, you could have one skin to display weather data and data provider plugins for france, england, the US, etc. That way you pick what features you want (like data, music player, etc) and then the look you want (since the skin is completely independent from the plugins).
Of course there is also support for serialized controls which means you can read in an xml file containing all the controls and their properties. The xml file can be done automatically in the skin designer or by hand. The reason we try to avoid this is that it slows things down (same reason we discourage use of ini files for settings).
openMobile - An open source C# Front End (why choose openMobile?)
- Always Recruiting Developers -
Like what you see? Donations are always welcome
So if I am not using ini or txt files for my data, where does it get stored?
*edit
BTW when I press the exit button (probably any buttons on the menu screen) the animation only does something in the top left corner of the buttons, looks weird.
See below
OpenMobile.Data.* (http://openmobile.sourceforge.net/wi...x.php/Database)
It's a shared thread safe database. If you want to start by using an ini or txt file and then once thats working start using the database that works too but the database will be far easier then trying to figure out why your plugins don't work right on linux or on multiple screens.
Edit-found it. It happens when full screen. Fixed as issue#10.
openMobile - An open source C# Front End (why choose openMobile?)
- Always Recruiting Developers -
Like what you see? Donations are always welcome
Bookmarks