On Jan 4, 2007, at 4:30 PM, Carl Karsten wrote:
> How about keeping the class code in the cdxml, which will promote
> the "event's
> call methods" practice: the .hit code in the cdxml will just be
> something.ImHit() in some module that can be edited with my
> favorite editor?
Does your editor properly handle Python code within XML? Does it
know to switch syntax coloring and block comment style when you move
from an XML section to Python code in a CDATA section?
If so, let me know, and I'll switch to that editor in a heartbeat.
Until then, the overwhelming choice of users is to keep the Python
code in a separate file. Of course, that's something you can
configure for yourself (Menu: File/Single File for Layout and Code)
> There shouldn't be lots of code in the UI anyway, right?
There should be as much as is needed. Look as the ClassDesigner*.py
files: they are 100% UI code. Is that too much?
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
