[wxPython] wxIDLE (just an idea)

this is just an idea...
"Why the hell hasn't wxPython become the standard GUI for
Python yet?" Eric S. Raymond is quoted on the wxPython home
page.
One of the symbols of Tkinter being the quasi standard GUI of
Python is IDLE. I think something like a "wxIDLE" could serve as a
very effective hint to demonstrate the qualities of wxPython vis-à-vis
Tkinter. It would probably be a good idea not to start from scratch
but with with the Editor of Boa (if that is ok with Riaan Booysen) so
wxIDLE would be kind of a little brother to Boa (my only objection
to Boa being that it will perhaps take a long time until it is finished,
just because it is so huge.)
If someone now says:"good idea, go ahead," then I must admit,
that I'm not an experienced programmer and would not dare to start
on such a challenge on my own. (However, I promise to do some
help on simple (and probably boring) tasks if someone does.)
Christoph

Good idea, go ahead. :sunglasses:

I just created a sourceforge project (nothing there yet).

Does anyone want to help? We could start with a web page. I can set up a wiki for ideas.

I use vi for most of my editing, but I do like the browser features in idle.

···

CCF.Herzog@gmx.net wrote:

If someone now says:"good idea, go ahead," then I must admit, that I'm not an experienced programmer and would not dare to start on such a challenge on my own. (However, I promise to do some help on simple (and probably boring) tasks if someone does.)
Christoph

Terrel Shumway wrote:

We could start with a web page.

Cut and paste from IDLEfork: http://wxidle.sourceforge.net/

I can set up a wiki for ideas.

Please contribute: http://wxidle.sourceforge.net/cgi-bin/wiki/

You might want to look at PyCrust. It is only the shell (it doesn't have a
file editor or debugger), but it does use wxPython.

···

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: wxpython-users-admin@lists.wxwindows.org
[mailto:wxpython-users-admin@lists.wxwindows.org]On Behalf Of Terrel Shumway
Sent: Wednesday, August 08, 2001 12:32 PM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] wxIDLE (just an idea)

CCF.Herzog@gmx.net wrote:

If someone now says:"good idea, go ahead," then I must admit,
that I'm not an experienced programmer and would not dare to start
on such a challenge on my own. (However, I promise to do some
help on simple (and probably boring) tasks if someone does.)
Christoph

Good idea, go ahead. :sunglasses:

I just created a sourceforge project (nothing there yet).

Does anyone want to help? We could start with a web page. I can set up
a wiki for ideas.

I use vi for most of my editing, but I do like the browser features in idle.

_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users

One of the symbols of Tkinter being the quasi standard GUI of
Python is IDLE. I think something like a "wxIDLE" could serve as a
very effective hint to demonstrate the qualities of wxPython vis-�-vis
Tkinter. It would probably be a good idea not to start from scratch
but with with the Editor of Boa (if that is ok with Riaan Booysen) so
wxIDLE would be kind of a little brother to Boa (my only objection
to Boa being that it will perhaps take a long time until it is finished,
just because it is so huge.)

I had thought seriously about doing it a few times, and then Boa came along
and I was relieved that Riaan would be the primary on that and I wouldn't
have to worry about an IDLE clone. When I realized how much *more* Boa was
going to be than what I had planned I was even happier.

