Just for clarification, when mentioning proprietary tool, Simon is referring to Adobe Flash Player. Flex itself has been open sourced.
On Tue, May 13, 2008 at 11:23 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I'd vote -1 on accepting this project into myfaces. > > I don't think the idea of a bridge between jsf and flex is a bad one, > but I don't believe that a wrapper for a proprietory tool belongs here > at Apache. I would suggest sourceforge instead. Myfaces members who are > interested in flex (eg Hazem, Grant) can of course equally well work > with a sourceforge project. > > We could certainly add a link from our pages pointing at "related > projects", such as this one, either on the wiki or on the main site > itself. And I think it would be quite reasonable for release > announcements to be posted on the myfaces user list; people subscribed > to the myfaces list might be interested. > > BTW, until javafx is propertly open-source, I would probably also vote > -1 to a wrapper around that being hosted here. > > Regards, > Simon > > Hazem Saleh schrieb: >> If the idea is accepted, I can give a part of my time to implement the >> standard converters, validators and other stuff. >> IMO, alchemy is a very nice name ( I really like :) ). >> +1 for Gerhard idea. >> >> On Wed, May 14, 2008 at 1:20 AM, Jihoon Kim <[EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]>> wrote: >> >> Hi thanks for the feedback! >> >> Yes, I was intending to support the other jsf artifacts such as >> converters and validators in the future. In the contribution, I did >> create the components for Flex's validators and converters. But since >> they belong in a swf file, they technically are actual jsf components >> [in order to keep to the design]. Yet since all components that take >> input and updates the model extend from UIInput, I do not think there >> will be too many issues in supporting the regular jsf converters and >> validators. Of course when the contribution does get accepted, I do >> plan on investing my free time in creating support for standard >> converters and validators as well as other areas that I wish to >> improve upon. >> >> I think that's a good idea, since in the future I was hoping to check >> out javafx and other technology as well. >> >> Thanks!!! >> >> On Tue, May 13, 2008 at 2:27 PM, Gerhard Petracek >> <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> >> wrote: >> > hello, >> > >> > i had just a very quick look at it. >> > >> > do you plan to support existing jsf artifacts (e.g. converters, >> > validators,...)? >> > >> > @subproject and name: >> > for each topic you have to start at least a vote. >> > >> > what's about the following idea: >> > let's start a subproject for component libs like alchemy. >> > in the future it might be nice to have also a component lib for e.g. >> > javafx,... >> > >> > [new subproject] >> > |_ [alchemy] >> > |_[...] >> > >> >> > >> > >> > > >> > > > I would suggest that the best place would be as a new >> subproject, like >> > > > "orchestra" or "portlet bridge" are. It would definitely >> belong in the >> > > > MyFaces family (rather than anywhere else in Apache) but I >> don't think >> > > > it fits as part of Tomahawk. As I noted earlier, people who use >> > tomahawk >> > > > won't always want Flex, and people who want Flex won't >> always want the >> > > > other tomahawk components. >> > > > >> > > > It could also be a new "myfaces commons" module, but we >> haven't really >> > > > figured out how to structure those anyway. And it isn't >> really a >> > "common >> > > > module", but a component library just like tomahawk is. >> > > >> > > So is there any documentation in regards to how a code becomes a >> > > subproject of MyFaces? I would like to possibly look into that >> area, >> > > since if that is the path that might be taken; I would like to >> know of >> > > the process ahead of time. >> > > >> > > I did previously read through the process within the >> incubator, but >> > > wasn't sure if that was solely for a standalone project or >> applies to >> > > subproject as well. >> > > >> > > In the case that the contribution does get accepted and does >> become a >> > > subproject, I even have a name that I would like to propose, >> which is >> > > alchemy. >> > > >> > > Thanks!!! >> >> >> <http://www.jroller.com/page/HazemBlog> > > -- Sincerely, Ji Hoon Kim
