Hello!
Soon I plan to start writing on PyQT application and considering that,
so far, I'm the only one working on it, it's a nice opportunity to use
Leo with @file not caring much about sentinels and later
collaboration.
Now, since I regularly use Emacs as my preferred editor, I wonder what
On Fri, May 13, 2011 at 12:45 PM, Gour-Gadadhara Dasa g...@atmarama.net wrote:
Soon I plan to start writing on PyQT application and considering that,
so far, I'm the only one working on it, it's a nice opportunity to use
Leo with @file not caring much about sentinels and later
collaboration.
On Fri, 13 May 2011 12:59:26 +0300
Ville M. Vainio vivai...@gmail.com
wrote:
Emacs has very little over leo in terms of body editing - macros and
muscle memory, perhaps.
Well, I use it for everything -- org-mode, writing reST,
markdown...and need editor for some PHP/JS/HTML...
How is support
As of rev 4052, codewise completions are ready for testing!
There are no items left on the to-do list for autocompletion! This is
an important milestone for Leo.
The autocompleter code is far simpler than it has ever been, so fixing
any remaining glitches should be very easy.
You may switch
Imo, the QCompleter code should be replaced by code based on a
QListView.
At present, the QCompleter code contributes exactly nothing to the
autocompleter, except a *lot* of wasted time. In addition, the
QCompleter code appears to run in a separate thread, which makes it
impossible to restart
On May 13, 9:49 am, Edward K. Ream edream...@gmail.com wrote:
1. I personally have zero interest in popup completers, so if you *do*
have an interest in them, the way to demonstrate that interest is to
write the code I have just described :-)
Well, this is one of the more foolish things I
On Fri, May 13, 2011 at 10:51 AM, Edward K. Ream edream...@gmail.com wrote:
My plan is to replace QCompleter by QListView today. It should take
just an hour or so.
The work has been straightforward, but once again it is much easier
for me to do it.
At present, the usual focus problems
On May 13, 12:20 pm, Edward K. Ream edream...@gmail.com wrote:
At present, the usual focus problems prevent the QListWidget from getting
focus initially.
Easily fixed, as it turned out.
Rev 4055 contains the first draft of the QListWidget code. Still to
do:
- Handle up/down arrow keys,
Why? I have seen it work just fine, and I don't see why hand rolling the coded
that is now automatic would help us.
Lähetetty Nokia-puhelimestani
alkuperäinen viesti
Lähettäjä: Edward K. Ream
Lähetetty: 13.05.2011, 17:49
To: leo-editor
Aihe: Replacing the QCompleter code with a
On Fri, May 13, 2011 at 10:49 AM, Edward K. Ream edream...@gmail.com wrote:
1. I personally have zero interest in popup completers, so if you *do*
have an interest in them, the way to demonstrate that interest is to
write the code I have just described :-)
Again, I don't get this. Why not
On Fri, May 13, 2011 at 2:13 PM, Edward K. Ream edream...@gmail.com wrote:
Because QCompleter sucks. The new QListView code *looks* like
QCompleter, but is spectacularly faster.
I didn't see slowness in QCompleter code.
The code is shaping up nicely. As of rev 4057, the QListWidget is,
On Fri, May 13, 2011 at 10:09 AM, Edward K. Ream edream...@gmail.com wrote:
You may switch between codewise completions and leo-centric
contmpletions by setting::
Why is switch needed? We know when we want eval completions, namely
from the fact that we have pattern starting with c. g. or p. We
So, nobody wants to help me with the simple tabwidth question?
--
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, May 13, 2011 at 1:26 PM, Ville M. Vainio vivai...@gmail.com wrote:
Why is switch needed? We know when we want eval completions, namely
from the fact that we have pattern starting with c. g. or p. We can
always use eval in those cases, and choose other way if that is not
applicable.
On Fri, May 13, 2011 at 1:23 PM, Ville M. Vainio vivai...@gmail.com wrote:
If you think this will lead to cleaner code, I'm happy. And can take
maintainership for it.
Thanks for the offer. The code that needs maintaining by you, imo, is
ac.get_codewise_completions and its helpers. I expect
On Fri, May 13, 2011 at 10:52 PM, Edward K. Ream edream...@gmail.com wrote:
Possible. However, it assumes that c, g, and p mean what they mean in Leo.
The worst that could happen in that case is that you get wrong
completions, i.e. no harm done. You are not likely to get too confused
as you'll
On Fri, May 13, 2011 at 12:47 PM, vivai...@gmail.com vivai...@gmail.com wrote:
Why? I have seen it work just fine
It doesn't work well at all on Windows.
Rev 4058 completes the transition to QListView, except for size and
placement issues.
and I don't see why hand rolling the coded that is
On Sat, May 14, 2011 at 12:44 AM, Edward K. Ream edream...@gmail.com wrote:
As you will see, the roll my own code in rev 4058 is actually
substantially simpler than the QCompleter code. It's all gain, and no
pain at all.
Okay, that's something to be happy about then.
Now that it's fully our
On Sat, May 14, 2011 at 1:30 AM, Edward K. Ream edream...@gmail.com wrote:
I just had a thought :-) *Do* use a QCompleter, but *only* to as a
way of drawing the popup. I think this will allow us to use the
QCompleter visuals, while bypassing everything else.
Hmm. That's dicey because of
On Fri, May 13, 2011 at 5:49 PM, Ville M. Vainio vivai...@gmail.com wrote:
On Sat, May 14, 2011 at 1:30 AM, Edward K. Ream edream...@gmail.com wrote:
I just had a thought :-) *Do* use a QCompleter, but *only* to as a
way of drawing the popup. I think this will allow us to use the
QCompleter
On May 13, 6:18 pm, Edward K. Ream edream...@gmail.com wrote:
But making it's parent one of the splitters does work. So the last
remaining nit is to move it to the right spot. I'm working on it...
Haha. I can steal Terry's code to create a temporary frame above the
body pane. That's
On Sat, May 14, 2011 at 2:18 AM, Edward K. Ream edream...@gmail.com wrote:
However, we can't make the parent the body widget, because then it
will, for sure, obscure part of the body pane.
Completers typically obscure part of the body pane. Usually under the
cursor, sometimes above
--
You
links
http://www.xjsfl.com/wp-content/uploads/komodo-editor-xjsfl.png
http://www.qweas.com/downloads/web/html-tools/600-scr-komodo-edit.png
http://www.wareprise.com/wp-content/uploads/2010/09/auto-complete.png
http://docs.activestate.com/komodo/5.2/img/editor_autocomp.gif
tons more if you do
On May 13, 6:29 pm, Edward K. Ream edream...@gmail.com wrote:
Haha. I can steal Terry's code to create a temporary frame above the
body pane. That's exactly what is wanted.
Yup. Here is the relevant code for the ctor of the subclassed
QListWidget::
def __init__(self,c):
splitter2 =
On Fri, May 13, 2011 at 6:33 PM, Ville M. Vainio vivai...@gmail.com wrote:
links [ to pictures of floating completion windows]
Floating completion windows are certainly another option. I hadn't
considered them because that's not how QCompleter appears. I like the
present scheme, with a
On Fri, 13 May 2011 20:00:59 -0500
Edward K. Ream edream...@gmail.com wrote:
Floating completion windows are certainly another option.
I like the ascetic of a floating window directly above or below the
line I'm typing on so my eyes don't have to track somewhere else and
back, likewise I
26 matches
Mail list logo
