On Saturday, July 7, 2012 3:29:06 AM UTC+2, Joseph Lust wrote:
>
> Jens,
>
> We've not yet solved redownloading those pieces. However, the overhead is
> worth it to us so that we can redeploy just a single module (entrypoint).
>
As you said though, this is a "radical step", and you could have built
"harnesses" to speed-up debugging without changing the final output; just
like –as I've already said it here and there– Wave has a specific module
with a specific EntryPoint that loads only the rich-text editor, and
another one for the threaded UI: using only part of your components
("screens", "widgets", etc.) can greatly speed-up DevMode, and you can make
specific tools to help you in debugging (the rich-text editor harness of
Wave let you generate operation-transforms from a pair of text boxes and
see their results in the document, and shows how the document is
represented as a "wavelet" –that it correctly detects where your cursor is,
what the current selection is, etc. all the things that will be sent to the
server so others will see your caret moving on their screen; the thing we
now have in Docs for a year or two).
In Wave, this was an "horizontal split", but in an "enterprise" app you
could probably split "vertically" (the "admin" screens, etc.) Overall, the
smaller the "source path" (and if you can, the classpath too), the faster
the DevMode.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/l59DFosqluUJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
