One of the schemes I'm contemplating would involve using non-printing plane
15 and 16 unicode codepoints as embeddable smart "tab-stops". Such would
interact with saving and reading, but probably all able to be taken care of
by hooks rather than hacking the read/write code.
Such templates would consume all the tab-stops if filled out, but if the
templates are to be completed in the future, after a save, some state info
would have to be saved. Note that any left over tab-stops would probably
choke a language's interpreter/compiler, but the non-tabstop uncompleted
template leftovers would not make sense either.
Several possibilities:
1. Save the file as is, hook a "on-save" callback to write the tabstop
triggered functionality to the pickleshare database.
2. Offer to convert the templates to a form that incorporates the
triggered functionality into normal characters.
3. Offer to purge the unused templates.
4. Convert the templates into a dumber, normal text based form.
I did some experiments a while ago that extended the codewise database
stuff to store templates, it looks real good as a place to handle templates.
Tom
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/leo-editor/-/Ud9SQKhAZocJ.
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/leo-editor?hl=en.
