Re: Push/pop hoist?

2015-12-02 Thread 'Terry Brown' via leo-editor
On Wed, 2 Dec 2015 11:52:20 -0800 (PST)
Phil  wrote:

> > The 'problem' with chapters, if you can call it that, is that they
> > 'feel' more permanent -- you're making a change to the tree
> > structure (with @chapter nodes) to accommodate it -- of course,
> > they're disposable if you wish, just not transparently so.
> >
> > Sure, that's a good point. I think I can work with that behavior,
> > but it 
> would also be nice to have a more "transient" stacking behavior that
> is independent of the outline structure. Maybe if I can find some
> time I'll try to figure out how to do that.  :)

You could look at the bookmarks plugin.  That can save locations, or
even groups of locations - you just have to do the (un)hoisting as a
separate step.

Cheers -Terry

-- 
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/d/optout.


Re: Push/pop hoist?

2015-12-02 Thread Phil


> The 'problem' with chapters, if you can call it that, is that they 'feel' 
> more permanent -- you're making a change to the tree structure (with 
> @chapter nodes) to accommodate it -- of course, they're disposable if you 
> wish, just not transparently so.
>
> Sure, that's a good point. I think I can work with that behavior, but it 
would also be nice to have a more "transient" stacking behavior that is 
independent of the outline structure. Maybe if I can find some time I'll 
try to figure out how to do that.  :)

-- 
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/d/optout.


Re: Can't run/install on OSX 10.11

2015-12-02 Thread Edward K. Ream
On Tue, Dec 1, 2015 at 4:55 PM, Matt Feifarek 
wrote:

> Hi there.
>
> I'm trying to run Leo 4.11-final on a Mac (10.11.1) on Python 2.7.
>
> I followed the instructions here:
>
> http://leoeditor.com/installing.html#installing-leo-on-macos-10-7-lion-and-later
>
> I am using the system python (2.7) because that's what brew seems to want.
> I was able to install qt/pyqt ok:
>
> $ python
>
> [GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.0.59.1)] on darwin
>
> Type "help", "copyright", "credits" or "license" for more information.
>
> >>> import PyQt4
>
> >>>
>
>
> But I can't run leo:
>

​File "/Users/mjf/Downloads/Leo-4.11-final/leo/plugins/qtGui.py", line
6435, in getCompositeIconImage

pix.fill(QtGui.QColor(None))  # transparent fill, default it random
noise

Hmm.  leo/plugins/qtGui is supposed to be a do-nothing.  It should contain
just:

'''qt gui plugin.'''
print('= qtGui.py: this module is no longer used.')

It looks to me like there are some old files around in your installation.
Could that be so?

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/d/optout.


Re: Push/pop hoist?

2015-12-02 Thread Jacob Peck
The 'problem' with chapters, if you can call it that, is that they 
'feel' more permanent -- you're making a change to the tree structure 
(with @chapter nodes) to accommodate it -- of course, they're disposable 
if you wish, just not transparently so.


-->Jake

On 12/2/2015 10:36 AM, Phil wrote:


Chapters provide a similar function.  I use them all the time for
this functionality.


Thanks for the tip, that is helpful. I had looked at chapters in the 
past but didn't really get how they work. Playing with it again, now I 
get it.

--
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/d/optout.


--
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/d/optout.


Re: Push/pop hoist?

2015-12-02 Thread Phil


> Chapters provide a similar function.  I use them all the time for this 
> functionality.
>
>
> Thanks for the tip, that is helpful. I had looked at chapters in the past 
but didn't really get how they work. Playing with it again, now I get it.

-- 
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/d/optout.


Re: Push/pop hoist?

2015-12-02 Thread Jacob Peck

Hmm...

Chapters provide a similar function.  I use them all the time for this 
functionality.


Hope this helps!
-->Jake

On 12/2/2015 9:44 AM, Phil wrote:


Not 100% clear on your goal - basically cut / yank / push a subtree,
which you're identifying by hoisting, to a stack, rather than the
single content clipboard, and the copy / pop it somewhere else later?
I guess I'm confused by the mix of moving subtrees and hoisting.

The quickmove plugin provides a number of ways (including buttons) to
move subtrees to targets.  You could create a node somewhere called
"stack-of-nodes" and set it as a target for "move to first child"
operations using quickmove.  Then you'd have a button to move the
current node / subtree to the first child position of that node, so
your stack would be the children of a node in the tree, which seems
Leonine.

It wouldn't be hard to script a button to move those children back to
the current position - could show some code, but not sure I'm
answering
the question?

Cheers -Terry


Terry, thanks for your response. I guess I didn't pose the question 
clearly enough; let me try again:


What I'm looking for might be called push/pop of "views" (and not 
cut/paste operations), with a "view" being what I see when I have a 
particular node hoisted. Ideally, this would also preserve the state 
of the expanded and collapsed subtrees in that view, but that would 
not be necessary. So, I don't want to change the tree structure, I 
just want to change the way I'm looking at it.


