On Saturday, February 4, 2017 at 3:21:26 AM UTC-6, Edward K. Ream wrote:
*> Summary*
> ...The colorizer will replace the wikiview plugin.
Still true, but the colorizer must handle *all* of what wikiview does,
including a variant of Leo's UNLs:
file://#some-->headlines-->mynode
and links such as:
`Python <https;//www.python.org/>`_
Live UNLs are alternative to clones! Live, good looking, links should also
be part of Leo's core.
> Hiding <img> tags will use the same machinery as hiding parts of urls.
But full support for pictures will involve numerous complications.
There is good news and bad news ;-)
The *good news* is that Leo can handle picture tags easily, without knowing
how Qt associates *different *images with multiple picture characters, all
of which are (apparently) *exactly the same character*.
When the colorizer sees an <img> element, the colorizer will *always* do
the following:
1. Delete all the following picture character, if it exists.
2. Insert a *new* picture character by calling:
widget.insertHtml('<img src="%s">' % path_to_picture)
The *bad news* is that inserting/deleting picture characters could (will)
trigger another call to QSyntaxHighlighter.highlightBlock. The colorizer
will have to futz with states so as not to loop. It should be doable, but
it's like to be tricky.
*New summary*
Support for live UNLs is huge.
On balance, the good news about <img> far outweighs the bad. The
simplifications are global. No need for uA's or anything else. The
complications strictly limited to the colorizer.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
