Hi, the server side of web pushing does not depend on HTMLNode heavily, and it will be a relatively easy task to migrate it to another base. As only a few UpdateableElements present yet, it shouldn't take more than a day of work. I'll be skiing for a week from today, so I can look at the new templating stuff 2 weeks from now.
sashee On Fri, Mar 5, 2010 at 12:52 PM, Matthew Toseland <toad at amphibian.dyndns.org> wrote: > Bombe has built a simple, fast template library for us. This is faster than > our HTMLNode code and is remarkably concise in the code to use it. It's > great. This should be used/merged soon. It should be ready very soon if it > isn't now, although it will take considerable work to apply it everywhere. > > sashee has written (as a SoC project) a branch which uses GWT to "push" > update HTML, so that it updates dynamically in many areas - lots of status > pages, progress bars etc. This should also be merged soon, especially as > sashee has done some important work lately in preparation for its being > merged. It will however be turned off initially due to some nasty bugs. I > hope that we can get it ready and fully debugged and enabled by default > before 0.8, but even if we don't, it's much easier to maintain in the tree > than out of it, and there are large parts which sashee has undone in order to > get merged / maintain out of tree more easily, which will be redone after > merge. > > Unfortunately the two conflict. web-pushing uses UpdateableElement's, which > are a kind of HTMLNode, to implement its API. > > AFAICS what we need to do is merge web-pushing (I can do this), then figure > out a way to do a push API with Bombe's new templates (can you deal with this > between you?)? Any input? >
