Brent,
> All good points. But one way to think about this: does multiple main windows
> *have* to be in there for a successful 1.0? Could it be considered for 1.1 or
> 2.0 instead?
definitely, yes.
but consider this: assuming the proper design and abstraction between data and
view, allowing to open multiple instances of the same main window should, quite
literally, be a question of exposing the option to do so, or not. it should not
be any significant development work to provide the feature.
iow, i'd say that if this is somehow "impossible" with the code base we'll have
for 1.0, then there's something fundamentally wrong with the model that can;t
be easily fixed for 1.1, either.
> It's common, when discussing a particular feature, to magnify its importance.
> (I do it all the time myself.)
>
> But getting to 1.0 is going to be a scarily ruthless process. (Or, it should
> be, anyway.) And the general rule needs to be something more like "does this
> *really* have to be in there for this release to be successful?"
>
> It's okay if users want more. And, no matter what you do, no matter how many
> features are added, people will *always* want more. ("I'd switch to
> Letters.app in a heartbeat if only it _____." If Letters is a success, we'll
> still be hearing that in five and 10 years.)
>
> Maybe this feature really does have to be there for a successful 1.0. (I
> don't know.) I'm just suggesting a way of thinking about design issues like
> this.
completely agreed on the principle.
> PS Should the code be written in a way that doesn't preclude this feature? My
> personal opinion: yes, since in this case that's just good architecture.
exactly. what i'm saying is, if the design and architecture on this is done
properly (which it should be regardless of whether this feature is wanted for
1.0 or not, or indeed wanted at all), this particular feature should come for
free, already. if it does not, that should raise concerns on an entirely
different level.
marc
_______________________________________________
[email protected] mailing list
List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
