Wow, I didn't realize either that there were bindings for clutter.
Printable View
Wow, I didn't realize either that there were bindings for clutter.
Just a thought... will you be using MDI?
Well-yes and no. No in the traditional sense. Virtually, however, kind of. Each "window" is actually a panel which takes up the whole screen. Multiple panels are loaded in memory similar to hidden windows and then when transitioning depending on the effect multiple panels may be visible. The exception that makes it kind of, is that navigation will be able to show a panel next to the main panel (next turn).Quote:
Originally Posted by Crinos
On top of that - panels can be used as overlays with multiple panels layered on top of each other. Each one potentially adding controls to the UI.
jw-Did you have something in mind?
Only if you where doing the same as I am, as in making "virtual childs".Quote:
Originally Posted by justchat_1
But I have not completely abandoned real MDI yet. At the moment, I'm playing with usercontrols from child to child.
You could just include the clutter.dll with your app. It is LGPL. The suck is that clutter also requires about 10-15 other dlls that you'll have to include for windows. All those are found quite easily on Linux though.Quote:
Originally Posted by justchat_1
What were you guys considering Silverlight for? Any specific use in mind? I'd stay away, personally, for this particular piece of software.
Well I think silverlight was listed as an option but I don't know if it was ever really in the "we're considering it" category. Its slow and buggy still and anyone who disagrees with me - try moving text, even for an animation or something - very blury. Why because they half assed the font engine until .net 4.0.Quote:
Originally Posted by KevinJD
As of right now the mockup I did was using GDI+ which maps natively using mono or .net on all platforms. I was originally just doing it to test some other things (all controls exist as true objects with events like click, etc. that can be hooked by the plugin using them). I released a small sample in the other thread to check performance when doing effects and feedback says it works pretty well so i'm going to leave that in and we can swap it out for openGL in the future. All of the calls are ones that easily translate over.
Alright question for the c#/skin devs. Would it be better to have button images selected from a dropdown with a list of button images the skin provides or to have an "open image" dialog so you can select any image you want?
Why not both? Like having a "Browse" or "More" at the end of the dropdown list that would allow you to browse you computer to find any image you want.Quote:
Originally Posted by justchat_1
That does sound good....the question though is how would that all work. For example, all the images used should be put in the skin folder so that when the app is distributed it can be easily skinned. So then should I have it copy over each image to the skins folder as its loaded?Quote:
Originally Posted by ws6vert