> I like the idea.  Though I'm not sure how to weigh the extra
> processing against the savings in keystrokes.

You are right, the processing must be kept as low as possible. This
feature could be optional.

But the new possibilities are great. Imagine a multi user site. The
webmaster could configure only three possible attributes for images:
r, l and c. That would be much easier for all users. And at any time
the webmaster could change the real XHTML parameters those pseudo
parameters produce. Really wiki!

> For example, probably between 427 and 428 in markups.php we could do
> something looks like:
>
> if (func_exists(BOLTlinkAttrsShortcuts)) $args = 
> BOLTlinkAttrsShortcuts($args);

Good idea. Now I'm experimenting with an alternative (a bit
simplified) version of BOLTMuploads:

MarkUp('links', 'uploads2', '/\{\{(.*?)\}\}/e',
'BOLTMmyuploads("$1")');

I'll send the code when ready. Some simplifications could be used in
the current BOLTMuploads.

> The function then would take the array of field => value pairs,
> iterate through them, and make any substitutions according to your
> predefined values, and then return the new array.

Some substitutions would need regexp somehow, I think. I see several
possible substitutions:

1) mnemonic to any ready XHTML:
r ===> class="right" border="2"

2) mnemonic to synonym:
t="bla bla bla bla" ===> title="bla bla bla bla"

3) mnemonic to several synonyms:
l="en" ===> lang="en" xml:lang="en"

In the last two cases, the original attribute content has to be used
in the right place(s) of the translation. That requires some kind of
internal markuping or regexp.

> What do you think?  I'd implement this happily if it sounds all right...

I think the idea is very interesting and worths further thinking. I'll
write some code and we'll see how it works.

Another idea: a similar simpler effect can be achieved rigth now using
{vars}:

$BOLTvar['$r'] = 'class=right';
$BOLTvar['$l'] = 'class=left';

{{ things/house.jpg|House|{r} }}
{{ things/cabin.jpg|Cabin|{l} }}

It can be used for the first kind of substitution.

Cheers,
Marcos

--
http://alinome.net

--~--~---------~--~----~------------~-------~--~----~
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