Re: Visions of Leo 5.0
On Wed, Jun 29, 2011 at 4:41 PM, Josef joe...@gmx.net wrote: It also wasn't entirely clear to me how to set up a myLeoSettings.leo file. I think Leo should offer to create a template file, if none exists yet, or this should be documented for the new and inexperienced user. Check out help - open quickstart.leo. This should in general be consulted as the first thing you do with Leo, before reading the documentation even. -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Persistent custom frame layouts with free_layout
I have persistent custom frame layouts with free_layouts working, just need to clean up a couple of minor things. Only problem is they work fine with this system: Python: 2.6.5 (r265:79063, Apr 16 2010, 13:57:41) [GCC 4.4.3] PyQt: 4.7.2 Qt: 4.6.2 Leo: 4424 terry_n_br...@yahoo.com-20110629025005-a7cbpyix5odpgqd8 Linux: DISTRIB_DESCRIPTION=Ubuntu 10.04.2 LTS but with this system: Python: 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53) [GCC 4.5.2] PyQt: 4.8.3 Qt: 4.7.2 Leo: 4424 terry_n_br...@yahoo.com-20110629025005-a7cbpyix5odpgqd8 Linux: DISTRIB_DESCRIPTION=Ubuntu 11.04 I get RuntimeError: underlying C/C++ object has been deleted and I can't work out why. Apart from that it appears to have a lot of potential. Cheers -Terry -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Persistent custom frame layouts with free_layout
Earlier free_layout stuff also segfaulted with me on maverick when I fiddled with it. Don't know what would cause it - you possibly had a parent for some QObject, the parent got garbage collected and the child c++ object deleted as a result (regardless of whether you still had a python reference to it). On Wed, Jun 29, 2011 at 5:35 PM, Terry Brown terry_n_br...@yahoo.com wrote: I have persistent custom frame layouts with free_layouts working, just need to clean up a couple of minor things. Only problem is they work fine with this system: Python: 2.6.5 (r265:79063, Apr 16 2010, 13:57:41) [GCC 4.4.3] PyQt: 4.7.2 Qt: 4.6.2 Leo: 4424 terry_n_br...@yahoo.com-20110629025005-a7cbpyix5odpgqd8 Linux: DISTRIB_DESCRIPTION=Ubuntu 10.04.2 LTS but with this system: Python: 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53) [GCC 4.5.2] PyQt: 4.8.3 Qt: 4.7.2 Leo: 4424 terry_n_br...@yahoo.com-20110629025005-a7cbpyix5odpgqd8 Linux: DISTRIB_DESCRIPTION=Ubuntu 11.04 I get RuntimeError: underlying C/C++ object has been deleted and I can't work out why. Apart from that it appears to have a lot of potential. Cheers -Terry -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en. -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Persistent custom frame layouts with free_layout
On Wed, Jun 29, 2011 at 9:35 AM, Terry Brown terry_n_br...@yahoo.com wrote: I have persistent custom frame layouts with free_layouts working, just need to clean up a couple of minor things. Only problem is they work fine with this system: Python: 2.6.5 (r265:79063, Apr 16 2010, 13:57:41) [GCC 4.4.3] PyQt: 4.7.2 Qt: 4.6.2 Leo: 4424 terry_n_br...@yahoo.com-20110629025005-a7cbpyix5odpgqd8 Linux: DISTRIB_DESCRIPTION=Ubuntu 10.04.2 LTS but with this system: Python: 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53) [GCC 4.5.2] PyQt: 4.8.3 Qt: 4.7.2 Leo: 4424 terry_n_br...@yahoo.com-20110629025005-a7cbpyix5odpgqd8 Linux: DISTRIB_DESCRIPTION=Ubuntu 11.04 I get RuntimeError: underlying C/C++ object has been deleted Right, that's what I get when I rclick on the divider and select Delete 1 right BTW, how do you retrieve the nice version list? and I can't work out why. Apart from that it appears to have a lot of potential. Cheers -Terry -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en. -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Visions of Leo 5.0
Thanks. As I was using Leo until 2 years ago, I never bothered to open the quickstart.leo. Perhaps it should be a bit higher in the Help menu? - note: I am still running 4.8, perhaps this has changed already. - Josef On Jun 29, 3:53 pm, Ville M. Vainio vivai...@gmail.com wrote: On Wed, Jun 29, 2011 at 4:41 PM, Josef joe...@gmx.net wrote: It also wasn't entirely clear to me how to set up a myLeoSettings.leo file. I think Leo should offer to create a template file, if none exists yet, or this should be documented for the new and inexperienced user. Check out help - open quickstart.leo. This should in general be consulted as the first thing you do with Leo, before reading the documentation even. -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Undo?
Iterate back through the global undo stack and only act on the undoings which affect the current node? :-) I'm sure it's not as simple as that, but it must also be possible. what happens in the case of [cut] text from NodeA and [paste] into NodeB? (with focus in NodeB) especially if there is intervening activity to muddy things up. I think node-specifc and global undo *could* work, but would need a tree visual to keep track of things. -matt -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Persistent custom frame layouts with free_layout
On Wed, 29 Jun 2011 10:25:41 -0500
Kent Tenney kten...@gmail.com wrote:
Right, that's what I get when I rclick on the divider and select
Delete 1 right
I think what you're seeing was just an old viewrendered / free_layout
integration bug.
But nonetheless this comment has jogged my awareness that everything is
working, including Delete 1 right, it's only the layout restoration
code which causes the problem. So there must be some piddly detail
there...
BTW, how do you retrieve the nice version list?
Run this script
from PyQt4 import QtCore
import sys
import os
g.es(Python: %s%sys.version)
g.es(PyQt: %s%QtCore.PYQT_VERSION_STR)
g.es(Qt: %s%QtCore.QT_VERSION_STR)
g.es(Leo: %s%open(os.path.join(
g.computeLeoDir(), '../.bzr/branch/last-revision')).read())
g.es(Linux: %s%open('/etc/lsb-release').read().strip().split('\n')[-1])
Cheers -Terry
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
Re: Visions of Leo 5.0
Dear Edward, if you want to increase the user base, there are 2 user groups I could think of: the ones using all these different editors will be often also people using LaTeX, and so far I find TeX support is a bit weak. I wish TeX support would be similar to ReST support, although there is an added complexity when implementing @auto for TeX, because LaTeX users tend to split up the source code into muliple files using \input, and that would somehow need to be mapped sensibly to the representation in Leo (probably using inputfile or so). If I ever find the time I will work on this, but I am too busy to promise anything. The second group are those who are using lots of non-text files, e.g. MS Office or similar, CAD tools, etc. These would benefit of a good integration of binary files. For example, when dragging a binary file to Leo, it should not attempt to create an @edit or @auto node, but an @mime node (needs the mime plugin). Alteratively an @url node would work. Note: I think this should result in a RELATIVE link. In my opinion, Leo should provide a way to specify what is a binary file and what is not, as this would be more portable, and also because I can immediately think of files which I want my system to treat differently as Leo does: TaskJuggler project files for example. I want Leo to open these as text (@edit or @file), but the OS should open these with the TaskJuggler program. The same should also work for the active_path plugin, which currently allows to specify only one type of default file directive, but it would be better to be able to specify the file directive per file type. Btw: I have just used Leo as a project management tool, handling a couple of hundred LaTeX, TaskJuggler, Excel, JPEG, PDF files and (ad hoc) Python scripts to generate with a team of 5-6 people a 600 page proposal. I could not have done it without Leo. - Josef -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Persistent custom frame layouts with free_layout
Using:
Python: 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53)
[GCC 4.5.2]
PyQt: 4.8.3
Qt: 4.7.2
Leo: 4413 edream...@gmail.com-20110621140518-lpagx1kq4z7p8kvf
Linux: DISTRIB_DESCRIPTION=Ubuntu 11.04
I do Plugins - active_path - about
then rclick - remove 1 right and get:
hook failed: idle, bound method ViewRenderedController.update of
leo.plugins.viewrendered.ViewRenderedController instance at
0x37f5170, leo.plugins.scrolledmessage
Traceback (most recent call last):
File /usr/fetching/leo-editor/leo/core/leoPlugins.py, line 336, in
callTagHandler
result = handler(tag,keywords)
File /usr/fetching/leo-editor/leo/plugins/viewrendered.py, line
562, in update
sb = w.verticalScrollBar()
RuntimeError: underlying C/C++ object has been deleted
On Wed, Jun 29, 2011 at 11:00 AM, Terry Brown terry_n_br...@yahoo.com wrote:
On Wed, 29 Jun 2011 10:25:41 -0500
Kent Tenney kten...@gmail.com wrote:
Right, that's what I get when I rclick on the divider and select
Delete 1 right
I think what you're seeing was just an old viewrendered / free_layout
integration bug.
But nonetheless this comment has jogged my awareness that everything is
working, including Delete 1 right, it's only the layout restoration
code which causes the problem. So there must be some piddly detail
there...
BTW, how do you retrieve the nice version list?
Run this script
from PyQt4 import QtCore
import sys
import os
g.es(Python: %s%sys.version)
g.es(PyQt: %s%QtCore.PYQT_VERSION_STR)
g.es(Qt: %s%QtCore.QT_VERSION_STR)
g.es(Leo: %s%open(os.path.join(
g.computeLeoDir(), '../.bzr/branch/last-revision')).read())
g.es(Linux: %s%open('/etc/lsb-release').read().strip().split('\n')[-1])
Cheers -Terry
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
Re: Persistent custom frame layouts with free_layout
On Wed, 29 Jun 2011 12:29:34 -0500 Kent Tenney kten...@gmail.com wrote: I do Plugins - active_path - about then rclick - remove 1 right and get: hook failed: idle, bound method ViewRenderedController.update of leo.plugins.viewrendered.ViewRenderedController instance at 0x37f5170, leo.plugins.scrolledmessage Yes, but I haven't pushed my refactor of the viewrendered / free_layout interaction, so that's a legitimate case of the C++ object being deleted because no one told viewrendered its window was closed. But your earlier mention of remove 1 right pushed me back into the code one more time and I've fixed the problem in the persistence branch - woohoo. Seems 4.8 required a widget to be constructed with a parent where 4.7 didn't - don't really see why as the widget was immediately inserted into the parent and I'm sure that sets the parent relationship. And apparently 'not w' works as expected in 4.7, but 4.8 requires 'w is None' because bool(w) is evaluating false in 4.8 where it didn't in 4.7. So, when I finish removing debugging code perhaps you can test this branch Kent? I'll let you know when it's on lp. Cheers -Terry -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Visions of Leo 5.0
There are many very good comments here! I have some things of my own laundry list to add. In a quick re-read before posting the list rings more of complaint than helpful feedback. Please understand that's not the tone I mean to impart. I really like Leo, but I do have a hard time getting completely comfortable with it. ;-) 1. The goal is to increase the number of Leo's users. As others have said, one click install would be very very nice. I'd like to extend that thinking to include one click use. I'm not being literal, I talking about the feeling of a one click install carried over to smoothly and easily using Leo. For example: Why do I have to edit a file, or multiple files, and read a whole bunch of stuff which only vaguely makes sense because a lot of it is new, to explore plugins? It would be so much easier if there were a menu/page/something which presented the list of available plugins with enable/disable checkboxes, a short description of what they do and clickable link for more information. http://lifehacker.com/5789781/step-up-your-notepad%252B%252B-game-with-powerful-plugins how many steps (clicks, types, etc.) does it take to build a myLeoSettings.leo on a new machine? What if personal preferences were automatically built from an dialog like the plugins manager floated above? (e.g. if user enables a plugin, the setting for that is copied from LeoSettings.leo to myLeoSettings.leo and saved. or something). Make edit node in external editor work out of the box seamlessly so people who are just testing the water don't feel like they're being asked to give up what they're familiar with. The search and replace experience is broken. My #1 use of external editor is in order to do simple s+r like a global rename fooBar to foobar in one step. Rich text (html) renderding enabled by default so that when looking at things like About plugin the [html] [text] buttons actually do something and the first thing one sees is not pre and gt; lt; etc. People like toolbars. Make it easy to add frequently used commands to a toolbar, maybe by dragging and dropping from the menus? (or nodes?) Helper text, defaults. For a while I thought the [Nav] pane was broken because the initial view is a completely blank area and I didn't realize it was search function. A simple phrase would help type and press enter to locate occurences of The confusion was minor and short lived, but it needn't have occurred at all. This is a good example of how a one-click install feeling could be carried over. Make the leo website a first class citizen: - acquire www.leo-editor.org (or variant) - fix the broken search - apply server side redirects so old links can find the new home page (for example the Flattr link is broken), or use a custom 404 that suggests alternatives (http://sixrevisions.com/design-showcase-inspiration/beautiful-and-useful-404-error-pages-for-inspiration/; I like #14 because it includes a search box) - fix the wiki or find a new one where user contributed recipes and documentation can be worked on (make sure it's hosted on leo-editor.org) Video's, screencasts, recipes, demos! Leo is unlike anything else. Reading the docs, asking questions on the forum, and the like is a great way to learn things but there is so much of what makes Leo useful that just can't be conveyed easily in words. Setup a ShowMeDo channel (http://showmedo.com/). Stories. It's things like this that first caught my attention http://webpages.charter.net/edreamleo/testimonials.html (the long ones). There were one or two by Edward that were inspirational but I can't find right now; perhaps they're buried in the mailing list. A faster fancier glitzier way of doing X is interesting but only for a moment or three. Far more intriguing is seeing how Leo enables things which just weren't possible before, or changes how one works or looks at data forever (regardless of whether Leo is actually used in X). cheers, -matt -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Visions of Leo 5.0
Does the edit in external editor not work seamlessly from rclick menu? On Wed Jun 29 21:09:43 2011 Matt Wilkie wrote: There are many very good comments here! I have some things of my own laundry list to add. In a quick re-read before posting the list rings more of complaint than helpful feedback. Please understand that's not the tone I mean to impart. I really like Leo, but I do have a hard time getting completely comfortable with it. ;-) 1. The goal is to increase the number of Leo's users. As others have said, one click install would be very very nice. I'd like to extend that thinking to include one click use. I'm not being literal, I talking about the feeling of a one click install carried over to smoothly and easily using Leo. For example: Why do I have to edit a file, or multiple files, and read a whole bunch of stuff which only vaguely makes sense because a lot of it is new, to explore plugins? It would be so much easier if there were a menu/page/something which presented the list of available plugins with enable/disable checkboxes, a short description of what they do and clickable link for more information. http://lifehacker.com/5789781/step-up-your-notepad%252B%252B-game-with-powerful-plugins how many steps (clicks, types, etc.) does it take to build a myLeoSettings.leo on a new machine? What if personal preferences were automatically built from an dialog like the plugins manager floated above? (e.g. if user enables a plugin, the setting for that is copied from LeoSettings.leo to myLeoSettings.leo and saved. or something). Make edit node in external editor work out of the box seamlessly so people who are just testing the water don't feel like they're being asked to give up what they're familiar with. The search and replace experience is broken. My #1 use of external editor is in order to do simple s+r like a global rename fooBar to foobar in one step. Rich text (html) renderding enabled by default so that when looking at things like About plugin the [html] [text] buttons actually do something and the first thing one sees is not pre and gt; lt; etc. People like toolbars. Make it easy to add frequently used commands to a toolbar, maybe by dragging and dropping from the menus? (or nodes?) Helper text, defaults. For a while I thought the [Nav] pane was broken because the initial view is a completely blank area and I didn't realize it was search function. A simple phrase would help type and press enter to locate occurences of The confusion was minor and short lived, but it needn't have occurred at all. This is a good example of how a one-click install feeling could be carried over. Make the leo website a first class citizen: - acquire www.leo-editor.org (or variant) - fix the broken search - apply server side redirects so old links can find the new home page (for example the Flattr link is broken), or use a custom 404 that suggests alternatives (http://sixrevisions.com/design-showcase-inspiration/beautiful-and-useful-404-error-pages-for-inspiration/; I like #14 because it includes a search box) - fix the wiki or find a new one where user contributed recipes and documentation can be worked on (make sure it's hosted on leo-editor.org) Video's, screencasts, recipes, demos! Leo is unlike anything else. Reading the docs, asking questions on the forum, and the like is a great way to learn things but there is so much of what makes Leo useful that just can't be conveyed easily in words. Setup a ShowMeDo channel (http://showmedo.com/). Stories. It's things like this that first caught my attention http://webpages.charter.net/edreamleo/testimonials.html (the long ones). There were one or two by Edward that were inspirational but I can't find right now; perhaps they're buried in the mailing list. A faster fancier glitzier way of doing X is interesting but only for a moment or three. Far more intriguing is seeing how Leo enables things which just weren't possible before, or changes how one works or looks at data forever (regardless of whether Leo is actually used in X). cheers, -matt -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en. -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: Visions of Leo 5.0
Does the edit in external editor not work seamlessly from rclick menu?
It does now, but I had to set it up in myLeosettings.leo.
...{does some tests}
...and it still works after removing my custom editor string. I guess
I'm remembering pain from before, which is now fixed. Happily we can
cross that one out!
-matt
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
Re: Persistent custom frame layouts with free_layout
On Wed, 29 Jun 2011 14:08:47 -0500 Kent Tenney kten...@gmail.com wrote: I've done bzr branch lp:~terry-n-brown/leo-editor/free_layout waiting for the word. Ok - version ready for testing at that location. free_layout.py must occur early in your @enabled-plugins list. In particular it should be before viewrendered.py. Other than that dependency these plugins are now quite independent. The context menu on the splitters now has a Save layout entry, and after you've saved a layout, there will be a Load layout and Delete layout entry, with all your named layouts as sub-menu-entries. When you load a layout open panes not needed for the layout are not closed, they just end up tacked on to the edge of the layout. Usually this is not a problem as you'll load a layout over the default layout, and typically all three default panes occur somewhere in all layouts. Viewrendered is working, although commands to activate/deactivate freeze/unfreeze it aren't. Rendering of plugin docs. also uses a viewrendered pane, and that seems to be working. Cheers -Terry -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
