Thread: Latest source download via SVN (rev 54)

Another thing...

To stop it from starting with three screens (i have three monitors connected) i changed the following code in Core.Main from:

for (int i = 1; i < theHost.ScreenCount; i++)
UICollection[i].Show();

to

for (int i = 1; i < 1; i++)
UICollection[i].Show();

but I suspect this still loads all screens but only show's one of them. Is this correct?
If so, is it the best way to force it to use only one screen to modify the "theHost.ScreenCount" property?

Cheers
Borte

A few more things...

I'mm still looking at creating an MMI style skin for OpenMobile but I'm a little confused about what files I need to replace / compile.

As far as I have understood the MainMenu.dll is the skin file for the main manu interface and the UI.dll is the file for the media bar that slides in.
But what if I don't want a sliding media bar, what if I don't want the media bar at all? I guess that I'll just keep the UI.dll file more or less empty to stop it from showing anything.

But what if I don't want the sliding effect that it has at startup? This effect is started from Core.loadMainMenu which as far as I have understood should not be compiled or changed with a skin.

Originally Posted by Borte

Sweet! The media bar slides much smother now but it seems to slide in at a slower rate than sliding out. Is this due to actual different speed or the fact that is has to draw an increasingly larger portion of the screen when fading in rather than fading out?

Also when running it fullscreen at 1900x1200 the fade transitions from one screen to another are slow and someehat "jerky" too. Is this due to scaling of the images?

Yea thats a higher resolution then blueray being rendered with software rendering. Theres probably some more optimizations I can do but I wont make any promises.

Originally Posted by Borte

Another thing...

To stop it from starting with three screens (i have three monitors connected) i changed the following code in Core.Main from:


to


but I suspect this still loads all screens but only show's one of them. Is this correct?
If so, is it the best way to force it to use only one screen to modify the "theHost.ScreenCount" property?

Yup change the ScreenCount property in PluginHost to return 1; There will be a setting for this in the future but haven't quite gotten all of the settings finished.

Originally Posted by Borte

A few more things...

I'mm still looking at creating an MMI style skin for OpenMobile but I'm a little confused about what files I need to replace / compile.

As far as I have understood the MainMenu.dll is the skin file for the main manu interface and the UI.dll is the file for the media bar that slides in.
But what if I don't want a sliding media bar, what if I don't want the media bar at all? I guess that I'll just keep the UI.dll file more or less empty to stop it from showing anything.

But what if I don't want the sliding effect that it has at startup? This effect is started from Core.loadMainMenu which as far as I have understood should not be compiled or changed with a skin.

Well UI.dll is the media bar, the home, volume and back buttons and the top bar with the song info but you can put anything you would like there or even nothing at all (although I imagine you may want a volume button). You may want to consider status notifications though as opposed to nothing at all as these can be useful.

The slide down transition is hardcoded now but in the near future it will be read from an assembly attribute of the main menu, so you can set it to any transition you would like or nothing at all. For now feel free to change it in loadMainMenu and ill make sure its fixed in the next commit.

Originally Posted by justchat_1

Well UI.dll is the media bar, the home, volume and back buttons and the top bar with the song info but you can put anything you would like there or even nothing at all (although I imagine you may want a volume button). You may want to consider status notifications though as opposed to nothing at all as these can be useful.

I do want them I just don't want them to behave and appear in that manner.
What I'm trying to build is this system: http://microsites.audi.com/satellite...emulation.html
Which behaves and looks completely different than the exisiting OpenMobile skin.

Originally Posted by justchat_1

The slide down transition is hardcoded now but in the near future it will be read from an assembly attribute of the main menu, so you can set it to any transition you would like or nothing at all. For now feel free to change it in loadMainMenu and ill make sure its fixed in the next commit.

What if this could be done from the MainMenu.dll instad, controlling all the transitions or any other effect when loading the system. I'd prefer if this was all up to the "skinner" to decide.

Originally Posted by Borte

I do want them I just don't want them to behave and appear in that manner.
What I'm trying to build is this system: http://microsites.audi.com/satellite...emulation.html
Which behaves and looks completely different than the exisiting OpenMobile skin.

I figured that but you said maybe you would keep the UI.dll more or less empty so I just wanted to double check.

Originally Posted by Borte

What if this could be done from the MainMenu.dll instad, controlling all the transitions or any other effect when loading the system. I'd prefer if this was all up to the "skinner" to decide.

Thats pretty much what I was describing. And its implemented in the latest code but I want to finish up volume control before I commit this version. Basically MainMenu now looks like this:

Code:

[InitialTransition(eGlobalTransition.SlideDown)]
public sealed class MainMenu : IHighLevel
{
//All the code
}

This tells the Core what transition to use to first show the main menu and from then on all the transitions are under your control. If you don't include that attribute, it defaults to "No Transition". Technically we could have the MainMenu transition itself in (using any transition the skinner wants), which is what I think your describing, but this method should be more future proof and does pretty much the same thing.

Hey, can you add me as a developer to the sourceforge project? I tried doing ti thru the website but it says I need to send you a request. My name is extide on there too.

Also, can you please make it so that this thing compiles out of the box? Right now I need to change the output path of all the plugins so they end up in the right place, and that's rather time consuming and not really necessary. Thanks!!

Also, (sorry I hate to be so nitpicky) but can you possibly make sure to name all of your controls? There were some things like Label1 TextBox1

Ans, do you still want me to work on a Bass.NET plugin? it looks like it currently can play music, so I dont know what you are using right now.

Anyways great job man keep up the good work.

Originally Posted by Extide

Hey, can you add me as a developer to the sourceforge project? I tried doing ti thru the website but it says I need to send you a request. My name is extide on there too.

np...Added

Originally Posted by justchat_1

I figured that but you said maybe you would keep the UI.dll more or less empty so I just wanted to double check.

The reason why I said I'd keep it more or less empty was that I tought I had to use the ui.dll file since it's hardcoded into the core.

Originally Posted by justchat_1

Thats pretty much what I was describing. And its implemented in the latest code but I want to finish up volume control before I commit this version. Basically MainMenu now looks like this:

Code:

[InitialTransition(eGlobalTransition.SlideDown)]
public sealed class MainMenu : IHighLevel
{
//All the code
}

This tells the Core what transition to use to first show the main menu and from then on all the transitions are under your control. If you don't include that attribute, it defaults to "No Transition". Technically we could have the MainMenu transition itself in (using any transition the skinner wants), which is what I think your describing, but this method should be more future proof and does pretty much the same thing.

Sweet.

Is there somewhere I can look to understand the skin consept of openmobile? I know how it all works and so on I just need to understand your view at skinning so I can "attack it from the right direction". What I'm looking for is something along; yes you can do this, but no you can not do this...

I see that in the PluginHost.getSkinImage you're adding ".png" to the last name of the image to load from the skin folder. Does this mean that OpenMobile can only work with png files?

Also how do I set the startup size of the screen? The only way to do it as far as I could see was to change the actual size property of the ui usercontrol in the OpenMobile project.