Chris Holmes ha scritto: ,,, > I had been thinking we'd just replace the backend UI technology during > the sprint, and do the actual UI rewrite later. But my thought on that > was that 1.7.0 would replace the UI technology and get stable, and then > 2.0 would be the new UI. But since 1.7.0 is just going to be the config > stuff, and hopefully rest interfaces, this means that it might be > advantageous to do the UI tech replacement at the same time as the UI > rewrite. Because I think it'd just slow us down a lot to fully > stabilize as 1.8.0. > > My other thought is that when replacing the UI with a new technology > we'll probably want to add in at least some of the little UI > improvements that Wicket offers. And then we'll probably be tempted to > fix the most egregious errors of the current UI, and UI improvements > will creep in, but won't be driven by a designer, and we'll end up > replicating work. I guess I'm also not convinced that it's going to > take 4 people 5 days to replace the UI tech.
I think the big question is, when do people learn about Wicket? If we are going to make a Wicket crash course at Bolsena, that alone will easily eat up 2 days (and btw, we need to schedule some time for whoever is teaching to learn how to use Wicket for good. I did read a Wicket book, but that was almost two years ago). It may also be a good idea to buy a few copies of "Wicket in Action" in PDF format (printouts won't be ready in time for the meeting). > So my thought was that the designer could work in parallel with the > development work, and get a bit of stability with the UI tech > replacement, but start to move on to the UI html and interaction design > replacement at the end of the week. And if we don't get all the way > there we'll at least be ready. And our designer can get some real good > exposure to geo stuff. > > But these are just some ideas I've been thinking about. If we feel it's > going to be a waste to have him there then we don't have to send him - > like we should feel it's a desired thing, since it is going to cost TOPP > a good bit. So what do people think? It may be a good idea anyways, so we'd start with 2 days of course whilst someone (you?) talks to the designer and make up a first cut of the new UI, then we spend half a day talking all togheter about the new design, and finally 2.5 days redoing the UI. How does this sound? Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
