Re: Official Plugins
On Tue, Aug 4, 2015 at 1:59 PM, john lunzer lun...@gmail.com wrote: I think it would be nice if there was a process in place to differentiate essential plugins in a community sanctioned, official, and at least partially objective way. They could be called official plugins and it would provide a much smaller subset of the most important plugins for new users to explore. Not a bad idea. A reasonable place to designate such plugins is in the @enabled-plugins node in leoSettings.leo. The principle is that we want the data to be as close to the action as possible. That avoids the typical problem that people don't read documentation. Alternatively, as Terry suggests, some standard comments could be added to the plugins themselves. 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Official Plugins
On Tue, 4 Aug 2015 11:59:55 -0700 (PDT) john lunzer lun...@gmail.com wrote: I think it would be nice if there was a process in place to differentiate essential plugins in a community sanctioned, official, and at least partially objective way. They could be called official plugins and it would provide a much smaller subset of the most important plugins for new users to explore. I think this is a good idea. I've more than once proposed a header of tagged information for plugins along the lines of: maintainer: terry_n_br...@yahoo.com status: tested 2015-08-08 depends: Noneupdated: 2014-11-22 default: False but this has never happened. Perhaps just labeling plugins Official or not would be more doable. I'd still be included to do it the same way, maybe with just a single tag: status: official 2015-08-08 or experimental or proof-of-concept or has-issues or duplicate or broken or ... Basically we need some triage on all of them - but simply tagging the premium or official ones would be a good start and smaller task. I'd probably use production rather than official. @enabled-plugins could sort entries based on the status: tag. Cheers -Terry Official plugins would ideally meet some higher quality standard and unmaintained plugins whose functionally degrades as Leo changes could lose official status. I believe that this step is important in creating a friendly default user experience for new users. I have expressed this before in a less official manner but now that the idea of marketing Leo has come up I'd like to get people's opinion in this context. -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Official Plugins
On 8/4/2015 2:59 PM, john lunzer wrote: I think it would be nice if there was a process in place to differentiate essential plugins in a community sanctioned, official, and at least partially objective way. They could be called official plugins and it would provide a much smaller subset of the most important plugins for new users to explore. Official plugins would ideally meet some higher quality standard and unmaintained plugins whose functionally degrades as Leo changes could lose official status. I believe that this step is important in creating a friendly default user experience for new users. I have expressed this before in a less official manner but now that the idea of marketing Leo has come up I'd like to get people's opinion in this context. -- Interesting idea. I think the set of plugins enabled by default in leoSettings.leo covers a good set of features: contextmenu.py leo_to_html.py mod_scripting.py nav_qt.py quicksearch.py stickynotes.py todo.py viewrendered.py In that list, I'd swap viewrendered with viewrendered2, and also add: bookmarks.py valuespace.py word_count.py node_diff.py python_terminal.py Those last two are my plugins, so I'm a bit biased... but I think they offer valuable features. In general, none of the above plugins do anything that would be deprecated as Leo grows, unless it switches GUI libraries again! They're also all pretty well maintained, or else feature stable. --Jake -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Official Plugins
I think it would be nice if there was a process in place to differentiate essential plugins in a community sanctioned, official, and at least partially objective way. They could be called official plugins and it would provide a much smaller subset of the most important plugins for new users to explore. Official plugins would ideally meet some higher quality standard and unmaintained plugins whose functionally degrades as Leo changes could lose official status. I believe that this step is important in creating a friendly default user experience for new users. I have expressed this before in a less official manner but now that the idea of marketing Leo has come up I'd like to get people's opinion in this context. -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
