David Burgun wrote:
I learnt Hypercard without a book,
and I extended my knowledge, as RR extended xTalk, in the
same way:
by doing!
That's great if you have all the time in the world to doing it
wrong many times! Especially when the documentaion is just plain
wrong!
As with the spelling
From: David Burgun
RunRev is different in this respect and many times no one seems to
actually know what is *supposed* to happen and I get a number of work
arounds to a problem (from this list mainly) that may or may not work in
all situations.
Wiki?
Dump the online docs into wiki pages,
David Burgun wrote:
This is from the Answer command:
The prompt is a string (or any expression that evaluates to a string).
The dialog box expands if necessary to fit the contents.
This just doesn't happen, in many cases it just gets chopped off. There
are other instances, but I really
I am not so psychologically naive to believe that everybody
will learn xTalk the way I did - and will not have the
luxury of very well paid half-time jobs so that they have
the time to devote to learning it the way I have done.
It is indeed true that the RR documentation is not
comparable with
Hi Dave,
Do you know what kind of book would represent the docs?
In front of me are 2 A4 books (I need my glasses to read them :-)
which were sent to me by Runrev with Rev Enterprise 2.0.
The first one (User Guide) is 370 pages and the other (Transcript
Language Reference) is 570 pages...
I
David Burgun wrote:
This is from the Answer command:
The prompt is a string (or any expression that evaluates to a
string). The dialog box expands if necessary to fit the contents.
This just doesn't happen, in many cases it just gets chopped off.
There are other instances, but I really
Hi Dave,
Do you know what kind of book would represent the docs?
In front of me are 2 A4 books (I need my glasses to read them :-)
which were sent to me by Runrev with Rev Enterprise 2.0.
The first one (User Guide) is 370 pages and the other (Transcript
Language Reference) is 570 pages...
I
Hi Dave,
Le 30 nov. 05 à 16:14, David Burgun a écrit :
Hi Dave,
Do you know what kind of book would represent the docs?
In front of me are 2 A4 books (I need my glasses to read them :-)
which were sent to me by Runrev with Rev Enterprise 2.0.
The first one (User Guide) is 370 pages and the
Hi Dave,
Le 30 nov. 05 à 16:14, David Burgun a écrit :
Hi Dave,
Do you know what kind of book would represent the docs?
In front of me are 2 A4 books (I need my glasses to read them :-)
which were sent to me by Runrev with Rev Enterprise 2.0.
The first one (User Guide) is 370 pages and the
Recently, David Burgun wrote:
It must be as hard or harder to maintain the online docs that
seperate PDF files.
If they made say broke it down into (say) 7 books, it shouldn't be so
hard to do. And as long as the latest updates were available online.
I am not necessarily talking about a
Subject: Re: Constant 'Nonsense' about RR documentation
There was at one point inside Apple a very serious discussion about
adding a TCP stack to HyperCard and stuffing it into the ROM. This
was a year or more before the Internet exploded. The guy who promoted
the idea got show down by Jean
The MOST useful book (to me) by far in many years of commercial scripting
with HyperCard was Dan Shafer's book on HyperTalk Scripting. It got used
almost everyday for ten years or so. Additions to the language were always
available in the What's New section of the users guide for each new
version.
I learnt Hypercard without a book,
and I extended my knowledge, as RR extended xTalk, in the
same way:
by doing!
That's great if you have all the time in the world to doing it
wrong many times! Especially when the documentaion is just plain
wrong!
Ludwig Wittgenstein said that too many
'Nonsense' about RR documentation
I learnt Hypercard without a book,
and I extended my knowledge, as RR extended xTalk, in the
same way:
by doing!
That's great if you have all the time in the world to doing it wrong
many times! Especially when the documentaion is just plain wrong
David Burgun wrote:
I learnt Hypercard without a book,
and I extended my knowledge, as RR extended xTalk, in the
same way:
by doing!
That's great if you have all the time in the world to doing it wrong
many times! Especially when the documentaion is just plain wrong!
As with the spelling
On 11/30/05, Richard Gaskin [EMAIL PROTECTED] wrote:
While there's always room to expand on the material that's there, I
don't recall any recent issue you've raised here in which the
documentation was just plain wrong.
Sure, some sections could be expanded to address a wider range of needs,
If you click on Topics and then type How into the Filter with: field,
you get a whole host of examples, most of which work right out of the box.
The problem is, these are really buried in the docs. They need to be
surfaced.
On 11/29/05, Kay C Lan [EMAIL PROTECTED] wrote:
If the documentation
Dennis Brown [EMAIL PROTECTED] wrote:
Another thing that makes it different (part of the depth and
complexity) is the type-less nature of containers.
Unlike AppleScript ;-
always baffled by type problems in AppleScript...
wonder why Apple didn't make Hypertalk system-wide
(apart
There was at one point inside Apple a very serious discussion about
adding a TCP stack to HyperCard and stuffing it into the ROM. This
was a year or more before the Internet exploded. The guy who promoted
the idea got show down by Jean-Louis Gassee and left the company.
Just imagine
--- jbv [EMAIL PROTECTED] wrote:
Dennis,
Ok that's fine... but still I'm wondering : what (if
anything) makes
Transcript different from other languages (beside
its almost plain
english syntax ?
Doesn't it feature variables, loops, if-then-else
structures, arrays,
functions, etc. just
I learnt Hypercard without a book,
and I extended my knowledge, as RR extended xTalk, in the
same way:
by doing!
Ludwig Wittgenstein said that too many people Philosophise
and not enough DO PHILOSOPHY.
Now if we all DID Runtime Revolution:
i.e. got in there, got our feet wet, realised that
Richmond,
While I agree with your sentiment (I learned programming the same
way, though a few years earlier), I don't see Transcript
documentation as something to compare to other languages from the
point of view of whose documentation is the worst.
I see what the documentation could be
Your feeling is right. I am 60. I don't worry about age. It's a
proven fact that people who have more birthdays live longer.
Besides, I always heard programming was a young man's game so I
figure if I keep doing it maybe the Universe will forget my
chronological age.
And for my feelings
Ok, here's my two cents about the state of the docs:
- The intro videos are well done. Although, I also had a big give-me-a-break
moment when I saw I had to pay $50 to finish watching the videos.
- The content of the docs is reasonable.
- The lack of a complete
Dennis Brown a *crit :
Transcript is different enough from other popular languages,
in what is it different (beside the fact that it's much closer to
natural english than any other language) ? just asking...
uses
different terms and metaphors,
same question as above... again, just
On Nov 27, 2005, at 4:17 PM, jbv wrote:
Transcript is different enough from other popular languages,
in what is it different (beside the fact that it's much closer to
natural english than any other language) ? just asking...
uses
different terms and metaphors,
same question as above...
Le 27 nov. 05 à 19:56, Dan Shafer a écrit :
It's a proven fact that people who have more birthdays live longer.
Thanks Dan for this Good Luck methodology reminder..., something very
closely binded with the points of view we are able to filter, the
actions and responsabilities we are able
Dennis,
Ok that's fine... but still I'm wondering : what (if anything) makes
Transcript different from other languages (beside its almost plain
english syntax ?
Doesn't it feature variables, loops, if-then-else structures, arrays,
functions, etc. just like so many other languages ?
so what
On Nov 27, 2005, at 5:47 PM, jbv wrote:
Ok that's fine... but still I'm wondering : what (if anything) makes
Transcript different from other languages (beside its almost plain
english syntax ?
Doesn't it feature variables, loops, if-then-else structures, arrays,
functions, etc. just like so
Another thing that makes it different (part of the depth and
complexity) is the type-less nature of containers. You tell it what
you want it to do generically, and it figures out how based on the
kind of data you give it --even if you switched data types the next
time through... Aaarrgh!
One man's Aaarrgh! is another man's Ahhh.
On Nov 27, 2005, at 5:03 PM, Dennis Brown wrote:
Another thing that makes it different (part of the depth and
complexity) is the type-less nature of containers. You tell it
what you want it to do generically, and it figures out how based on
Different people learn in different ways. In my own case, it is
indispensable to read through entire manuals first in a systematic way.
That's the way
I learned Hypercard (Danny Goodman's and Dan Shafer's books), Supercard,
mTropolis, Revolution (including Dan Shafer's book), Photoshop,
Hi JB,
Date: Sun, 27 Nov 2005 23:47:37 +0100
From: jbv [EMAIL PROTECTED]
Subject: Re: Constant 'Nonsense' about RR documentation
Ok that's fine... but still I'm wondering : what (if anything) makes
Transcript different from other languages (beside its almost plain
english syntax ?
Doesn't
33 matches
Mail list logo