Hi Franz,
Hello Adi,
startup is slower (if I start it from cmd line, the black screen is visible (behind the frame)
some problems to compare (it was not the last version, I uploaded, where you based the changes)
I have separated filling window and shell, because in filling coloring makes no sense (at least for me).
The intro is not coloured in my version (I don't like it).
Well, currently it uses the built in python lexer for filling as it was before,
it could be activated for filling if wanted.
the coloring of methods or instances is somewhat mysterious (see screenshot for the word "shell")
http://mitglied.lycos.de/drpython/ClipBoard-version-ajs.png
Sometimes it is coloured, sometimes not.
Forgot that one. I just works for methods and functions
in the namespace not as part of an object.
Did you try to find "known" variables or instances? for example wx, shell, Frame?
Then this could be a powerfult feature!
Yes, this is implemented. I use the list returned by get autoCompXXXXX
I like the coloring of the braces.
Taken a short glance of your source:
Interesting solution (thats what I like on creating different versions, both could
learn from the other:))I like the source code, it is very clean; also the solution with the EVT_LEX_CONTAINER
and EVT_STC_STYLENEEDED and the usage of constants.
Also the evaluation of the tokens is more accurate.For me applies: if I make some experiments or prototype, at first place
i don't care on good code style. Only if I'm sure before,
things work, I pay more attention to this
I like using some basic good code style, because I never have the time/nerve
to change it. That's why I always use constants, etc. pp.
I suggest, let other users and/or Robin Dunn decide, what to use.
I imagine and admit, your solution with the EVT_STC_STYLENEEDED is cleaner and more lucid, and in the sense of the philosophy of the stc.
Well, let's see.
adi