On Sat, 13 Nov 1999 Alain Farmer <[EMAIL PROTECTED]> wrote:
> Alain: Besides, given the fact that our engin is not
> ready yet and, consequently that we will be using
> MetaCard's engin for the time being, we cannot allow
> standalones because MetaCard's engin is not open
> source.
Correction: there'd be no such limitation. The only limitation would
be that the development environment would be restricted to the Starter
Kit script-length limits (currently 10 effective statements per object).
> Alain: Does Scott already make available a free
> player? Would he be willing to provide one? In the
> negative, we will have to wait for our own to be
> developed. What will our end-users use to run their
> OpenKard stacks while our engin/player is not ready?
You could certainly develop and distribute with the MetaCard Starter
Kit. This isn't a good long-term strategy because of the
script-length limits, but would get you a damn good head start.
And from another message (sorry, I get the digest ;-) "M. Uli
Kusterer" <[EMAIL PROTECTED]> wrote:
> I think it'd be smartest to just let Scott decide this. If someone on the
> list decides he wants to take part in developing the UI, he has to tell us
> about it, and what he intends to do (e.g. show us a sketch of a new menu
> layout he'd want to implement) and if we like it we go to Scott and ask him
> whether he'd shell out another license for that person. It would thus be a
> per-person contract.
I'd prefer *not* to have to work this way, if possible, as it'd be a
lot more work for me. For example, it makes tracking things like tech
support contacts much more difficult.
> This is practicable, since this kind of collaboration with MC will only
> happen as long as OpenCard is not finished. When it is, we'll do our
> development in OC and someone else would have to convert it into a MetaCard
> project.
It might be practical if we're talking about 2 or 3 people. It's not
if we're talking about 20 or 30. The way I'd prefer it to work is for
the partners to make this decision and then just send the new person
a licensed Home stack. We'll probably generate a specific Home stack
for this project so that you don't have to mess with the
name/organization/key stuff and to make tracking these Home stacks
(e.g., for tech support) easier.
Regards,
Scott
> Cheers,
> - -- M. Uli Kusterer
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
