I think the goal is to eventually replace all mentions of DevMode in gwtproject.org with SuperDevMode with up-to-date information (now that DevMode is only usable in IE and GWTTestCase, but because of GWTTestCase we still need to talk about how code is executed in the JVM with a JS/JVM bridge, rather than compiled to JS).
From my POV, this would build on my blog post and StackOverflow answer.
…but note that in GWT 2.7 we introduce an easier way to run SDM with a single command-line, with the two servers in a single process (just like in DevMode, with an embedded Jetty server to host the webapp)
Feel free to propose patches to gwtproject.org if you have ideas (or just come discuss them on gwt-contrib); you have my permission to copy text from my blog post and StackOverflow answer.
On Mon, Jul 28, 2014 at 5:35 AM, Blake McBride <firstname.lastname@example.org> wrote:
Embarrassing. Yes, that is exactly what I was looking for. I've seen the link but never followed it because I thought it was meant to go into highly technical details that I wasn't yet up to.
It is clear that a lot of people are having a lot of trouble with SDM. There are a few good pages that contain valuable information on setting up SDM. In spite of this, many people are still having a lot of trouble. Perhaps I can propose this.1. Create a single "master" SDM page. Perhaps it would start with one of the already existing pages that tell a person how to setup SDM.2. The page would contain very detailed information on setting up and using SDM in eclipse, intelliJ, and NetBeans.3. It would contain links to all of the places this list points people to.4. It would be updated very often - even if the procedure hasn't changed. Every time someone is confused with the instructions, rather than just answer them, the "master" page will get updated to clarify the point in question.Every time some asks how to setup or use SDM, we can refer them to that single (root) page. If we do this, that page will quickly evolve into a single source containing the most up-to-date, complete, and unambiguous instructions.Just a thought.Thanks.BlakeOn Sun, Jul 27, 2014 at 3:39 PM, Thomas Broyer <email@example.com> wrote:
On Sunday, July 27, 2014 5:22:53 PM UTC+2, Blake McBride wrote:I spent a little time many months ago trying to get SDM working. I think I succeeded but was very surprised about the number of steps required. The thing that surprised me most, however, was discovering that I had to have two servers running (if I am correct) - an app server, and a code server. All of the docs I've seen provide the steps but never explain at a higher level what is going on (unless you understand far more internal details than many of us). The biggest difficulty occurs because the instructions were leading me down the path of two servers but I kept fighting it - trying to get one server to perform both functions. The fight occurred because I didn't understand what was being attempted. I didn't understand that I needed two servers running.So, what is needed is a better up-front description of what you end up with (two servers), and a block diagram that depicts the parts and the data flow between them. Understanding this would make the instruction much more clear.(Sorry if I am totally wrong and confused. Quite possible.)Does that help?
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.