Now Boa has taken a long time (understandably) and still has a ways to go,
(also understandably.) So when I got a sneak peak at PyCrust a while back I
started thinking about doing a wxIDLE again. Now Terrel and others have
stepped up to work on it (and Patrick with PyCrust) and once again I am
relieved that I don't have to worry about it and can continue to focus on
wxPython itself. (Isn't Open Source grand?!?!)

My one request for wxIDLE: Be sure to design it with a plug-in
architecture. (Plug-in Editors: code editor, layout editor, menu editor,
etc. Plug-in Tools: simple debugger, remote debugger, Bob's debugger,
class browser, PythonCard, etc...) I don't know much about IDLEfork but I
think that is why IDLE hasn't progressed much, it's too hard for people to
add new capabilites without disrupting the whole thing. (In that light,
thinking of it as "IDLE - tkinter + wxPython" may not be a good thing.) If
people can easily work on individual plug-ins without impacting other
plug-ins or the framework then many more people can contribute to the
project.

···

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!

You might want to look at PyCrust. It is only the shell (it doesn't have a
file editor or debugger), but it does use wxPython.

PyCrust download | SourceForge.net

I'll also reccommend PyCrust to be included in wxIDLE or any similar
project. I was quite impressed with it when I played with it a few days
ago. In fact I've been thinking of deprecating the Python shells currently
in the wxPython library and putting snapshots of PyCrust in the distribution
instead. (Is that okay with you Patrick?)

···

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!

Hi Christoph and Terrel,

this is just an idea...
"Why the hell hasn't wxPython become the standard GUI for
Python yet?" Eric S. Raymond is quoted on the wxPython home
page.
One of the symbols of Tkinter being the quasi standard GUI of
Python is IDLE. I think something like a "wxIDLE" could serve as a
very effective hint to demonstrate the qualities of wxPython vis-à-vis
Tkinter.

Boa tries hard to do just that.

It would probably be a good idea not to start from scratch
but with with the Editor of Boa (if that is ok with Riaan Booysen) so
wxIDLE would be kind of a little brother to Boa (my only objection
to Boa being that it will perhaps take a long time until it is finished,
just because it is so huge.)

Boa is your wxIDLE.
This is the *primary* role that Boa tries to fulfill, GUI building,
Zope, etc are secondary for me. This is complete overlap!
The IDE/Editor component that you talk about is ready for use in Boa,
stable and offers equivalent functionality to IDLE.

With the next release (soon!) the version number will be 0.1.0 and Boa
will go alpha, further releases will bump the second digit and major
CVS updates bumping the last.
Most people familiar with Boa should know that it is much more
complete than the version number suggests.
My own milestone is to deliver a stable Boa that will be feature
complete (the beta) before the end of the year.

Also, something which might cause people to think, "this app is too
big we need something smaller", has been the resource usage (esp. on
win9x but also menu problems on NT/2000)
I've really spend some time on this problem since the 0.0.5 release
and things have improved a lot!
To people who have had doubts about wxPython because of Boa's resource
usage, mea culpa, I'm sorry.
There were a few naive 'non-scalable' strategies like storing menus and
caching pictures have been fixed or made optional.
The bottom line is that on windows, windows resources is a limited
resource no matter how much memory you have and any app of
significant size needs to be aware of it's resource management.
It was not wxPython fault, blame it on Bill and me.

If someone now says:"good idea, go ahead," then I must admit,
that I'm not an experienced programmer and would not dare to start
on such a challenge on my own. (However, I promise to do some
help on simple (and probably boring) tasks if someone does.)
Christoph

I don't think this is a good idea, and am against yet another ide.
Please help out with Boa. Even if it is with decoupling components so
that more of Boa can be switched on and off at will :wink:
This idea to have more of the components in Boa optionally turned on or
off was mentioned on the Boa mailing list again very recently.
This is something Boa does already (you may turn off the Zope, FTP
and other transport support if you choose) but this can be taken much
further. This will also lessen newbie feature overdose/confusion.
Thoughts? Problems?

Why not work together on a wxPython IDE for Python instead of
dividing resources and duplicating work? Boa aready does everything
you want, you can help make it work the way you want it.

···

CCF.Herzog@gmx.net wrote:

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

One of the symbols of Tkinter being the quasi standard GUI of
Python is IDLE. I think something like a "wxIDLE" could serve as a
very effective hint to demonstrate the qualities of wxPython

vis-à-vis

Tkinter. It would probably be a good idea not to start from scratch
but with with the Editor of Boa (if that is ok with Riaan Booysen)

so

wxIDLE would be kind of a little brother to Boa (my only objection
to Boa being that it will perhaps take a long time until it is

finished,

just because it is so huge.)

