At 08:08 PM 5/29/2001 -0500, Ian Bicking wrote:
>Python code is well-structured and far richer than what a spreadsheet
>can represent, because it structures it in a grammar. No novice is
>ever going to edit a model description, so it's no hinderance to use.
I've had novices read MK models and glean much information from them. Heck,
I even have users reviewing models so they know what information is being
tracked and can speak up if something is missing.
Furthermore you can use a model in combination with code to do things. For
MiddleKit models, we have SQL creation statements, runtime SQL code, HTML
input forms and HTML tables.
There's a place for models and there's a place for general programming code.
>Probably. But I think a good English description is useful too, and
>general enough to be all-encompassing, flexible enough to be as formal
>as you desire. And it's easy to inline ASCII representations of the
>description, and I suppose possible (though more difficult :) to
>inline spreadsheets.
You can't generate anything precise off of an English description, which in
general can't be reasonably formalized (while still being worthwhile to
read, write and parse for these purposes).
>I mean, I'm not *opposed* to them or anything. It just always seemed
>like organizational cruft to me, but I've never actually been in a
>situation where they've been used.
I'll have to hire you some day, so I can make you use models, config files,
metadata, etc. :-)
-Chuck
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
