a. Installing Leo, which is specially difficult for non-programmers like my
students. I will try to prepare my classes dealing previously with that
problems using alternative installing strategies not found here until now
like pyinstaller[2] and/or Zero Install[3]
[2]
There will be a new Start Menu link called OSGeo4W Shell which can
be freely deleted. All it does is call D:\portable\OSGeo4W.bat, which
we want to keep, but can be renamed as wished.
The `shell` package is the only one which touches the host system
outside the D:\Portable tree. It includes
I think I figured out a solution combining both methods as so
import leo.core.leoGui as leoGui
fn2='test2.leo'
nullGui = leoGui.nullGui(nullGui)
c2,frame = g.app.newLeoCommanderAndFrame(fileName=None,gui=nullGui)
c2.frame.createFirstTreeNode()
c2.save()
ok, frame = g.openWithFileName(fn2,c)
c3
Summary - it's easy to make a .zip file containing Leo and all it's
dependencies.
Inspired by Matt's recipe, using VirtualBox throw away 1GB Windows XP
32 bit machines, I tried the following.
Install Python (installer from python.org) 2.7.2 to
C:\Docouments and
Nevermind. Setting the filename was right in front of my nose in
newLeoCommanderAndFrame(fileName=
So the working script is
import leo.core.leoGui as leoGui
## Create and save an empty leo outline
fn2='test2.leo'
nullGui = leoGui.nullGui(nullGui)
c2,frame =
It sounds like your biggest issues are OSX-related
well, I have trouble introducing Leo in my company, because we do have
some OSX users here (next to Debian/Ubuntu and Windows). Ironically I
chose Leo originally because it being based on Python promised cross-
platform functionality.
This
On Mon, 2 Jan 2012 11:04:11 -0600
Terry Brown terry_n_br...@yahoo.com wrote:
Summary - it's easy to make a .zip file containing Leo and all it's
dependencies.
Of course this is for Windows, so I think it's an improvement over
asking people to install Python and PyQt first, but neither of those
lp:leo-editor now points to
https://code.launchpad.net/~leo-editor-team/leo-editor/trunk3
which can be branched on a 1 Gb XP system over HTTP.
It would be great if anyone who was experiencing the out of memory
problem could confirm it works for them now.
Branches that were pointing at
Hi,
I read all the thread on db-oriented version of Leo. I got lost on
implementation details (what is a shame... :-/), so I'm just want to say
that the things that Alia points here about a single db file containing
all data (external or not) of a project, and collaboration for free is
On Mon, 19 Dec 2011 22:37:12 -0500
Brian Theado brian.the...@gmail.com wrote:
I wasn't aware of the multi-select functionality.
Does it make sense to change contextmenu.py to fall back to the core
code when there is just a single node selected (untested--but you get
the idea?):
if
I wish it were that easy. The problem is installing PyQt. I finally gave
up, it wasn't worth the hassle. The only way I can run Leo on my Mac is in
a Windows virtual environment.
Rob.
--
You received this message because you are subscribed to the Google Groups
leo-editor
On Jan 3, 2012, at 8:39 AM, Largo84 wrote:
I wish it were that easy. The problem is installing PyQt. I finally gave up,
it wasn't worth the hassle. The only way I can run Leo on my Mac is in a
Windows virtual environment.
What kinds of problems were you encountering?
Personally I use
On Jan 3, 2012, at 3:30 AM, Josef wrote:
well, I have trouble introducing Leo in my company, because we do have
some OSX users here (next to Debian/Ubuntu and Windows).
Indeed, this is exactly the kind of barrier to adoption that can occur when a
major platform is not seriously supported.
On Tuesday, January 3, 2012 6:23:20 AM UTC+7, gcrosswhite wrote:
generic Leo files cannot be merged automatically.
I am not sure what you mean by this. It is true that you don't want to
merge an outline when you have a number of open nodes and some cloned nodes
for personal purposes, but
On Jan 3, 2012, at 11:36 AM, HansBKK wrote:
I understood him to mean that while it is straightforward to share the @
file output files, it is difficult to share outline information contained
in the .leo files themselves, as the XML doesn't lend itself to merging.
Since the XML produced by
On Mon, Jan 2, 2012 at 4:04 PM, Offray Vladimir Luna Cárdenas
off...@riseup.net wrote:
Hi,
I read all the thread on db-oriented version of Leo. I got lost on
implementation details (what is a shame... :-/),
I think the single thing that will best get db-oriented Leo going will
be someone just
On Tuesday, January 3, 2012 3:30:58 AM UTC+7, Terry wrote:
lp:leo-editor now points to
https://code.launchpad.net/~leo-editor-team/leo-editor/trunk3
which can be branched on a 1 Gb XP system over HTTP.
It would be great if anyone who was experiencing the out of memory
problem could
I went to test on my minimal sample file, but I'm afraid the latest at
the nightly builds page:
http://www.greygreen.org/leo/leo-editor-latest.zip
is stuck at 4904, dated 12-28
maybe still pulling from trunk2?
--
You received this message because you are subscribed to the Google Groups
For the sake of those googling later, Terry posted a quick and dirty
example of setting up a portable Leo
herehttps://groups.google.com/d/msg/leo-editor/jnpkrQeo9Hk/Ds3QsUe1W-QJ
.
My more involved scenario above is only needed when maintaining a more
complex portable Python dev environment,
19 matches
Mail list logo
