From: Mark D. <mar...@zn...> - 2007-03-17 21:13:25
|
Eric Wilhelm wrote: > 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. > So ... (and sorry for getting all gui designer specific) what's needed is a dialog designer written in perl that gets 80% of things right so you can fix the other 20% to meet your own needs. The thing is, once one has attained the level of basic competence that allows one to make a reasonable job of writing such a thing - one has probably lost a lot of the incentive to do so. I'm just going to attempt to get the ball rolling by shoving something out that does stuff the way I want it to. With regard to your WxPerl::Declares section, the main attraction to me is getting named accessors for your child controls /menus /toolbars etc. I think I'd consider something a touch more verbose involving Class::Accessor::Fast. As it stands, the syntax does look very inaccessible. Good luck with it. Mark |