8 Apr
2009
8 Apr
'09
11:24 a.m.
Anca Paula Luca wrote:
Ludovic Dubost wrote:
How about a hidden sidepanel, with a handle 8px wide, with an arrow in
the center, that opens when you click it? And when it does, the current
document is already selected.
Or, if we'll have more such tabs, mayba something like the sidebar
Acrobat Reader has: a vertical bar with nice big icons, that open a
sidebar when clicked: pages, bookmarks, howto.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
I'm having some thoughts about the
attachments and image insert. I just
tested the current work on attachment link insert.
The more I think about it, the more I believe that images and
attachments should be mainly attached to the CURRENT page.
It is a nice to have to be able to use images or attachments for other
pages (and even less upload to another page).
However, when I look at the superbe tree UI, I have the feeling it will
actually get in the way of the main usage, which is having the file
attached to the current page.
1/ I can make sure the currently selected page in the tree on loading the dialog
is the current page, so that the main usage is facilitated: either one selects a
file attached to the current page, either she hits "Add attachment" and uploads
a new one.
Therefore I believe we should have 2 different
UIs. One simple and one
advanced. The simple one would only manager files or images attached to
the current page. The advanced would be the tree one.
So one would not be able to add a link to an attachment / image from another
page, using the simple UI? I think this is acceptable only if we provide the
simple and advanced UIs accessible almost as easy.
2/ One idea for this would be to have 2 tabs in the selection step, one with a
simple UI, the other with the advanced tree, and let the user select an attached
file / image from any of them.
3/ Another idea is that the simple UI is still the tree, but drawing only the
current page's node. On hitting a "More" button, the tree will be completed
with
the whole wiki, so that the user can select other things too (we need to check
if that's possible with the tree)
My vote goes for 1/ for consistency reasons (same widget everywhere), for not
crowding the UI with tabs, buttons, options, for not having to make the user
understand what is the difference between the two and why she needs two, and
because I think it would do its job smoothly (will get the tree out of the way
of the main usage).