Marius Dumitru Florea wrote:
> Hi devs,
> 
> A) Should xwiki/2.0 support multi-line headers?
> 
> I'm +0. Wikimodel, HTML and Open Office support them.
> 
> B) What should happen when you press Enter inside a header in the new 
> WYSIWYG?
> 
> B1) Currently, the text is moved on a new line, but still inside the 
> header (multi-line header).
> 
> I'm +1 since it's already done (We agreed that you have to press Enter 
> twice to generate a new paragraph).

Indeed, from a user pov, this does not make too much sense. All headings are 
titles of some sort and you wouldn't add a new line in a title that often, 
right?

however, double enter for paragraph is efficient and consistent with the 
bahaviour in paragraphs (users would "learn" that double enter means "new unit" 
(new para, etc)).

> 
> B2) Text is moved in a new paragraph, below the header. Shift+Enter 
> would have the effect described in B1).
> 
> I'm -0.
> 
> B3) Text is moved in a new header of the same level, below the current 
> one. Shift+Enter would have the effect described in B1). This is what 
> Open Office does (and we agreed not to follow it).
> 
> I'm -0.
> 

As for B2 and B3, indeed, B3 sounds better: 2 headings of the same level but 
then how would you add the paragraphs in between? You'd need to type stuff in 
and then change the formatting? a little uncomfortable, so, even if it's not 
very nice, I think we could make a difference on the position of the cursor:

B2) if cursor is at the end of text since that what users would expect (with B1 
on Shift + Enter)

B3) if cursor is inside text (with B1 on Shift + Enter).


However, I think B1) is _good enough_ so, _for now_, +1 for B1), +0 for B2) and 
B3).

Happy coding,
Anca Luca


> Please cast your vote asap.
> 
> Thanks,
> Marius.
> _______________________________________________
> 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