On Fri, 25 Apr 2014 08:13:29 -0700 (PDT)
"Edward K. Ream" <[email protected]> wrote:

> - This scheme is only useful when multiple Leonine programmers work
> in a non-Leonine project.  Solo Leonine programmers in a non-Leonine
> project may as well use @shadow or @auto.

First off welcome back and good luck with the hips.  It was kind of
weired how quiet the forum got after reaching a new high of activity -
I'm way overloaded work-wise at the moment, still using Leo all the
time for doing the work, of course :)

I was confused by your post until the above statement - so it's
basically about sharing the content of ~/.leo/shadow?  But you're
thinking of adding some things, sha1 hash of public files for
example, although what that buys you over existing @shadow I'm not
following.

Although it would be cool to share other people's views of files, to me
it's not a priority - I could see each of the 3 Leo users in a 7 person
team having their *own* view of the public files all 7 are sharing.
I use the hierarchical bookmark system to have my own view of LeoPyRef
and LeoPluginsRef, for example.

On the directions for Leo front, supporting Python 3.x / Qt *5*.x
should probably get addressed at some point, even though it's kind of
annoying if we want to keep supporting Qt 4.x simultaneously.
It appears that Riverbank is not making a Python 2.7 Qt 5 combo, so
we'll have to keep 4.x compatibility to go with 2.7.

Poking around the Riverbank site I see they have a new product, 
www.riverbankcomputing.com/software/pyqtdeploy/intro
for deploying PyQt apps cross platform - an installer basically I
think, but PyQt specific.  Although pyqtdeploy itself runs in Python
3.2 / Qt 5 it deploys 2.x/3.x / 4.x/5.x.

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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to