RE: [PyCrust] Thoughts...

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

I'm not sure if this gets you exactly what you want, but here is an example.
I modified the wxPython demo file, PyShellWindow.py, to load PyCrust in the
wxPython Demo application. This loads the PyCrust editor into the demo app
the same exact way as the previous one, inside the sliders and all that.
Does this help? (Note that this uses the PyCrust version 0.5.2 module names
and I had to add a docstring to the shell module to keep Main from hanging
at lead = text[:6])


from PyCrust.shell import Shell

#----------------------------------------------------------------------

def runTest(frame, nb, log):
    shell = Shell(nb)
    return shell.editor

#----------------------------------------------------------------------

import PyCrust.shell

overview = PyCrust.shell.__doc__


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

-----Original Message-----
From: pyc...@li...
[mailto:pyc...@li...]On Behalf Of Robin Dunn
Sent: Monday, August 13, 2001 10:26 AM
To: pyc...@li...
Subject: Re: [PyCrust] Thoughts...


> I'd like to see more discussion about this. The Shell and Editor are
> intentionally separate and Shell has no wxPython code. If you want more
> control over the location of the Editor, you can. It's just a wxSTC
derived
> class. I'm not sure I fully understand what you want to accomplish.

Basically to have a Shell object that is also a window, so I only have to
construct a single object and use it as a window (ie, using all the wxWindow
methods, passing to sizer.Add, etc.) without having to know the guts of the
class to have the knowledge that to do all that I have to use
shellobj.editor to do 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