This question really belongs on the user list, not the dev list, but... Tap5 worked great for me for a mobile site recently. You can make it as lightweight as you want and still have the advantages of a component-based approach when needed. To make it work, about all you really have to do is add more pages to your existing Tapestry-based web app, probably with a different layout component tailored for the mobile pages. On Oct 31, 2012 5:19 PM, "Thiago H de Paula Figueiredo" <[email protected]> wrote:
> Hi! > > On Wed, 31 Oct 2012 09:59:05 -0200, tarunsamrai <[email protected]> > wrote: > > Tapestry adds a lots of components and assets on its own; >> > > Tapestry doesn't add components on its own, just the ones you declare in > your template. The assets are either used by the components you use or the > ones you've added. You can prevent the Tapestry .css file from being > included just by using a simple configuration key. You'd probably use > Prototype (provided by Tapestry itself) or jQuery (tapestry5-jquery) > anyway. Tapestry combines JavaScript files and gzips them and other assets > on the fly when the browser supports it. I really don't know what you meant > in the sentence above. > > but for mobile an app has to be as light as possible. And, hence I was >> thinking of starting from scratch and thought of using struts 1.3 which >> is very raw and not as sophisticated as tapestry. Please advice. >> > > Struts 1.x is horrendous and [your favorite cursing word here]. The worse > Java web framework ever. Its only value is historical, as the first Java > web framework largely used (instead of just writing servlets and JSPs), > nothing more than that. Stay away from it. Many years ago I've used to > teach it. That's when I started to hate it with passion. Just use Tapestry > and use just the components you really need. You can also build your own > which are more adequate for mobile. The huge amount of time needed for > writing anything in Struts (I cringe every time I remember > struts-config.xml, argh) will be better used writing your mobile site in > Tapestry, writing light pages and components, and tweaking T5 if needed > (which isn't hard and we on the mailing lists can help you). In addition, > you already have the non-mobile website working on T5, so you'll probably > reuse at least a good part of the web layer in the non-mobile version. > > Advice given. :D > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@tapestry.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
