RE: [PyCrust] Thoughts...

[Patrick K. O'B. <po...@or...>]

I think we're on the same page now, thanks. The problem is mostly my
ignorance of wxPython, but I'm working on that. I just started doing some
pretty hefty refactoring to get you all this and more. I'll keep you posted.

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

-----Original Message-----
From: pyc...@li...
[mailto:pyc...@li...]On Behalf Of Robin Dunn
Sent: Wednesday, August 15, 2001 4:57 PM
To: pyc...@li...
Subject: Re: [PyCrust] Thoughts...

> I'm not sure if this gets you exactly what you want, but here is an
example.

Not quite, I had already done something like that.  What I was saying is it
would be nice if there was a class, say ShellWindow, that had wxWindow as an
ancestor and had the same basic __init__ interface (parent, id, pos, size,
style) plus any extra parameters for the Shell such as a locals dict, intro
text, etc.  That way you wouldn't have to know that the "window" is really
"shell.editor" and not just "shell", and it could more easily be used as a
control/widget/component like any other in app builders like Boa or
wxDesigner.

What I've got:

> from PyCrust.shell import Shell
>
> #----------------------------------------------------------------------
>
> def runTest(frame, nb, log):
>     shell = Shell(nb)
>     return shell.editor
>

What I would like:

from PyCrust.shell import ShellWindow   # or whatever

def runTest(frame, nb, log):
    shell = ShellWindow(nb)
    return shell


Creating a ShellWindow class that derives from both Shell and Editor almost
does it, but there are attribute and method name clashes between the two so
it never quite worked right when I tried it.



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





_______________________________________________
PyCrust-users mailing list
PyC...@li...
http://lists.sourceforge.net/lists/listinfo/pycrust-users