I'm not sure if it's mostly a question of
"You're-most-comfortable-with-what-you-learn-first", but I found that for
most of my SuperCard projects, I preferred using an environment that "keeps
out of my way", graphically speaking.
For example, I was alot more comfortable using SC 2.x's "Runtime
Editor"(RTE) than v3.x's "Project Editor"(PE). I like the fact that the few
palettes (in the RTE) are mostly vertical, long and narrow, and can be
easily kept at the side of the screen. I prefer the dialogs used to set
individual object preferences to a whole mess-o'-buttons on a toolbar or
palette. I also like the availability of just about everything from the
menus, if desired (menus stay out of the way when you don't need them).
I also prefer having the RTE (this is also true for the HC editor) kept
running constantly, i.e., not like the PE, which has a "run" and "edit"
mode. For editing with scripts "off", a utility like SuperEdit is more
predictable and flexible in its function. (Incidentally, I rarely used SE
-except to "set up" a project at the start- when I was using the RTE, but
more recently I find that I use SE alot more, as a more predictable "edit"
mode than is offered by the PE.)
But what about the project browser feature of the PE?
For a time I was using OMO, and someone (I don't have the name handy at the
moment) produced an object browser (a library stack) which worked well in
OMO's RTE-like editing/running environment.
(I'm well aware that others do not share my views, and I do not mean to
belittle the amazing effort that produced a tool such as the PE; I certainly
could not have done it myself!)
So, that's my 2 or 3 cents...
-Kurt
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
