Dave, We use the "new-ui" branch as a repository for the HTML+CSS files for the new UI. We have made several changes to trunk/server sinc the new-ui branch got created, so we don't use it to develop on. I suggest you use Dick's approach: " I didn't use the branch to develop but copied everything into an existing deployment based on the current code-base." This way we make sure we always developed against the latest code-base.
Hope this helps. Best, Anne On 22. des. 2009, at 22.37, Richard Hirsch wrote: > My new changes are in the branch. The first challenge is to get the > first page working with the public timeline. We have to add a comet > back-end that feeds just one message instead of 40 (which is the > existing implementation) and then map the existing javascript > (display_messages.js) to the new ids or change the new ui to match the > ids in the existing javascript. > > On Tue, Dec 22, 2009 at 9:50 PM, Dave Briccetti <[email protected]> wrote: >> I’m confused about where things are. I can svn checkout and mvn jetty:run >> from both trunk/server and branches/new-ui. Running the latter I see what’s >> obviously a new UI. Is this where I want to be, to observe the comet >> problem?
