Re: vnodes, tnodes, and unknownAttributes
On Tue, Feb 26, 2008 at 2:14 AM, Terry Brownterry_n_br...@yahoo.com wrote: What I struggle with is that some attributes should be universal for the (t)node in any context, and others only make sense in some contexts. For example you might color code the backgrounds of cloned nodes in an active task list to indicate urgency. But when you're looking at the node in it's primary location you don't want to be distracted with why is that one node pink? type noise. (*bump*) I am replying to this old thread because it's important. As it appears, most of the advantages of vnode uAs (and vnodes in general) seem to be misunderstandigs (i.e. assumption that vnode is somehow like position, i.e. tree position specific). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Copy/paste bug in Qt GUI?
I'm experiencing some strange behaviour when using Qt GUI (current trunk, r2050). I had an outline open today, tried Copy node, then Paste node from Outline main menu and it didn't work. I have tried the commands copy- node and paste-node instead, they didn't work as well. I have tried one more time, to get some clear steps for reproducing the behaviour, and this is what I've got: Run leo with Qt GUI. It loads the default workbook.leo. Copy/paste works! Open an existing outline from Recent Files menu. Copy/paste doesn't work anymore. I didn't fill (yet!) a bug report at launchpad. I'm a bit skeptical, because it doesn't always go wrong. If at least one more person will be able to reproduce this, then it will go to the bug tracker. --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 1:10 PM, zpcspmzpc...@gmail.com wrote: I didn't fill (yet!) a bug report at launchpad. I'm a bit skeptical, because it doesn't always go wrong. If at least one more person will be able to reproduce this, then it will go to the bug tracker. Is that about unicode chars in body? Can you isolate the prob to particular subtree? -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
On Jun 17, 1:58 pm, Ville M. Vainio vivai...@gmail.com wrote: On Wed, Jun 17, 2009 at 1:10 PM, zpcspmzpc...@gmail.com wrote: I didn't fill (yet!) a bug report at launchpad. I'm a bit skeptical, because it doesn't always go wrong. If at least one more person will be able to reproduce this, then it will go to the bug tracker. Is that about unicode chars in body? Can you isolate the prob to particular subtree? Good hint, thank you. Indeed I had a line of unicode chars in that subtree. Removing it fixed the issue. I'm still unhappy about how leo behaves in this situation. I can use the Tk GUI fine till this will be fixed, but maybe you guys can stick a debug message to be printed to the console in this situation? --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 2:10 PM, zpcspmzpc...@gmail.com wrote: Good hint, thank you. Indeed I had a line of unicode chars in that subtree. Removing it fixed the issue. I'm still unhappy about how leo behaves in this situation. I can use the Tk GUI fine till this will be fixed, but maybe you guys can stick a debug message to be printed to the console in this situation? Actually, that bug was fixed earlier, but seems it has broken again. It's easy to fix (perhaps this time with a new unit test to go with it). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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 tools, new thinking
Consider emacs. One could imagine Leo viewers for emacs that would show thin Leo files in various ways: - Raw: how Emacs would typically show any file, complete with sentinels. - Outline: how Leo would show a thin file: as an outline and body text. - Cleaned: a plain text view of the file without sentinels. I previously posted the VIM settings to automatically fold any sentinels into a single line containing dashes (i.e. ---). I've since learned that it is also possible to hide them entirely. I assume Emacs has similar functionality. If so, this handles the Raw and Cleaned views. TL --~--~-~--~~~---~--~~ 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: vnodes, tnodes, and unknownAttributes
On Wed, Jun 17, 2009 at 4:29 AM, Ville M. Vainio vivai...@gmail.com wrote: On Tue, Feb 26, 2008 at 2:14 AM, Terry Brownterry_n_br...@yahoo.com wrote: What I struggle with is that some attributes should be universal for the (t)node in any context, and others only make sense in some contexts. For example you might color code the backgrounds of cloned nodes in an active task list to indicate urgency. But when you're looking at the node in it's primary location you don't want to be distracted with why is that one node pink? type noise. (*bump*) I'm beginning to agree that unifying nodes will be clearer. BTW, there is never any such thing as a primary location. All clones are exactly equivalent. But to agree with you on your fundamental point: eliminating the distinction between vnodes and tnodes in Leo's core should help. For example, I just now did a little research to determine why clones work in the unified scheme :-) My first thought was that cloned nodes must be distinct in the unified scheme just as they are in the non-unified scheme. The bogus proof was that the nodes will have different v.parents entries. In fact, though, p.clone updates v.parents for the node, so cloning a node does *not* create a new node in the unified scheme, but only updates v.parents. So while eliminating the distinction between vnodes and tnodes should help in the long run, it will take me awhile to switch mental gears :-) To me, having tnodes be the unit of sharing is second nature. 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: New tools, new thinking
On Wed, Jun 17, 2009 at 7:46 AM, TL t...@tltools.net wrote: Consider emacs. One could imagine Leo viewers for emacs that would show thin Leo files in various ways: - Raw: how Emacs would typically show any file, complete with sentinels. - Outline: how Leo would show a thin file: as an outline and body text. - Cleaned: a plain text view of the file without sentinels. I previously posted the VIM settings to automatically fold any sentinels into a single line containing dashes (i.e. ---). I've since learned that it is also possible to hide them entirely. I assume Emacs has similar functionality. If so, this handles the Raw and Cleaned views. Thanks for this. It's good to know. As for normal Leo view, it would entail a rewrite of an emacs outline view. Non-trivial, but clearly possible. 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 6:10 AM, zpcspm zpc...@gmail.com wrote: On Jun 17, 1:58 pm, Ville M. Vainio vivai...@gmail.com wrote: On Wed, Jun 17, 2009 at 1:10 PM, zpcspmzpc...@gmail.com wrote: I didn't fill (yet!) a bug report at launchpad. I'm a bit skeptical, because it doesn't always go wrong. If at least one more person will be able to reproduce this, then it will go to the bug tracker. Is that about unicode chars in body? Can you isolate the prob to particular subtree? Good hint, thank you. Indeed I had a line of unicode chars in that subtree. Removing it fixed the issue. Thanks for the original report and your help, Ville. I'll fix this before b2 and add a unit test :-) Oh my, maybe I should relax just a bit more and allow the b2 date to maybe slip again. I've got some (enjoyable) family matters to attend to today, and more importantly, I would like to fix all urgent bugs before b2. Still, I'm shooting for Friday. 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 5:00 PM, Edward K. Reamedream...@gmail.com wrote: Thanks for the original report and your help, Ville. I'll fix this before b2 and add a unit test :-) This works for me on xp and ubuntu. I can repro it on Ubuntu 9.04. Body '' -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
What to do about the windows installer?
Problems with the windows installer persist. The 'make' button in dist.leo creates the installer's exe with a pretty gross hack: appending the .zip file to an already-existing .exe file. I don't know whether this hack contributes to the problems users are having. The hack uses the Python 2.5 version of the original .exe file, and the make button ensures that dist.leo was opened using Python 2.5. I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth. I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about this mess? 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: Problems when installing Leo
On Wed, Jun 17, 2009 at 8:14 AM, derwisch johannes.hues...@med.uni-heidelberg.de wrote: On Jun 16, 6:17 pm, Edward K. Ream edream...@gmail.com wrote: On Tue, Jun 16, 2009 at 10:00 AM, LordMax lord...@gmail.com wrote: It's a bug. I believe this bug has been fixed in the trunk. Does it help when I wait for 4-6-b2? Yes, the bug should be fixed in the official b2 release. The only way to test it yourself now is to get the latest bzr code. I highly recommend taking the trouble to install Leo using bzr. You will be glad you did. You will never have to wait for official releases to get bug fixes: you'll get them as soon as they are posted to Leo's bzr repository. 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 9:04 AM, Ville M. Vainio vivai...@gmail.com wrote: This works for me on xp and ubuntu. I can repro it on Ubuntu 9.04. Body '' Works for me on 9.04. What is your default string encoding? 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: 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 5:15 PM, Edward K. Reamedream...@gmail.com wrote: Works for me on 9.04. What is your default string encoding? [~]|9 sys.getdefaultencoding() 9 'ascii' Nothing should be reliant on that, but it may help you reproduce the problem. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 5:30 PM, Ville M. Vainiovivai...@gmail.com wrote: On Wed, Jun 17, 2009 at 5:15 PM, Edward K. Reamedream...@gmail.com wrote: Works for me on 9.04. What is your default string encoding? [~]|9 sys.getdefaultencoding() 9 'ascii' Nothing should be reliant on that, but it may help you reproduce the problem. I enabled tracing in Qt gui--@thin qtGui.py--Gui wrapper--class leoQtGui--Clipboard (qtGui) ctrl+shift+c on a node that has body 'ää' shows: replaceClipboardWith: 0 type 'str' -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 5:35 PM, Ville M. Vainiovivai...@gmail.com wrote: Nothing should be reliant on that, but it may help you reproduce the problem. I enabled tracing in Qt gui--@thin qtGui.py--Gui wrapper--class leoQtGui--Clipboard (qtGui) ctrl+shift+c on a node that has body 'ää' shows: replaceClipboardWith: 0 type 'str' Culprit is this: 6867def toUnicode (self,s,encoding='utf-8',reportErrors=True): 6868 6869try: 6870return unicode(s) 6871except Exception: 6872 - return '' -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
Our current clipboard approach has a fundamental problem: we are treating clipboard as text (unicode), but the xml data (outline structure) is not text. It's 8 bit binary data (that happens to be in utf8). Separate method should be used to put binary data to clipboard (in tk, it's probably always binary data?). We should use setMimeData of QClipboard to set binary data: http://doc.trolltech.com/4.5/qclipboard.html#setMimeData -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 9:38 AM, Ville M. Vainio vivai...@gmail.com wrote: Culprit is this: 6867def toUnicode (self,s,encoding='utf-8',reportErrors=True): 6868 6869try: 6870return unicode(s) 6871except Exception: 6872 - return '' Thanks for your help. Doesn't this have to fail if the default encoding is ascii? What happens if you replace with: try: return unicode(s,'utf-8') except Exception: return unicode(s,'utf-8',errors='replace') 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 9:53 AM, Edward K. Ream edream...@gmail.com wrote: Doesn't this have to fail if the default encoding is ascii? What happens if you replace with: try: return unicode(s,'utf-8') except Exception: return unicode(s,'utf-8',errors='replace') Actually, the above is pretty similar to: return g.toUnicode(s,'utf-8') EKR --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 5:54 PM, Edward K. Reamedream...@gmail.com wrote: Doesn't this have to fail if the default encoding is ascii? What happens if you replace with: try: return unicode(s,'utf-8') except Exception: return unicode(s,'utf-8',errors='replace') It works. I committed and pushed. This is still fundamentally a wrong thing to do, so I emit a g.trace warning as well. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: B2 coming Monday!? Please test.
The leoSettings.leo file defines an add-test button. This should be removed as a default button and placed in the myLeoSettings.leo file for those who are developing/testing Leo functionality. TL --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 6:00 PM, Ville M. Vainiovivai...@gmail.com wrote: This is still fundamentally a wrong thing to do, so I emit a g.trace warning as well. Suggested correct approach: In Code--Core classes--@thin leoCommands.py--class commands--Command handlers...--Outline menu...-- Top Level... (Commands)--Cut Paste Outlines--copyOutline Do not call replaceClipboardWith - rather, call clipboardSetBinary(application/leo-outline, s) On tk, that can call replaceClipboardWith directly. In Command handlers...--Outline menu...-- Top Level... (Commands)--Cut Paste Outlines--pasteOutline It shouldn't call getTextFromClipboard, but rather a new method getBinaryFromClipboard(application/leo-outline) I think this will also eliminate accidental pasting of outline xml to nodes. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: B2 coming Monday!? Please test.
On Jun 16, 11:59 am, Edward K. Ream edream...@gmail.com wrote: One big bug is the tk chapters problem (docs with chapters crash with Ubuntu Jaunty) that has been reported by several users. My guess is that this can be fixed easily. I'll try to do so in b2. However, b2 *will* go out the door no later than Friday, no matter what has to be left behind. A work-around for an apparent tk/Pmw bug is on the trunk at rev 2051. Leo now loads on ubuntu with the tk plugin, but the work-around causes only the main chapter to be shown in the chapter selection widget. I'll do nothing more for b2 on this. 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: B2 coming Monday!? Please test.
On Wed, Jun 17, 2009 at 10:04 AM, TL t...@tltools.net wrote: The leoSettings.leo file defines an add-test button. This should be removed as a default button and placed in the myLeoSettings.leo file for those who are developing/testing Leo functionality. It should be disabled, not removed. 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 10:14 AM, Ville M. Vainio vivai...@gmail.comwrote: On Wed, Jun 17, 2009 at 6:00 PM, Ville M. Vainiovivai...@gmail.com wrote: This is still fundamentally a wrong thing to do, so I emit a g.trace warning as well. Suggested correct approach: Thanks for your quick fix. I don't have time this morning to review your suggestion. I'll do so asap. I also think that all calls to unicode in qtGui.py should be replaced by g.toUnicode. This must happen anyway to support Py3k. 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 6:29 PM, Edward K. Reamedream...@gmail.com wrote: I also think that all calls to unicode in qtGui.py should be replaced by g.toUnicode. This must happen anyway to support Py3k. I disagree about this - in fact I think we should never convert to unicode. We use unicode() to get python unicode objects from QStrings (i.e. no conversion happens). Calling a function that *possibly* does conversion is a recipe for trouble because it hides errors (as happened today). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: Copy/paste bug in Qt GUI?
On Wed, Jun 17, 2009 at 6:34 PM, Ville M. Vainiovivai...@gmail.com wrote: I disagree about this - in fact I think we should never convert to unicode. We use unicode() to get python unicode objects from QStrings (i.e. no conversion happens). Calling a function that *possibly* does conversion is a recipe for trouble because it hides errors (as happened today). Actually, what happened today (and what was fixed by doing utf8 conversion) was not really a fix at all. We just did a workaround that incidentally works, but the bug revealed a logical fallacy in the codebase (confusion of binary vs. unicode). I think we should fail as loudly as possibly whenever something like this happens, instead of sweeping the problem under the rug by catch-all functions like g.toUnicode. The only canonical place to deal with non-unicode data is when reading/writing binary files - or, as with this bug, when reading/writing binary data to clipboard. The amount of conversions should be few and far apart. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: vnodes, tnodes, and unknownAttributes
Doing some more archaeology... On Tue, Feb 26, 2008 at 9:16 PM, Edward K. Reamedream...@gmail.com wrote: This seems like something of an oversimplification to me. The topology of vnodes defines the context in which your referencing a tnode. Yes, you are correct. I misspoke. Vnodes *used to* correspond to nodes on the screen, but that is ancient history. Ah, so this explains existence of vnodes - they were analogous to positions before , but this analogy was removed at some point (effectively making vnodes redundant). -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Debian package available
You can grab a proper beta2 package when it's done, but this is something to try anyway. http://vvtools.googlecode.com/files/leo_4.6-2_all.deb Installed ok on Jaunty. Later on, I'll make them downloadable via apt from PPA repos. The package description is currently this: Description: Literate Editor with Outlines Leo is a tree-structured outliner with direct support for literate programming. Apart from programming, Leo provides a rich interface for tasks involving visual manipulation of hierarchical data (project management, mind mapping, concept experimentation). The whole DAG object model is exposed to the user through complete (Python based) scripting API. Leo ships with both Qt and Tk based user interfaces. Marketing-minded may find something to polish there (I'd also like to make the qt default for a more compelling first experience ;-). Note that I stripped some stuff that was harming the build - pmw + tests is a good example. Users are expected to sort out their own deps. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ 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: vnodes, tnodes, and unknownAttributes
On Wed, Jun 17, 2009 at 11:45 AM, Ville M. Vainio vivai...@gmail.comwrote: Doing some more archaeology... On Tue, Feb 26, 2008 at 9:16 PM, Edward K. Reamedream...@gmail.com wrote: This seems like something of an oversimplification to me. The topology of vnodes defines the context in which your referencing a tnode. Yes, you are correct. I misspoke. Vnodes *used to* correspond to nodes on the screen, but that is ancient history. Ah, so this explains existence of vnodes - they were analogous to positions before , but this analogy was removed at some point (effectively making vnodes redundant). Yes, you could put it that way. The key picture was fingers holding beans. The fingers are positions; the beans; vnodes. This allows the *combination* of positions and vnodes to do what was previously done by vnodes and tnodes. Thus, the unified node world was born. 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: What to do about the windows installer?
On Jun 17, 10:07 am, Edward K. Ream edream...@gmail.com wrote: Problems with the windows installer persist. The 'make' button in dist.leo creates the installer's exe with a pretty gross hack: appending the .zip file to an already-existing .exe file. I don't know whether this hack contributes to the problems users are having. The hack uses the Python 2.5 version of the original .exe file, and the make button ensures that dist.leo was opened using Python 2.5. I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth. I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about this mess? Since I never delivered my modifications to the NSIS-based Windows installer for Leo, you might with justice question my right to comment here. Just let me know whether you want me to share what I got done or what I learned. Details follow. I got the modified installer almost finished before work issues and personal constraints forced me to put it down. The work issues are no longer an issue, and I can manage the personal constraints at this point. I gather that the installers for Leo 4.5 and Leo 4.6 are written in Python instead, and that they use the Python-standard tools. If you wish to apply what I learned to the Python-based installer, I can share what I learned while working on the NSIS-based one. If it would make more sense to go back to the NSIS-based installer, a bit of work should make it possible to incorporate my changes with current Leo and start from there. I tested my modified installer with Leo 4.3 and 4.4 under Windows XP Professional; I did not have access to a Windows Vista box. I do not remember for certain whether I tested it with Python 2.3; I definitely tested it with Python 2.4 and Python 2.5. This modified installer correctly handled installation of a single Leo for all users, using a Python installed for all users. If offered the option of a Leo for the current user only, that worked with a Python installed for that current user only also. Windows makes this set-up relatively easy, and I concluded that this would simplify testing on multiple versions of Python. It also supports testing Leo on multiple installations of a given release of Python, which allows for testing Leo with more than one configuration of Python. The modified installer also checks to make sure that it does not break in various ways. Let me know what you want me to do. --~--~-~--~~~---~--~~ 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 to do about the windows installer?
Google Groups hiccuped, and may have devoured my reply. Just in case, I am re-writing it. On Jun 17, 10:07 am, Edward K. Ream edream...@gmail.com wrote: I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth. I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about this mess? Since I never delivered the revised NSIS-based Windows installer that I was working on, you would be entirely within your rights to discount what I write now, but here goes. Let me know what you want me to do. The revised installer is almost finished. It runs on Windows XP Professional; I had no access to Windows Vista for testing. It correctly handles Leo 4.3 and Leo 4.4, and works with Python 2.4 and Python 2.5. It checks for a Python that is installed for the current user, and then it checks for a Python installed for all users. It installs a copy of Leo for the current user only if it finds a copy of Python that is available to that user only. It installs a single copy of Leo for all Windows users when it finds a copy of Python that is available to all users. Installing for the current user only might appear to be of limited importance, but consider how I used it: I created a couple of Windows users for testing the installer, and was able to test with multiple versions of Python, multiple installation scenarios... without breaking the set-up that I used for compiling the installer. I gather that the installers for Leo 4.5 and Leo 4.6 are written in Python. If you think the Python-based installer is worth continuing I will be happy to share what I learned in my work on the NSIS-based installer. If you think it would make more sense to pick up the NSIS installer, a bit of work with my revised version may bring it into the current era. I gather that one of the goals of the switch to the Python-based installer was to install Leo as a package. I expect that it ought to be possible to use NSIS to drive that intelligently, too. --~--~-~--~~~---~--~~ 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 to do about the windows installer?
On Jun 17, 10:07 am, Edward K. Ream edream...@gmail.com wrote: I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth. I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about this mess? Since I never delivered my modifications to the NSIS-based Windows installer for Leo, you might with justice question my right to comment here. Just let me know whether you want me to share what I got done or what I learned. Details follow. I got the modified installer almost finished before work issues and personal constraints forced me to put it down. The work issues are no longer an issue, and I can manage the personal constraints at this point. I gather that the installers for Leo 4.5 and Leo 4.6 are written in Python instead, and that they use the Python-standard tools. I gather that one of the goals of the switch to the Python-based installer was to install Leo as a package. I expect that it ought to be possible to use NSIS to drive that intelligently, too. If you wish to apply what I learned to the Python-based installer, I can share what I learned while working on the NSIS-based one. If it would make more sense to go back to the NSIS-based installer, a bit of work should make it possible to incorporate my changes with current Leo and start from there. I tested my modified installer with Leo 4.3 and 4.4 under Windows XP Professional; I did not have access to a Windows Vista box. I do not remember for certain whether I tested it with Python 2.3; I definitely tested it with Python 2.4 and Python 2.5. This modified installer correctly handles installation of a single Leo for all users, using a Python installed for all users. If offers the option of a Leo for the current user only, that worked with a Python installed for that current user only also. This simplifies testing on multiple versions of Python. It also supports testing Leo on multiple installations of a given release of Python, which allows for testing Leo with more than one configuration of Python ... without breaking the set-up that I used for compiling the installer. The modified installer also checks to make sure that it does not break in various ways. Let me know what you want me to do. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