[...]
My one request for wxIDLE: Be sure to design it with a plug-in
architecture. (Plug-in Editors: code editor, layout editor, menu

editor,

etc. Plug-in Tools: simple debugger, remote debugger, Bob's

debugger,

class browser, PythonCard, etc...) I don't know much about IDLEfork

but I

think that is why IDLE hasn't progressed much, it's too hard for

people to

add new capabilites without disrupting the whole thing. (In that

light,

thinking of it as "IDLE - tkinter + wxPython" may not be a good

thing.) If

people can easily work on individual plug-ins without impacting

other

plug-ins or the framework then many more people can contribute to

the

project.

I'm going to write an editor with wxpython, it's temporary name is
Galileo, but I have 2 big problems: my English and that I'm not an
expert programmer. To solve the second problem I'm writing a plug-in
interface so I have to write only a little part of the editor and
anyone can create plug-ins (for instance to manage C++ files, Ruby
files...).

Marco Barisione

Hi Christoph and Terrel,

With the next release (soon!) the version number will be 0.1.0 and Boa
will go alpha, further releases will bump the second digit and major

I'm looking forward to this

I don't think this is a good idea, and am against yet another ide.
Please help out with Boa. Even if it is with decoupling components so
that more of Boa can be switched on and off at will :wink:

I am no expert in IDLE, and just started to use Boa - but I think I can support
that. Boa appears to be stable enough (never crashed or lost data), even when
it appears to be slowish (linux / Celeron 500 / 128 MByte)

The interface might not be fully intuitive, but after following the Getting
Started Guid, I didn't need much more documentation, except the wxPython, ...
things I had to learn about.

Thanks,

Horst

This idea to have more of the components in Boa optionally turned on or
off was mentioned on the Boa mailing list again very recently.
This is something Boa does already (you may turn off the Zope, FTP
and other transport support if you choose) but this can be taken much
further. This will also lessen newbie feature overdose/confusion.
Thoughts? Problems?

Why not work together on a wxPython IDE for Python instead of
dividing resources and duplicating work? Boa aready does everything
you want, you can help make it work the way you want it.

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users

Horst@freedict.de
Horst Eyermann
Germany

You need a dictionary? - visit http://www.freedict.de
for free (GPL) dictionaries (unix; windows work in progress)
For windows, visit http://www.freedict.de/wbuch

A article (in German) about dictionary efforts on the net
http://www.heise.de/tp/deutsch/inhalt/on/5927/1.html

···

On 09-Aug-01 Riaan Booysen wrote:

Riaan Booysen wrote:

Hi Christoph and Terrel,

>
> this is just an idea...
> "Why the hell hasn't wxPython become the standard GUI for
> Python yet?" Eric S. Raymond is quoted on the wxPython home
> page.
> One of the symbols of Tkinter being the quasi standard GUI of
> Python is IDLE. I think something like a "wxIDLE" could serve as a
> very effective hint to demonstrate the qualities of wxPython vis-à-vis
> Tkinter.

Boa tries hard to do just that.

And does a very good job of it, imo. Boa is my favorite editor for any
python project, not just ones involving wxPython. While I do also use IDLE
and PythonWin, nine times out of ten you'll find me using Boa.

> It would probably be a good idea not to start from scratch
> but with with the Editor of Boa (if that is ok with Riaan Booysen) so
> wxIDLE would be kind of a little brother to Boa (my only objection
> to Boa being that it will perhaps take a long time until it is finished,
> just because it is so huge.)

Boa is your wxIDLE.
This is the *primary* role that Boa tries to fulfill, GUI building,
Zope, etc are secondary for me. This is complete overlap!
The IDE/Editor component that you talk about is ready for use in Boa,
stable and offers equivalent functionality to IDLE.

I agree completely. In addition, Boa has features that I would hate to be
without: being able to bookmark directories, presenting all open python
files as tab pages, remembering which files were open from session to
session (great when you are working on the same set of files day after day),
a tree-like explorer view of source code files (great for finding stuff in
other people's files and getting an handle on just what exactly is
available), a shell editor always available as the first tab in the editor,
etc. Boa is chock full of really wonderful features.

<snip>

