Dufriz is facing the same exact problems with GUI config I had when I joined Leo. I knew very few of programming, nothing of python, and now I know both, because I had the time, loved the concept of Leo, and could devote my time to study both.
I also asked for a settings GUI, because IMO, this is screening out a lot of people that would otherwise use Leo for non-programming related stuff. Something as simple as Notepad++ settings/preferences menu, just a simple tick menu, would make much more people remain in Leo. Even if you love the concept, clones, etc, if you must learn python and pyqt and Leo structures and Leo @node_id inheritance before you can edit that, you simply wont. I know someone will think "its not neccesary to know pyqt to change the background colors", but I have been there, and otherwise you dont really know what you are touching // how to edit that. Also, having to restart the app for every change to make effect makes everything much slower (for a newbie), all of this resulting in non programmers running away from Leo as fast as they can. Just a few comboboxes with option lists, + tickboxes for boolean values, would make a huge difference. If the need to restart Leo was removed, that would make things perfect. But then again, this is a dev time problem, so only thing I can do till I get some extra time to develop that myself, is to remain extremely grateful for Leo as is right now. On Thu, Aug 14, 2014 at 6:35 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > On Thu, 14 Aug 2014 09:26:30 -0700 (PDT) > Chris George <technat...@gmail.com> wrote: > > > "It's not ok to require that people use `git` to get it, > > that's unreasonable." > > > > Why? > > > > The primary target user for Leo is a programmer, is it not? > > No, although I can understand why someone might think that was the > case :-) > > Also, there are programmers (the docutils dev. team for example) who > are not interested in using git, and would probably regard needing to > use it to download and try a piece of software as a reason not to try > the software. > > > Perhaps > > once the development solidifies enough and begins targeting > > non-programmers (average user), then it might need a little dumbing > > down of the distribution method. > > > > I may be a bit on the edge as a user, I use a rolling distribution > > for my operating system so I am familiar with the model, but Leo is > > currently fluid, and as a user that is one of its strengths to me. > > Installing git and writing a script to pull down the latest Leo and > > start it was simple, and I can't see it being any more difficult on > > other platforms. I guess I see the use of git as a feature. :-) > > For a programmer. I think expecting people to unzip a zip is not > unreasonable, although it will screen out some people, but they were > probably not going to find Leo to their liking. Hence the problem with > the .zip reporting misleading version info. > > Cheers -Terry > > > Chris > > > > On Thursday, August 14, 2014 8:59:02 AM UTC-7, Terry wrote: > > > > > > On Thu, 14 Aug 2014 10:40:23 -0500 > > > "Edward K. Ream" <edre...@gmail.com <javascript:>> wrote: > > > > > > > On Thu, Aug 14, 2014 at 9:02 AM, Dufriz <duf...@gmail.com > > > > <javascript:>> > > > wrote: > > > > > I am on Windows 8.1, running Python 3.3.5 with > > > > > PyQt4-4.10.4-gpl-Py3.3-Qt4.8.5-x64. > > > > > I am using Leo 4.11 final, build 6240. > > > > > > > > Thanks for this. This looks like ancient history, though I might > > > > be mistaken. Recent builds (from git) look like: > > > > > > > > Leo 4.11 final, build 6e21a6dc12f0 (branch: master), 2014-08-13 > > > > 08:30:03 > > > > > > That's a good point of course, my comments about needing "c, " > > > added in that call apply to the current trunk, not sure about that > > > version. > > > > > > Actually.... Houston, we have a problem. > > > > > > Leo uses the model "use the trunk, it's stable" - ok > > > > > > It's not ok to require that people use `git` to get it, that's > > > unreasonable. > > > > > > But no problem, they can use the snapshot, > > > https://github.com/leo-editor/leo-editor/archive/master.zip > > > > > > But... that identifies itself in the log window as > > > > > > Leo 4.11 final, build 6240, 2013-11-06 > > > Python 2.7.6, PyQt version 4.8.6 > > > > > > which is completely misleading. It does that because it falls back > > > on version.py or similar, I assume, when the .git directory's not > > > present. > > > > > > So, we need a git commit hook to update version.py on every commit. > > > > > > Or, not use git-hub for snapshots, but it seems git-hub is so close > > > to doing exactly what we need it's worth getting version reporting > > > in git-hub snapshots to work. > > > > > > (Summary - quite possibly Dufriz is using the latest code, can't > > > tell from the log pane content) > > > > > > Cheers -Terry > > > > > > > Could you pull down the latest git version? Alternatively, you > > > > could get a recent daily snapshot? That way we can all be > > > > discussing recent code. If you use git you can instantly get any > > > > improvements. > > > > > > > > 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. > -- 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.
