|
From: Alex T. <al...@tw...> - 2005-07-26 22:45:49
|
Kevin Altis wrote:
> On Jul 26, 2005, at 2:59 PM, Alex Tweedly wrote:
>
>> Kevin Altis wrote:
>>
>>>
>>> So, again my suggestion is that your resourceEditor be added to
>>> tools as its own directory and files.
>>>
>> Cool, I'll do that.
>> (btw - it's only 4 files that have changed plus two new ones added -
>> but they amount to 3400 out of a total of just over 4000 lines, so I
>> don't think there's noticeable saving from keeping the unchanged
>> files in common).
>>
>> I'll see if there's any feedback on the self-adjusting layout, and
>> expect to do the commit this week (pending any other opinions in
>> response to this)
>>
>
> Hmm, if it is only four files, then it might be better to just do some
> module name changes if that is possible. This would be similar to how
> codeEditorR was done, which would give you the option of subclassing
> if that makes sense. What are the four files and what dependencies do
> they have that would cause problems?
>
It changes
resourceEditor.py
modules/resourceOutput.py
modules/propertyEditor.py
modules/propertyEditor.rsrc.py
and adds
modules/multiComponents.py
modules/multiComponents.rsrc.py
The two that matter - resourceEditor.py and propertyEditor.py are both
fairly extensively changed. I can't see how it could be done by
subclassing - but I'll go look at the codeEditoR some more in case I'm
over-estimating the problems.
--
Alex Tweedly http://www.tweedly.net
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.4/57 - Release Date: 22/07/2005
|