>You get around the "no business purpose" (necessary to prevent liability) by
>later forming other partnerships among yourselves. That is, by 'forking'.
>Naturally, 'spin off' associations would have a profit motivation. How you
>wish to do this may be a subject you wish to raise and discuss before i draw
>up a first draft of a partnership agreement.
Eric,
I think as long as your first draft doesn't include anything that makes
founding other partnerships that sell copies of OC impossible, I don't see
a problem.
>Really, once you open up business purposes you open up potential liability for
>contracts entered into by your partners. True, partners owe each other a
>fiduciary duty (which is a higher level of duty than 'ordinary care' - sorta
>like marriage, you have to watch out for your partners interests as well as
>your own). The liability is prevented by 'nipping' any commercial object in
>the bud.
That's why our partnership should be "no business", then. Right?
>Again, thank you for correcting my misperceptions about MC not being involved.
>If i (finally?) understand properly, they let us use MC to develop some
>graphics for them (e.g. icons, dialogue boxes, and a tool palette) and they
>get to distribute the interface developed in exchange for a license for a
>certain number of our developers.
>
>If that is the case let me know - cause other than cheesy icons and a sort of
>ok tool palette, i think their gui is ok. And i actually enjoy drawing
>icons... and will happily start - would that be useful?
There are more problems. For example, the menu editor requires you to
enter a menu item's name with metacharacters if you want a shortcut or
styles. Here a real editor would be cool. Also, the arrangement of the menu
items is pretty counter-productive. Too many frequently-used things are
hidden away behind three clicks, instead of being placed in a menu, while
other commands are in the menu even though they're used only once at the
beginning of creating a stack.
It misses a hierarchic view of all stacks and substacks etc. and in my
book it uses too much screen space. Also, some parts (like the script
editor) don't ask you whether you wish to save often enough. There are lots
of subtle things wrong there, which you notice once you try creating a real
project with it.
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
