No, I think that's the point. The free Starter Kit can be used to
produce commercial applications just like the regular license. The
only difference is that there is a *technical* limitation on setting
scripts in the Starter Kit (10 effective statements) that doesn't
apply with the regular license (even the 64K limit has been removed
for the 2.3 release). And the only thing you can't distribute if you
get the regular license is the licensed Home stack or the license key
(both of which have your name in it, to help discourage you from doing
this ;-)
:Eric: Ok, if I understand correctly the lite and heavy license are the same
except for the script limitation (and field limitation for the 2.3 edition).
That said, you could ask end users to include a 'made with metacard' somewhere
in their stack. I _think director does this (i know they do for their academic
version).
I'm going to do a screen shot of the splash screen and play with it - using
all primary colors is good, but i think that its a bit too blue...
Regarding icons, I have started drawing them and shall limit my palette to
less then 256 colors - in fact my preference is for the quickdraw eight
because most people do not have such refined color accuity (believe it or not
the french are significantly color blind - like 10% of the population. Paris
is an annoying shade of green. And it rains like in london... too much
inbreeding)
We should choose a default font. Helvetica is readable but I think it prints
better than it looks on screen. MS Sans Serif?
I have started drawing icons. I have a few done as CICN and ICON resources.
But if I understand correctly it is actually better that I draw them as picts.
Not a problem, but it does seem 'strange'. I intend to post them as an
attachment (sorry) in a later letter. Please not that with six arrows, and ten
pixel sizes you wind up with a few hundred icons pretty quickly. The icons
will be formatted in PICT unless there is a problem with that? I shall use the
extension .PNG but I am clueless about which extension to use, so tell me
otherwise if necessary.
Oh, I'v also developed some graphics for cursors, and even a toolbar... Will
submit today or tomorrow as an attachment.
If it matters(?) i would be content if we just make a player which allows
writing of stacks. If we get to the point of standalones, well and good, but i
sort of think that would be competing with metaCard - why bite a hand that
feeds? If our player is less than 1 meg that increases portability. I for one
am looking at my nice metaCard 2.3 meg standalone and wondering, hmm, how can
I put it on a 1.44 meg disk? If it were hypercard i'd just res edit out the
resources I do not need - but i cant because its all data fork! Do I use a hex
editor? does it remain executable? Probably not.
So, I would like our player to be less than one meg so that it could be easily
distributed, i.e. on one disk, or at least less than 1.44 meg compacted.
Yes, the metaCard license is incredibly generous and open which is why I had
difficulty believing it also applied to the lite version.
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
