Scott,
> >
> > I have a glossary stack that loads from an html file. I would like users
> > to be able to load a stack from their own "glossary" html file. Unless I
> > don't understand the nature of the MetaCard license, this would require
> > that each user who ever wanted to import their own glossary items--and
> > save that glossary--would need a MC license. The only way I know to get
> > around this would be to have the html file load each time on the fly as
> > the stack is opened, but never be saved.
> >
> > Am I missing something? Or is there a way to create a stack that users
> > can modify periodically, not from MC scripts, but by revising input files?
>
> Your stacks *can* be saved after loading the glossary information, so
But I want users to be able to load their own info, like words or contacts
or phone numbers or syntax information. It would be like an address-book
stack that each user might want to have several different types of
information in.
> I see no problem here (other than the fact the MetaCard doesn't
> support HTML yet ;-) Your stacks can also create cards, which might
(I have a script that parses a subset of html as it's read into the stack
from an external file, so that's no problem.)
I guess if non-licensed users can create cards in existing stacks, and
when closed those new cards are saved as part of their original stacks,
then I can do what I want to.
> also be useful in a glossary. What they can't do is create new
> stacks, buttons, or fields (unless you use Embedded MetaCard) or edit
!!!(I don't know about Embedded MetaCard; where do I read about it?)!!!
> scripts, none of which should be necessary for your application.
No, I don't need to edit scripts or create new buttons or fields. Adding
cards to existing substacks should make my task possible. I guess I need
to try this as a non-licensed user to see if it works.
Thanks for the inputs!
Sincerely,
Clark Parsons