Marcos, I'm very encouraged by your work. The more I think about this
line break thing, the more I realize we need to get it fixed
carefully...  And that to get good XHTML we will need a better core
solution.

First, if it's ok with you, I'd like to make some or all of your wiki
creole plugin actually a part of the core--with a simple on/off config
value like creole: true in site.config.  We can handle it just like
honorlines, by putting conditionals in markups.php.

Second, we will need to track down any markups/functions that are
deleting/adding line returns. It seems we should make each of them
exactly accurate, like the [if] function which adds nothing itself.
Some things delete line breaks before or after like -> <-, [form],
<box> etc., and other things add line breaks extra line breaks
[messages], etc. It would be nice to make BoltWire work really
perfectly either way, and also make it easy to switch.

It's important enough we might even want to make the switch doable in
various ways: per zones, per pages, as an option in includes/source,
etc. Because the line honoring behavior is definitely better for
simple users who are used to a word processor/blog kind of thing. It's
getting the two to work together well that is tricky.

In fact, I prefer the current approach as the default, but it bugs me
that we can't get it working perfect for a professional user. I'd like
BoltWire to appeal to both types. Anyway, I eagerly anticipate your
code, and am eager to explore the very best ways to integrate it into
the core.  Even if it means requiring sites to make a few tweaks here
and there. Let's hope we can do it smoothly.

Till then,

Cheers,
Dan

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to