Yes, good example. This can be done somewhat in advance (creating the sections with the text description of the new features), then It's relatively easy to capture and crop the final screenshots when we get to Release Candidate stage.
I think this kind of document makes it very easy to appreciate the incremental advances in UI and new features that have been added since the previous release. I'm strongly in favor and volunteer to create the document to put in the News section. Pieter On 3/10/06, Ted Leung <[EMAIL PROTECTED]> wrote: > Sheila Mooney wrote: > >> > >>> > >>> + There are no special demos, screen shots etc. for an alpha > >>> release. The > >>> existing demos/screens shots for 0.6 would remain on the project page. > >> > >> -1 > >> see my comment above. I think there should be "some" screen shots > >> showing new UI available for the 1st time in this alpha release, e.g. > >> list grouping. > > > > > > Where would you put this? On the readme. Keep in mind that some of the > > UI will be "test UI". For instance, we will likely not have the search > > box in the toolbar until alpha 3 but have a popup search dialog in the > > interim for alpha 2. It doesn't make sense to show some temp UI that > > probably won't look great anyhow. Perhaps the right approach will be > > to evaluate this per release. For example, it may not be appropriate > > to have screen shots in alpha 2 but maybe for alpha 3. > I'm not advocating that we include screenshots, etc, but the Eclipse > project does do this kind of thing. Here's an example > <http://download.eclipse.org/eclipse/downloads/drops/S-3.2M5-200602171115/eclipse-news-M5.html> > > Ted > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > Open Source Applications Foundation "Design" mailing list > http://lists.osafoundation.org/mailman/listinfo/design > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
