Those look great, great theme too.
Thanks!
100 is a view of a desktop with a single project on it. This project
has been minimized.
Placing projects like that tends to lead to an overcrowded desktop,
making it hard to figure out which is which, naming the minimized
projects or labelling of some sort could make it easier.
Well, there are a few solutions. One, would be different colored
desktops, or different wallpaper per project. Two, you _could_ give
projects names, but if you don't want to, you're not required to.
200 is a view of that same project zoomed in. I haven't determined
how to indicate where you currently are in the hierarchy of projects,
if that's even necessary. I also haven't decided how to zoom back out
of the project (perhaps double-clicking on the desktop...?). Some
additional things you can see from this mockup:
would it be possible to "zoom in" only one object from a project --
in situations where a project has very many objects and you just
want one without opening everything in the project.
Yes -- opening a project doesn't open every file. In the view you see
here, there are only two open documents: the big document and the
chat. Everything else is closed and in icon view -- there is no
distinction between "closed" and "minimized".
Would it be possible to zoom multiple projects at the same time?
How would window management between the different documents and
projects be like?
No -- only one project can be viewed on screen at a time. This is
equivalent to virtual desktops. Moving windows or documents from one
project to another requires use of the shelf as an intermediary step
-- there may be other solutions to this problem as well.
Would it be possible to put windows of non-document based apps like
configuration tools into a project?
Yes.
- Not all files have file names. Creating a new file does just that
-- it makes a blank document in some predefined, user-customizable
size. As such, you don't need to necessarily name the document. This
is handy for things like photos that are more readily identifiable
based on looking at a thumbnail. Some documents, like code, may
require a file name in order to compile. This would be set in the
Settings... menu option, as seen in the next image.
file names may be a little burden to a user but if done away with,
users then _have_ to tag objects with some other info to easily
identify that object i.e. when searching or telling an object from
a near identical copy.
File names aren't done away with -- they are just not required. If
you look at 200, you'll see that two of the text documents do have
names. File names aren't necessary to create a file, but can be added
later on, for differentiation or as a requirement of the type of file
(like the two in the example, which require filename in order to
compile them).
400 is a different interpretation of the Shelf. This is something
that Nicolas and David and I discussed yesterday. It's kind of a
cross between the OS X Dashboard and the pasteboard, and how we had
intended to use the shelf-within-the-panel. The Shelf is a place to
store things temporarily. When you Pick something, this is where you
can Drop it. The advantage over the panelized-shelf is that it's not
crowding the screen, and it's 2 dimensional and spatial.
my take on this is that if the shelf is for storing temporary
things, it becomes only as useful as a clipboard -- only bigger.
"Temporary" is very loosely defined. The Shelf has to be manually
cleared out, but the idea is that you wouldn't put tons of things
there, as it would get rather messy. But I might store things like
(in 400), my name or email address, or bits of text that I regularly
use across multiple documents, so that I can very easily pick and
drop them.
not sure what the location for plugins should be called. maybe all
of it could just be the shelf.
The dock box was supposed to be launch box -- it contains launchers
for all installed apps.
My idea of a clip board was that it captures objects when a user
cuts (ctrl+x) or copies (ctrl+c) the object(s) and has additional
features like:
- unlimited objects.
- a user can set any object on the clipboard to be pasted (ctrl+v)
- persistent objects even after shutdown
This is equivalent to my version of the Shelf, and I think it's a
smart way to handle the clipboard/pasteboard.
Shelf Mockup
see: http://www.flickr.com/photos/[EMAIL PROTECTED]/440737039/
see: http://www.flickr.com/photos/[EMAIL PROTECTED]/440737047/
This shelf mockup works a little different from my last.
- It can be oriented both vertically and horizontally and plugins
would account for the different orientations when displaying content.
- it has 3 styles to display shelf objects text only, icons only
and icons and text .
- a user can create multiple strips of the shelf.
(1) when the address book is selected, the shelf retracts to reveal
the address book. clicking any other plugin tab shows its content.
(2) using a key stroke i.e. ctrl+shift+left_click, to click a
plugin tab causes it to migrate to the next strip, if the strip
isn't there, it is created. one of the projects/stacks is pushed to
another strip.
(3) the stack on the second strip can be open at the same time as
the address book on the first strip.
(4) clicking the open tabs (address book and the project/stack)
closes them leaving 2 collapsed strips of the shelf. Another key
stroke i.e. ctrl+shift+right_click, pushes the stack on the second
strip back to the first strip -- the second strip thereafter vanishes.
I do really like this as a UI structure -- however I think it may
work better to have the tabs stay fixed at the left of the screen
though, for persistency of things like the Trash can. It depends on
what people think our users will be more apt to need to click on.
J.
_______________________________________________
Etoile-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-discuss
