13 Nov
2009
13 Nov
'09
12:33 a.m.
Hello !
;-)
2009/11/12 Ecaterina Valica <valicac(a)gmail.com>
CC-BY-SA-Don'tCleanIt
Liscence... Files that are not clean and should not be
cleaned because it would be a waste of time. ^_^
On Wed, Nov 11, 2009 at 19:24, Thibaut DEVERAUX
<thibaut.deveraux(a)gmail.com>wrote;wrote:
You speak of using "in place" evrywhere ?
It should, lol. ^_^
More seriously, this is a mater of choice for the UX strategy. I would
recomand it, yet it is only my advice. :-)
Hi thanks,
I understand. :-)
Well, sites use a lot a form that is completly different than the output.
This is not the best, I agree. Generally the reason is that the
information
from a single form is redispatched in different
pages.
User understand this. The fill a form with data, and the site will use
them
data to create a page.
Yet, this can be a bit "burocratic" in the feelings. Also user get a bit
lost in the resulting page because they have to take new reperes. Also
this
limit the feeling of "I create my
page".
I prefer too versions most "in place", most "WYSIWYG". Well... Most
in
the
Wiki logic too.
I think you can even do best than doubling the name as a compromise to
make
Interesting concept - I am not really sure about the implementation of the
fields inside the page's title. This is a classic "edit in place" pattern.
Could be useful also when we are editing the page's name, content, etc. The
problem is that this pattern isn't widely adopted inside XWiki's
implementation.
Have a nice day
Nice you use also svg. I'm using this one a lot, find it to be faster to
re-arrange, make tests, etc.
Thibaut
PS :
/!\ Sharing the UX sources in an Open Source project /!\
It took me more than half an hour to photoshop your renders to make my
proposal.
If I had sources I could modify quickly, it would have been 5mn.
A simple mockup on the paper does not help enough to make a comparaison.
(Using feelings to drive thinking is important too)
Yet, here, this is complicated. You use HTML to make your proposals. I'm
most at ease with Photoshop/Gimp/svg. So I'm not sure it would take me
less
time if I get to design in HTML.
Since I start working for XWiki I had SVG mockups, HTML/CSS mockups or even
partial prototypes.
There is no "standard" format when I make mockups - it's all a matter of
the
complexity/time degree of the proposal and also the probability that
someone
else will want to modify them (this probability slightly increased in the
past time).
Cool, I understood it bad last time. :-) All of this does not really makes it easy open
source UX collaboration. I
don't know what to say. You have to use the medium you are the most at
ease
too, so I don't have the solution...
At least please share your HTML files, if this is simplely a few lines to
change it will be faster in HTML.
I'll do more of that in the future. The thing with sharing HTML/CSS is that
when you make mockups with this technologies, you don't necessarily clean
them - since you are experimenting a lot.
Lol, add a warning at the top of the file ? ;-) Thanks,
Caty
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Have a nice day !
Thibaut