8 Jun
2012
8 Jun
'12
3:32 p.m.
Hi,
On Fri, Jun 8, 2012 at 3:14 PM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com>wrote;wrote:
On Fri, Jun 8, 2012 at 2:37 PM, Ecaterina Moraru
(Valica)
<valicac(a)gmail.com> wrote:
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/RenderSwitches…
This solution is interesting. I have a couple questions about it:
- What happens when an user tries to edit the rendered content?
- What happens when the code in the field cannot be rendered and / or
throws an error?
This solution makes a lot of sense for applications, where the page title
of entries might be automatically computed from data entered in an object
by the user.
However for the wiki home page the real issue is that we should not have
translation string in the title field to begin with. Every user I speak to
is afraid of changing the title of the wiki home page because of this. The
translation key should be replaced with pure text on that page. Same thing
for the widgets, their titles should be easy to change by users (as opposed
to translation keys). This is a big usability hurdle right now.
Thanks,
Guillaume
Hi,
One of the big problems for simple users when trying to use XWiki is the
mix we have between text content and syntax/code content.
If the user wants to edit the title of the WebHome he will see
"$msg.get('xe.home.title')". Same happens for other use cases, like
editing
the title of the 'Welcome' gadget, etc.
This is an idea for having a switch for rendered/syntax content for
inputs:
Read the full proposal at:
What I see in the examples looks more like a preview than a swith
between two modes. Same than what we have in the comment basically.
Thanks,
Caty
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs