Robert Brenstein wrote:
But as far as I am concerned it is a kludge and a kludge that anyone
writing such plugins must always remember to follow. If I open Plugin
Manager and see something marked as a library, it should be a library.
May be I am a purist, but since plugins are new to MC, it would
On 07 May 2004, at 08:04, [EMAIL PROTECTED] wrote:
Message: 6
Date: Thu, 06 May 2004 23:05:06 -0700
From: Richard Gaskin [EMAIL PROTECTED]
Subject: Re: Plugins, fonts
To: Discussions on Metacard [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii;
Oops typo, can must be can't, sorry...
Please review the credit for your contributions that I added in B4 and
let me know if you feel it's appropriate (Help-Licensing, Version
History tab). Also, please consider updating the Read Me to include a
descriptions of this new active plugin feature.
Auto-open plugins -- plugins that are opened automatically at
startup. Any MetaCard or Revolution stack can be set to be an
auto-open plugin. The standard sequence of preOpen and open messages
is sent when the stack opens.
(new) Active plugins -- plugins that are executed automatically at
Could they also be done via the auto-open type:
on preOpenStack
doMyOneStartupThing
close this stack
end preOpenStack
Cheers
Monte
Well, Monte, and how do you know whether preOpenStack is to run the
doMyOneStartupThing and close or whether to open the stack properly
(see the example as I
Robert Brenstein wrote:
But as far as I am concerned it is a kludge and a kludge that anyone
writing such plugins must always remember to follow. If I open Plugin
Manager and see something marked as a library, it should be a library.
May be I am a purist, but since plugins are new to MC, it would
I was hoping to post the B5 build you sent, but it crashes my
Stuffit Expander:
I double-checked my Stuffit installation by downloading a fresh copy
of B4, which decompressed without error. While I haven't had issues
with other attachments I can't rule out a Mozilla email issue (I'm
testing
I found it at last, I must have been blind. But...
(Help-Licensing, Version History tab).
I didn't think about the help menu and
started with the help button on the home stack.
This way you reach a license button which opens
the Licensing Metacard stack where no version history button
is.
May be
Okay, I promise this to be the last post from me today. I have
already used more bandwidth than normal :) I split my reply to
Richard's long email to cover different aspects more clearly.
For Rev compatibility it's useful to support the auto-open option,
and with preOpenStack as a hook the
Robert Brenstein wrote:
Okay, I promise this to be the last post from me today. I have already
used more bandwidth than normal :) I split my reply to Richard's long
email to cover different aspects more clearly.
For Rev compatibility it's useful to support the auto-open option, and
with
Wouter wrote:
I found it at last, I must have been blind. But...
(Help-Licensing, Version History tab).
I didn't think about the help menu and
started with the help button on the home stack.
This way you reach a license button which opens
the Licensing Metacard stack where no version history
Wouter wrote:
That' s what I was looking for, version history, but unfortunately I
still can find it.
May be an embedded version history in the script of the Home stack or
somewhere near
would be a nice addition to make sure there always is a guide to what
has changed since the previous
Robert Brenstein wrote:
Why did you add the library as plugin type?
Because two people presented an argument that there may be times when a
stack should only be libraried at startup but not when opening the
stack. Moreoever, most good libraries are designed to be initialized
with start using
On 07 May 2004, at 18:00, [EMAIL PROTECTED] wrote:
Message: 1
Date: Fri, 07 May 2004 08:24:53 -0700
From: Richard Gaskin [EMAIL PROTECTED]
Subject: Re: Plugins, fonts
To: Discussions on Metacard [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii;
Most of the handful of people who still use the MC IDE have businesses
based around it. They're mostly building applications, not IDE
components. The relative few who do make publicly-distributed
plugins usually make them for Rev, or at least Rev-compatible.
As one who is still using MC as it
Wouter wrote:
Modifying the Home stack is problematic, for reasons I can get into more
if needed. The plan for the moment is to update the Home stack when it
becomes necessary to do so with the next license change. I think I'll
need some code from Dr. Raney for that, and he may be back in Colorado
Sorry for breaking my promise to keep quiet, but either I presented
my case badly or you are misreading my words, Richard.
For Rev compatibility it's useful to support the auto-open option,
and with preOpenStack as a hook the world is the scripter's
oyster. But beyond the most basic
Shari wrote:
Been a busy girl, just took two months off to marry my IBM fella :-)
Congratulations.
Good to see you back here. You've been missed.
Have not joined the Rev list as my version is from before the
marriage of MC and Rev.
The Rev list is where the meaty language discussion happens
From: Richard Gaskin [EMAIL PROTECTED]
I propose removing those but keeping the optionKey section for script
access:
on commandKeyDown which
if the optionKey is down then
switch which
case S
edit script of the topStack
break
case C
edit script of this card of
Robert Brenstein wrote:
Why did you add the library as plugin type?
Because two people presented an argument that there may be times
when a stack should only be libraried at startup but not when
opening the stack. Moreoever, most good libraries are designed to
be initialized with start using
Once upon a time this was all so simple: folks wanted a menu to
provide convenient access to extra utilities, and decided it would
be useful to also have the option of having some of those
automatically opened if they choose. At that point, everything else
possible with the engine is
on Fri, 07 May 2004 12:32:28 -0700
Scott Rossi wrote:
[snip]
The MC IDE is supposed to be after
all open source now, so
I think it should be possible to develop new
features and then have folks
try them out.
[snip]
Does exist a wish list for new features for the
mc ide?
For example, i've
Is it possible to mail directly from a MC stack?
My users will complete several activities and a final grade will be
given.
This grade, users name, ID and several other bits of information are
put into a variable.
How do I have this variable mailed to me?
Does anyone have the script to do
'Evening Rick,
Yes. In between other ways, Sao Sean's libSMTP 2 great stack is the
perfect tool to handle such kind of services.
Name: libSMTP
#Version : 1.5.0
#Build : 2003.06.24.1
#Authour : Shao Sean [EMAIL PROTECTED]
#Website : http://shaosean.tk/
Best, Pierre
Le 8
Robert Brenstein wrote:
Once upon a time this was all so simple: folks wanted a menu to
provide convenient access to extra utilities, and decided it would be
useful to also have the option of having some of those automatically
opened if they choose. At that point, everything else possible
25 matches
Mail list logo
