Several recent revs today have updated about 20 plugins. All tests pass and indeed most changes actually involve comments. Nevertheless, these changes may have broken one or more plugins in some way. I apologize for this, but imo the changes were overdue. Clearly, they should be done before the a1 release.
Please report any new problems with plugins immediately. I plan no further mass changes to plugins. Here is a summary of the changes: 1. Changed the style guide for plugins in the node leoPlugins.leo#Plugins--> Templates. 2. Many plugins have been brought up to the revised "style code": - Smallish << docstring >> sections have been moved to the top-level node, where they are more visible. - Smallish << imports >> sections have been moved to the top-level node, where they are more visible. - Unused/underused << version history >> sections have been eliminated, moving author attributions to the top-level node. I have retained longer << version history >> sections, but you could say that such sections have been deprecated. - Leo directives now appear at the end of the top-level node (and hence the end of the external file.) - All top-level init methods now have a proper docstring. 3. The bookmarks.py plugin (and maybe others) now calls g.assertUi to ensure it fails gracefully when using a null gui. This is a real bug fix. 4. All changed plugins now pass pylint. Most changes were minor: unused imports and the like. To repeat, these changes were necessary, imo, but they carry a risk. Please report any problems immediately. 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/d/optout.
