On Mon, Nov 18, 2013 at 1:56 PM, rengel <[email protected]> wrote:
My first impression: > > Leo is too hard to work with! Even seemingly simple things are way to > complicated to figure out. > I agree completely. I am working on it intensely, with help from many people. > First: The default font size is too small > . > Others consider it too large. But now it's easier (not dead easy yet) to experiment. - Look at the various leo-x-pt.leo files in the leo/config directory. Find the one that looks best to you. - Copy the @data qt-gui-plugin-style-sheet node from the file to your myLeoSettings.leo file. - Delete all other @data qt-gui-plugin-style-sheet nodes if they exist, and make sure the newly-copied @data node is, in fact, a child of the @setting node. > Second: I wanted to import a Django project structure into Leo. Leo has a > File|Import command that works well - but only with files. Now, a project > folders/files structure is a perfect example for hierarchically arranged > things, and thus it should be easy to import such a structure into Leo. I > would expect the Import command to do this. But I had do research just to > find out, that there are some obscure plugins or scripts that do the job. > This is a harder problem to solve with documentation. I've just put recursive import on the list of topics for screencasts. My impression is that making a screencast on any topic instantly makes it clearer for every (newbies or experts) *or* the screencast reveals a big opportunity for improvement. For instance, I am working as hard as I can to improve Leo's find command. > > Don't get wrong. IMHO Leo is a brilliant tool, but apart from the rather > steep learning curve its usability is wanting. > Everything is pretty simple for me, so I'm not sure I agree with you. @button is a great tool. It will have a separate screencast. Recursive import is, for now at least, one of the hardest things to do because nobody has figured out how to pass arguments to scripts (or commands, for that matter) in a completely easy way. Alan Kay has said: "*Simple things* should be *simple*, complex things > should be possible." > Leo shines when it comes to the second half of this sentence. > I am always looking for ways to make simple things simpler. Specific suggestions help a lot, even seemly small ones. For example, a comment about having <enter> initiate Leo's find command has resulted in a cascade of simplifications. I'll be discussing that soon. A completely reworked screencast about the Find command will happen as soon as I finish it. Maybe in a day or so. > What I want to say: People that are willing to try out some new tool, > don't want to wade through documentation in order to accomplish simple task. > > I you want to break out the narrow group of developers who like such > things, > > finding out common tasks like changing settings, importing files and file > structures etc. shouldn't eat up all the time people are willing to invest > in trying out a new product. > I agree completely. Screencasts are the way to much bigger exposure. Before this week, I thought that screencasts entailed a significant amount of work. But this weekend I did three screencasts in a few hours. This is a very exciting development. Certainly, Leo must have a screencast for each topic you mention. Preferably yesterday ;-) Many thanks for your comments. 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/groups/opt_out.
