neos team mailing list archive

[Johannes Wettinger <revager@xxxxxxxxxxxxxx>]

Now some feedback on the blueprint itself.  :-)

1) I suggest to move the repository link (UI prototypes etc.) into the
summary of the blueprint, because this is some static additional
information which doesn't belong to the specification itself.

2) For the "REQUIREMENTS & SPECIFICATION" chapter I think it would be
better to summarize the target as well as the requirements shortly;
otherwise you always have to go through the whole discussion in order to
get some basic information.

3) You don't have to link to the FR bug report because the blueprint is
already linked to it. ;-)

4) For the "DESIGN & TECHNICAL SOLUTION" chapter we should definitely add some more information about the implementation details, e.g.:
----
The whole assistant dialog will be re-implemented. After removing the class 'org.revager.gui.dialogs.AssistantDialog', we are going to create a new package called 'org.revager.gui.dialogs.assistant_dialog'. The package will contain the following classes:

AssistantDialog (extends AbstractDialog) - the assistant dialog itself which contains one of the following panels
FirstScreenPanel (extends AbstractDialogPanel) - the first screen (see prototype)
OpenReviewPanel (extends AbstractDialogPanel) - the open review screen (see prototype)
AddAttendeePanel (extends AbstractDialogPanel) - the add attendee screen (see prototype)

The AbstractDialogPanel contains the following property 'private
AbstractDialog parent' as well as the following constructor and method

public AbstractDialogPanel(AbstractDialog parent) { super(); this.parent
= parent; }

public void setHint(String hintText) { parent.setMessage(hintText) }

and will be located inside the 'org.revager.gui' package. By this
strategy we can access the description text area inside the dialog
itself.

Inside the AssistantDialog class there is one private property for each "screen class".
----

What do you think? ;-)

-- 
(FR) Startup-screen needs re-design
https://bugs.launchpad.net/bugs/493797
You received this bug notification because you are a member of Team
N.E.O.S., which is subscribed to RevAger.

Status in RevAger: In Progress
Status in RevAger 1.3 series: New

Bug description:
After choosing "instant review" on the startup screen (RevAger assistant), the user is offered the option to open an existing Review. But why? If there is already a saved review, this should be rather covered by the "scribe" mode already. Or is there something special about opening previous instant reviews?

Actually I think that both options offered there - the catalog manager and the "open review" function - should be part of the first screen, since they are not really mode-specific. Of course, putting all that those options in the startup screen would make it a bit too cluttered up, since we would have:

- Moderator mode
- Scribe mode
- Instant mode
- Language selection
- Catalog manager
- Open review

Maybe it would be worth considering a re-design of the first screen, i.e. offering only:

- Start new review
- Open existing review
- Open Catalog manager
- Select language

Choosing the first option would allow the user to specify the mode in the following wizard step.