From: Eric W. <scr...@gm...> - 2007-03-17 20:16:55
|
# from Mark Dootson # on Saturday 17 March 2007 11:22 am: >Eric Wilhelm wrote: >> IS NOT SMALLTALK! No matter what wxglade or other tool does, it >> still has to generate a text file, which is an all-or-nothing >> operation. Even with the "start" and "end" markers, you're left with >> a blob of code that can't be changed in your editor. It's a one-way >> street, which means the workflow is perverted into something like >> "make, then edit." Until a gui tool can deal with *incoming* >> changes to the code, we're not even close to solving this. > >Nah. > >Have the GUI tool generate a separate template class from which you >inherit. Never edit the template class 'cause it just has your window >construction stuff in it. >Edit your derived class in whatever you like. > >So that's it solved. Right, and that's what I was doing until I ran into problems. It's not solved because it's still a one-way street, wxglade still generates code that doesn't do what I want in some cases, drops menu-items on the floor (requiring me to maintain a mirror of numeric ID's), etc. If it were solved, I would be a happy clam, but I'm not. --Eric -- Those who cannot remember the past are condemned to repeat it. --George Santayana --------------------------------------------------- http://scratchcomputing.com --------------------------------------------------- |