Thanks for the feedback and describing the improvements in other
areas. I'll start documenting
the problems, put them on this list for any comment or discussion and
then file as bugs.
On Aug 7, 1:42 pm, "Ville M. Vainio" wrote:
> On Fri, Aug 7, 2009 at 11:07 PM, rhh wrote:
> > plugins. I tried
Very nice. Now we need to make the one on the right gvim. ;)
--~--~-~--~~~---~--~~
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 thi
On Fri, Aug 7, 2009 at 11:07 PM, rhh wrote:
> plugins. I tried leo 4.6.2 final, in both qt and tk mode, and ran
> into a number of snags. I have not followed the rewrite discussions
> in detail but from what I have read it seems that some tk stuff will
> necessarily be broken as you improve and
> Probably plugin or even core-worthy.Works well and +1 on making it part of
the core app.
--~--~-~--~~~---~--~~
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@googlegrou
The calioPY structural engineering IDE I wrote with Leo relies heavily
on leo button, log pane and menu scripts, and on a variety of
plugins. I tried leo 4.6.2 final, in both qt and tk mode, and ran
into a number of snags. I have not followed the rewrite discussions
in detail but from what I hav
Thanks a lot, that solves the problem.
--~--~-~--~~~---~--~~
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
On Fri, Aug 7, 2009 at 9:20 PM, Steve Zatz wrote:
>> Run this script to create stand-alone window for body editor:
> Thanks. I think that can be very helpful when you want to focus on the body
> and/or have a lot of screen real estate. Any way to re-attach it?
> Steve
Not yet. I imagine it won
> Run this script to create stand-alone window for body editor:Thanks. I
think that can be very helpful when you want to focus on the body and/or
have a lot of screen real estate. Any way to re-attach it?
Steve
--~--~-~--~~~---~--~~
You received this message becau
On Fri, Aug 7, 2009 at 4:12 PM, zpcspm wrote:
>
> I've launched an instance of Ubuntu 9.04 (Jaunty) in VirtualBox,
> installed fluxbox and PyQt4, switched to fluxbox and saw the same
> issue.
Alright, that confirms it. I have removed the hiding code, so fluxbox
should be good to go again. Unfort
On Fri, Aug 7, 2009 at 2:20 AM, Rudi wrote:
>
> Hi, new Leo user here I really like Leo so far. However, I haven't
> figured out a good way to quickly navigate through the nodes without
> using the mouse. Can I get some tips please?
When the focus is in the outline, plain arrow keys will move f
On Fri, Aug 7, 2009 at 9:04 AM, William Strømsvold <
william.stromsv...@gmail.com> wrote:
> Alt+Arrows :)
>
>
> http://webpages.charter.net/edreamleo/outlines.html#navigating-through-the-outline
This section applies, at present, only when using the tk gui.
Edward
--~--~-~--~~--
On Aug 7, 11:45 am, "Ville M. Vainio" wrote:
> On Fri, Aug 7, 2009 at 12:34 PM, Nik wrote:
> > to a large extent smoothly now! That should be a very good
> > starting point for future refinements.
>
> > However, without the option --gui=qttabs one observers
> > a similar behaviour as before!!
>
On Fri, Aug 7, 2009 at 5:04 PM, William
Strømsvold wrote:
> Alt+Arrows :)
>
> http://webpages.charter.net/edreamleo/outlines.html#navigating-through-the-outline
Help -> open quickstart.leo is also a good place to check.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~
On Fri, Aug 7, 2009 at 4:58 PM, Zoom.Quiet wrote:
>
> i'm in Ubuntu 8.04.1
> usage setup.pt install to installed Leo 4.6/4.6.2
> all can not running!
Try this:
https://answers.launchpad.net/leo-editor/+faq/632
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~
Alt+Arrows :)
http://webpages.charter.net/edreamleo/outlines.html#navigating-through-the-outline
Regards
-
William S.
2009/8/7 Rudi
>
> Hi, new Leo user here I really like Leo so far. However, I haven't
> figured out a good way to quickly navigate through the nodes without
> using the mouse.
Hi, new Leo user here I really like Leo so far. However, I haven't
figured out a good way to quickly navigate through the nodes without
using the mouse. Can I get some tips please?
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed
i'm in Ubuntu 8.04.1
usage setup.pt install to installed Leo 4.6/4.6.2
all can not running!
error such as:
$ /usr/bin/leo
Traceback (most recent call last):
File "/usr/bin/leo", line 8, in
leo.core.runLeo.run()
File "/usr/lib/python2.5/site-packages/leo/core/runLeo.py", line 95, in run
On Aug 7, 3:05 pm, "Ville M. Vainio" wrote:
> Works on Qt 4.4 for me (Ubuntu Hardy). I'm thinking the window manager
> may be behind the issue...
I believe my further testing confirms this.
I've launched an instance of Ubuntu 9.04 (Jaunty) in VirtualBox,
installed fluxbox and PyQt4, switched to
Came over this excellent tool.. Could this be useful implementing in Leo?
http://code.google.com/p/wkhtmltopdf/
mvh
-
William S.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this gr
On Fri, Aug 7, 2009 at 2:44 PM, zpcspm wrote:
> PS: Ville, I've mentioned in another thread a couple of days ago that
> I'm using Qt/PyQt4-4.4.4, not 4.5. Maybe that's the reason why it
> doesn't work for me? Unfortunately, I can't have Qt/PyQt-4.5 installed
> ATM, because it'll take at least one
PS: Ville, I've mentioned in another thread a couple of days ago that
I'm using Qt/PyQt4-4.4.4, not 4.5. Maybe that's the reason why it
doesn't work for me? Unfortunately, I can't have Qt/PyQt-4.5 installed
ATM, because it'll take at least one day to build and I can't afford
that.
--~--~-~
On Fri, Aug 7, 2009 at 2:34 PM, zpcspm wrote:
> f.top.hide()
> f.top.show()
> f.top.setVisible(True)
>
> doesn't change anything. I can see something flashing, but nothing
> more.
Ok, I guess we'll have to remove the code then, as it seems unreliable.
Just to double-check - can you try with ano
On Aug 7, 2:26 pm, "Ville M. Vainio" wrote:
> On Fri, Aug 7, 2009 at 2:19 PM, zpcspm wrote:
> > It doesn't work even for this scenario:
>
> > f.top.hide()
> > f.top.show()
>
> What if you add f.top.setVisible(True) to go with f.top.show()?
This scenario:
f.top.hide()
f.top.show(
On Fri, Aug 7, 2009 at 2:19 PM, zpcspm wrote:
> It doesn't work even for this scenario:
>
> f.top.hide()
> f.top.show()
What if you add f.top.setVisible(True) to go with f.top.show()?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~
Take a look at "Scripts-->@thin leoScripts.txt-->Important-->Write
cleaned files to 'clean' directory" in leo/scripts/scripts.leo.
To see how it works, copy this node to your outline and create a
script button from it.
It just populates your source tree with clean version of your files,
it doesn
On Fri, Aug 7, 2009 at 2:04 PM, William
Strømsvold wrote:
> Maybe I've missed something here, but what is the simplest way to "export" a
> file I'm working on, without the sentinels?
>
> The scenario is this:I'm working on my files in Leo, with a full structure.
> I use @thin-nodes. If someone wan
On Aug 7, 1:58 pm, "Ville M. Vainio" wrote:
> Try moving f.top.show upwards line by line until it works, report back.
Done. I've moved the call to show() upwards line by line as you
suggested.
It doesn't work even for this scenario:
f.top.hide()
f.top.show()
f.create
Maybe I've missed something here, but what is the simplest way to "export" a
file I'm working on, without the sentinels?
The scenario is this:I'm working on my files in Leo, with a full structure.
I use @thin-nodes. If someone wants a copy of my work, without the
sentinels, what is the simplest wa
On Fri, Aug 7, 2009 at 1:50 PM, zpcspm wrote:
> I'm running it from console, I can see the main window of leo flashing
> for a moment (perhaps because I have a relatively old and slow
> computer) then disappearing. And that's all. No additional messages
> are printed to the console.
>
> Reverting
I'm running it from console, I can see the main window of leo flashing
for a moment (perhaps because I have a relatively old and slow
computer) then disappearing. And that's all. No additional messages
are printed to the console.
Reverting to r2299 seems to help, after that leo is working again.
On Fri, Aug 7, 2009 at 1:23 PM, Ville M. Vainio wrote:
> Run this script to create stand-alone window for body editor:
>
> QQQ
>
> wdg = c.frame.body.bodyCtrl.widget
> wdg.setParent(None)
> wdg.show()
>
> QQQ
>
> Real life implications are unknown. However, it may be handy if you
> want to focus
Run this script to create stand-alone window for body editor:
QQQ
wdg = c.frame.body.bodyCtrl.widget
wdg.setParent(None)
wdg.show()
QQQ
Real life implications are unknown. However, it may be handy if you
want to focus to always be in the body, even when you are moving
around with alt+arrows.
On Fri, Aug 7, 2009 at 12:34 PM, Nik wrote:
> to a large extent smoothly now! That should be a very good
> starting point for future refinements.
>
> However, without the option --gui=qttabs one observers
> a similar behaviour as before!!
>
> Another interesting point is that without --gui=qttabs
On Aug 6, 11:15 pm, "Ville M. Vainio" wrote:
> On Thu, Aug 6, 2009 at 11:58 PM, Ville M. Vainio wrote:
> > The hiding seems to be a rather fragile thing. Luckily, in the process
> > I learned about the spell tab issue (lost ownership. which makes it
> > disappear) and various hacks that go into
34 matches
Mail list logo
