>Heh heh, yes I see your point =). Assuming it doesn't become a headache, I
>vote for variable length strings. Perhaps NULL-terminated, if that is to be
>the native string type anyway? Or else a p-string with two length bytes? I
>really can't imagine anyone wanting object names longer than 65536 characters
>=P...
Brian,
zero-terminated strings would cause similar problems as HyperCard has (it
chokes in NULL characters), so this is definitely not what we want. I'd
suggest using an unsigned long instead of the length byte for a "pascal"
string. SInce this is what OTString is very likely to work with, too, we'll
be able to use that.
>BTW, while we are on the 32k note, are we planning to build this on top of
>WASTE instead of TextEdit? Does WASTE have a Windoze port (lest we have to
>use two engines to be cross-platform)?
I still have to investigate whether wxWindows contains a text editing
mechanism (I've heard about one called RichEdit which could be what we're
looking for). AFAIK there's no Windows WASTE, and in a worst-case scenario
we'd have to write our own text-editing class. Any volunteers?
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