Does this help?

Thanks!
Phil
--
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/d/optout.


--
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/d/optout.


Re: Push/pop hoist?

2015-12-02 Thread Phil


> Not 100% clear on your goal - basically cut / yank / push a subtree, 
> which you're identifying by hoisting, to a stack, rather than the 
> single content clipboard, and the copy / pop it somewhere else later? 
> I guess I'm confused by the mix of moving subtrees and hoisting. 
>
> The quickmove plugin provides a number of ways (including buttons) to 
> move subtrees to targets.  You could create a node somewhere called 
> "stack-of-nodes" and set it as a target for "move to first child" 
> operations using quickmove.  Then you'd have a button to move the 
> current node / subtree to the first child position of that node, so 
> your stack would be the children of a node in the tree, which seems 
> Leonine. 
>
> It wouldn't be hard to script a button to move those children back to 
> the current position - could show some code, but not sure I'm answering 
> the question? 
>
> Cheers -Terry 
>

Terry, thanks for your response. I guess I didn't pose the question clearly 
enough; let me try again:

What I'm looking for might be called push/pop of "views" (and not cut/paste 
operations), with a "view" being what I see when I have a particular node 
hoisted. Ideally, this would also preserve the state of the expanded and 
collapsed subtrees in that view, but that would not be necessary. So, I 
don't want to change the tree structure, I just want to change the way I'm 
looking at it.

Does this help?

Thanks!
Phil

-- 
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/d/optout.


Can't run/install on OSX 10.11

2015-12-02 Thread Matt Feifarek
Hi there.

I'm trying to run Leo 4.11-final on a Mac (10.11.1) on Python 2.7.

I followed the instructions here:
http://leoeditor.com/installing.html#installing-leo-on-macos-10-7-lion-and-later

I am using the system python (2.7) because that's what brew seems to want. 
I was able to install qt/pyqt ok:

$ python

[GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.0.59.1)] on darwin

Type "help", "copyright", "credits" or "license" for more information.

>>> import PyQt4

>>>


But I can't run leo:


$ python launchLeo.py 

Traceback (most recent call last):

  File "launchLeo.py", line 8, in 

leo.core.runLeo.run()

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/runLeo.py", line 81, 
in run

g.app.loadManager.load(fileName,pymacs)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoApp.py", line 1903, 
in load

ok = lm.doPostPluginsInit()

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoApp.py", line 2260, 
in doPostPluginsInit

c1 = lm.openEmptyWorkBook()

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoApp.py", line 2314, 
in openEmptyWorkBook

c = lm.loadLocalFile(fn,gui=g.app.gui,old_c=None)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoApp.py", line 2510, 
in loadLocalFile

c = lm.openFileByName(fn,gui,old_c,previousSettings)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoApp.py", line 2561, 
in openFileByName

lm.initWrapperLeoFile(c,fn)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoApp.py", line 2668, 
in initWrapperLeoFile

c.chapterController.finishCreate()

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoChapters.py", line 
62, in finishCreate

cc.selectChapterByName('main',collapse=False)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoChapters.py", line 
431, in selectChapterByName

cc.selectChapterByNameHelper(chapter,collapse=collapse)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoChapters.py", line 
465, in selectChapterByNameHelper

chapter.select()

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoChapters.py", line 
900, in select

self.chapterSelectHelper(w,selectEditor)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoChapters.py", line 
947, in chapterSelectHelper

c.redraw_now(p)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/core/leoCommands.py", line 
7294, in redraw

p2 = c.frame.tree.redraw(p)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/plugins/baseNativeTree.py", 
line 155, in full_redraw

self.drawTopTree(p)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/plugins/baseNativeTree.py", 
line 242, in drawTopTree

self.drawTree(p)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/plugins/baseNativeTree.py", 
line 257, in drawTree

item = self.drawNode(p,parent_item)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/plugins/baseNativeTree.py", 
line 215, in drawNode

self.drawItemIcon(p,item)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/plugins/baseNativeTree.py", 
line 1210, in drawItemIcon

icon = self.getIcon(p)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/plugins/qtGui.py", line 
6403, in getIcon

return self.getCompositeIconImage(p,val)

  File "/Users/mjf/Downloads/Leo-4.11-final/leo/plugins/qtGui.py", line 
6435, in getCompositeIconImage

pix.fill(QtGui.QColor(None))  # transparent fill, default it random 
noise

TypeError: arguments did not match any overloaded call:

  QColor(Qt.GlobalColor): argument 1 has unexpected type 'NoneType'

  QColor(int): too many arguments

  QColor(QVariant): argument 1 has unexpected type 'NoneType'

  QColor(): argument 1 has unexpected type 'NoneType'

  QColor(int, int, int, int alpha=255): argument 1 has unexpected type 
'NoneType'



Any tips? Perhaps a version mismatch?


-- 
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/d/optout.