Re: Status of Leo wrt. wxPython?
Hi Terry OK, thanks. I may take a look ... Regards J^n --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: $200 reward for gui plugins
Hi Edward out of interest, do you know which version of wxWidgets you last looked at? Regardless, all this interest activity on the GUI side of things is very interesting to me! ;-) Thanks Jon N --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
AttributeError when attempting to startup qt-plugin
Hi there after following all the recent qt-pluging work with excitement, I thought I'd take a look. This is from qt-plugin branch rev. 1360. It's probably a newbie error, but here's what I'm seeing after running $ python launchLeo.py --gui=qt reading settings in /transfer/qt-plugin/leo/config/leoSettings.leo Using menus from leoSettings.leo reading /home/jkn/.leo/.leoRecentFiles.txt loaded plugin: qtGui @enabled-plugins found in leoSettings.leo can not load enabled plugin: mod_scripting rst3 plugin: SilverCity not loaded rst3 plugin not loaded: can not load docutils can not load enabled plugin: rst3 can not load enabled plugin: UNL can not load enabled plugin: nav_buttons can not load enabled plugin: hoist image.py: can not import ImageTk can not load enabled plugin: image can not load enabled plugin: threading_colorizer You must be using Python 2.5 or above to use aspell on Linux Traceback (most recent call last): File launchLeo.py, line 8, in ? leo.core.runLeo.run() File /transfer/qt-plugin/leo/core/runLeo.py, line 120, in run c,frame = createFrame(fileName,relativeFileName,script) File /transfer/qt-plugin/leo/core/runLeo.py, line 170, in createFrame c.chapterController.finishCreate() File /transfer/qt-plugin/leo/core/leoChapters.py, line 50, in finishCreate cc.createChaptersNode() File /transfer/qt-plugin/leo/core/leoChapters.py, line 473, in createChaptersNode p = root.insertAsLastChild() File /transfer/qt-plugin/leo/core/leoNodes.py, line 2307, in insertAsLastChild n = p.numberOfChildren() File /transfer/qt-plugin/leo/core/leoNodes.py, line 1263, in numberOfChildren return len(p.v.t.children) AttributeError: 'NoneType' object has no attribute 't' Thanks fro all the great work on Leo. I might mention that it's great to 'look over your shoulders' as things progress. Cheers J^n --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Feature request
me too! Cheers J^n PS: I was seeing reference to right-mouse clicks, assume that it's possible to assign to this (someone mentioned context editing of nodes etc.). Where do I look to learn more about this please? Thanks, J --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Demo qt gui using docking widgets instead of splitters
On Nov 25, 7:03 pm, leo_hag [EMAIL PROTECTED] wrote: The code is in leo\test\qtOutlineDemo.py. It is not a real leo just a demo which uses leoBridge to get the data. I think you mean leo\plugins\qtOutlineDemo.py? # s/\\/\/ to suit... Thanks for the docking demo. I for one think I prefer the minibuffer at the top, as has already been discussed somewhat. J^n --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Aha!!! simple, extremely fast tree updates!
Hi Edward I've said it before, but it's worth repeating - I really enjoy reading of your insights as you rework this kind of thing. As a developer myself, It's fascinating 'looking over your shoulder' at the decisions, insights, mistakes(?) and aha's you encounter, and to compare them with my own in other areas. Thanks for making this public. Regards Jon N --~--~-~--~~~---~--~~ 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: Aha!!! simple, extremely fast tree updates!
Anyway, the great mathematicians are my inspiration. Many continually reworked their important theorems, seeking the simplest, most elegant proofs. That is some consolation now :-) Yep, the aesthetic beauty of a good proof or theorem is certainly something to be aimed at ... Jon N --~--~-~--~~~---~--~~ 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: leo\plugins\wxGui.py on trunk
I for one am still interested in the wx port/attempt, and thank you for your work in pursuing it. I do not think that the recent Qt license changes are the be-all and end-all of the matter, and (for educational and familiarity purposes if nothing else) would like to have a look at this myself in the course of time. thanks Jon N --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
startup problem with new bzr checkout?
(I tend to checkout a clean version of the trunk ... not sure if this is why I'm seeing this:) $ bzr branch lp:leo-editor [...] $ cd leo-editor $ python launchLeo.py --gui=qt reading settings in /transfer/leo-editor/leo/config/leoSettings.leo Using menus from leoSettings.leo reading /home/jkn/.leo/.leoRecentFiles.txt loaded plugin: qtGui @enabled-plugins found in leoSettings.leo rst3 plugin: SilverCity not loaded rst3 plugin not loaded: can not load docutils can not load enabled plugin: rst3 can not load enabled plugin: nav_buttons can not load enabled plugin: hoist can not load enabled plugin: image can not load enabled plugin: threading_colorizer opening default_leo_file: /home/jkn/.leo/workbook.leo Traceback (most recent call last): File launchLeo.py, line 8, in module leo.core.runLeo.run() File /transfer/leo-editor/leo/core/runLeo.py, line 104, in run c,frame = createFrame(fileName,relativeFileName,script) File /transfer/leo-editor/leo/core/runLeo.py, line 141, in createFrame ok, frame = g.openWithFileName(relativeFileName or fileName,None) File /transfer/leo-editor/leo/core/leoGlobals.py, line 2200, in openWithFileName gui=gui) File /transfer/leo-editor/leo/core/leoApp.py, line 657, in newLeoCommanderAndFrame frame.finishCreate(c) File /transfer/leo-editor/leo/plugins/qtGui.py, line 1234, in finishCreate f.top = DynamicWindow(c) File /transfer/leo-editor/leo/plugins/qtGui.py, line 164, in __init__ self.ui = uic.loadUi(ui_description_file, self) File /usr/lib/python2.5/site-packages/PyQt4/uic/__init__.py, line 93, in loadUi return loader.DynamicUILoader().loadUi(uifile, baseinstance) File /usr/lib/python2.5/site-packages/PyQt4/uic/Loader/loader.py, line 25, in loadUi return self.parse(filename) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 569, in parse actor(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 428, in createUserInterface self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 160, in createWidget self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 301, in createLayout self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 309, in handleItem self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 160, in createWidget self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 160, in createWidget self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 160, in createWidget self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 301, in createLayout self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 309, in handleItem self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 160, in createWidget self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 301, in createLayout self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 309, in handleItem self.traverseWidgetTree(elem) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 406, in traverseWidgetTree handler(self, child) File /usr/lib/python2.5/site-packages/PyQt4/uic/uiparser.py, line 153, in createWidget self.stack.push(self.setupObject(widgetClass(elem), parent, elem)) File /usr/lib/python2.5/site-packages
Re: startup problem with new bzr checkout?
re-emerg'ing (I'm on Gentoo Linux) qscintilla and qscintilla-python fixed things. Not quite sure why, but anyway ... apologies for the noise. J^n --~--~-~--~~~---~--~~ 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: Robin Dunn's mission
This is probably rather a jump, but never mind... The text editor I have most fondness of is Brief, which ran under DOS. It was sold to Borland, who later killed it off. When MS-windows came along, Premia Codewright was a very capable editor which used the Brief API ... until Premia sold it to Borland, who killed it off ;-( For programming, I currently use CRiSP, which has been around for a very long time. It started life as a shareware version of Brief, but is nowadays a licensed product runs under many GUI operating systems. CRiSP is *extremely* configurable, in a similar way to emacs, but IMO does this much more elegantly. Partly this is because it is mainly written by one person. It has a macro programming language, similar to C but with added data types (strings, dictionaries, dynamic arrays...). It happens to be compiled down to a lisp-like virtual machine, but that is not relevant here. The CRiSP macro language allows creation of key mappings, dialogs, and all sorts of things I won't go into here. My main reason for posting this is to point you at the primitive API. As I mention, this is based on the original BRief API, which was very elegant. you could push() and pop() a keyboard mapping, which allowed you to map things temporarily, for instance. Also, the naming was very consistent; inq_xxx() and set_xxx() were used to inquire and set, respectively, various parameters, etc. etc. This: http://www.infoload.net/CRiSP/user.pdf is a pdf of the CRiSP macro primitives guide (note: the PDF has 'bookmark not defined' errors). I think it is worth looking at if only to see the API of an extremely mature and capable editor. Cheers Jon N --~--~-~--~~~---~--~~ 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: New qt scrolling policy on trunk: comments please
On Feb 2, 5:06 pm, Mike Crowe drmikecr...@gmail.com wrote: Why should expanding a node scroll the tree up at all? Aren't we making this too hard? Every experience with tree's I've had, you should be able to click and expand, and click and contract w/o moving the mouse (i.e. the current tree node doesn't change positions). Exactly my experience and expectation. FWIW there might be room for a slightly quirky command when on a child node: contract my parent node, making this node invisible and moving the selection from this child node to that parent node. But I can't say it's something I'm hankering after... Jon N --~--~-~--~~~---~--~~ 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: Making Qt the default?
On Feb 2, 6:26 pm, Mike Crowe drmikecr...@gmail.com wrote: I'm trying to get the Qt GUI when I double-click on a .leo file you can set up the file association to run Leo with the --gui=qt setting when you double-click on a .leo file. In Windows = XP) this is done via the Explorer. J^n --~--~-~--~~~---~--~~ 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: New qt scrolling policy on trunk: comments please
I haven't really got enough experience of the old vs. the new to say ... but I will make a few comments anyway ;-o. This is on rev 1502. I actively dislike what I see when I expand/contract a node, which is that the vertical position of the selected parent node shifts within the outline pane. IMO it is the (vertical) position of the 'parent node' which should be stationary in this case. This observed behaviour may depend on the number of child nodes, whether they go off the bottom of the outline pane. I've just had a look at the tk behaviour and it doesn't seem very much different, so maybe the behaviour I dislike has always been there ... Nevertheless, HTH Jon N --~--~-~--~~~---~--~~ 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: New qt scrolling policy on trunk: comments please
Hi Edward Rev 1507 contains my latest attempt at minimizing scrolling. It seems to work better. What do you think? Better, but still not right IMHO. The (unwanted) scrolling still seems to occur if: - you have a child node highlighted and contract the parent - you contract a parent node such that the bottom node of the tree becomes visible in the outline pane. (I don't think this is a definitive list) I can supply a simple outline if that would help describe things. Are we aiming at the same end result, I wonder? FWIW I do think this is really important to get right. For anyone used to working within other tree paradigms, odd visual behaviour here really stands out. Thanks Jon N --~--~-~--~~~---~--~~ 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: New qt scrolling policy on trunk: comments please
Hi Edward Maybe, but there are much bigger fish to fry at present that don't involve drawing. Reducing flash would, imo, be a much better first step as far as drawing goes. sure - I was really lumping screen flash in with the scrolling as things which should work so's you don't notice them. If screen jump really bothers you, I suggest using the alt-arrow keys to move around the tree :-) I'll bear this in mind, thanks. J^n --~--~-~--~~~---~--~~ 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: How to simplify key handling
Hi Edward
very sensible idea IMO. I had wondered what representation you
used internally for keystrokes, given some of the machinations around
keybindings etc. I'd read about here.
Doesn't emacs (and Vi?) have the idea of one or more 'meta' ('M')
keys, rather than hardcoding it as 'Alt'?
Bearing in mind my recent mumblings about the Crisp editor, I may have
more to suggest around this in future.
Regards
Jon N
--~--~-~--~~~---~--~~
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: New intro on Leo's wiki
I'm still writing as a 'wannabe-user' of Leo here, and showing my ignorance, but that's OK ;-/. Something that I was reminded about by reading the new intro: ?? why is it called the 'minibuffer'?? Is there a 'maxibuffer'? or a 'buffer' somewhere? (apart from the underlying implementation, of course). Is it important **to the user** that it is a buffer? When I use other editors with a command capability and a space on the screen to use it, it's called something like the 'command area'. IMO the term 'minibuffer' is unhelpful to understanding (unless I've misunderstood, which is quite possible...) and I suggest that an alternative term would help foster takeup of Leo. HTH Jon N --~--~-~--~~~---~--~~ 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: New intro on Leo's wiki
On Feb 19, 8:58 pm, zpcspm zpc...@gmail.com wrote: On Feb 19, 10:55 pm, jkn jkn...@nicorp.f9.co.uk wrote: IMO the term 'minibuffer' is ... ... tied to emacs I believe. Yes, I wondered that from the way the page was written. I think linking Leo to emacs in this way is A Bad Thing. The last thing you want prospective users to think is 'hey, Leo is like emacs...' Not because I wish to slag off emacs, but because it has a reputation that I don't think you want to saddle Leo with. How about calling it a 'Command Area' (with the screen prompt saying 'Command:' instead of 'Minibuffer:') and then describing it in those terms. It would then be possible to say something like For emacs users, the command area is similar to emacs' minibuffer facility. If you are familiar with this, then many of the actual commands used here have the same, or similar, format to minibuffer commands That way, new users don't have to know about emacs, and emacs users can migrate their understanding easily. jon N --~--~-~--~~~---~--~~ 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: New intro on Leo's wiki
Hi Edward ?? why is it called the 'minibuffer'?? I have no problem with mimicking/stealing(*) such a feature from emacs - I just think that calling it a minibuffer is weird, and loses you more than it gains. This from a potential Leo *** with 25+ years experience using many different editors. 'Minibuffer' comes over to me as another new paradigm within Leo that I need to shift my brain to think about. 'Command area' or similar doesn't. [...] The great advantage of the new top-level page is that I *don't* have to define everything. The top level is more like a chatty table of contents. The in brief sections are haiku hinting at what the child pages contain. This can mean that terms are undefined, but the alternative, in my experience, is *much* worse. The crucial narrative is lost when I have to stop to explain every little thing :-) Yes, I appreciate the tension between these two cases. That's why I think 'command area' would be better - less 'cognitive dissonance' when encountered at the overview level. Regards jon N (*) Good artists borrow, great artists steal - Picasso, or T S Eliot, maybe --~--~-~--~~~---~--~~ 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: New intro on Leo's wiki
'Minibuffer' comes over to me as another new paradigm within Leo that I need to shift my brain to think about. 'Command area' or similar doesn't. I'm starting to be convinced. Maybe I'm resisting because 'minibuffer' and 'minibuffer commands' are entrenched Leo terms now. Yeah, I appreciate this - that's partly why I've not brought it up before. It's because you are re-working the documentation ( I like the end result so far) that now might be a good time to streamline the terminology. Oh, I see didn't finish my earlier posting properly - it should have said This from a potential Leo *advocate* with 25+ years experience using many different editors. As you can probably tell I'm almost looking at this from a *marketing* angle (hence my comments in earlier threads about the requirement (as I see it) for 'seamless' expanding/contracting of outline nodes. Regards Jon N --~--~-~--~~~---~--~~ 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: New intro on Leo's wiki
On Feb 20, 3:35 pm, tfer tfethers...@aol.com wrote: An attempt at the page for external files: Even in this draft form I found this very helpful - thanks. Jon N --~--~-~--~~~---~--~~ 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: Headline vs. Heading
Just wondering what the general opinion is--is that a stumbling block for others? For newbies? I wouldn't put it as strongly as a 'stumbling block', but I too find the 'heading' term sweeter. Jon N --~--~-~--~~~---~--~~ 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: A rewrite of the qt key handling may be needed
Surely the (a) difference is that CTRL-0, and SHIFT-0, both represent ASCII characters. CTRL-SHIFT-0 does not - it's an entirely different species. I agree with Ville (I think) - without knowing much about the Qt representation: press 0: reported as a '0' key (0x30) press CTRL-0: reported as a control character (0x10) press SHIFT-0: reported as a ')' key (0x29) press CTRL-SHIFT-0: reported as some form of keystroke [press ALT-SHIFT-0: reported as some form of keystroke etc.] Furthermore, there is no way for Leo to convert recognize Ctrl-Shift-0 as Ctrl-) in a keyboard-independent manner. This problem was the cause of the just-deleted horrors. Why should there be? IMO Ctrl-Shift-0 should be totally available independent of Ctrl-). If there is a desire for this to map to something 'like' Ctrl-) [eg. for when making pairs of key bindings 'work well' together on the keyboard] then this should be done at a different (higher) level. I imagine there are international keyboards where ')' is on a different key to '0' anyway. jon N On Apr 8, 12:09 pm, Edward K. Ream edream...@gmail.com wrote: On Wed, Apr 8, 2009 at 2:02 AM, Ville M. Vainio vivai...@gmail.com wrote: I think it makes perfect sense to not parse bindings partially, so that you see 0 instead of ). If tk does that, i would say it is broken instead. Imo, when the ctrl key is not down, it would be quite wrong to report ) as shift-0. Qt does not do that. But why change the reporting of the character from ) to shift-0 when the Ctrl key is down? I don't think of Ctrl-) as Ctrl-Shift-0. I much prefer the Tk way. Furthermore, there is no way for Leo to convert recognize Ctrl-Shift-0 as Ctrl-) in a keyboard-independent manner. This problem was the cause of the just-deleted horrors. Anyway, after sleeping on this problem, I think I'll simply add two sets of bindings in leoSettings.leo for the cases where Tk and Qt differ in how they report the key event. This should not cause problems for either of Leo's gui plugins. It's not a perfect solution: the multiple bindings will show up in the print-commands and print-bindings listings, but that can't be helped. I personally can't avoid this problem while I still support both the Tk and Qt plugins, but most people will use just one of the plugins, so they can put only the required bindings in myLeoSettings.leo. The alternative would be to require the user to describe the upper and lower case versions of problematic keys. I'd rather not do that unless there are serious problems with the multiple bindings approach. Any other comments or suggestions? Edward --~--~-~--~~~---~--~~ 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: mercurial?
I use mercurial and like it a lot. But I don't think anyone is saying it has huge advantages over bzr, for instance. If we/EKR is/are happy with bzr then I would leave well alone, for now at least. J^n --~--~-~--~~~---~--~~ 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: Getting unstuck with qt designer
It reminds me of remarks that Bjarne Stroustrup about the C++ parser. I can't find them now, and perhaps I am misremembering them, but as I remember it he said that he chose an LL1 parser for cfront because LL1 parsing was supposedly the best way. But he regretted the choice. He, like me, is much more comfortable with recursive-descent parsing. So he ended up constantly fighting the supposedly better LL1 tool. see Bjarne Stroustrup, The Design and Evolution of C++, pp. 69. (fascinating book!) I can type in the paragraph or two if anyone's really keen... J^n --~--~-~--~~~---~--~~ 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: What are Leo's worst bugs?
It may seem to be a 'worst bug' only to me, but the continuing jumping around within the tree when expanding/contracting nodes (still present I believe in Qt, dunno about Tk) remains the biggest thing stopping me from spending much time with Leo. That may be a poor excuse, I grant you - but it's an annoying fundamental IMHO, and I *want* to be spending my learning/frustration/ excitement quotient in getting to grips with Leo beyond the very basics of nodes and outlines. Regards Jon N --~--~-~--~~~---~--~~ 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: What are Leo's worst bugs?
Hi Ville Now I realized why this is bothering you - you are probably using the mouse to move around, right? It feels much better on the keyboard. Yep, I'm using the mouse. (in part because I use a few other outline-based systems that have different key bindings, I don't yet want to start changing key- bindings) That being said, here might be the way to solve it on expand as well (I won't solve it, I'm going to sleep ;-): [details omitted ...] Thanks, looks interesting. More details appreciated when you're awake ;-) j^n --~--~-~--~~~---~--~~ 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: What are Leo's worst bugs?
On May 22, 2:33 pm, Edward K. Ream edream...@gmail.com wrote: On May 22, 7:47 am, Edward K. Ream edream...@gmail.com wrote: Yep, I'm using the mouse. Thanks for this clarification. The bug report was mystifying me. I'll attempt a fix immediately. I hadn't realised the action would be significantly different between mouse and keyboard, or I'd surely have mentioned it before ;-/. Shurely clicking on a node is entirely the same as move cursor to selected node; perform same action as arrows? But anyway... The current version feels much better from a cursory play - many thanks. [...] As several people have suggested, using keys to navigate the outline will give you a better experience. Use alt arrow keys to put the focus in the outline, if it is not already there. Once that is done, you can use plain arrow keys. I think you will quickly come to prefer this way. I will work with both and give feedback asap. Thanks again Jon N --~--~-~--~~~---~--~~ 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: What are Leo's worst bugs?
On May 22, 7:59 pm, Edward K. Ream edream...@gmail.com wrote: On Fri, May 22, 2009 at 1:38 PM, jkn jkn...@nicorp.f9.co.uk wrote: I hadn't realised the action would be significantly different between mouse and keyboard, or I'd surely have mentioned it before ;-/. Surely clicking on a node is entirely the same as move cursor to selected node; perform same action as arrows? Conceptually yes. But as far as gui event are concerned, they are different. Interesting ... without wishing to bang on quite as loudly as Jesse, this smells like a refactoring thing. I might have a look at this area - if nothing else it's a motivation for me to get into the code a bit. Regards Jon N --~--~-~--~~~---~--~~ 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: What are Leo's worst bugs?
The problems involved in writing event handlers have little to do with refactoring. It's not so much the code itself that is complex; it is the varying contexts in which the code can be called. Yes, I understand how this can be - I've written plenty of GUI code in my time... Things are especially tricky with Leo, because some code can be called both from event triggers and also as the result of executing Leo's commands. Sure - although again I'd hope that the 'exposed API' makes these cases look reasonably uniform. I'll take a look when I get chance anyway... it still surprises me in this use case, and as I say it may be a useful 'way in' for me. Jon N --~--~-~--~~~---~--~~ 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: Any more urgent or annoying bugs?
A couple of things which probably don't fall into the 'urgent or annoying category', but nevertheless ... - I've just done a full 'bzr checkout' and got revno 1990. But 'Help | about Leo' still shows Leo 4.6 Beta 1, build 1.244, March 24, 2009'. It would help bug reports etc. if this was correct... - (a suggestion from a naive user). Experimenting between using Alt-T and Alt-D to switch between the tree and the body; the only visible difference of where the focus is seems to be the presence or absence of the cursor in the body. I think it would be useful if the focus was more obvious; how about changing the colour of the tree's 'current node' highlight, for instance so it was light grey when the focus was not in the tree, and a darker grey when it was? HTH Jon N --~--~-~--~~~---~--~~ 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: Any more urgent or annoying bugs?
On Jun 2, 2:25 pm, Edward K. Ream edream...@gmail.com wrote: [...] I use the following settings (in myLeoSettings.leo) to switch colors in the body pane depending on focus: @string selected-background-color = #fdf5f5 A kind of pink, for when the body has focus @string unselected-background-color = #f2fdff A kind of blue, for when the body does not have focus. Thanks - I hadn't realised this configuration was possible. Anything similar for the tree highlight? I'm just starting to try and use Leo in anger, after a lot of watching with interest from the sidelines. I will collect some observations questions together in a separate topic posting. Jon N --~--~-~--~~~---~--~~ 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: Any more urgent or annoying bugs?
Thanks - I hadn't realised this configuration was possible. Anything similar for the tree highlight? The hack was to add FocusIn/Out methods to the leoQtBody class I doubt that anything similar exists for the leoQtTree class. Feel free to add a wish-list item if you like athttps://bugs.launchpad.net/leo-editor/+bugs OK. FYI, whilst having a look at the code (can't yet get the above settings to work, but I'm just exploring at the moment) I found this typo: qtGui.py, line 5842: def traceFocuse (self,eventType,obj): should be def traceFocus(self,eventType,obj): HTH Jon N --~--~-~--~~~---~--~~ 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: Any more urgent or annoying bugs?
OK, got the @string thing to work. I was putting eg. @string selected-background-color = #fdf5f5 in the *body* rather than the headline. I'm not sure to what extent this is a 'Doh!', and to what extent this might be better spelled out somewhere. J^n --~--~-~--~~~---~--~~ 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: Any more urgent or annoying bugs?
On Jun 4, 12:16 pm, Ville M. Vainio vivai...@gmail.com wrote: Perhaps your pattern of working is suboptimal, This is quite possible... you if explicitly switch between tree and body modes. I always start moving around the tree by pressing alt + arrow, then either keep the alt key down or release it, depending how I feel like ;-). Then, I return to body pane by pressing enter. I do think some illustrations of workflow like this would be useful in the tutorial; to me there is a bit of a gap between the 'learning about outlines' stage, and the 'using Leo productively' stage. For instance, I wasn't sure if the 'return to body pane by pressing enter' was a design feature, or an accidental side-effect, or what (no doubt someone will point me to this part of the doce ;-/). I am very familiar with outlining, and very familiar to moving within and between windows and modes. I just haven't yet worked out the best way to do this in Leo (partly I also want to change the key bindings!). While we're vaguely on the subject - and I appreciate this is probably the wrong thread - how, when navigating the tree using the keyboard, can one go into 'edit node highlight' mode? Thanks Jon N --~--~-~--~~~---~--~~ 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: Any more urgent or annoying bugs?
On Jun 4, 2:41 pm, Ville M. Vainio vivai...@gmail.com wrote: The deal is that @ is not a reserved character in any way. At best, @ tells the user that leo, or a leo plugin, might have a special interpretation for this character. sure - but it should still be mentioned (as might your added explication above) in the docs J^n --~--~-~--~~~---~--~~ 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: Any more urgent or annoying bugs?
On Jun 4, 7:19 pm, Ville M. Vainio vivai...@gmail.com wrote: [...] There are only a few keyboard shortcuts that are really needed, so I think a document that only explains these is better. I'll those to the introductory docs. A chart of the commands in the 'using leo as an outliner' section of Chapter 2 (with default key bindings! - they could sensibly be added to that section), together with those in the 'editing body text' section of Chapter 3, and some of the one's we've discussed here, would be a very useful reference section, I think. I was going to volunteer to create one as well... It might also be useful to have the equivalent minibuffer commands where appropriate. J^n --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
minibuffer modes question
Chapter 18 of the docs describes two ways of entering minibuffer command mode: full-command, and quick-command-mode. The default key binding for *both* of these is ALT-x. Is this intentional? Alt-X gets me to full-command mode; how do I get to quick-command-mode? Thanks Jon N --~--~-~--~~~---~--~~ 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: Any more urgent or annoying bugs?
On Jun 4, 9:35 pm, Ville M. Vainio vivai...@gmail.com wrote: [...] I have already added the default bindings to that section. I have some stuff still not committed. OK. I don't really see a point in Chapter 3 Editing body text, it could be replaced by Body editing is like in most mainstream text editors. Yes, especially at this stage in the docs I think it would be best to keep the description of editing body text as light as possible. Perhaps descriptions of any 'surprises' here, and a reference to an appendix with the full list? I do think 'editing body text' should be almost the first thing in this section - well ahead of autocompletion, clones etc. BTW, is node drag 'n' rop supposed to work (in Qt)? It might also be useful to have the equivalent minibuffer commands where appropriate. I guess that's the advanced stuff for people who like to rebind the keys. Yes, I was thinking of maybe having the default keybindings listed in the tables in chapter 5, so that one could say ah, so the the 'insert- node' minibuffer command is equivalent to a CTRL-I. Cheers Jon N --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
AttributeError when trying to edit node headline
After Ville clued me in about the ctrl-H shortcut: - Press ALT-T to enter tree pane - Navigate to a node - Press Ctrl-H to edit the node headline Traceback (most recent call last): File /transfer/leo-editor/trunk/leo/core/leoCommands.py, line 385, in doCommand val = command(event) File /transfer/leo-editor/trunk/leo/core/leoCommands.py, line 3299, in editHeadline tree.editLabel(c.p) File /transfer/leo-editor/trunk/leo/plugins/baseNativeTree.py, line 850, in editLabel e = self.editLabelHelper(item,selectAll,selection) File /transfer/leo-editor/trunk/leo/plugins/qtGui.py, line 4423, in editLabelHelper self.connectEditorWidget(e,item) # Hook up the widget. File /transfer/leo-editor/trunk/leo/plugins/qtGui.py, line 4339, in connectEditorWidget wrapper = self.getWrapper(e,item) File /transfer/leo-editor/trunk/leo/plugins/qtGui.py, line 4474, in getWrapper wrapper = self.editWidgetsDict.get(e) AttributeError: leoQtTree instance has no attribute 'editWidgetsDict' (There's a typo in the docstring for getWrapper() BTW: 'healineWrapper' - 'headlineWrapper') Cheers Jon N --~--~-~--~~~---~--~~ 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: AttributeError when trying to edit node headline
On Jun 5, 6:10 pm, Edward K. Ream edream...@gmail.com wrote: On Fri, Jun 5, 2009 at 12:03 PM, jkn jkn...@nicorp.f9.co.uk wrote: File /transfer/leo-editor/trunk/leo/plugins/qtGui.py, line 4474, in getWrapper wrapper = self.editWidgetsDict.get(e) AttributeError: leoQtTree instance has no attribute 'editWidgetsDict' I can't duplicated this, and clearly, leoQtTree's *do* typically have editWidgetsDict ivars. You might trying pulling a fresh copy of the bzr repository. Hmm, I can't reproduce it with a recent sync either (I thought I was close enough to the tip not to need to have to do this) - apologies. It does seem odd though that the appearance is different if I edit a node highlight via the mouse (highlight under edit goes blue) and via Ctrl-H (highlight stays same colour). Also, I notice that via both methods, if I'm in 'edit highlight' mode and alt-tab to another application, and then back to Leo: - I am taken out of edit-highlight mode - the focus is now in the body pane! Both of these, and the latter for sure, seem odd behaviour to me. I hope all these recent observations are useful. For me, the basic editing functionality of any editing environment (such as Leo) I might think of using has to be both rock-solid and consistent if I'm going to stick with it. It doesn't have to be the same as other environments I use, just 'solid'. Regards Jon N --~--~-~--~~~---~--~~ 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: Tk vs Qt again
On Jun 10, 3:13 am, Ville M. Vainio vivai...@gmail.com wrote: Perhaps porting it all would be a bit too big for a starter project. You could start by providing the essence of what the plugin does (it is reasonably documented) by adding a rclick_qt.py. I don't think 100% compatibily is as important as the possibility of having a node specific context menu in the first place. OK, sounds good. I'll have a look - was meaning to ask about the status of rclick.py anyway... One thing I wanted to ask in the context of some of the recent discussions about documentation and workflow, is about the actual workflow of editing the .py files which make up Leo. The trunk contains (eg) rclick.py, which IIUC is a 'derived' file. In order to read this into Leo and navigate the outline structure etc. I have been using File | New, then File | Import | Import Derived File. This gives me an @thin node with the file present as subnodes etc. Presumably I should edit this and then ... export as a derived file in some way, to create a new rclick.py? I wasn't clear if this was the expected method, or whether there was, perhaps, a corresponding 'rclick.leo' which I should be generating or using. Thanks for answering these newbie questions. I do think the documentation suffers a bit from (as Edward puts it) the 'curse of knowledge', and I hope to chip in with some suggestions for improvement when I can. Cheers Jon N --~--~-~--~~~---~--~~ 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: Tk vs Qt again
Hi Ville On Jun 10, 9:07 am, Ville M. Vainio vivai...@gmail.com wrote: [...] You are doing it wrong. This is probably an example story that needs to be mentioned in the docs (unless it is already). File - Open - leo/plugins/leoPluginsRef.leo [...] Ah, excellent - so leoPluginsRef.leo is the 'parent' file for all the derived .py files etc. I hadn't seen this 'use case' (story ;-) in the docs. There's a definite gap between Chapter 2 and Chapter 4 I think. Info on this sort of workflow would IMO be a *big* help up on the learning curve. Thanks again jon N --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
small but annoying Qt observation when editing headlines
When a node headline is selected, the selection is in grey and looks fine. But when I *edit* a headline (selected text is dark blue), the height of this selection rectangle is too small by a pixel or two - it looks as if it's the 'inside' of the previous grey selection area. So you lose sight of the node headline you're changing, and descenders and underlines etc. in the node headline are not visible. Not the greatest problem in the world, but it would be nice if it were cleaned up ;-) Regards Jon N --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
curiosity seen in qtGui.py
def killGui(self,exitFlag=True): Destroy a gui and terminate Leo if exitFlag is True. def killPopupMenu(self): pass I would have thought that there is a missing 'pass' here, although having experimented, I find that: def dummy(): dummy statement is valid python, as is def dummy(): '''dummy docstring''' but not def dummy(): #dummy comment I thought they all needed a 'pass'. You live and learn. Still think a 'pass' would be nice though... Jon N --~--~-~--~~~---~--~~ 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: small but annoying Qt observation when editing headlines
Hi Ville It's on Gentoo Linux. The font was (I learn from qtconfig) Deja Vu Sans. I'll have a play with fonts etc. and report back. J^n --~--~-~--~~~---~--~~ 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: small but annoying Qt observation when editing headlines
looks like the settings are held as Qt stylesheet elements within
leoSettings.leo, eg:
/* Headline edit widgets */
QTreeWidget QLineEdit {
background-color: cornsilk;
selection-color: white;
selection-background-color: blue;
font-family: DejaVu Sans Mono;
font-size: 12px;
font-weight: normal; /* normal,bold,100,..,900 */
font-style: normal; /* normal, italic,oblique */
}
More likely cause is Ubuntu putting extra care for stuff like this
(fonts). You may be able to fiddle with them in your kde system
settings...
I'm running kde 4.2 (spit...) which doesn't seem to allow much font
configuration via menus etc. I'll have a look around for other ways to
do things. I don't think Ubuntu does things much differently to Gentoo
though.
J^n
--~--~-~--~~~---~--~~
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: small but annoying Qt observation when editing headlines
Also, I'm running PyQt version 4.4.4-r2, when the latest seems to be 4.5. Might this be the problem? (looks like fun trying to upgrade on this system...) Thanks Jon --~--~-~--~~~---~--~~ 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: small but annoying Qt observation when editing headlines
Hi Terry On Jun 10, 10:28 pm, Terry Brown terry_n_br...@yahoo.com wrote: On Wed, 10 Jun 2009 14:06:06 -0700 (PDT) jkn jkn...@nicorp.f9.co.uk wrote: Also, I'm running PyQt version 4.4.4-r2, when the latest seems to be 4.5. Might this be the problem? (looks like fun trying to upgrade on this system...) My experience with that sort of upgrade is that I wouldn't try it. Particularly seeing it might not fix the problem, and the problem's not that bad. Sure - I just mentioned in case it drew noises of sucking teeth, and 'that explains it...' in general. Cheers Jon N --~--~-~--~~~---~--~~ 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: Node dclick overload
On Jun 11, 5:42 pm, Kent Tenney kten...@gmail.com wrote: On Thu, Jun 11, 2009 at 10:49 AM, Ville M. Vainiovivai...@gmail.com wrote: On Thu, Jun 11, 2009 at 6:47 PM, Kent Tenneykten...@gmail.com wrote: If possible, I'd rather people use commands (and corresponding keystrokes). There are a *lot* more possible command names than click types :-) What is the status of easily configured right click menus? Not done yet for qt. jkn started investigating the port just recently. Great! Since I seem unable to stay abreast of the feature flood, I think I would benefit from the following workflow; - spot an interesting sounding capability introduced on the mailing list - enable it - add it to the rclick menu - evaluate at my convenience - ditch it if it's not useful - if it's useful, either leave on menu or commit to command and memory Thanks, Kent very early days for my investigation learning curve, but thanks for the list Kent ;-) Cheers Jon N --~--~-~--~~~---~--~~ 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: How likely are sha-1 collisions?
http://bitcache.org/faq/hash-collision-probabilities I read an example comment years ago when UUIDs came in, the gist of which was (don't quote me), if you created one UUID every millisecond for a million years, the probability of you seeing a collision was (some small number ;-/). If I can find the quote I'll post it. Of course, one day it *will* happen... J^n --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
cruft in rclick.py and base leo code?
As mentioned previously, I'm trying to get to grips with the innards of Leo by having a look at porting rclick.py to qt. I'm mostly reading at the moment - both the leo code, and about pyQt in general. But I would like to check one thing. It look like there is a fair bit of cruft in the places I am looking. for instance, in qtGui.py, def OnBodyRclick(self, event = None): appears not to be connected to anything. The current (non)-action of rclick.py in the Qt framework connects to this; I guess I'm learning that there is less working in this area that I imagined. I'm really just looking for confirmation that I am likely to find 'orphaned' or no-longer-relevant bits of code in both the base leo code and in the plugin code, presumably from earlier or Tk days. I don't want to get led down too may stray paths whilst getting to grips with things. thanks jon N --~--~-~--~~~---~--~~ 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: cruft in rclick.py and base leo code?
Hi Ville If I were you, I'd implement something simple from scratch - I don't think there is much working in the rclick area right now. [...] Thanks, that's another form of the sort of advice I was after ;-) I will probably adopt a simultaneous 'bottom-up' and 'top-down' approach - start with something simple to get the understanding, whilst keeping an eye on the original design for compatability in the future... Cheers Jon N --~--~-~--~~~---~--~~ 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: cruft in rclick.py and base leo code?
I realise that this will show that i'm trying to run before I can walk, but never mind... I have, in .../trunk/leo/config/leoSettings.leo, and @enabled-plugins node: # Leo loads plugins in the order they appear here. # File names may be indented as desired. #Standard plugins enabled in official distributions. # This plugin creates the Plugins menu. plugins_menu.py # [...] rclick_qt.py # ie. the rclick file I'm experimenting with. Leo tells me in the log pane that it loads this leoSettings.leo when it start up. But, it does not display *any* plugin buttons or any pluging menu. Only when I explicitly open .../leo/config/ leoSettings.leo do these appear. I thought the reading of the @enabled-plugins node in this config file would enable plugins at startup. What am I missing here? Thanks jon N --~--~-~--~~~---~--~~ 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: cruft in rclick.py and base leo code?
On Jun 16, 8:24 pm, Ville M. Vainio vivai...@gmail.com wrote: On Tue, Jun 16, 2009 at 9:59 PM, jknjkn...@nicorp.f9.co.uk wrote: I thought the reading of the @enabled-plugins node in this config file would enable plugins at startup. What am I missing here? Ah, the @enabled-plugins, bane of everyone at some point... glad to hear I'm not alone... Have you checked if you have @enabled-plugins in myLeoSettings.leo (help-open myleosettings)? Yes, I do - I tried it here first, IIRC (I hadn't seen the 'Help - ...' access, thanks). This didn't seem to work so I added it to .../ leo/config/leoSettings.leo, along with all the others From my reading of the docs these entries should be read in turn, so presumably the noted plugins concatenated? Is your @enabled-plugins within a @settings tree? Yes, in both files. Thanks J^n --~--~-~--~~~---~--~~ 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: cruft in rclick.py and base leo code?
never mind, I've got the plugin loading bit working at least. Not quite sure what fixed it - a combination of things I suspect. J --~--~-~--~~~---~--~~ 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: pdf version of the docs generated
Great stuff Ville, thanks. On Jun 21, 2:05 am, Edward K. Ream edream...@gmail.com wrote: At this point, I think the pdf generation process is more of a curiosity, but perhaps that's just a sign of my ignorance. If anyone wants to explore this process in detail, feel free to do so: it would be great to have a first-rate pdf version of Leo's documentation. I might look into this- I used to know TeX/LaTex pretty well, and although that isn't probably too relevant I still enjoy playing in this area... J --~--~-~--~~~---~--~~ 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: A first draft of the rST chapter intro
Hi Ville It seems RST is suggested instead: [...] Hmm, interesting, thanks. I guess using 'RST' also helps what with the nodes also being called @rst etc. I think I will still use ReST for my own purposes though... Cheers Jon N --~--~-~--~~~---~--~~ 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: cruft in rclick.py and base leo code?
Hi Ville On Jun 21, 9:00 pm, Ville M. Vainio vivai...@gmail.com wrote: On Mon, Jun 15, 2009 at 3:21 PM, jknjkn...@nicorp.f9.co.uk wrote: As mentioned previously, I'm trying to get to grips with the innards of Leo by having a look at porting rclick.py to qt. I'm mostly reading Was thinking of this briefly, here's an idea how this could be implemented the easiest (and most flexible) possible way: - Do not try to write any wrappers (they will only confine what can be done) - Follow the pattern of visit_tree_item, that is: - When you right click somewhere (or do show-popup-menu), instantiate the popup menu (QMenu) and pass it as arg to a chain of functions. Also pass the clicked widget (so you can right click tree item, body, ...) - The functions well add their own actions to the many^H^H^H^H Menu any way they wish. Thanks - that's not dissimilar to what I've been playing with - though it's early days at the moment. I have a learning curve of Leo/Qt/ plugins to go through, and In theory this is done in my spare time... but I'm getting there... Regards Jon N --~--~-~--~~~---~--~~ 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: rclick functionality for core on trunk
Hi Ville [...] BTW jkn, I realize you were working on this too - do you have something that could be synced with this approach (e.g. wrapping rclick.py stuff so existing Tk plugins would work)? Thanks for the thought. At the moment I'm still playing rith rClick_qt.py, and not for many minutes each day I'm afraid. This looks like a great first approach, and I'll certainly bear it in mind when I get a bit further on. In the meantime, sweet indeed. Cheers jon N --~--~-~--~~~---~--~~ 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: Leo 4.6 is feature frozen. Please limit commits to the trunk
On Jul 2, 8:07 pm, Ville M. Vainio vivai...@gmail.com wrote: I took the liberty to commit setLeoWindowIcon that sets the icon for window title and task bar. This is somewhat important for branding and not appearing sloppy to the end user. Good idea IMO - I've been meaning to mention this as a simple improvement that reaps rewards in terms of professionalism. J^n --~--~-~--~~~---~--~~ 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: Updated pdf docs available
On Jul 3, 3:41 pm, Ville M. Vainio vivai...@gmail.com wrote: BTW2: if someone is looking for a little project, he could work on replacing all the gif files in bzr with png files. I've just run a little script using gif2png to do this. What's the best way to pass on the results? I can point [you] at a .tgz file if you like. j^n --~--~-~--~~~---~--~~ 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: Updated pdf docs available
On Jul 3, 7:27 pm, Ville M. Vainio vivai...@gmail.com wrote: On Fri, Jul 3, 2009 at 9:21 PM, jknjkn...@nicorp.f9.co.uk wrote: I've just run a little script using gif2png to do this. What's the best way to pass on the results? I can point [you] at a .tgz file if you like. I figure you'll need to mess with the source files as well and remove references to the old files everywhere. Try using bzr bundle to provide the patch. Oh, that makes sense - it seemed rather a small project as-is ;-). OK, leave it with me. J --~--~-~--~~~---~--~~ 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: Thoughts on Leo coding style
On Jul 15, 7:45 pm, Ville M. Vainio vivai...@gmail.com wrote: On Mon, May 18, 2009 at 4:17 AM, Jesse Aldridgejessealdri...@gmail.com wrote: [...] One quick personal aha about section references: I only recently figured I should use ctrl+shift+s (extract-section) more. It's pretty fun. For those that don't know it, selecting the following text: section here a=1 b=2 creates a new section and moves the code there. Now, the aha is - sections should be for code that is *not important for the reader*, but in the meantime is not reusable enough to warrant creating a function. That is, a section means you can skip this part to the reader of the code. The important stuff is close to the root of tree, boring (or cryptic) stuff is in sections. An example: def add_for_polling(self, srcfname): if not self.pollset: set up timer for timer_poll self.polldict[srcfname] = 0 [...] This is where I came into Leo - 'Sections' here are like 'folds' in a folding editor (eg. Origami, in the Transputer Development System). I was looking for Folding Editors when I came across Leo. I think it is worth emphasising this feature in the docs (and the extract-section keybinding - I didn't know about that) for newcomers to Leo who may also have seen this elsewhere. J^n --~--~-~--~~~---~--~~ 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: ~/.leo/plugins
On Jul 16, 7:51 pm, Ville M. Vainio vivai...@gmail.com wrote: [...] However, this sort of sucks for the end user. Perhaps we should introduce ~/.leo/plugins directory, where users could install third party plugins? definitely agree J^n --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
News: Canonical releases source code for Launchpad
perhaps of interest to some: http://www.ubuntu.com/news/canonical-open-sources-launchpad J^n --~--~-~--~~~---~--~~ 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: error while trying to save file
To me, his description: I have leo file on the disk. Open that file. Rename the file on the disk. Try to save opened file- error happened. *possibly* sounds like he's renaming the file behind Leo's back, ie. via Explorer rename, or mv, or something. Of course in these circumstances I'd expect him to get an error that this is not allowed - 'file in use' or similar. So I may be wrong. This is of course something that is very different from renaming a file via 'save as', and if your OS allows it, is likely to give much trouble... J^n --~--~-~--~~~---~--~~ 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: Anyone tried KeyNote?
On Sep 21, 11:17 am, Dave da...@conscious.co.nz wrote: After looking around, I came across an exquisite piece of abandonware called KeyNote - open-source (delphi). Awesome for structured rich- text editing, super fast, perfect for the job, but definitely not a programmer's editor. Anyone who's interested can get it fromhttp://www.tranglos.com/free/ I came the other way - have used KeyNote for many years as an outline capturing program. It's a really nice program for what it does. However (a) as you say it's abandonware, (b) only runs under Windows really - I do run it under Linux using Wine but it's a bit problematical, and (c) lacks all the ways of manipulating the underlying data that make Leo ... Leo. I still use KeyNote for some small legacy sets of information, but hope to move those to Leo at some point in the near future. Keynote being abandonware (a pity- the author 'burned out' on it), I wouldn't advocate anyone to move to it. I do think the keybindings for node creation and navigation are superior to Leo's defaults. One day I mean to change them for myself. J^n --~--~-~--~~~---~--~~ 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: Anyone tried KeyNote?
On Sep 21, 9:48 pm, Ville M. Vainio vivai...@gmail.com wrote: On Mon, Sep 21, 2009 at 7:12 PM, Ville M. Vainio vivai...@gmail.com wrote: Please elaborate, I'm all ears. Urgh, now that I re-read that, I realized it looks like I'm being sarcastic. That's definitely not the intention. I'm just thinking that we want the best possible tree manipulation in Leo :-). I didn't take it as being sarcastic... It's partly what you're used to, of course. But I took to the Tree keybindings in KeyNote immediately. Here are the ones I like most. When in the tree pane: EnterAdd new node Space Rename Selected Node # I could do without this Shift-Enter add new node as child of current node Ctrl-Enteradd new node immediately after current node Insert insert new node before current Delete Delete Selected node (optionally, delete all children too) Shift-Del Delete all Children of the selected node Shift-Insert Rename Node by pasting text from clipboard Shift-Down move selected node down Shift-upmove selected node up Shift-left move selected node left (promotion) Shift-rightmove selected node right (demotion) 'Grey' + expand all nodes in tree 'Grey' - collaps all nodes in tree J^n --~--~-~--~~~---~--~~ 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: Don't be such a (computer) scientist
On Nov 4, 9:48 am, Edward K. Ream edream...@gmail.com wrote: Here is another draft. [...] In terms of arousal - which I agree is a good way of approaching it, and one unfamiliar, nay scary, to many of a technical bent - it's good to remember to *make it personal*. Use the *You* word... [suggestion] Leo aims to be your ultimate power tool, allowing you to manage a wide variety of complex data forms. Computer programs, books and databases are all examples of domains where Leo can make your life easier. Leo started life as a way to help users understand complex computer programs. It has grown from there to become what we call a 'data management environment'. One way of thinking about this is that it blends the best features of relational, hierarchical and object oriented databases. ... [/suggestion] J^n --~--~-~--~~~---~--~~ 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: Don't be such a (computer) scientist
On Nov 5, 1:25 am, Edward K. Ream edream...@gmail.com wrote: That may be part of it. The best example of friendly writing about Leo is my brother's intro: http://webpages.charter.net/edreamleo/SpeedReam.html To me, this is chatty, warm and somehow friendly, though I can't put my finger on exactly why. To write this way more often would be a big step forward for me. It reads almost as though Speed is talking to a friend, over a coffee, or something. So do the same Imagine talking about Leo to a non-technical friend - they're interested, but don't want or need to know much about what goes on under the hood. What would you say? What questions would they ask? How ywouldyou get them *excited*? You might try actually sitting down and doing this - actually talk to someone instead of typing. Record yourself, with a little MP3 recorder or something. I know I have to force myself not to revert to tech- style when I'm at a keyboard. Your unedited speaking sentences may well be better than your typed ones for this purpose. It's a bit of a cringe getting over how your voice sounds at first, but that soon goes. Listen back and transcribe the bits that you like. It's a useful thing to do in many ways. J^n --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
OTish: problems signing up to Google Wave
Hi all After getting my invitation to Google Wave via Matt (Thanks Matt!) I am having problems activating the invitation, and I wondered if anyone else has seen this. I already have a Google account (seems to be a different thing that a Google Apps account); but when I try to use the invitation link with that account I get stuck in a maze of twisty little web pages, all alike, saying something like 'an account with that email address already exists'. This doesn't make sense - do I have to create a whole new Google Account just for wave, or what? Thanks for any pointers. J^n --~--~-~--~~~---~--~~ 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: OTish: problems signing up to Google Wave
Hi Ville Log in with your gmail account [...] I don't have a gmail account - at least, not one I use. I have an old gmail account that is unconnected to the email address the invitation was sent to. I presume (I hardly ever used my gmail account, can't remember) that in some way my gmail account username (xxx@googlemail.com) is linked to the 'real' email address that google is complaining about. Would this cause problems similar to what I am seeing? I did think of trying deleting my google mail account, but wanted to check further ... and click on the invitation. That should work. you mean 'click on the invitation URL, having logged into gmail'? or 'having logged into gmail, you should see an invitation link'? It can't be the latter in my case, since as I mention the accounts are I believe) unconnected. And it was the former I was trying, except with my 'straight' Google Account. Thanks J^n --~--~-~--~~~---~--~~ 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: Don't be such a (computer) scientist
Hi Edward [..] There are two, and *only* two key elements of Leo: 1. Leo is a new way of seeing data, including programs. 2. Leo is a new way of applying scripts to data. FWIW I think this a better kind of 'elevator script' than the 'vision and power' stuff. J^n --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Comments on beginner's guide...
As the subject says, I'm taking a bit of time to walk through Leo's documentation pages, from the perspective of a naive user who also knows enough to be dangerous... A couple of things so far: 1) Does the print() command still work, or are you supposed to use g.es() exclusively? Chapter 2 of the tutorial, and also parts of Chapter 7, reference the use of print(), but it doesn't seem to work for me. I recall on this mailing list when g.es() was recommended, but haven't seen anything about print() being deprecated. 2) I have comments about the content and maybe wording of parts of Chapter 2. What would be the best approach to suggest improvements? Thanks J^n -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-edi...@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: Comments on beginner's guide...
Hi Edward print() sends its output to the console, so to see the output you must run Leo from a console. Oops - I meant to check that before posting ... however my defence is that my (forethought) comment is that the beginner's guide needs to make the distinction clear ;-o. 2) I have comments about the content and maybe wording of parts of Chapter 2. What would be the best approach to suggest improvements? Comments here are fine. OK, I'll make a sub-editor-comments posting... Cheers Jon N Edward -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-edi...@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: Does anyone know of a pep8 *fixer* ?
I don't know of one, I'm afraid. I think it's a lit easier to just check warn than to fix; false positives (or is that negatives?) are also a lot less dangerous in a checker only. Personally, there are enough things I don't like about PEP-8 that I've never felt the need to adopt it. There is IMO no problem with having a 'house style' if you prefer. Of course making everything adhere to such a style might still involve a checker/fixer program... J^n -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-edi...@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: The step-by-step tutorial is here
On Oct 20, 1:16 am, Terry Brown terry_n_br...@yahoo.com wrote: Some monitors might make it quite hard to see those colors, they're almost subliminal. You could throw the word pale in, perhaps. I definitely agree - unless/until you know about the colours, they are invisible. I'd go as far as to say 'very pale pink' and 'very pale blue'. On LCD monitors it also depends on the angle you are at to the screen. (my colour vision is good ;-). A few typos I noticed: slide 5: could do with the same arrow as slide7 slide 6: 'Alt-T puts foucs' - focus slide 7: 'one again' - 'once again' if a node is no longer 'dirty', what is it - clean? slide 13: 'ctrl-z' (lower-case), but elsewhere 'ctrl-H' (upper-case). Stick with upper case for consistency? J^n -- You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-edi...@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: LEO as web app
On Feb 22, 11:09 pm, Stefan Fruehwirth stefan.fruehwi...@uni-graz.at wrote: +1, that would definitely be very useful. But the effort seems to me to be huge. As far as I can see the only way that this would lead to an acceptable tool is to port _everything_ to JavaScript. [...] FWIW, there is an interesting-looking project 'pyjamas' which purports to contain a Python to JavaScript converter, together with a port of the Google Web Toolkit widget set. Together they are supposed to building apps which run both inside a browser and 'on the desktop' (which I think means 'as a normal app - without a browser- ;-). http://code.google.com/p/pyjamas/ HTH J^n -- 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: Open source alternatives for Microsoft OneNote
FWIW I am (still) an Ecco Pro user. I mostly run it under Linux using Wine, which works pretty well. There is still a pretty vibrant community for Ecco Pro, eg. via the 'ecco_pro' yahoo group (different to the 'eccopro' group!). There have been some very impressive add-ons and patches written for Ecco, allowing eg. scripting via Lua. The main problem with Ecco is perceived to be ever-more limited sync support with modern devices. In many ways I would love to move from Ecco Pro to Leo. The ability to use the Python scripting would be great. However I've never found how to be able to use Leo to match Ecco's column/folder paradigm. And Ecco's sheer speed is great. I'd be interested to know more about how, as an ex-Ecco user, you set up your Leo files, and your workflow in general. Cheers jon N On Aug 17, 11:11 pm, Largo84 larg...@gmail.com wrote: As a long-time ECCO-Pro user and now refuge, the biggest things I miss from ECCO-Pro moving to Leo is the integrated Calendar and Contacts. Of course, i can't (or won't) go back now as ECCO-Pro has been dead for over a decade. I do almost everything now in Leo but would love to be able to integrate those two pieces again. (I can't ditch Outlook entirely, though I'd like to, but the less I need it, the better.) My 2 cents. Rob.. On Aug 16, 4:40 pm, Offray Vladimir Luna Cárdenas off...@riseup.net wrote: -- 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: EKR: Gnu indent follies
Hi Edward I don't know what research you have done beforehand but FYI there are a fair few alternatives to GNU indent for beautifying C code. See for instance this StackOverflow thread: http://stackoverflow.com/questions/841075/best-c-code-formatter-beautifier Artistic Style has the --add-brackets option - I dunno how robust it is. I'm about to look into this myself ... Regards Jon N -- 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: Oh, the irony
FYI re ROOT: http://www.theregister.co.uk/2011/09/22/cern_coverity/ Jon N -- 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: Python-based text preprocessing (not only static HTML)
Hi Hans On Feb 5, 7:33 pm, HansBKK hans...@gmail.com wrote: Thanks Terry, but it looks to me like all of these are dynamic, running via server-side add-ons. I'm looking to locally generate static HTML+CSS - maybe some javascript for stuff like analytics but that's all - that can be uploaded to a plain-vanilla Apache host. I realize that you (sing + most of you plural) wouldn't do things this way, but just in case these details jogs anyone else's memory. -- 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: Python-based text preprocessing (not only static HTML)
Hi Hans I have previously used Cheetah: http://www.cheetahtemplate.org/ (and, later,) Jinja: http://jinja.pocoo.org/ to create static HTML websites. I also used CleverCSS as a way of writing 'structured' CSS which is preprocessed into 'the real thing': http://sandbox.pocoo.org/clevercss/ https://github.com/clevercss/clevercss All are python based ;-) HTH Jon N -- 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.
ability to specify Numeric Keypad keys in keybindings?
Hi all (I tried to send this a few days ago and thought it got through, but I haven't seen the posting since. Apologies if this is a double post. I'm using Google Groups; I presume there is no alternative for this group?) I would like to play around with my own keybindings for some parts of Leo. I would also like to use the Numeric keypad keys for some specific features. Is it possible to specify such keys, for instance Numeric-minus # could be for contracting a node Numeric-Insert# could be for creating a node etc.? I would want these to be distinct from the normal Key-minus, Key-Insert kinda keys. Apologies if this is a Qt, rather than a python, issue. Thanks a lot Jon N -- 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/groups/opt_out.
can I specify key bindings using the Numeric keypad keys?
(apologies in advance: I have only done minor searching before asking. This may be a Qt, rqather than a Leo, question... ) I am starting to look into creating my own set of Key bindings for Leo. Is there a way to specify that, on a 'standard' PC keyboard, a particular key on the numeric keypad has been pressed? For instance, I want to use 'Keypad-Insert', 'Keypad-minus', 'Keypad-plus' to have specific keybindings cf. 'Insert', 'minus', 'plus'. I'd like to know if this is possible and if so what the actual names to use would be. Thanks a lot Jon N -- 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/groups/opt_out.
Re: can I specify key bindings using the Numeric keypad keys?
Hi Edward Thanks for the reply. I've raised a wishlist bug (hope I've done that right) I'll take a look at the code area you mention myself as I'm interested in learning more about the action... Regards Jon N On Thursday, 1 August 2013 16:04:48 UTC+1, Edward K. Ream wrote: On Mon, Jul 29, 2013 at 8:05 AM, jkn jkn...@nicorp.f9.co.uk javascript: wrote: (apologies in advance: I have only done minor searching before asking. This may be a Qt, rqather than a Leo, question... ) It's both. I am starting to look into creating my own set of Key bindings for Leo. Is there a way to specify that, on a 'standard' PC keyboard, a particular key on the numeric keypad has been pressed? Not yet. It should be possible, but it won't be easy because it two very messy parts of Leo: 1. Translation of key codes to canonical key representation. This is done in the eventFilter method of the leoQtEventFilter class. This code is not only unbearably ugly, but it may also be keyboard specific. 2. Translation of user settings to canonical key representation. This is done in the keyHandlerClass class in leoKeys.py, specifically the nest of methods at: leoPy.leo#Code--Gui base classes--@file leoKeys.py-- class keyHandlerClass--k.Shortcuts bindings For instance, I want to use 'Keypad-Insert', 'Keypad-minus', 'Keypad-plus' to have specific keybindings cf. 'Insert', 'minus', 'plus'. I'd like to know if this is possible and if so what the actual names to use would be. This would be a reasonable addition to Leo. Feel free to file a wishlist bug at: https://bugs.launchpad.net/leo-editor A quick check of the Qt QKeyEvent class shows that key events have a KeypadModifier bit in the KeyboardModifier field, so it should be possible to distinguish keypad keys. It's just that Leo doesn't do it. And as indicated above, the change is not entirely trivial ;-) 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/groups/opt_out.
feature request - insert headline before current
Hi Edward (Background - I am experimenting with changing my Leo Key bindings to make it work more closely to other (lesser ;-) outliners I am more used to than Leo) One thing that I think is missing from Leo is a primitive command 'insert headline before current'. I would like to bind 'Insert' to this rather than ''insert-node', which of course inserts after the current headline. I've taken a quick look at def insertHeadline() in key-handling-notes.txt but I'm not initially confident of making the necessary additions. Would it be appropriate to raise a wishlist item for this? Thanks. Also, whilst I'm looking at the source - can you explain to me where/how 'key-handling-notes.txt is 'included' as part of Leo? I can't work this out from an initial skim... Thanks a lot Jon N -- 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/groups/opt_out.
Re: feature request - insert headline before current
Hi Fidel Jacob Thanks both - that's very useful and just the sort of experimenting that will be good for me to have a go at ;-) Regards Jon N -- 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/groups/opt_out.
Re: feature request - insert headline before current
On Monday, 23 September 2013 14:19:05 UTC+1, Edward K. Ream wrote: [...] A good start, but the script does not handle undo properly. I'll attempt an improvement. Edward Heh - it was in part understanding the the undo functionality that put me off trying to 'replicate' insertHeadline(), at first anyway. Improvements very gratefully received, I'm hoping I can learn from this discussion, thanks. Jon N -- 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/groups/opt_out.
Re: feature request - insert headline before current
Hi Edward On Monday, 23 September 2013 15:45:49 UTC+1, Edward K. Ream wrote: On Mon, Sep 23, 2013 at 8:19 AM, Edward K. Ream edre...@gmail.comjavascript: wrote: A good start, but the script does not handle undo properly. I'll attempt an improvement. Rev 6030 adds the new insert-node-before command. many thanks, I'll be trying it out tonight, I hope. One thing, you might want to correct the docstring ;-o 4282 #@+node:ekr.20130922133218.11540: *7* c.insertHeadlineBefore (new in Leo 4.11) 4283 def insertHeadlineBefore (self,event=None): 4284 4285 '''Insert a node after the presently selected node.''' Regards jon N -- 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/groups/opt_out.
Re: feature request - insert headline before current
Hi Edward On Monday, 23 September 2013 19:18:26 UTC+1, Edward K. Ream wrote: On Mon, Sep 23, 2013 at 11:18 AM, jkn jkn...@nicorp.f9.co.ukjavascript: wrote: you might want to correct the docstring ;-o Fixed at rev 6032. EKR Looking good, thanks very much! And I can now see eg. def insertHeadline(...) in LeoCommands.py ... not sure why my search-fu wasn't working earlier. I do have a supplementary question ... It looks like you can use 'context' when defining keybindings, for instance a keybinding can be listed as tree: Next = scroll-down-page text: Next = scroll-down-page but I'm not 100% convinced that this is the syntax I should be using in my @settings|@keys|@shortcuts nodes- can you confirm? Thanks muchly Jon N -- 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/groups/opt_out.
Re: ellipsis on Command menu items?
On Friday, 13 September 2013 14:18:37 UTC+1, Terry wrote: On Fri, 13 Sep 2013 03:41:06 -0700 (PDT) rholland rod.h@gmail.com javascript: wrote: 1) no ellipsis for flyouts - the triangle provides the indication 2) use an ellipsis if the primary menu brings up a dialog box (or something that require further user input). +1, they're redundant where the only indicate sub-menus, as the triangles do that. I think of ellipsis as a promise not to act immediately without further input - e.g. I often use the Print... menu rather than a print button because I want to know for sure the software's going to ask for settings etc. and not just Print immediately. Cheers -Terry I agree with this, and surely this means that (on the main 'file' menu, there should be ellipses on: Save As ... Save as Unzipped... Save To ... Import File ... J^n -- 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/groups/opt_out.
Re: feature request - insert headline before current
Hi Edward Ah - I think you didn't quite get what I was asking. I've got it now, so have written it below for reference and clarity: A pane-specific keybinding is *created* with entries in @settings-@keys-@shortcuts like: scroll-down-page ! tree = Next but it is *reported* (eg. if I press Tab in the minibuffer) in the form tree: Next = scroll-down-page I originally tried to use the latter form in my @shortcuts node. My changed settings were reported in that form, leading me to think it the setting had been applied, but didn't seem to actually work. When I changed it to the first form, all was fine. (But what is the 'Next' key?! I chose that just as an example, and only later I realised that I don't know what key refers to...) Thanks Regards Jon N -- 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/groups/opt_out.
Re: feature request - insert headline before current
On Wednesday, 25 September 2013 22:17:26 UTC+1, jkn wrote: Hi Edward Ah - I think you didn't quite get what I was asking. I've got it now, so have written it below for reference and clarity: A pane-specific keybinding is *created* with entries in @settings-@keys-@shortcuts like: scroll-down-page ! tree = Next but it is *reported* (eg. if I press Tab in the minibuffer) in the form tree: Next = scroll-down-page I originally tried to use the latter form in my @shortcuts node. My changed settings were reported in that form, leading me to think it the setting had been applied, but didn't seem to actually work. When I changed it to the first form, all was fine. (But what is the 'Next' key?! I chose that just as an example, and only later I realised that I don't know what key refers to...) Thanks Regards Jon N -- 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/groups/opt_out.
Re: feature request - insert headline before current
(oops, apologies for double-posting ... Google Groups grr...)
Spurred on by my triumph I have experimented with adding a new primitive of
my own! This allows me to have a key combination to expend or contract a
node
depending on its current state.
Apologies if there's already a way of doing this ... I submit the following
for possible inclusion into Leo:
{{{ in leoCommands.py
def toggleExpandState (self,event=None):
Toggle the expand state of the current node
trace = False and not g.unitTesting
c = self; p = c.p
# set up the functions to call
if p.isExpanded():
fa = p.contract
frd = c.redraw_after_contract
else:
fa = p.expand
frd = c.redraw_after_expand
# perform the calls
fa()
if p.isCloned():
if trace: g.trace('***redraw')
c.redraw()
else:
frd(p,setFocus=True)
}}}
and the obvious entry in leoEditCommands.py:
{{{
'toggle-expand-state': c.toggleExpandState,
}}}
I bind this to Ctrl-E (Expand) and Ctrl-H (Hide) FWIW.
Cheers
Jon N
--
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/groups/opt_out.
Re: feature request - insert headline before current
Hi Edward On Thursday, 26 September 2013 01:37:02 UTC+1, Edward K. Ream wrote: On Wed, Sep 25, 2013 at 5:00 PM, jkn jkn...@nicorp.f9.co.uk javascript: wrote: Spurred on by my triumph I have experimented with adding a new primitive of my own! Welcome to the world of Leo scripts. Yes indeed ;-). I've now worked out how to create a script and bind it to a key. Took me a while to realise that the @commands-@command part actually had to be @settings-@commands-@command but I think I'm there now. I've also added a couple of config settings: @string insert-headline-time-format-string= ... etc. into my myLeoSettings.leo. BTW there are a few references in the code to LeoConfig.txt, which i think no longer exists? Playing around with these sort of things is getting some good practice in using Leo, as well as thinking about its capabilities... Cheers Jon -- 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/groups/opt_out.
some novice scripting event handler questions
Hello there:
1) I'm starting to play with event handlers in scripts. I see that as well
as registerHandler() (documented) there is also unregisterHandler()
(seemingly undocumented).
unregisterHandler() seems to require a/the handler function to be in the
same node as the call, which seems a bit weird; if I have node:
# node 1
def myHandler(tag, keywords):
g.es(OnBodyClick called)
g.es( Tag:, tag)
g.es( keywords:, keywords)
g.registerHandler((bodyclick1, command1), myHandler)
g.es(handler registered)
Then do I need to have this for node 2:
# node 2
def myHandler(tag, keywords):
pass
g.unregisterHandler((bodyclick1, command1), myHandler)
g.es(handler de-registered)
?
(I may be misunderstanding something about the 'scope' of scripts
within/between nodes ...)
2) I want to intercept a key (eg, the Home key on the keyboard) to
potentially alter its effect. An event handler for 'bodykey1' only seems to
act on
'normal' characters, and not 'special' keys like Home etc. But using
'bodyclick1' seems to cause the event handler to receive the interpreted
command string
('back-to-home'), rather than the Home key itself. Is there a way I can get
the event with the key itself, before interpretation?
Thanks a lot
jon N
--
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/groups/opt_out.
Re: some novice scripting event handler questions
Hi Terry [...] I think it's the scope issue, you need to pass the handler back in to g.unregisterHandler. So if the unregister call is in a separate node, called separately, you probably need: Node 1 def foo(): blah() g._foo = foo g.registerHandler((bodyclick1, command1), foo) Node 2 g.unregisterHandler((bodyclick1, command1), g._foo) Ah, I see, thanks. That happens to also answer a question I had about creating accessing new global variables ;-) Cheers Jon N -- 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/groups/opt_out.
