On Thu, Jul 16, 2015 at 1:04 PM, Jens <[email protected]> wrote:
> I think I would not invest too much work into the current documentation. > That is the reason this proposal for removing obsolete documentation. It does not requires so much work. > > I strongly believe we should create a team of 2-3 people that re-think a > new TOC along with a description what content each TOC entry should contain > and then write up a new, up-to-date documentation for the 2.8 branch and > later one for the 3.0+ branch. Without having a thought-out plan about the > documentation I think GWT will never have great documentation. We need some > people responsible for documentation. > +1, but it sounds like it would not be immediate, so in the meanwhile we can just remove obsolete sections > > Given your above proposal I think it is too much to remove. I would keep > the whole Ajax section and maybe just update the content a bit (it is > interesting for people coming from Swing, PHP is valid if you want to host > some simple stuff on any web host like the stock watcher example, RPC is > old but a valid choice because there is no suitable alternative inside GWT > SDK). Tutorials -> Junit is also fine as its part of the stock watcher > example app. Basically the whole "Tutorials" item is based on the stock > watcher app and should not be treated as single tutorials. > Well, being realistic, and at least in most projects I know few people using RPC in modern apps. They use solutions based on third party libraries and I have not seen large projects parsing Json by hand like we point in these tutorials. My proposal is not remove RPC and hide the rest from menus write a paragraph in RPC enumerating some alternatives (RF, AutoBeans, RestyGWT, gwtquery.Ajax, etc), but the current tutorial handling json makes GWT look as a complicated framework for doing Ajax. About the junit part we can simplify it like Thomas suggests. > > Also I think the GWT + Hibernate article is still valid (even for other > JPA providers like Eclipselink which we use at work). > > What I would definitely remove are: > - the GAE stuff > - all case studies > - developer spotlight (and then combine the remaining community pages > under the Resources -> Community section) > - from the Examples page the Notes example as well as every example that > is closed source and can not be easily tested in the browser right away > (instead maybe use something like "these companies use GWT as well: ...") > - all presentations. Instead I would link up GWT.create > presentations/videos and if some interesting stuff is missing you already > know a session for the next GWT.create. > good point > - all old books and all books not dealing with GWT proper (= no related > books) > yes should be removed as well > > > -- J. > > -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/56d35a78-d06c-4395-b177-3800c354db89%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/56d35a78-d06c-4395-b177-3800c354db89%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAumVDs%2Bcz3Xv%3DLqE%3Dz7g%2BaggR41e6qOsZQ%3DJOyHzAGjdg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
