Note that I started a new demo, but got tired and have taken a long break. The source code is here:
https://svn.apache.org/repos/asf/myfaces/trinidad/branches/exhibition_branch The demo is a new example: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/exhibition_branch/trinidad-examples/trinidad-exhibition/ The skin is here: https://svn.apache.org/repos/asf/myfaces/trinidad/branches/exhibition_branch/trinidad-skins/myfaces-skin/ I would be willing to re-create this branch off of the current trunk. It is already setup for correct deployment (skin jar file). I just got into having to work with some renderer issues (they have been addressed since) and kept debating what should be in a demo skin vs the actual skin (like a watermark, should that be in the myfaces-skin ?) I would love to have help on the skin side and I could do more of the demo side. With some help, I could get motivated to work on it again. -Andrew On Wed, Feb 18, 2009 at 11:06 AM, Matthias Wessendorf <[email protected]>wrote: > On Wed, Feb 18, 2009 at 6:54 PM, Kito Mann <[email protected]> wrote: > > Hello Adonis, > > > > I'm very glad to see this -- Trinidad _really_ needs a new demo :-). > > +1 > > Trinidad has a pretty solid framework, but the default look-and-feel > (and the other skins) are really....oldschool. > > Looking forward to see the result, Adonis! > > -Matthias > > > > > --- > > Kito D. Mann -- Author, JavaServer Faces in Action > > http://twitter.com/kito99 http://twitter.com/jsfcentral > > http://www.virtua.com - JSF/Java EE consulting, training, and mentoring > > http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info > > +1 203-404-4848 x3 > > > > > > > > > > > > On Wed, Feb 18, 2009 at 8:16 AM, 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 >
