I'm going to extrapolate further on the afore
mentioned Dashboard layout to describe the second
level of windows that could be accessed by double
clicking items in any of the Dashboard's frames.
This is given in line below.
--- selva r <[EMAIL PROTECTED]> wrote:
> Im making a modification to my recent suggestions
> on
> this thread regarding a possible 2 or 3 frame model
> for Dashboard.
>
> As it stands now, we would have an ideal base from
> which to build on for user friendly triaging even in
> high email volume situations, as well as for
> creating
> user friendly drag and drop stamping processes.
>
> However, the main weakness at this point is that it
> forces the user to double click an item from any of
> the list views inside each frame in order to read
> the
> content of the item. We could remedy this by adding
> an extra tab to each frame so that users are not
> forced to double click an item to read its
> contents.
>
>
> Hence, when a user selects an email from the list
> view
> of the email InBox in Frame 1, four potential tabs
> may
> be created for that frame depending on the
> qualifications of the selected item:
>
> Tab 1 - for the original InBox list view itself
> Tab 2 - for displaying the contents of the selected
> email
> Tab 3 - for displaying all messages in the thread of
> the selected email
> Tab 4 - for displaying any collections that the
> selected item may have been previously assigned to
> by
> the user.
>
> Similarly, when a user selects a memo from the memo
> list view in Frame 2, up to three tabs may be
> created
> depending on the qualifications of the selected
> item:
>
> Tab 1 - for the original Memo InBox list view
> Tab 2 - for displaying the contents of the selected
> Memo
> Tab 3 - for any linked items
>
> If, in the future, Frame 3 might be employed for
> triaging and stamping of OOo documents then this
> could
> be approached similarly to the Memo frame.
>
> Tab 1 - for the original OOo document file list view
> Tab 2 - for displaying the first few lines of the
> selected document
> Tab 3 - for any linked items
>
> Hence, in practice, the user would have the choice
> of
> either reading the selected item contents either,
>
> (a) within the frame itself (by single clicking the
> item from the list view and then selecting the
> contents tab) or
>
> (b) opening the item into a separate window above
> Dashboard (by double clicking the item from the list
> view).
The first level of Dashboard as previously described
is given below.
Email Inbox folders v
_______________________________________________
I frame 1 I I
I I frame ->I
I12:05 xx email subject x x ->I 2 I
I I ->I
I ->I I
I I ->I
I ->I_______________I
I I frame ->I
I ->I 3 I
I I ->I
I I I
I I ->I
I_____________________________I_______________I
The pull down email inbox folder tree button would be
included in the button bar for Frame 1.
The triage summary status lines for each frame would
be displayed on the first line within each frame but
this has not been shown here.
The sample item entered into Frame 1 is a single email
item. Again, this email may be single clicked and its
contents then read on the Contents tab that appears
within Frame 1, or it could be double clicked to open
up the email contents into it's own separate window.
If the email item was double clicked then the
following window could be opened up.
_______________________________________________
I I I
I I I
I Frame 1 I Frame 2 I
I<-Thread I I
I Tab I I
I I Contents I
I I I
I<-Cactus I I
I Tab I I
I I I
I I I
I I I
I_______________________I_____________________I
The contents of the selected email item would be
displayed on Frame 2 of this second level Dashboard
window. There are no tabs on this frame.
Frame 1 has two tabs:
1) Tab 1 for depicting the email thread of the
selected message, and,
2) Tab 2 one for depicting any collections that the
user may have previously assigned the selected email
item to. (The Cactus tab in the above diagram).
Hence, in practice, the user could double click an
email in first level of Dashboard Frame 1, and then
access its contents in Dashboard second level Frame 2.
Then they could easily click up and down the thread of
the email using the Thread Tab of Frame 1 on the
second level Dashboard to read read their contents in
Frame 2. This allows for easy scanning and triaging of
entire email threads at a time.
(Of course, if the thread list is very long as can
happen in some discussion groups, the user may not end
up triaging all items on the list, and this would then
commit those untriaged items to the archive and delete
setting futures that the user has previously assigned
for that InBox folder as I recently described on an
earlier message.
In addition if the item selected from Dashboard Frame
1 qualifies, then there may be a Cactus (collections)
Tab displayed in Frame 1 of the second level of
Dashboard. If this is the case, then the user could
click this tab to see a graphical representation of
the the collection the selected item belongs to.
Single clicking on title bars of any of the collection
members could then present the contents of the item
within Frame 2 (the contents frame of Dashboard level
2).
Double clicking a collection item on the Cactus Tab
could open the item into its own window above
Dashboard level 2 window.
Similar approach could of course be used also for
Dashboard level 2 layout when an item within the Memo
InBox frame is double clicked. However, the
difference here is that
(a) there are no threads as in the Email InBox frame
of Dashboard Level 1
(b) some Memo items may belong to collections while
others may not.
Hence, when an item in Dashboard level 1 Memo InBox
frame is double clicked, the second level Dashboard
window opened up may have either two frames or no
frames. Those memo's that have been previously
assigned to a collection would open up into level 2 of
Dashboard as a two framed window as shown below.
_______________________________________________
I I I
I I I
I Frame 1 I Frame 2 I
I I I
I Cactus / I I
I Collection I Contents I
I Tree I I
I I I
I I I
I I I
I I I
I I I
I_______________________I_____________________I
Because there are no threads to bother with here,
Frame 1 does not need to have any tabs. So, in
practice, the user could click any of the title bars
of items within the collection tree displayed in Frame
1 to view its contents in Frame 2.
However, if the selected memo has not previously been
assigned to a collection, then the second level
Dashboard screen would not have any frames as it only
has to show just the contents of the selected (double
clicked) memo.
As mentioned previously, we may use Frame 3 of
Dashboard Level 1 for triaging and stamping activities
involving Writer documents.
When a particular Writer document here is double
clicked into level 2 of Dashboard, and if the document
has previously been assigned to a collection, then we
could have the Writer document displayed in Frame 2 of
Dashboard Level-2, and the collection tree would be
displayed in Frame 1 of Dashboard Level-2.
In this format, the Writer app itself could open up
within Frame 2 so that the collection depicted in
Frame 1 acts essentially as a sidebar as the user can
continue work on the document.
If the Writer document title bar in Dashboard Level-1
that's double clicked has not been assigned to a
collection, then no frames would be neccessary in the
second level Dashboard window for this. In fact, the
second level Dashboard window opened up could
essentially be the Writer subapplication itself with
the selected Document being displayed.
Of course, a Chandler version of the Writer app would
have along the top left corner of the border of the
document window, the eight embedded triaging buttons
as previously described for all item content windows.
This is shown below.
_________________________
Ioooo I
Io ^ I
Io < triaging I
Io buttons I
I I
I Writer document I
I I
I I
I I
I I
I I
I I
I_______________________I
Why the top left corner? Because the user may want to
quickly scan any documents revceived as email
attachments and then quickly triage it and cactus it
without having to read the whole document.
--Selva
>
> Another related subject to consider is the alias
> issue, i.e., what if an item belongs to more than
> one
> collection? For this, we could allow for icon
> coding
> of the tabs so that all collections tabs display the
> same icon, ex. a small green cactus. Hence, if an
> item belongs to more than one collection, we might
> see
> two or more tabs for the item, all with small green
> cactus icons but numbered in sequence, for example
> a, b, c.
>
> --Selva
>
__________________________________________________________
Find your next car at http://autos.yahoo.ca
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
