John Levon wrote:
> Because your solutions are really awkward otherwise, if we allow it "a
> bit". The user won't know what hit them if their empty pars have some
> mark around them.
The first-time user doesn't know what kind of finger paralisis has got that
forbids him to inserts spaces or newlines now... After this first time, he
doesn't have any more problem with both implementations.
What about this behaviour (for empty pars): if the cursor is at the end or
at the start of a par and press enter, then the cursor becomes horizontal
and places itself between the two pars. if he inserts or types something
then a new par is created and the text is put there. If he goes away then
nothing happends. Same final result as now (so we don't need retrain for
old users).
A similar behaviour but with a different visual feedback could be
implemented for double spaces.
Anyway, I think that space & newline removal is broken interface. The
const'ness of cursor movement was engraved in the tables of ui from the
first day. If mine is not the solution, then the solution is out there, but
it cannot be this.
>
>> > The only way you could get this to work is only allow a paragraph
>> > split, ie you have to enter some text before you get to press return,
>> > and you have to have some in front and behind. I wonder what that would
>> > feel like. I wonder if it would be possible to maintain the
>> > no-empty-pars
And let me add that we don't need new code for this option.
>> > I don't think anybody would grieve for the loss of DEPM, as initiates
>> > into its ways know it. I would say: GO FOR IT. I bet it's not even
>> > mega-hard !
I feel really dumb, but, given that it's probably not department of
epidemiology and preventive medicine, what's DEPM?
Regards,
Alfredo
