[MonoDevelop] Designer Problems
m.j.hutchinson at gmail.com
Wed Oct 19 19:24:22 EDT 2011
On Tue, Sep 13, 2011 at 3:00 PM, Bradley M. Small <bradley_small at hotmail.com
> This raised a few questions in my mind. Wouldn't it make more sense to have
> one stetic.gui file for each widget? As it is there is one hidden .CS file
> for each one which makes sense, but if I wanted to do some cut and paste
> code reuse, I could easily move the hidden .CS file, but would have to break
> apart the stetic.gui file. Is there a design philosophy that I am missing
> (was not able to find any documentation on this) that mandates the
> stetic.gui to be monolithic to a project? Doesn't this cause all the hidden
> files to have to be remade whenever you make a change to just 1 of them?
> I had designed a complex window in my MainWindow widget. Later, I decided
> that I wanted to have multiple window instances that are all the same, so I
> manually cut and pasted in the stetic.gui file to create the GameWindow.
> Seems like this would be better handled if there were more granularity in
> the files. This is just an observation.
Stetic has been much improved by a Summer of Code student over the past two
summers, and one of the improvements is to use one file per widget/window.
It's been developed outside of the MD repository but we hope to integrate it
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Monodevelop-list