+1 let me use that...
On Thu, Jan 20, 2011 at 12:16 PM, Jakob Korherr <jakob.korh...@gmail.com> wrote: > Maybe MFHTML5 like we did in MyFaces commons (--> MFCOMMONS). > > Regards, > Jakob > > Am Donnerstag, 20. Januar 2011 schrieb Matthias Wessendorf > <mat...@apache.org>: >> the issue is, something like MYFACES-HTML5 does not work (because of -) >> :-) >> >> On Thu, Jan 20, 2011 at 8:18 AM, Gerhard <gerhard.petra...@gmail.com> wrote: >>> +1 for a new jira project >>> regards, >>> gerhard >>> >>> http://www.irian.at >>> >>> Your JSF powerhouse - >>> JSF Consulting, Development and >>> Courses in English and German >>> >>> Professional Support for Apache MyFaces >>> >>> >>> >>> 2011/1/20 Matthias Wessendorf <mat...@apache.org> >>>> >>>> Question: >>>> >>>> Should we add a new JIRA project (MYFACESHTML5) >>>> Or is it enough to have a HTML5 component ? >>>> >>>> I personally don't mind having a new project for it.. >>>> >>>> -M >>>> >>>> On Thu, Jan 20, 2011 at 6:06 AM, Matthias Wessendorf <mat...@apache.org> >>>> wrote: >>>> > Nope >>>> > >>>> > On Wednesday, January 19, 2011, Ali Ok <al...@aliok.com.tr> wrote: >>>> >> Hi, >>>> >> >>>> >> totally - let's create a jira instance for myfaces-html5 ?Do we need >>>> >> voting for this? >>>> >> >>>> >> Cheers,Ali >>>> >> On Tue, Jan 18, 2011 at 3:50 PM, Ali Ok <al...@aliok.com.tr> wrote: >>>> >> >>>> >> Hi, >>>> >> For example, for the hx:video component there is a "fallback" facet. >>>> >> But I can't say we're able cope with this problem (yet). So far, I've >>>> >> experimented Html5, CSS and other Javascript APIs; created some >>>> >> components, >>>> >> behaviors and etc. >>>> >> >>>> >> >>>> >> Providing fallbacks automatically is not that easy and for some >>>> >> features, it is impossible. Of course, we would have allow users to >>>> >> plug in >>>> >> their fallbacks.That would be an important part of this project. >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> How do others cope with this situation? Is there an established pattern >>>> >> for this case? If so, then we should add it to our WIKI.There is a >>>> >> Javascript library called "Modernizr" [1] which can detect the support >>>> >> for >>>> >> features. AFAIK, people use that to use Html5 features or fallback to >>>> >> old >>>> >> stuff. >>>> >> >>>> >> Furthermore, Html side of the Html5 (Html + JS APIs + CSS3) mostly >>>> >> designed in a way that old browsers will just ignore the component, but >>>> >> not >>>> >> it's children elements. So, that is another way of providing fallbacks, >>>> >> as >>>> >> nested elements, since new browsers will consider the Html5 elements, >>>> >> but >>>> >> ignore it's non-applicable children. >>>> >> >>>> >> >>>> >> [1] https://github.com/Modernizr/Modernizr >>>> >> Greetings,Ali >>>> >> >>>> >> On Tue, Jan 18, 2011 at 3:31 PM, Mark Struberg <strub...@yahoo.de> >>>> >> wrote: >>>> >> Please allow me a question (I'm a complete noob on this topic), just >>>> >> for getting the 'big picture': >>>> >> >>>> >> The html5 components are obviously only for html-5 compatible browsers. >>>> >> >>>> >> Is there a strategy to also serve older (xhtml-4 only) browsers? Or do >>>> >> we just show them a 'not available for your old browser' page in this >>>> >> case? >>>> >> How do others cope with this situation? Is there an established pattern >>>> >> for this case? If so, then we should add it to our WIKI. >>>> >> >>>> >> LieGrue, >>>> >> strub >>>> >> >>>> >> --- On Tue, 1/18/11, Matthias Wessendorf <mat...@apache.org> wrote: >>>> >> >>>> >>> From: Matthias Wessendorf <-- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > -- > Jakob Korherr > > blog: http://www.jakobk.com > twitter: http://twitter.com/jakobkorherr > work: http://www.irian.at > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
