[result][vote] start up a MyFaces Facelets project

[Mario Ivankovits <ma...@ops.co.at>]

Hi!

+1
Mike Kienenberger
Andrew Robinson
Jesse Alexander
Bruno Aranda
Mario Ivankovits

Not that impressiv than the MyFaces Commons vote, but passed anyway.

Ciao,
Mario

Re: Scope of MyFaces Facelets project

[Matthias Wessendorf <ma...@apache.org>]

On 10/30/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
> > Before this is considered "passed", could there be a re-definition of
> > the scope of this project as there has been some discussion?
> >
> For me the scope is to provide components which primarily works with
> facelets ONLY. There might be a JSP tag provided, but this is not a must
> have for the facelets project.
> In contrast, I think, a tomahawk component has to work with JSP in any case.

+1 it would be odd if a component lib. doesn't support the "default"
env. from the JSF spec, which is (today) JSP(x). So JSP should still
be first-class-citizen for Tomahawk.

-M

>
> That is the main difference I think. I don't want to contaminate
> tomahawk with facelets only stuff.
>
> Even if possible, I do not care if we move the tomahawk facelets taglib
> stuff in here. The best will be that tomahawk is self-contained, but I
> do not have time to get in touch with the generator, so, as a temporary
> solution we can add this taglibrary in here. Since this facelets project
> will be smaller it can have faster release cycles.
>
> > FYI, please also see my thread on the refactoring of Tomahawk with the
> > major intention to include facelets support in Tomahawk directly as a
> > new sub-folder (jar).
> >
> Yep, this is an interesting option.
>
> Ciao,
> Marip
>
>


-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org

Scope of MyFaces Facelets project

[Mario Ivankovits <ma...@ops.co.at>]

Hi!
> Before this is considered "passed", could there be a re-definition of
> the scope of this project as there has been some discussion?
>   
For me the scope is to provide components which primarily works with 
facelets ONLY. There might be a JSP tag provided, but this is not a must 
have for the facelets project.
In contrast, I think, a tomahawk component has to work with JSP in any case.

That is the main difference I think. I don't want to contaminate 
tomahawk with facelets only stuff.

Even if possible, I do not care if we move the tomahawk facelets taglib 
stuff in here. The best will be that tomahawk is self-contained, but I 
do not have time to get in touch with the generator, so, as a temporary 
solution we can add this taglibrary in here. Since this facelets project 
will be smaller it can have faster release cycles.

> FYI, please also see my thread on the refactoring of Tomahawk with the
> major intention to include facelets support in Tomahawk directly as a
> new sub-folder (jar).
>   
Yep, this is an interesting option.

Ciao,
Marip

Re: [result][vote] start up a MyFaces Facelets project

[Andrew Robinson <an...@gmail.com>]

Before this is considered "passed", could there be a re-definition of
the scope of this project as there has been some discussion?

FYI, please also see my thread on the refactoring of Tomahawk with the
major intention to include facelets support in Tomahawk directly as a
new sub-folder (jar).

On 10/29/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
>
> +1
> Mike Kienenberger
> Andrew Robinson
> Jesse Alexander
> Bruno Aranda
> Mario Ivankovits
>
> Not that impressiv than the MyFaces Commons vote, but passed anyway.
>
> Ciao,
> Mario
>
>