|
From: Patrick K. O'B. <po...@or...> - 2002-02-07 19:35:17
|
If you examine an object in the PyCrust namespace tree you will see that it is easy to get the source code for a particular method of an object. So it wouldn't be impossible to do a VB-like edit-the-code-behind-the-object IDE environment. Or at least position the user on the relevant starting point in the code file. (Which Kevin's FindFiles app already does as well.) --- Patrick K. O'Brien Orbtech > -----Original Message----- > Kevin Altis wrote: > [snip] > > We already have the Shell component, we just continue to use PyCrust. > > > In the "six blind men describe the beast" thread, Neil Hodgson said: > "Writing a small editor isn't all that hard. I don't expect the initial > version of an editor for PythonCard that handled the vast > majority of needed > features would take long at all. You can get tied up in details > though. The > biggest question to me would be how do you determine which files > are part of > a PythonCard project and where within those files are the event > handlers? Do > you do VB style file segmentation or just present the whole file to the > user?" > > ka |