On Saturday, February 4, 2017 at 11:42:18 AM UTC-6, Edward K. Ream wrote:
images in the body editor could save a lot of real estate during demos, for
> instance. I'm pretty sure that we will enjoy having this feature. And why
> turn our backs on a really cool feature?
>
I'm going for put this project on indefinite hold, for the following
reasons:
1. I am thinking that what we really want is your (Terry's) new VR4 widget,
or whatever you call it.
Do I remember correctly that this pane would allow both rendered and "raw"
views of text. If so, there would be little or no need for a *separate* VR
pane.
In that case, users could put pictures into the body pane using rST
syntax. There is, in reality, little or no need to put pictures into code,
but perhaps the VR4 widget could even handle intermixed @languages.
Terry, please correct me if I have this all in a muddle.
2. Putting picture characters into text is more difficult than I imagined.
There must be a way to associate data (the full path to the picture) with
picture characters. The data must be an *intrinsic *part of the picture
character, not affected by recoloring, deleting, moving, cutting or pasting
picture characters. There probably *is *a way using:
QTextImageFormat.setName(path-to-image).
However, my patience is at an end. I want to get Leo 5.5b1 out the door
with a minimum of major changes.
As it is, reconciling the wikiview plugin with the new colorizer is turning
into a headache. I'll say more about this in #388
<https://github.com/leo-editor/leo-editor/issues/388> itself.
Terry, your comments have been most helpful. Any other comments you want to
make?
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.