> If someone now says:"good idea, go ahead," then I must admit,
> that I'm not an experienced programmer and would not dare to start
> on such a challenge on my own. (However, I promise to do some
> help on simple (and probably boring) tasks if someone does.)
> Christoph

I don't think this is a good idea, and am against yet another ide.
Please help out with Boa. Even if it is with decoupling components so
that more of Boa can be switched on and off at will :wink:
This idea to have more of the components in Boa optionally turned on or
off was mentioned on the Boa mailing list again very recently.
This is something Boa does already (you may turn off the Zope, FTP
and other transport support if you choose) but this can be taken much
further. This will also lessen newbie feature overdose/confusion.
Thoughts? Problems?

Why not work together on a wxPython IDE for Python instead of
dividing resources and duplicating work? Boa aready does everything
you want, you can help make it work the way you want it.

Again, I have to agree. Please don't read this as an attempt to derail
anyone's efforts to start something new. Instead, consider this is an
invitation to leverage a great code base and make it better. I have found
Riaan to be surprisingly receptive to suggestions, ideas and patches, and I
think you will too. If you browse the CVS you'll see that Riaan releases
improvements to Boa on an incredible pace. I don't know how he does it. Now
is the time to bring other developers into the effort. I don't think anyone
who wants a wxIDLE-thingie would be disappointed by jumping on the Boa
bandwagon.

···

CCF.Herzog@gmx.net wrote:

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

Robin Dunn wrote:

wxIDLE would be kind of a little brother to Boa (my only objection
to Boa being that it will perhaps take a long time until it is finished,
just because it is so huge.)

I had thought seriously about doing it a few times, and then Boa came along
and I was relieved that Riaan would be the primary on that and I wouldn't
have to worry about an IDLE clone. When I realized how much *more* Boa was
going to be than what I had planned I was even happier.

I am not familiar with Boa. I will have to check it out.

Now Boa has taken a long time (understandably) and still has a ways to go,
(also understandably.) So when I got a sneak peak at PyCrust a while back I
started thinking about doing a wxIDLE again. Now Terrel and others have
stepped up to work on it (and Patrick with PyCrust) and once again I am

PyCrust is also on my list.

relieved that I don't have to worry about it and can continue to focus on
wxPython itself. (Isn't Open Source grand?!?!)

My one request for wxIDLE: Be sure to design it with a plug-in
architecture. (Plug-in Editors: code editor, layout editor, menu editor,
etc. Plug-in Tools: simple debugger, remote debugger, Bob's debugger,
class browser, PythonCard, etc...) I don't know much about IDLEfork but I
think that is why IDLE hasn't progressed much, it's too hard for people to
add new capabilites without disrupting the whole thing. (In that light,
thinking of it as "IDLE - tkinter + wxPython" may not be a good thing.)

I have never looked at idle's guts to know how it is organized, but my sense is that tkinter does not ecourage good design. In saying "IDLE - tkinter + wxPython" I was thinking more on a functional level. It would be nice to be able to share code (IDEs are a good place to reuse code), but I know that the warts of legacy code are often the very motivation to start fresh.

If
people can easily work on individual plug-ins without impacting other
plug-ins or the framework then many more people can contribute to the
project.

Plugins are an essential feature. For example, I like the browser functions of IDLE, but my fingers are hopelessly configured for vi for editing. My vision for architecture is something along the lines of netbeans -- the IDE serves only to *integrate* the functionality of the plugins.

That is more than okay with me. In fact, I would be honored. Let me know
what I need to do to make this feasible.

···

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: wxpython-users-admin@lists.wxwindows.org
[mailto:wxpython-users-admin@lists.wxwindows.org]On Behalf Of Robin Dunn
Sent: Wednesday, August 08, 2001 9:44 PM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] wxIDLE (just an idea)

You might want to look at PyCrust. It is only the shell (it doesn't have a
file editor or debugger), but it does use wxPython.

PyCrust download | SourceForge.net

