"Like GWT, the documentation is in a book reader ("bookreader" means it is an AJAX reimplementation of static HTML -- so you get static pages, but search engines can't index it"
this is a standard well-known, well-understood problem associated with ALL ajax applications. as an AJAX developer, you will know this, and will have catered for it by providing HTML "alternative" pages, usually enclosed in < noscript > tags, along with a "redirect" to the AJAX equivalent so that any search engine people who see the "redirect" can see that the HTML "static" page looks identical to the AJAX equivalent, and don't cut your site off from the search engine. this problem has NOTHING to do with pyjamas, and EVERYTHING to do with AJAX. regardless of the AJAX framework chosen, be it GWT, DoJo, extjs, prototype - whatever: you WILL have to deal with this issue, period.
"you can't easily download it for off-line viewing"
it's a demo app, created by a free software developer (me), unpaid, in their free time - what do you expect, miracles? if you want me to create a special "PDF" button so you can download the same material for your convenience, *pay me*!
honestly, some people :)
"It wasn't compatible with the old Firefox we had there. I tried viewing them in the latest Opera at home. No go on the compatibility front"
where's the bugreport? did you raise a bugreport?
"It brags that it cut GWT's 80,000 lines to 8,000 lines, but it appears to have lost a lot of the functionality of GWT in the process. Part of this is that it is a thinner layer than GWT, but a big part of it is that it cut important things".
and? so? pyjamas does what the developers who CONTRIBUTE to it want it to do. if you don't like what it provides, *contribute*, don't complain. you can contribute in two ways to this unpaid and community-driven project: 1) code 2) money.
80,000 lines of code means that a team of engineers working round-the-clock, full-time, is required, and those engineers have to be paid money. a large corporation like google can sink large amounts of money into GWT.
by contrast, pyjamas is a community-driven effort.
"Pyjamas done right (which may happen in a year or two) would be sweet."
1) complaining and stating that pyjamas "isn't right" just because it doesn't do everything YOU want it do doesn't help, and is factually incorrect. pyjamas is quotes right quotes for those people who choose to work with it.
2) if it's "not done right", provide some code, or some money, to make that happen. otherwise, please do stop accusing the developers of having "done it wrong", and be grateful for what you get.
Posted Nov 16, 2009 5:01 UTC (Mon) by foom (subscriber, #14868)
[Link]
> this is a standard well-known, well-understood problem associated with ALL ajax applications
So, then, why isn't it well-known and well-understood that you should not use an AJAX
application where a standard HTML page is easier to create, more functional for users,
and better in every possible way (such as presenting static documentation)?
> if you want me to create a special "PDF" button so you can download the same material for
> your convenience, *pay me*!
No, I think he wanted a nice, simple, *non-ajax* normal webpage. Then he could've simply used
the browser's save menu option.