Hi Edward.

I totally agree with your observation and a through overview of Leo is in 
order to really sell it in an unified way.

Following are my thoughts on making this happen
1. Create a document or presentation called "The Essence of Leo" or "Leo at 
a Glance" (For presentation http://leoeditor.com/slides.html is a good 
2. Create updated videos showing each item being presented in Step 1
3. When a new feature is added in Leo, right away document following Step 1 
and Step 2
4. Since Leo supports Markdown and Rst share Leo on those community forums 
as well.

Let me know what you think.


On Friday, March 2, 2018 at 8:27:59 AM UTC-8, Edward K. Ream wrote:
> Leo probably *already has* the features you want.  Alas, these features 
> can be hidden from casual sight. This is driving me crazy :-)
> My top priority is to make it obvious to everyone, newbies and devs alike, 
> what Leo can do.  Happily, this is a *much easier* task than some of the 
> grand projects we have been discussing lately. A few weeks work should make 
> a *huge* difference.
> This post lists hidden features and enhancements (actions items) that will 
> make a big difference.
> This is a long post, but concise.  Please study it carefully. As always, 
> comments are welcome and encouraged.
> *Leo's hidden features*
> *Hidden feature 1: Leo's Python console*
> Someone recently said he uses another editor because it has a python 
> console. How sad is that! The python_terminal.py plugin puts such a console 
> in a Log pane tab,* with full support for Leonine features*.
> *Action*: #760: Move python_console plugin into Leo's core. 
> <https://github.com/leo-editor/leo-editor/issues/760> This feature must 
> be made much more obvious.
> *Hidden feature 2: Live evaluation of objects*
> How many times has Terry reminded me and others about the valuespace 
> plugin? This plugin creates live objects, which can be 
> introspected/auto-completed, as in jupyter notebooks.
> *Action*: #761: Make the valuespace plugin more visible 
> <https://github.com/leo-editor/leo-editor/issues/761>. Not sure how, but 
> this item is worth any amount of work.
> *Hidden feature 3: Sophisticated rendering*
> Leo's *existing* markdown rendering is extremely powerful. In particular, 
> *you 
> can embed html into markdown*. The <img> element can insert svg graphics 
> and movies in Leo's rendering pane.  In particular, the style attribute 
> allows virtually unlimited flexibility! For example, open Leo in the 
> leo-editor folder, put this in any node, and show the rendering pane with 
> Alt-0, vr-toggle:
> @language md
> <img style="float: right;" src="../Icons/SplashScreen.ico" alt="Splash 
> Screen">
> Line 1
> Line 2
> Line 3
> Line 4
> *Action*: #762: quickstart.leo & CheatSheet.leo should demo Leo's features 
> <https://github.com/leo-editor/leo-editor/issues/762>. Including markdown 
> rendering.
> *Hidden feature 4: Good looking themes*
> The screen shot on Leo's home page is amateurish. It should have a dark 
> theme and smallish fonts. Something like atom dark.  Leo's existing theme 
> machinery can do this, but see #766 
> <https://github.com/leo-editor/leo-editor/issues/766> below...
> *Action*: #764: Improve the screen shot on Leo's home page 
> <https://github.com/leo-editor/leo-editor/issues/764>.
> *Other hidden features*
> Leo could use better "implicit" documentation in the Cmds menu and perhaps 
> elsewhere.
> *Action*: #765: Improve the Cmds menu 
> <https://github.com/leo-editor/leo-editor/issues/765>.
> *New projects*
> Here are two smallish projects that would greatly enhance Leo. Each might 
> take a week.
> *1. Better theme setting and pre-built themes*
> #766: Create a Themes menu and simplify theme settings 
> <https://github.com/leo-editor/leo-editor/issues/766>. Don't panic.  
> Existing Theme settings will remain in place.
> *2. Better support for markdown*
> #767: Add markdown command similar to rst3 command 
> <https://github.com/leo-editor/leo-editor/issues/767>. I want to move 
> Leo's docs to markdown.
> #763: Use html comments to support @file x.md 
> <https://github.com/leo-editor/leo-editor/issues/763>. This will allow 
> structured markdown files.
> *Summary*
> - Some of Leo's most powerful features are hidden. They must be revealed.
> - Two, smallish, *urgent* new items will add better support for themes 
> and markdown.
> *It doesn't have to be difficult.* The work described here is 
> straightforward, yet no other project is even *remotely *as important as 
> these items. All work can probably be done in a month or two, but this 
> uber-project is worth *any* amount of work. All items mentioned here have 
> a target of 5.7.1.
> All comments and suggestions 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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to