I'll also reccommend PyCrust to be included in wxIDLE or any similar
project. I was quite impressed with it when I played with it a few days
ago. In fact I've been thinking of deprecating the Python shells currently
in the wxPython library and putting snapshots of PyCrust in the distribution
instead. (Is that okay with you Patrick?)

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!

PythonCard is a software construction kit (in the spirit of Apple's
HyperCard) written in Python.

Prototype release 0.3.1 contains ten sample applications to show off the
features of the latest PythonCard prototype. Sample screenshots are at:
http://pythoncard.sourceforge.net/samples.html

Latest release files:
http://sourceforge.net/project/showfiles.php?group_id=19015

PythonCard home page
http://pythoncard.sourceforge.net/

SoureForge summary page
http://sourceforge.net/projects/pythoncard/

Mailing list
http://groups.yahoo.com/group/pythoncard

0.3.1 changelog:
Fixed line ending problems with PyCrust files that caused 0.3 release to not
work correctly on *nix systems. Also, removed the background.gif file from
the proof sample which is not needed.

0.3 changelog:
Changes:
added changelog.txt and readme.txt files
menubar is now optional
    if a 'menubar' key is not found in a Stack's resource file then a
menubar
    won't be created.
log.py documented
    proof.py updated to work with log.py changes
MessageEvent was removed from proof.py since message sending
    between widgets is currently disabled
The working directory is changed to the directory of the main resource file
    such as minimal.rsrc.py when PythonCard starts up to avoid problems
    with filenames in the .rsrc.py files and any data files used by the
    application.
Property Editor and Shell windows can be overlapped by the main app window
    Due to a bug, the Message Watcher must still remain on top
added getCurrentBackground to PythonCardApp class
PythonCard now includes PyCrust (-s on command-line)
    interactivePrompt renamed to shell, all references changed
    PyCrustFrame class moved to debug.py along with test for PyCrust import
    PyCrust shell is version 0.3
PythonCard turned into PythonCardPrototype package
    All samples changed to use the new package naming
    All samples can now be run "standalone" so any _standalone.py
    files in the samples have been removed.
    __version__.py contains the current release number
    New cvs tree on SourceForge, the old proto tree is no longer used
PythonCard.py renamed to loader.py and loader.py overhauled
added deleteWidget method
added find, deprecated findByName
added turtle graphics sample
added a Property Editor (-p on command-line)
    due to time constraints, the Property Editor is only a property viewer
    in this release. You can use the set methods for widgets to change
    values inside the shell if you need to.
added gainFocus and loseFocus messages to all widgets
added StaticLine widget
ComponentSpec and AttributeSpec classes added to enhance parsing of spec.py

ka

···

---
Kevin Altis
altis@semi-retired.com

Maybe Boa's a good idea in its way and works perfectly for most things,
however I gave up on it because I wanted to do something quite simple: make
a tabbed notebook based application, and the code it produced simply
crashed; not just the code, as I recall, but boa as well. I haven't the time
to fling emails back and forth for days for something like that. I simply
used another tool that could do what I wanted: I built one by hand that
worked.

Ron

Hi Ron,

Ron Williams wrote:

Maybe Boa's a good idea in its way and works perfectly for most things,
however I gave up on it because I wanted to do something quite simple: make
a tabbed notebook based application, and the code it produced simply
crashed; not just the code, as I recall, but boa as well.

Just tried it, works for me...

