Hi Adonis, this is a nice looking skin, much better than the default. Not sure if the skin really meets the current laf of Web-2.0 apps but it is indeed much much more sexy than current one. Thanks for doing this.
I wonder if you already had a chance to make the demo part of a real skin, and if yes, how did it go ? If we plan to add this, I'd recommend to not make it ASAP the default. Once the skin is stable we can change the default LAF. Thanks again, Matthias On Wed, Apr 8, 2009 at 10:15 AM, Adonis Raduca <[email protected]> wrote: > Hi, > > We finished the design phase for Trinidad, so now we have all elements > designed. > We also have a demo for Trinidad new skin ;) ... please look in the > attachment ... > > We intent to name this skin Casablanca, like a tribute to the water and the > sand. > Accordingly the convention for that interface is: > - we use a grayish-brown shades for all controls > - we use water-blue shades for selections for emphasizing > > So, that is, ... I hope you like it ... > > ciao > Adonis > > P.S. > Please use Firefox to this demo, I don't invested the time to test and to > make it work on all browsers for this demo. > There are only several controls in this demo, but if you want to see more in > order to have a complete image I can made some screen-shots. > > > On Wed, Feb 18, 2009 at 4:16 PM, Adonis Raduca <[email protected]> > wrote: >> >> Hi, >> >> Almost an year ago a discussion take place regarding the Trinidad skin and >> components demo rewriting. >> There is also an issue opened on wiki regarding this subject. >> http://wiki.apache.org/myfaces/Trinidad_MyFaces_Skin_and_Demo_rewrite >> >> Now I have some time and I want to start to work on this subject ;) >> >> Because I'm an organized guy I think is better to have a little action >> plan. >> So I've made this action plan that looks like this: >> - components overview (a little investigation on the already existing >> components) >> - components reclassification (we can improve the already existing >> classification of the components) >> - Trinidad shining mechanism study (very useful to understand what is >> possible what is not) >> - components skin design (all stuff regarding the components look and >> feel) >> - skin implementation >> - demo site design (components demo application look and feel) >> - demo site implementation (if is needed) >> >> For the beginning I've started with the component overview. >> So I made a table with all components and several related information >> like: >> - component category >> - a field that indicate if the component manifests in the visible way (is >> a button, a panel ...) or is a invisible one (like the iterator) >> - have interactive samples (demos) >> - is documented. >> - have skinning capabilities. >> - have skinning keys documentation. >> - a short description of the component >> >> All these information was taken from Trinidad component demo page: >> http://www.irian.at/trinidad-demo/faces/componentDemos.jspx >> >> Please look in the atached *.xls file. >> >> So, what do you think about this component overview table and about the >> approach in general ? >> If anyone find a wrong piece the information and/or posses information >> that is not present in this table, can notify me and I will made the >> required change. >> >> >> Have a nice day ! >> Adonis > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
