You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Adonis Raduca <ad...@codebeat.ro> on 2009/02/18 14:16:23 UTC
Trinidad skin and demo rewrite
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
Re: Trinidad skin and demo rewrite
Posted by Andrew Robinson <an...@gmail.com>.
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 <ma...@apache.org>wrote:
> On Wed, Feb 18, 2009 at 6:54 PM, Kito Mann <ki...@virtua.com> 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 <
> adonis.raduca@codebeat.ro>
> > 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
>
Re: Trinidad skin and demo rewrite
Posted by Matthias Wessendorf <ma...@apache.org>.
On Wed, Feb 18, 2009 at 6:54 PM, Kito Mann <ki...@virtua.com> 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 <ad...@codebeat.ro>
> 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
Re: Trinidad skin and demo rewrite
Posted by Kito Mann <ki...@virtua.com>.
Hello Adonis,
I'm very glad to see this -- Trinidad _really_ needs a new demo :-).
---
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 <ad...@codebeat.ro>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
>
RE: Trinidad skin and demo rewrite
Posted by Alan Hancock <su...@gmail.com>.
Is the documented process of creating a skin?
I would like to create skin that is mostly white and blue, similar to the
Oracle ADF Faces skin. Trinidad needs a skin or set of skins that are
suitable for corporate web sites, which will help encourage adoption. A lot
of the productivity gains are lost in the effort required to develop or
modify skins.
_____
From: Adonis Raduca [mailto:adonis.raduca@codebeat.ro]
Sent: Wednesday, February 18, 2009 7:16 AM
To: dev@myfaces.apache.org
Subject: Trinidad skin and demo rewrite
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