Traceback (most recent call last): File
"d:\local\leo-editor\leo\plugins\mod_http.py", line 419, in send_head f =
self.leo_actions.get_response() File
"d:\local\leo-editor\leo\plugins\mod_http.py", line 788, in get_response
return self.add_bookmark() File "d:\local\leo-editor\leo\plugins\mod_http.py",
line 697, in add_bookmark config.css, # EKR: Add config.css to
style.AttributeError: type object 'config' has no attribute 'css'
However, rather than make sure config.css is defined (i.e. setting it to "" in
@file mod_http.py-->class config), I'd suggest not injecting it into the HTML
in add_bookmark(), seeing that's entirely different HTML than the HTML
config.css is designed to style. I.e. just revert the changes in
add_bookmark().
Cheers -Terry
From: Edward K. Ream <[email protected]>
To: leo-editor <[email protected]>
Sent: Tuesday, October 4, 2016 6:20 AM
Subject: mod_http has been (partially) rewritten
The advanced features of the plugin remain as they were. Let me know if I have
messed anything up.
What's new
1. Look and feel. The plugin now renders Leo outlines almost exactly as they
appear in Leo. The plugin loads the entire outline into the page, and then
allows you to expand and contract nodes as usual. Even the icon boxes are
accurate. Reloading the page reloads everything.
2. Custom .css, using two new settings.
The default .css is in @data @data http_stylesheet defined in leoSettings.leo.
You can and should leave this stylesheet as is. You should put your own
overrides in @data user_http_stylesheet, in myLeoSettings.leo.
The html generated by the server contains both stylesheets as inline <style>
elements, with the user_http_stylesheet contents last. Thus, @data
user_http_stylesheet adds to @data http_stylesheet.
3. Custom javascript, using @data mod_http script.
If you define this in myLeosettings.leo, the contents of this node replaces the
default javascript defined in @data mod_http script in leoSettings.leo. I
don't expect people to use this settings often, but it was useful during
development as I'll describe in another thread.
4. Changed the generated html. <node> elements carry structure. <headline>
elements carry headlines. This allows headlines to have borders as usual. I
experimented with putting all data in <node> elements, but borders would
include all visible children.
5. Fixed html nits. The summary page now contains complete html, including
<!DOCTYPE> and <meta> elements.
I plan no further work on this plugin at this time. All comments welcome.
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.
--
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.
