<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Georgia">Fundamentally, the question is whether you are
trying to create a new kind of windowing behavior (if so,
subclassing may be the right approach) or if you just want your
new widget inside a window for ease of moving, collapsing,
expanding, etc (if so, </font>adding your morph to a plain
SystemWindow is probably better).<br>
<br>
Also ask yourself if you could ever want more than one of your
widgets inside a single window. Or if you could ever want your
widget naked in the World or inside some other graphical structure.
Yes to any of these is a further indication to move away from
subclassing and toward assembling components into larger components.<br>
<br>
Cheers,<br>
Bob<br>
<br>
On 2/5/12 10:16 AM, Dave Mason wrote:
<blockquote
cite="mid:E55F0A02-8F9A-4C1B-B7F1-D37B128CC403@mason-rose.ca"
type="cite">
<pre wrap="">On 2012-Feb-5, at 10:11 , Bob Arning wrote:
</pre>
<blockquote type="cite">
<pre wrap="">One thing to consider is whether you really want to subclass SystemWindow or if it might be better to instantiate a vanilla SystemWindow and install your specialized morph inside it.
</pre>
</blockquote>
<pre wrap="">
What are the considerations for one approach over the other? (In broad terms - not asking for a tutorial here! :-)
Thanks ../Dave
</pre>
</blockquote>
</body>
</html>