On Sun, Feb 1, 2015 at 11:02 AM, Dufriz <[email protected]> wrote:
> > why not keep track of the users' suggestions/feature requests in a more > organized way? > That's what wishlist items are for: https://github.com/leo-editor/leo-editor/issues This system should suffice, imo, provided that people actually file items. There are also a deprecated wishlist items at: https://bugs.launchpad.net/leo-editor/+bugs > the best judgement [re user friendliness] is that made by the outsiders, or newcomers Sure. Newbies often see things that are hiding right under our noses. > the leading node-type @ markers in the headlines are very ugly to see, and clutter the screen. Why not replace them with customized note-type icons? Because scripts, especially the mod_scripting plugin, use @<whatever> nodes as markers. Yes, Leo could *render* headlines starting with @ using icons, but that's a cosmetic feature that complicates creating @<whatever> nodes. > Of course, they are an important metadata, which should be preserved somewhere. But why make it a part of the headline? Because it's easier for scripts to discover the metadata and for users to create and modify them. > Changing settings is very awkward, as pointed out in several old posts. Something needs to be done. The general principle is that when loading any .leo file, settings should be recreated *as if* from scratch, that is, as if leoSettings.leo were first loaded, then myLeoSettings.leo, and then the local .leo file being loaded. There may be some bugs lurking here, and I plan to look into this. However, the general principle must be amended in some cases, especially for plugins. Indeed, there is no way to unload a plugin once loaded, so loading a .leo file can only *add* to the loaded plugins. This can cause problems, but I see no real solution. > more standard default key bindings. For instance, what about F2 for editing a headline? I am not aware that F2 has any standard meaning concerning outlines. > I know, this is not such a big deal, because users can change the key bindings to their liking, but why not make things easier for newcomers? Imo, the present default bindings are a decent starting point. This is a non-trivial problem. There are already (inactive) vim-like bindings that the user can choose, and it would be easy to create others. > there are several other UI improvements that would be really welcome. The tutorial videos have virtually eliminated comments from newbies of the form, "help, I'm lost". Imo, this shows that Leo has already become substantially easier to learn. > why not go in a sort feature-freeze mode for some time (i.e. stopping adding new features), and focus instead on improving the user interface? You haven't begun to make your case for this. I have zero interest in adding features for features' sake. Rather, I see my primary role as guiding Leo's long-term development. This may involve new features and support for other languages. Better support for IPython and markdown come immediately to mind. 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.
