Hi, I've been "lurking" for a few days, and seeing some of the posts made me
want to jump in and ask a few questions:
> >Adrian: I disagree, I think we need to include them or an equivalent of
> >them. There is no real way to avoid this and it will add flexibility to
> >OpenCard. One of my biggest complaints about VB is that a button is a
> >button is a button, there's not much you can do with it. Lets not fall
into
> >that same trap.
>
> I fully agree. HyperCard has button styles. That means, OpenCard will also
> need button styles or it won't be HyperCard. We need 100% HyperCard first.
>(snip)
I don't understand: is OpenCard intended on being initially an OpenSource
version of HyperCard? Or is it supposed to be an OpenSource application that
is the "next step" from today's current offerings (HC, MC, SC, etc.)?
The reason I ask is that there are a number of things you have to do in
HyperCard that you don't need to do in SuperCard or MetaCard because HC
doesn't support vector graphics. If OpenCard supports vectors (which IMHO it
should), then the need to keep "opaque" buttons can go away as you can
implement them as "cover" graphics.
In any event, my primary question still stands: what is OpenCard *supposed*
to be when it is released?
Ken Ray
Sons of Thunder Software
Email: [EMAIL PROTECTED]
Website: http://www.sonsothunder.com/
