it's the same API (just convert - to . and
remove type declarations, and you are pretty much there).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group
tedious to do by hand).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
pretty impressive, considering how little time has been spent
with it so far.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
too much.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
memory-efficient to only
maintain this dict in my tree model, at least I can garbage-collect
the positions when tree is re-created.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
whatever scintilla
uses, you can nuke all the leo bindings related to body editing.
- The widget passed to k.masterKeyHandler must be a leoQtBody, not a
Scintilla object in some situations. I'm not sure how to handle this
at present.
Just translate the scintilla object to leoQtBody.
--
Ville M
On Tue, Oct 7, 2008 at 8:38 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Note that this will change soon, if I manage to hack up the tree in
QTreeView. It will be a bit more setup, but will lead to a much more
flexible, faster and more memory efficient representation of the tree
Here's a yet another idea:
Saving should happen in a thread, or idle phase. If we mark the
headline as read-only during the saving phase, it should not be a
problem.
Of course this assumes headline CAN be marked read-only somehow.
--~--~-~--~~~---~--~~
You
that
way.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
/revision/1253
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
It seems leo calls tree.editLabel too early.
I tried to make editLabel works like this:
def editLabel (self,p,selectAll=False):
Start editing p's headline.
c = self.c
w = self.treeWidget
it = self.vnodeDict[p.v]
w.editItem(it)
But, starting the editing is attempted
in the tree.
I might have been harboring a huge misunderstanding about vnodes, but
don't vnode and position have one-to-one mapping? What is the occasion
when vnodeDict value has multiple positions and tree items?
--
Ville M. Vainio
http://tinyurl.com/vainio
On Sat, Oct 11, 2008 at 1:02 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Yes, it only seems to run when you press numpad return.
Note that this is broken for the body pane as well.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You
= self.treeitems[id(self.treeWidget.currentItem())]
self.textEdit.setText(self.cur_tnode.bodyString())
self.selecting = False
self.widget_dirty = False
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
.
I don't see why anything else would be needed for this...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo
, and let
them be handled natively in the scintille/tree widget?
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo
On Sat, Oct 11, 2008 at 8:52 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
Why not blacklist a certain set of keys known to behave badly, and let
them be handled natively in the scintille/tree widget?
Better yet, why not scrap the old key binding stuff altogether (as far
as qtgui goes)? It's
, for
example. However, we really want QTextEdit, since that's editable.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo
as gui code goes.
That really shouldn't be true, because the scintilla widget will never
see the key event if the filter chooses to filter it out.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
deviations from
that are probably bugs or misunderstandings on the users part.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
, here:
http://doc.trolltech.com/4.2/qobject.html#installEventFilter
I will have to try it when I get home (yeah, had to come to office on
sunday) ;-)
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
disable the raw data widget there.
Obviously, serializing / deserializing data to xml is a performance
hit, so it shouldn't be done all the time (only when node is dirty and
something that needs the data is executed, perhaps.
Leo3k, here we come ;-)
--
Ville M. Vainio
http://tinyurl.com/vainio
On Sun, Oct 12, 2008 at 1:49 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
I will have to try it when I get home (yeah, had to come to office on
sunday) ;-)
Ok, I made some tests and it seems to work properly.
Add a print statement to leoQtEventFilter.eventFilter. You see that
it's the first
.
This might work. I well change the body editor to QStackedLayout soon.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email
.
(and possibly also shows why previous gui plugin projects were not finished).
The wx plugin didn't get finished because the wx people kept blowing
off my complaints.
There was also a gtk plugin that fell under the radar a while ago
(that I never saw running).
--
Ville M. Vainio
http://tinyurl.com
the choice between simplicity and features, I
would be the first one to throw away features.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
this.
Are you SURE you return True to all the events? The KeyReleased thing
seems fishy to me. You really need to deal with all the events. Just
try returning True immediately, and see that no events get passed to
the body editor.
--
Ville M. Vainio
http://tinyurl.com/vainio
-with plugin are probably in this group as well.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
with) and
the scintilla people, but it probably hasn't gone through the
stringent quality assurance that Qt goes through (for commercial
reasons, they as a pure open source story can afford more screwups
than Qt people).
--
Ville M. Vainio
http://tinyurl.com/vainio
that entered insert mode, you would return to
standard mode from this minimal vi mode.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
is 0.5 secs, and expand all on a created
tree is close to 0). Though you can't expect everything to be
optimized already ;-)
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
); otherwise it must return FALSE.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
.
Typically, things seem to be triggered on keypress rathen than
release.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email
On Tue, Oct 14, 2008 at 5:46 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
- Making editing headlines work with Leo's core, not necessarily using
much code *from* Leo's core. Should be straightforward.
I can do this today.
Done.
http://bazaar.launchpad.net/~leo-editor-team/leo-editor/qt
On Tue, Oct 14, 2008 at 1:24 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Tue, Oct 14, 2008 at 1:03 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
- Making editing headlines work with Leo's core, not necessarily using
much code *from* Leo's core. Should be straightforward.
I can do
a partial redraw if there aren't.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
Would it be ok to short circuit at least a few keys directly to the
widgets at this point?
These keys include:
- Arrow keys (for navigation). Currently they don't work at all in
tree widget, and the cursor blinks annoyingly in body widget when
holding arrow keys pressed.
- Enter (focus body
On Tue, Oct 14, 2008 at 7:04 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
I know this has been on the table for a while, but I'd like a more
fine-grained tree redraw hints from the core.
After playing around with leoPyRef a little bit (expanding and
contracting nodes), I'd upgrade it from I'd
the node expansion mark.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
of Leo UI they want in ui
designer (while we produce a few good choices out-of-the-box). As long
as the key objects (tree, body, minibuffer, tab widget) have the same
name, it will work out-of-the-box.
--
Ville M. Vainio
http://tinyurl.com/vainio
try to focus
the tree. Weird. It has nothing to do with event filters, even if I
immediately return False from the event filter the focus can't be set
to tree widget.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message
, but the Leonine way of doing that is to change settings.
In short, I think this issue has been completely resolved by
integrating the qt plugin with Leo's core.
Yes, that is true. There is nothing blocking us here, so we can move
forward quickly.
--
Ville M. Vainio
http://tinyurl.com/vainio
On Wed, Oct 15, 2008 at 12:02 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
It seems the focus gets moved to text body, even if you try to focus
the tree. Weird. It has nothing to do with event filters, even if I
immediately return False from the event filter the focus can't be set
to tree
On Wed, Oct 15, 2008 at 3:46 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Wed, Oct 15, 2008 at 3:40 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
1. We can be absolutely sure that eventFilter is working properly,
because the trace in k.masterKeyHandler shows that masterKeyHandler is
being
then calls k.masterKeyHandler. At present,
k.masterMenuCallback passes no widget to k.masterKeyHandler, so
k.masterKeyHandler defaults to the body pane and all is not well :-)
^^^ see my other mail.
--
Ville M. Vainio
http://tinyurl.com/vainio
events work or not. They do.
Yes, this is not at all abount eventFilters. They do work correctly.
The accelerator thing is a wholly different thing. It's related to
QActions, and it's the thing that is broken (with arrow keys).
--
Ville M. Vainio
http://tinyurl.com/vainio
On Wed, Oct 15, 2008 at 5:37 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
^^^ see my other mail.
Note that we now have duplicate mechanism for command dispatching. One
through QAction shortCuts (accelerators), one via key bindings.
--
Ville M. Vainio
http://tinyurl.com/vainio
.
... and peripheral stuff like plugin windows can be done safely already.
Once the body editing is safe (today? no pressure ;-), I'll be
switching immediately.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
freetime
as well. That, and the gut feeling that we are close enough to having
something that's useful for dogfooding in a weeks time. :-)
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed
: white }
The advantages are:
- No coding needed (translation of color codes, ...)
- The way to do it is generally applicable to qt apps, i.e. users
don't need to learn leo-specific way to customize the look.
--
Ville M. Vainio
http://tinyurl.com/vainio
(if that is really
the case) is a bad and quite rare practice...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
approach. So far, this is only
speculation though.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
eric4-4.3-snapshot-20081005.tar.gz
cd eric4-4.3-snapshot-20081005/eric/QScintilla/Lexers/
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
probably did break this thing (as you can clearly
see by doing bzr revert -r 1251, test, bzr revert -r 1252, test).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor
sent straight to Qt. Safe mode is a nice blend of
prototyping and full Leo implementation.
I agree.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group
named setuptools
Any idea how to resolve this?
- Install setuptools
- Observe that setup.py install gives you the warning (i.e. it won't work)
- Run setup.py develop
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message
On Thu, Oct 16, 2008 at 3:19 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
And arrows work in tree tab.
Hmm. Arrows work in the tree tab on XP even without this.
Yes, they work now (i.e. you fixed it in earlier commit).
--
Ville M. Vainio
http://tinyurl.com/vainio
handled too late for this).
Just create 2 startup scripts (leoqt and leotk).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
for snippets
is Symbian C++. Python, at least, is so concise that the only
necessary boilerplate is 'if __name__ == '__main__'...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
), but update the
expanded/contracted status on itemCollapsed / itemExpanded signals of
QTreeWidget.
In any case, the current behaviour is a bit surprising. It's not a big
problem, though, and this should already be usable, if not as fast
as it could be.
--
Ville M. Vainio
http://tinyurl.com/vainio
On Thu, Oct 16, 2008 at 3:55 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
Well, that was easy :-) This is definitely going to happen, and
tkinter is going to be demoted to a plugin.
Perphaps it's time to do this now, to get people actually testing and
playing with the plugin.
--
Ville M
while leo is running.
Hopefully this won't matter long, since I'm starting to implement Qt
version of ipython any day now...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
)
sw.setCurrentIndex(1)
Note that I don't think we should rig widgets like this to the core,
and notably not install the event filter for these (since the wanted
behaviour should be dictated by the current widget).
--
Ville M. Vainio
http://tinyurl.com/vainio
On Sun, Oct 19, 2008 at 1:49 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
Here are the items needed before I can use Leo for real:
- Ensure that changes to headlines stick when saving a file.
Seems to work for me.
--
Ville M. Vainio
http://tinyurl.com/vainio
the best choice for code
editing, without reimplementing much (i.e we get pretty much
everything for free).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor
without consuling
core, e.g. by mouse clicks).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
(choosing the right lexer for nodes, etc). The current performance is
not a usability-killer anyway.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group
More stuff:
- Again, expanding doesn't move the tree so that the focus is at
center of the tree pane (I've fixed this a few times already, it
probably got lost again with some change)
- The body pane feels quite a bit slower than the scintilla one. I
don't have any measurements, and I
event.key() would be better? We
can get the actual char by chr(event.key())...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
for a while.
Here's an example of dynamically loading the ui (using uic module):
http://www.riverbankcomputing.com/pipermail/pyqt/2007-April/015902.html
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you
time travel into Leo outlines.
Also consider mercurial for this, it also provides a prorammatic api
(if a bit higher level than bzr, so it might not be applicable). If it
could do the trick, it might be quite a bit faster than the bzr
version..
--
Ville M. Vainio
http://tinyurl.com/vainio
benefits to code quality.
On a related note, you may be interested in python2.6 abc module:
http://docs.python.org/dev/whatsnew/2.6.html#pep-3119-abstract-base-classes
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message
people were
regretting their overuse of interfaces. Interfaces look better on
paper, but in practice they are not all that handy. Apart from
statically typed languages like C++, where they are mandatory layer of
abstraction for many problems.
--
Ville M. Vainio
http://tinyurl.com/vainio
to change when you have an idea what the language
of the node is...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo
with nodes, which nodes you actually edit, etc).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
On Fri, Oct 31, 2008 at 7:37 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
- It needs to be fast, fast, fast. End users reject an editor
immediately if it feels clunky.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message
be nice to separate out the various components
of the leo interface into different windows for use with multiple
desktops, or quick switching to save screen real estate.
Yes, it is easy.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
On Sun, Nov 2, 2008 at 1:35 PM, Kent Tenney [EMAIL PROTECTED] wrote:
Could Leo split out it's panes as windows?
Yes, and this does not require any coding, just fiddling with the ui
designer (once we implement the run-time loading of the ui).
--
Ville M. Vainio
http://tinyurl.com/vainio
for better first impression. QTextEdit is still
too slow to use comfortably (IMHO).
- The scintilla widget should choose the lexer according to the
programming language (on @nocolor, @killcolor...).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You
delegates to use. Perhaps we
can use the default drawer for most items, but have custom delegates
for some items. That's something to expore anyway, it will grant
infinite flexibility.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
still broken:
- When focus is on tree, ctrl + i does not work.
- The change is not applied to the tree. See it by:
* focus body, press ctrl +i, enter text, press enter
* Repeat = it turns back to NewHeadline
--
Ville M. Vainio
http://tinyurl.com/vainio
On Mon, Nov 3, 2008 at 9:37 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
On Mon, Nov 3, 2008 at 9:33 PM, Ville M. Vainio [EMAIL PROTECTED] wrote:
- When focus is on tree, ctrl + i does not work.
The same applies to tree manipulation (e.g. ctrl+R). If it matters,
I'm using the scintilla
It seems PySmell now supports emacs and textmate - maybe leo won't be
a problem either?
http://orestis.gr/blog/2008/11/02/pysmell-v07-here-supports-emacs-textmate-and-vim/
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received
On Tue, Nov 4, 2008 at 2:15 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
This will work, is easy to implement and will be fast. In fact it's so
obvious that I feel a slight shame for not thiniking of it before:
Actually, I may have an idea why this hasn't been done before - we
didn't have
On Tue, Nov 4, 2008 at 2:15 AM, Ville M. Vainio [EMAIL PROTECTED] wrote:
This will work, is easy to implement and will be fast. In fact it's so
obvious that I feel a slight shame for not thiniking of it before:
There is a dir ~/.leo/filecache
It has file named after md5 sums
is a
premature optimizations, since it can mean lots of disk space (i.e.
the difference between having to clean up the cache dir few times per
month, as opposed to never having to clean it).
Also, computers with small drives are becoming commonplace (e.g. asus
eee 700 only has a 4gig flash drive).
--
Ville M
offsets is the right way to go, but that
optimization can be done later.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send
, you can create the whole thing
from scratch, but you need to have the widgets with the same names
(treeWidget, tabWidget...) and types.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed
somewhere, right?
Yes, that dict can be pickled as well.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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
On Tue, Nov 4, 2008 at 9:07 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
BTW, are there any source (QDesigner) files for the gui work that
you have done? If so, could you add them to the repository?
qt_main.ui is the source file.
--
Ville M. Vainio
http://tinyurl.com/vainio
.
BTW, if you get new layouts done, do push them to launchpad so others
can play with them as well...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post
, it's because of a new feature in Qt4 that does double-buffering
automatically.
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group
And, if you sceptical about whether this will increase the performance
that much (since we need to read in files to acquire md5sums anyway),
here are some benchmarks for just using md5sums program (python md5
module is written in c as well):
Second run:
%time md5sum core/*.py
...
CPU times:
On Wed, Nov 5, 2008 at 3:35 PM, Edward K. Ream [EMAIL PROTECTED] wrote:
qt_main.ui is the source file.
Is this file all that I would need to use the designer tool?
Yes. Handy :-).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You
with overriding the qtGui code in a script.
The dicts that map list item positions to leo positions are freely
accessible. They can be used with setItemWidget for good effect (but
this needs some testing).
--
Ville M. Vainio
http://tinyurl.com/vainio
if $Q
Where c.h runs any_child_match_head(node, childhead)
Implementation is quite trivial.(just run eval and present the hits).
I might add this to my qt quicksearch plugin if I get bored ;-)
Is this what you wanted?
--
Ville M. Vainio
http://tinyurl.com/vainio
the body editor features that
much...
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
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 /usr/local/lib with debug symbols, ensure that
it get used, and run it in gdb (or analyze the coredump with gdb).
--
Ville M. Vainio
http://tinyurl.com/vainio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
leo-editor
released and is available from the usual place.
It is based on Scintilla v1.77 and also includes some minor API
enhancements.
Phil
___
QScintilla mailing list
[EMAIL PROTECTED]
http://www.riverbankcomputing.com/mailman/listinfo/qscintilla
--
Ville M
and still use
leo to handle it. It's done by @thin or @shadow nodes. So any kind of
text retrieval program is not needed.
This is leo source code itself is managed as well (you can see that
it's all in leo*.py files, with special sentinels to denote tree
structure).
--
Ville M. Vainio
http
101 - 200 of 2371 matches
Mail list logo
