No subject

Tue Aug 27 04:49:46 EDT 2019

I've done so myself, as I did just last week with the diskspace function.
There is no shame in that, it's just part of being human; we just get the
answer and move on, and it probably helps other readers along the way.  No
big deal.

But to extrapolate that overlooking something obvious always means that
there's something critically wrong with the UI or its documentation is not
likely to hold up in some cases, and in such cases slows the learning
process for others unnecessarily.

We're not talking about cooking, which my failed attempts suggest is hard
enough to learn (for at least this bachelor).  Developing software is an
inherently complex task, and while Rev is arguably among the easiest ways to
accomplish as much as it lets you do, there's only so much it can do to
simplify the process.  A 1000+ token interpreter like Rev's is a complex
system, integrating with even more complex systems like QT, database
engines, and 12 different operating systems.  While imperfect, Rev makes the
software process orders of magnitude more efficient and easier than
traditional methods like C++ or even Pascal (in some cases yielding superior
results), and is far simpler to learn than the world's most popular
scripting language, JavaScript.  And at version 2.0 it's still quite young,
with many areas in which it can learn and grow to make that process ever

There are areas where Rev could better exploit the principle of progressive
disclosure (a long rant about the evils of Photoshop's UI on the evolution
of software design is growing increasingly hard to resist), but as a whole
it's not bad and specific suggestions for improvement seem to be heard.

More information about the use-livecode mailing list