[pmwiki-users] TextFormattingRules and BasicEditing

Bronwyn Boltwood bronwyn at bronwynb.info
Sun Mar 5 23:58:01 CST 2006

On 06 Mar 2006 12:12:49 +1300, John Rankin <john.rankin at affinity.co.nz> wrote:
> On Friday, 3 March 2006 6:38 PM, Patrick R. Michaud <pmichaud at pobox.com> wrote:
> >On Fri, Mar 03, 2006 at 11:24:30AM +1300, John Rankin wrote:

> >The hardest part is deciding what to include or exclude.
> >BasicEditing was intended to be short, but it doesn't work
> >out that way.
> I think to get started, one wants to learn about 3 areas:
> - paragraph markup (eg lists and headings)

Specifically bulleted and numbered lists -- the other kinds can wait.

>  I kinda prefer 'paragraph' to 'block'
>  I kinda prefer 'character' to 'inline'

Another advantage is that word processing programs use the terms
"character" and "paragraph" for inline and block formatting

> Each topic would also have a link to a fuller page.

Yes please.

> Finally, I'd link to the MarkupMasterIndex, only I think
> I'd rename it to MarkupVocabulary or something similar
> (TopicMap, MarkupGuide, ...)

How about AllMarkups?

> >> MarkupQuickReference -- show/hideable on the edit screen
> >> StyleQuickReference -- show/hideable on the edit screen
> >> TableQuickReference -- show/hideable on the edit screen
> >
> >I like this idea very much.  I like it so much that I'm likely
> >to add the show/hide capability into the core.  (I was leaning
> >in that direction already -- it just seems too useful to
> >ignore.)
> Perhaps also a DirectiveQuickReference.

I like these ideas too.  Especially if I ever get round to putting the
quickrefs in a column to the right on the editform.


More information about the pmwiki-users mailing list