Re,
On Wed, Apr 8, 2009 at 1:09 PM, Ludovic Dubost <ludovic(a)xwiki.org> wrote:
Anca Paula Luca a écrit :
Ludovic Dubost wrote:
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.
This option in my opinion is not good enough. The tree will actually go
in the way of people understanding the tool.
I believe the first impressio of the user needs to be simple and simple
means less information shown on the screen.
So it means a UI much more like the current Image UI (with the page
choice removed).
The tree or whatever concerning images or attachments from different
pages than the current one should be hidden from the user.
And this feature is actually NOT a priority. I'm not even sure we have
had any people asking for inserting images from other pages did we ?
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.
Yes Tabs is an option.
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)
I think this is less optimal for the simple case. We need to focus on
making the simple case optimal.
I vote for 2/ or sergiu's hidden tree idea.
Ludovic
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).
Happy coding,
Anca Luca
I understand this is more work, but if you ask
me, if we should do only
one, then it should be the one with file or images in the current page.
WDYT ?
Ludovic
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Ludovic Dubost
Blog:
http://blog.ludovic.org/
XWiki:
http://www.xwiki.com
Skype: ldubost GTalk: ldubost
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
I've thought a bit more about the topic and I think an elegant solution that
would both match user expectations and be elegant exists. I'll explain it
after providing some context.
- Our aim in the new WYSIWYG has been to let users do more than they
could in the previous one
- We dissussed a lot about what the best way to achieve easy browsing of
pages & other items
- We eventually agreed on using a treeview approach for most purposes
- However, the tree view isn't necessarily the most effective for some
use cases such as the one Ludovic identified
- Thus we may want to look at the way other pieces of software resolve
this type of file browsing issue
- For instance, Mac OS X's finder offers 4 different kind of views:
folder contents, tree, miller columns & coverflow
- Some users favor the tree view while other like the folder view better
(the last 2 are pretty much superfluous)
- The view Ludovic is pushing forward would be pretty much covered by a
standard folder view showing the images / files attahed to the current page
as thumbnails (similar to
,
we see that it would be pretty easy (from an UI point of view, not a
technical one) to add a zone at the top of the screen (between "select an
image" and the tree itslef) that would provide the following 2 elements:
- Buttons / select box to switch between tree view and folder view
- A search box (Vincent has been asking for it and I believe it's
important too)
- Here's a tentative mockup showing what I have in mind:
- We could hide the Wiki address field from standard users (show it only
for advanced users)
- The default view would open on the folder view for insert image and
insert attachment links
- This feature can be implemented at a later stage, once the current tree
is done, so it doesn't disrupt the current planning
- The WYSIWYG editor would provide a configuration option allowing to
choose whether to hide some of the views in some cases (show only the folder
view on the current page for instance)
- Note: my proposal doesn't have back / forward buttons since it doesn't
take into account the possibility of full folder browsing: the folders opens
only on the current page attachments. This might have to be discussed.
I think this proposal would address most (if not all) of the points still
under discussion about our dialog boxes (view on the current page only,
search, possibility to browse other pages, etc). However it implies a lot of
additional work by the WYSIWYG team, and it's not necessarily the direction
we want to push the editor forward.
Thus I'd like to get everybody's feedback about it before pushing for any
kind of implementation plan.
Thanks,
Guillaume
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc