- Also, quickstartguide should be open by default (instead of current Leo workbook) at least until the user changes some config and prevents that from happening. Is there any "load previous tabs" functionality? (IE open the Leo files which where open when it was closed the last time)
On Thursday, May 9, 2013 9:36:36 AM UTC+2, Fidel Pérez wrote: > > Hi: > > - Im having trouble also linking Leo files to Leo. I have tried this: > > > Associate .leo filetype batch file: >> ftype LeoFile=C:Python25pythonw.exe “C:Python25Libsite- >> packagesleolaunchLeo.py” “%1” assoc .leo=LeoFile > > > Which I found > here<https://groups.google.com/forum/?fromgroups=#!searchin/leo-editor/associate/leo-editor/3Ry5o8gE16E/Ble8B8RCRUsJ>, > > but leolaunchleo.py doesnt even exist anymore (the post is old). > > > - I guess others have had this idea but It would be great to include a > small file within the Quickstart guide which would associate files > automatically. (Or maybe asking for imput, which can be done through a Leo > node and this way the user learns about its functionality). > > > > - Also, I miss some more buttons or scripts in quick start > guide, preferably before the "programming" section, so when a new > user opens it, he has had the opportunity to do Ctrl+B on several scripts > (for instance, showing in the log the name of all the nodes within the > selected one, having some subnodes with numbers and doing math on them and > showing the result on the log pane, and as much "silly" but visual > functions as possible so the user, by going pressing ctrl+b on each, gets > a > bigger chance to understand what is Leo. In my oppinion some users will > just stop in the quickguide if they are not presented with such a thing > before going to docs.leo etc. > > > > - Another thing is the plugin activation, the description of the > plugins is not as accessible as it should be (opinions here, focusing > in new users, and as I always say, appreciating and fully grateful for Leo > as is now),and a script for activating them easier, been a week using Leo > and still cant quite activate, find the descriptions or use them freely... > And if each plugin or script had an example of use that would be > priceless, > for instance, including them all in quickstart (both scripts, plugins > branchs) and then the new user could just go through all clicking on the > examples and just seeing Leo work and show its potential. I know some of > those are done but as I said, after a week or so I still am very > confused... > > > Thank you. > -- 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?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
