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
it :

http://thibaut.deveraux.free.fr/xwiki/Profil-In_place_render.png

http://thibaut.deveraux.free.fr/xwiki/Profil-In_place_edit.png


Have a nice day

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.

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.

Thanks !













2009/11/11 Ecaterina Valica <[email protected]>

> Hi Thibaut,
>
> So, what is freigntening me is that the number of elements and the
> > altenances field-name/field-content may make it diffcult to scan the
> list.
> > Since users generally start looking for informations in scan mode it can
> be
> > a limitation.
> >
>
> I thing there is separation for the profile, so the scan mode is not that
> limited.
> You have:
> - subcategories (Personal, Contact Informations)
> - left-right + change in background color between the information a user
> can
> edit and the ones he cannot (Rights+Recent Activity)
> - also we have space between pairs of field-name/field-content
>
>
> > By removing the "first name" and "last name" fieds (*since this
> information
> > is already at the top*) we can limit this.
> >
>
> The main reason I don't want to remove this fields is the compatibility -
> symmetry for the profile in view/edit mode.
>
> View mode:
>
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/UserProfileProposal/generalProfilesSimple.png
> Edit mode:
>
> http://incubator.myxwiki.org/xwiki/bin/download/Improvements/UserProfileProposal/defaultFields2Edit.png
>
> In edit mode, the fields are in the same position like in the view. If I
> enter a value in Edit mode, I can clearly see the modification in View
> mode.
>
> Imagine a user entering his First and Last Name. He hits save, but he can't
> find this fields anywhere in the profile page. How you will explain him
> that
> he need to look in the page title? Usually in a form, the user expects the
> same structure of the form after save.
>
> I would like to check the relevance ot this, is the code available
> somewhere
> > ? (I'm sorry I'm not a dev so I'm a bit lost in using svn)
> >
>
> The code is not available on svn. This are just mockups, ideas. They will
> go
> into the SVN when they will be implemented.
>
> Thibaut, you should try to make a quick mockup in an graphical editor or
> even on a piece of paper and scan it. Sometimes I don't fully understand an
> idea and the best solution is to represent it in a picture.
>
> Thanks,
> Caty
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to