Will work on improving RPC and JSON and not remove them. And agree, devmode is the next step. Also I want to write something about jsinterop although it's experimental.
On Thu, Jul 16, 2015 at 11:57 AM, Thomas Broyer <[email protected]> wrote: > > > On Thursday, July 16, 2015 at 10:50:12 AM UTC+2, Manuel Carrasco Moñino > wrote: >> >> Dear contributors: >> >> In my opinion there is a lot of stuff in our site which is obsolete, or >> is not useful or even could confuse new developers. >> > > +1 > > >> I also spoke with Julien and he agrees that we should remove many of the >> entries, so we want open a thread before in the mailing list to get some >> feedback from you. >> >> Although we can remove those page totally from the site, I think it >> should be fine if we remove links from our TOC, so as they start being >> removed from crawlers, but we don't break external links. >> > > +1 > And add a notice/warning at the top of the "removed" pages. > > >> These are the items I consider to be removed: >> >> * Tutorials -> AJAX Communication. >> - Introduction: is quite trivial and most people knows about ajax. >> - RPC: it's an old protocol >> > > …but we don't really have anything better to propose for now > (RequestFactory? It doesn't really fit in a tutorial, too complex). > > >> - JSON: it's a tedious task and makes the user feel that JSON in GWT >> is laborious, it says nothing about autobeans, or many popular gwt >> libraries widely used. >> > > …or JsInterop (though it's still "beta" as of the last release) > Also note that AutoBeans don't work well when the root of the JSON is an > array. > I think the JSNI approach is OK until we can safely recommend JsInterop. > > >> - Cros-site: it's out dated since does not say anything about modern >> CORS >> > > +1 to remove it. > > >> - JSON php: I don't think so many people are interested on php >> > > I wouldn't bet on that ;-) > But +1 for "hiding" it. > > >> I think everything here is obsolete or confusing. The only thing to >> maintain could be RPC, but >> >> So in my opinion we could either remove all points here, or just >> maintain the RPC section, picking up some paragraphs from the introduction, >> adding a disclaimer about it is a former protocol, and noticing that there >> are many other 3party options nowadays. >> > > Sounds good. > > >> >> * Tutorials -> jUnit testing >> We could remove this, since we already have a doc about junit, and we >> don't have to maintain this page which is outdated and a complex section >> for beginners. >> > > I would simplify it (remove the part about running the tests: just run it > like any other JUnit test, just make sure your sources are in the classpath > –like with the compiler and devmode–, this is all taken care of for you by > the plugin for Eclipse) but not remove it. > > >> * Tutorials -> GAE Deploy >> I don't think we should maintain it. Half of the tutorial is about how >> to setup a GAE project and how to use some stuff in server side. I think >> most of our audience might not being using GAE and there is plenty of info >> about how to deal with GAE in other forums. >> > > +1 > But on the other hand, it's the *only* page on the site that talks about > the AppEngineLauncher for DevMode. > > >> * Resources -> Presentations >> Everything here seems outdated 9/10 years ago, probably we should link >> or embed recent GWT events like GWT.create or GWTconf, but I think it's >> better to remove this section until we have something better. >> > > +1 > > >> >> * Resources -> Articles >> >> - GWT & Hibernate, is it still valid ? >> - Memory Leaks, is it still relevant ? >> - GWT iPhone, imo definetively should be removed. >> > > +1 > > >> * Resources -> Case Studies >> Probably we should disable this until we add some modern case studies >> because it seems like nothing happened in GWT since 2011 >> > > +1 > > >> * Resources -> Developer Spotlight >> I don't see so much value here right now, Link to submit more stuff is >> broken, linked gallery does not work anymore, project list is a query to >> google code, and videos are very old. >> > > +1 > > >> I volunteer to remove all those entries after your feedback >> > > Next step: rework the page about DevMode to no longer talk about "classic" > DevMode and the browser plugins. > > -- > 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/77ead255-598d-4378-9918-ab40501b39a6%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/77ead255-598d-4378-9918-ab40501b39a6%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/CAM28XAtw1uNEWSQ7TsSe%3D3G5bDdWaNMxRm64yHR-LwGD8ewUDw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