I can't really tell from the above when the crash occured.
If your use the Run module option, the module is run in a seperate
process. If this new process crashes, it cannot crash the first
process. If it does, it's not my fault and there is nothing I can do
about it (out of process is usually as safe as you can get short of
running it on another machine :wink:

I haven't the time
to fling emails back and forth for days for something like that. I simply
used another tool that could do what I wanted: I built one by hand that
worked.

There is one thing you have to remember when working with a wxNotebook
in the Designer: When you add a new page to the notebook, the red dashed
area on the new page signifies an area that must receive a control.
I've tried before to have this generate a warning when you close the
Designer, but it wasn't easily doable at the time. I'll try again.

If it was something else, it could have been fixed by now if you had
reported it, who knows, maybe it was fixed after someone did take the
time to report it.

Seeing that you have brought it up now, do you mind explaining how
to reproduce this? Operating system, wxPython, Boa version?

···

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

That is more than okay with me. In fact, I would be honored. Let me know
what I need to do to make this feasible.

Just let me (or this list) know when there are stable releases in CVS (and
tag them) and I'll just take snapshots of that and copy it to my CVS so it
is already there when I make releases.

···

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!

That's a pretty harsh judgment against a software tool that bills itself as
"alpha" level code. I personally think the code is well beyond the alpha
level, but Riaan will have none of that. He has some pretty high standards,
knows what feature set he considers necessary just to release a "beta"
version, and won't budge an inch on the whole issue. I respect that.

And I would expect to have to work through a few issues using a tool that is
at version 0.0.5. Of course, I use Boa every day, all day long, hardly ever
have a problem and have never lost any code. And I'm hardly the patient
type.

The bottom line is that Riaan bends over backwards to help anyone who is
having the slightest problem with Boa. Even a fool like me who tries to use
the CVS features of Boa without having even read one bit of CVS
documentation. Guess what's included in the latest version of Boa - a CVS
manual in the form of a help file. You gotta love that.

Boa won't be right for everyone. But it can, and does, work. It's getting
better all the time. And I think it is worth the time and effort to get
involved and help it continue to get better.

···

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: wxpython-users-admin@lists.wxwindows.org
[mailto:wxpython-users-admin@lists.wxwindows.org]On Behalf Of Ron Williams
Sent: Thursday, August 09, 2001 7:15 PM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] wxIDLE (just an idea)

Maybe Boa's a good idea in its way and works perfectly for most things,
however I gave up on it because I wanted to do something quite simple: make
a tabbed notebook based application, and the code it produced simply
crashed; not just the code, as I recall, but boa as well. I haven't the time
to fling emails back and forth for days for something like that. I simply
used another tool that could do what I wanted: I built one by hand that
worked.

Ron

_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users

Okay, Robin. Here it is. PyCrust 0.5.2 is now available. The CVS tag is
PyCrust-0-5-2. A zip file with all the sources is also available at:

···

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: wxpython-users-admin@lists.wxwindows.org
[mailto:wxpython-users-admin@lists.wxwindows.org]On Behalf Of Robin Dunn
Sent: Friday, August 10, 2001 1:01 AM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] wxIDLE (just an idea)

That is more than okay with me. In fact, I would be honored. Let me know
what I need to do to make this feasible.

Just let me (or this list) know when there are stable releases in CVS (and
tag them) and I'll just take snapshots of that and copy it to my CVS so it
is already there when I make releases.

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!

Hello,
I started to use a Grid for a large list of words. - I managed to follow the
example in the wxPython demo folder.

But now I would like to change the length and contense of the list (grid) each
time I change the source file.
I tried to set a new reference, and then send it a wxPaintEvent
"self.wxPaintEvent()" - which did not work. Can anyone please explain how to do
it / where I can find more information on handling large lists.

Thanks,

Horst

Horst@freedict.de
Horst Eyermann
Germany

You need a dictionary? - visit http://www.freedict.de
for free (GPL) dictionaries (unix; windows work in progress)
For windows, visit http://www.freedict.de/wbuch

A article (in German) about dictionary efforts on the net
http://www.heise.de/tp/deutsch/inhalt/on/5927/1.html

Hello,
I am using wxPython 2.3.1 on linux, and I try to use a wyGrid in my application.

I have to use a custom Grid due to the size of entries in the Grid ( 100000).
I would like to place the Grid into a wxSplitterWindow, with one single list,
where the cell witdth spans the whole size available from the SplitterWindow.
How would I do this, I did not manage to get the sizing correct.

Another problem I do have is with the double click
(EVT_GRID_CELL_LEFT_DCLICK(..)). My routine is called until the point, when I
change the size of the splitterWindow. After that I can edit the entry, but my
routine is not called anymore. Why?

One last question: some elements respond to the mouse wheel, others do not. Why
is this, and how can I make all Controls resond to mouse wheel events?

Thanks,

Horst