On Fri, Feb 28, 2014 at 5:19 AM, Peter Mills <[email protected]>wrote:
I've put a rough version of the additional manual materials below - > hopefully this will help in the short term. > Indeed it does. Many thanks for the attachments. > > I've also added the example Leo outline (VR2test.leo) that I used to > generate the screenshots. Note that the @thin file included shouldn't be > refreshed from disk since this won't be in your file system at this > location, but I think it should still show what is intended. > Very helpful. In the future, I recommend changing @thin to @@thin in this kind of situation: that way Leo doesn't issue a warning about @ignore when attempting to load the file. > > I think there was a question about the css that I used to make the html > look the way I like (it should still work fine without this css stuff > though!). I've attached css.zip, which should be unzipped and the > resulting css folder placed in the same folder as VR2test.leo. Much of > this already comes from Leo, but the leo_vr.css is the main one for this. > VR2test.leo has a built-in setting to find this css file if you include > this css directory as described. > > Note that the text below is valid reST and if you paste it into a node, > should produce a more readable version in viewrendered or viewrendered2. > Excellent documentation. I'll make this the VR2 docstring. BTW, it does seem prudent to merge the VR and VR2 plugins. For example, selecting a plugin is supposed to show its docstring with the VR plugin, but that doesn't work when VR2 is enabled. I'll look into this soon. 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
