Ed Leafe wrote:
> On Jun 5, 2006, at 2:52 PM, Uwe Grauer wrote:
>
>> Custom methods would get referenced from the new class.
>
> OK, you lost me here. What new class? Right now in my mind there is
> only a single class: the one defined in the .cdxml file.
>
A newly derived class.
class DaboGenerated:
def amethod(self, ...):
pass
class MyClass(DaboGenerated):
def amethod(self, ...):
...
>> How should dabo know beforehand that any function would call this custom
>> method? That's the reason i think there should be stubs for functions
>> dabo would call.
>
> We're not talking about Dabo calling the functions; we're talking
> about binding code to events. The code has to exist in order for this
> binding to occur. If the code exists somewhere outside of the class, how
> is the class supposed to know it's there?
>
>> If this would not work, we could just write out a new class form
>> dabo-generated code and the additional code which comes from the extra
>> code-file.
>
> But that's easier said than done. In the .cdxml file, code is
> explicitly bound to the object by the XML structure. But let's say that
> there are 5 buttons on the second page of a 3-page pageframe that is
> sitting on a panel inside a frame, how would you propose that some code
> in a separate .py file be linked to the Hit event of the third button in
> that group?
>
>
> -- Ed Leafe
> -- http://leafe.com
> -- http://dabodev.com
Didn't think that much about it.
But you are right, it seems to be hard to do.
Anyway, i do not like it as it is now.
I want to take a look at all of my classcode at once.
I do not like to only look at one function at a time.
Perhaps the new functionality to have the classcode in
temp-files is enough to get me happy.
Uwe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
