Yeah, after your previous post [not of this chain but from an another] regarding the structure =>
> [new sub-project] > |_ alchemy > |_ ... I thought it made sense to create a [new sub-project] and have Flex + JSF integration as a component library beneath it. However, since it made sense to name the component library specifically, I thought it would be better to name it FlexFaces [this way users will understand what it's about before they delve into it]. Then we could use more of a generic name Alchemy to specify the intention of the component libraries as its [new sub-project] name. Since Alchemy in definition is basically altering the form of an element, I thought the name would be fitting for the contribution as well as any other component libraries that integrates other technologies as well. Sorry about the miscommunication and let's direct further conversation regarding Alchemy proposal at the previous post http://www.nabble.com/-PROPOSAL--MyFaces-Alchemy-as-a-subproject-under-MyFaces-p17464170.html Thanks!!! On Tue, May 27, 2008 at 10:40 AM, Gerhard Petracek <[EMAIL PROTECTED]> wrote: > it was my suggestion -> +0.9 > reason: maybe a restructuring of component libs as a whole is essential? > at the moment: -0.5 (because there are some issues i haven't thought about > so far) > i think we should discuss it within an alchemy proposal. > > i think the main misunderstanding was: > we thought alchemy should be the name for your lib: > [new sub-project] > |_ alchemy > |_ ... > > maybe some other sub-projects fit in myfaces-extensions. > e.g. werner mentioned [1] orchestra. > > however, for me flexfaces and other similar component libs don't fit in > myfaces-extensions. > ok - i didn't wrote [2] it explicitly... -> no pure component libs. > > regards, > gerhard > > [1] > http://www.nabble.com/Re%3A-myfaces-groovy-support-first-pre-alpha-showcase-p17345888.html > [2] http://www.nabble.com/Re%3A--PROPOSAL--myfaces-extensions-p17474665.html > > > > 2008/5/27 Jihoon Kim <[EMAIL PROTECTED]>: >> >> Quick two cents regarding Alchemy. >> >> As discussed in previous posts and written within the following Wiki >> page => http://wiki.apache.org/incubator/MyFacesAlchemyProposal, I was >> thinking perhaps we have a new subproject named MyFaces Alchemy. >> Under this project, there will be component libraries such as >> FlexFaces [credit to Zubin Wadia and referral from Hazem Saleh for the >> name] which bridges Web 2.0 and other dynamic control solutions to >> JSF. >> >> So for example as discussed in a previous post: >> >> Alchemy [sub-project] >> FlexFaces [bridge of Flex and JSF] >> ... >> >> Thanks!!! >> >> On Tue, May 27, 2008 at 1:56 AM, Werner Punz <[EMAIL PROTECTED]> >> wrote: >> > Gerhard Petracek schrieb: >> >> >> >> ok - i'm fine with that. >> >> what i mean: there are also other suggestions out there (concerning >> >> alchemy) and it's a different kind of project - so let's discuss >> >> alchemy >> >> later on... >> >> >> >> regards, >> >> gerhard >> >> >> >> >> > Well this is indeed a good question I am working on a Tomahawk extension >> > project for dojo myself which will show the first sources in a few weeks >> > so >> > this cuts into the same wood as Alchemy, a set of dynamic controls which >> > will need a home once alpha stage is reached. >> > The original idea was to add it sort of as tomahawk extensions >> > but maybe we can find a common place for all this. >> > >> > >> > Anyway I dont think we should start to discuss that yet. >> > >> > >> >> >> >> -- >> Sincerely, >> >> Ji Hoon Kim > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces -- Sincerely, Ji Hoon Kim
