What do you mean by "components/pages resolution" ?
-----Message d'origine----- De : Sebastian Hennebrueder [mailto:use...@laliluna.de] Envoyé : jeudi 3 septembre 2009 21:47 À : Tapestry users Objet : Re: Supporting multiple devices, eg. browser + mobile + TV Robin K. schrieb: > myapp/components // the ordinatry > myapp/wap/components / the wap overwrites > > We also already test this solution. It can be done for pages with not so > much pain. For components it was a lot more complex. We finally abandonned > this solution. > I assume that there are quite some things to do but wouldn't it be the cleanest approach with the maximum of reusability? It might be naive but doesn't it only require to adapt the page and the component resolution? I can already overwrite default components so there needs to be a kind of hierachical resolution already. -- Best Regards / Viele Grüße Sebastian Hennebrueder ----- Software Developer and Trainer for Hibernate / Java Persistence http://www.laliluna.de > > > Sebastian Hennebrueder wrote: >> The approach followed by Ramaze (a Ruby based framework) is to deliver >> different content depending on the suffix. >> >> I like the approach but Tapestry probably doesn't fit in very well with >> such a concept as content is created by Java Code or templates both in >> pages and components. >> >> The idea to setup a separate application introduces a lot of redundant >> code. >> >> What about a shadow directory structure holding components and templates >> I would like to overwrite. >> >> myapp/components // the ordinatry >> myapp/wap/components / the wap overwrites >> ... >> This allows to reuse what you can and replace what you need. >> >> Depending on the request you dispatch to one namespace or another. >> >> >> Best Regards / Viele Grüße >> >> Sebastian Hennebrueder >> ----- >> Software Developer and Trainer for Hibernate / Java Persistence >> http://www.laliluna.de >> >> >> >> Komiwes Robin schrieb: >>> Hi, >>> >>> We've done that here, and it wasn't a real pleasure party. >>> >>> but yes, for each component and pages, we can use the same system than >>> localization: i.e. : index.tml, index_fr.tml, index_iphone_fr.tml >>> >>> You've got to decorate a lot of internals services (PagePool, >>> ComponentTemplateSource), hack the locale and prey for no API changes in >>> the future. :-) >>> >>> I agree with others comments, a web for desktop browser should never be >>> the same web than a web for SmartPhones. You should do a specific >>> app/page for other devices. >>> >>> >>> Robin K. >>> - Atos Worldline >>> >>> >>> -----Message d'origine----- >>> De : Christian Edward Gruber [mailto:christianedwardgru...@gmail.com] >>> Envoyé : jeudi 3 septembre 2009 06:04 >>> À : Tapestry users >>> Objet : Re: Supporting multiple devices, eg. browser + mobile + TV >>> >>> I'd go further - interfaces for the blind, for the hard of hearing - >>> these are still more clients. If the user experience is going to be >>> substantially altered, then you can "convert" from some meta-interface >>> and have everything automatically expressed, but that often requires >>> that the framework make trade-off choices that are better handled by a >>> good User Experience designer. A lot of what makes a good iPhone- >>> ready application is a different user-flow that's consistent with the >>> device's unique properties. Shoe-horning a normal web-interface will >>> often result in a bad iPhone experience (though better than WAP >>> phones, to be sure). >>> >>> cheers, >>> Christian. >>> >>> On 2009-09-02, at 23:13 , Thiago H. de Paula Figueiredo wrote: >>> >>>> Em Wed, 02 Sep 2009 20:36:21 -0300, Alfie Kirkpatrick >>>> <alfie.kirkpatr...@ioko.com >>>>> escreveu: >>>>> So I think T5 helps separate concerns and assists in building >>>>> multi-device apps (ie. it's a decent framework to do this in), but >>>>> the >>>>> framework itself could do more if this becomes something many web >>>>> developers end up having to build for in future. >>>> What exactly could the framework do? There's a framework that does >>>> it: JSF. Then it got too complicated. Of course, we could be smarter >>>> than the JSF creators. :) But I agree with Howard: different devices >>>> with different capabilities, different frontends. >>>> >>>> -- >>>> Thiago H. de Paula Figueiredo >>>> Independent Java consultant, developer, and instructor >>>> http://www.arsmachina.com.br/thiago >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>>> >>> Christian Edward Gruber >>> e-mail: christianedwardgru...@gmail.com >>> weblog: http://www.geekinasuit.com/ >>> >>> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.