User Story #332 (closed)
Opened 18 years ago
Closed 18 years ago
Managing windows
Reported by: | jburel | Owned by: | jburel |
---|---|---|---|
Priority: | major | Milestone: | 3.0-M3 |
Component: | Insight | Keywords: | iteration5 |
Cc: | Story Points: | n.a. | |
Sprint: | n.a. | Importance: | n.a. |
Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
How do manage windows?
Exploration and implementation of various ideas:
- old version i.e. A desktop and all windows in the desktop. Implemented in Shoola M2 only on JM's machine.
- Actual version: i.e. a taskbar and severals windows. dataManager, viewers, hiViewers. Implemented in Shoola M2
- Hybrid version: taskBar not visible. and the menu displayed by the taskbar is now added to the dataManager's menu bar. When the user opens a new viewer or hiViewer, the new window is added to the task bar. Reminder: The task bar is a service initialized (cf. Shoola doc and design) during the init process of the container, that agents can then access. So this approach doesn't break the agents/plugins architecture, b/c the entry is added to the task bar and the viewer (or hiviewer) has no reference to the dataManager. Implemented in Shoola M3. Really easy to roll back.
Comments
- First approach known issue: User has the ability to open several viewers/Hiviewers at the same time. The fact that we use a JDesktopPane slows down the painting process. This is an important point to take into account for final decision.
- Third approach: Give more responsability to the dataManager and really consider this agent has the entry point.
Change History (4)
comment:1 Changed 18 years ago by jburel
- Milestone changed from Unscheduled to 3.0-M3
comment:2 Changed 18 years ago by jburel
- Component changed from General to Shoola
comment:3 Changed 18 years ago by jburel
- Keywords iteration5 added; iteration4 removed
comment:4 Changed 18 years ago by jburel
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
We decided to go for the third version i.e. the hybrid one.
cf. client meeting 13/09/2006