Hi, I agree with Ali. The current myfaces-html5 module should not be seen as a total solution for "JSF += HTML5", but it is a good starting point for developers.
Regards, Jakob 2011/5/17 Ali Ok <al...@aliok.com.tr> > Hi, > > @HTML5 > > Release this stuff in the near future give us the advantage to know > which things are required to include on the spec to support it fully. > I don't see any technical reason why this couldn't be done, and given > the code available and the effort required I think it is worth to do > it. > +1 > > Would be cool to provide HTML5 stuff if platform supports it and > provide graceful degradation for legacy(IE) > Cagatay, I see you do it in PrimeFaces successfully, which is great. In > PrimeFaces you can freely include other open source libraries which do the > degradation for IE and legacy browsers. However that is kind of hard in > Myfaces because of the ASF and ASL policy. > I remember, once I couldn't find a reasonable flash video player whose > license is compatible with ASL. I tried to use one for automatic > degradation, then I decided to provide a way for component library users to > define their fallback. > > So, we have to write all of those stuff by ourselves which is really hard, > or bundle them outside ASF and use them the other way. > I say writing them are really hard, since writing that kind of JS for IE > and legacy browsers, which either ignore the standards or interpret them > wrong, are painful. > > From my point of view, current effort of Html5 support is useful for the > future and it is great to have a know-how about JSF+Html5 integration. Of > course that doesn't mean current codebase is not to be used in production. > > Cheers, > Ali > > On Tue, May 17, 2011 at 7:55 PM, Jakob Korherr <jakob.korh...@gmail.com>wrote: > >> Totally agreed, Leo! >> >> Regards, >> Jakob >> >> 2011/5/17 Leonardo Uribe <lu4...@gmail.com>: >> > Hi >> > >> > @HTML5 >> > >> > Release this stuff in the near future give us the advantage to know >> > which things are required to include on the spec to support it fully. >> > I don't see any technical reason why this couldn't be done, and given >> > the code available and the effort required I think it is worth to do >> > it. >> > >> > @Advanced ResourceHandler: >> > >> > It is good to know there is some effort to include this into the spec. >> > But I think our position related to changes or enhancements to do >> > should be if there is no technical reason that prevent us to include >> > it in a module or even inside myfaces core, the way to go is just do >> > it now and later if the EG is willing to include it, well, we can help >> > with that. >> > >> > In the two previous cases this advice applies. It is important that >> > myfaces can be seen as a source of innovation in jsf and develop these >> > ideas goes into that direction. Additionally, this helps to the spec >> > to move more faster and that's good for everybody. >> > >> > Leonardo >> > >> > 2011/5/17 Jakob Korherr <jakob.korh...@gmail.com>: >> >> Hi, >> >> >> >> @HTML5 >> >> >> >> I think a first alpha release of Ali's project would be very good to >> >> have in the near future >> >> >> >> >> >> @Advanced ResourceHandler: >> >>>Of course there should be some additional work in the JSF EG, but I >> think Jakob pinged Ed already on this topic, right? >> >> >> >> Yeap, we (the JSF 2.2 EG) are/will be working on it, see >> >> JAVASERVERFACES_SPEC_PUBLIC-947 >> >> >> >> The commons-resourcehandler module currently is a prototype for the >> >> new JSF 2.2 resource handler. It has the advantage that JSF 2.0 apps >> >> (even those running on Mojarra) can already use it (but more on that >> >> in the other mail). >> >> >> >> >> >> @JSF 2.2 prototyping branch: >> >> >> >> +++1! I'd like to have a branch for the resource-handler work! >> >> >> >> Regards, >> >> Jakob >> >> >> >> 2011/5/17 Cagatay Civici <cagatay.civ...@gmail.com>: >> >>> There is still no really lightweight component framework for >> >>> >> >>> JSF-2. >> >>> >> >>> I disagree :) >> >>> >> >>> The HTML-5 components from Ali are really great stuff too, but >> >>> >> >>> might take some time to be widely supported. But anyway, being >> >>> >> >>> a step ahead is always a good thing! >> >>> >> >>> Ali's work is great but why brand it as HTML5? JSF is widely used in >> >>> corporates which depend on IE so branding it as HTML5 might have a >> negative >> >>> effect on adoption. Would be cool to provide HTML5 stuff if platform >> >>> supports it and provide graceful degradation for legacy(IE). For >> example in >> >>> PrimeFaces I try to integrate HTML5 stuff like fileupload, >> charts(canvas) >> >>> with this way under the hood. "A component framework with HTML5 >> features" >> >>> sound better to me instead of just "HTML5 components". >> >>> On May 17, 2011, at 2:34 PM, Martin Koci wrote: >> >>> >> >>> Gerhard Petracek píše v Út 17. 05. 2011 v 11:59 +0200: >> >>> >> >>> hi, >> >>> >> >>> >> >>> imo we should prototype some jsf 2.2 features (at least in a branch). >> >>> >> >>> that would help the eg to specify some of the new features (like the >> >>> >> >>> window-id) easily and we can get the feedback of the whole community >> >>> >> >>> and we would have the basic implementation quite early. >> >>> >> >>> so we increase the chance that the new features won't have to be >> >>> >> >>> deprecated in the next version (see the target attribute of >> >>> >> >>> composite-components). >> >>> >> >>> ++++1 ! JSF need feedback from real usage before features are >> specified >> >>> (as final), not after. Only that way leads to framework with real >> >>> useability. >> >>> >> >>> since html5 is planned as a part of jsf 2.2, we should do the same >> >>> >> >>> here. >> >>> >> >>> >> >>> @lightweight component framework >> >>> >> >>> that might fit to tomahawk. >> >>> >> >>> >> >>> regards, >> >>> >> >>> gerhard >> >>> >> >>> http://www.irian.at >> >>> >> >>> Your JSF powerhouse - >> >>> >> >>> JSF Consulting, Development and >> >>> >> >>> Courses in English and German >> >>> >> >>> Professional Support for Apache MyFaces >> >>> >> >>> >> >>> 2011/5/17 Mark Struberg <strub...@yahoo.de> >> >>> >> >>> +1 >> >>> >> >>> Especially the advanced resource handler is a great goodie. >> >>> >> >>> Currently it is not easily possible to deliver those resources >> >>> >> >>> with a cache header. Of course there should be some additional >> >>> >> >>> work in the JSF EG, but I think Jakob pinged Ed already on >> >>> >> >>> this topic, right? >> >>> >> >>> The HTML-5 components from Ali are really great stuff too, but >> >>> >> >>> might take some time to be widely supported. But anyway, being >> >>> >> >>> a step ahead is always a good thing! >> >>> >> >>> >> >>> Also Tomahawk still contains a few features which might be >> >>> >> >>> interesting in JSF-2 (Marcus Büttner is using those) >> >>> >> >>> * file upload >> >>> >> >>> * table sorting >> >>> >> >>> * table autosuggest >> >>> >> >>> * isUserInRole (would be great in conjunction with CODI >> >>> >> >>> manages Voters?) >> >>> >> >>> There is still no really lightweight component framework for >> >>> >> >>> JSF-2. >> >>> >> >>> We could of course possibly drop all the 'basic' components >> >>> >> >>> like t:inputText and stuff. >> >>> >> >>> >> >>> LieGrue, >> >>> >> >>> strub >> >>> >> >>> --- On Tue, 5/17/11, Leonardo Uribe <lu4...@gmail.com> wrote: >> >>> >> >>> From: Leonardo Uribe <lu4...@gmail.com> >> >>> >> >>> Subject: [myfaces] ideas and things to do >> >>> >> >>> To: "MyFaces Development" <dev@myfaces.apache.org> >> >>> >> >>> Date: Tuesday, May 17, 2011, 3:48 AM >> >>> >> >>> Hi >> >>> >> >>> Thinking about how can we do MyFaces even better, I think >> >>> >> >>> we should >> >>> >> >>> focus on these areas in the short term: >> >>> >> >>> 1. HTML 5 project: there is some code in this area, so it >> >>> >> >>> is only >> >>> >> >>> necessary a bit of effort to get it out. >> >>> >> >>> 2. Enhanced Resource Handler: again we have some code. >> >>> >> >>> 3. Agent detection support: again, there is some code >> >>> >> >>> extracted from >> >>> >> >>> trinidad long time ago, but now with JSF2 we can do some >> >>> >> >>> cleanup/update over this project. >> >>> >> >>> Any suggestions? >> >>> >> >>> Leonardo Uribe >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> Çağatay Çivici >> >>> Principal Consultant >> >>> PrimeFaces Lead | JSF EG Member >> >>> >> >>> Prime Teknoloji >> >>> Bilkent Cyberpark, A-303d >> >>> 06800 Ankara/Turkey >> >>> Tel: +90 312 265 05 07 >> >>> http://www.prime.com.tr >> >>> >> >> >> >> >> >> >> >> -- >> >> Jakob Korherr >> >> >> >> blog: http://www.jakobk.com >> >> twitter: http://twitter.com/jakobkorherr >> >> work: http://www.irian.at >> >> >> > >> >> >> >> -- >> Jakob Korherr >> >> blog: http://www.jakobk.com >> twitter: http://twitter.com/jakobkorherr >> work: http://www.irian.at >> > > > > -- > My Blog: http://blog.aliok.com.tr > Twitter: http://twitter.com/aliok_tr > > -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
