metacard Digest, Vol 37, Issue 19

FlexibleLearning at aol.com FlexibleLearning at aol.com
Mon Oct 16 13:52:31 CDT 2006


 
In a message dated 16/10/2006 18:01:11 GMT Daylight Time,  
metacard-request at lists.runrev.com writes:

Send  metacard mailing list submissions to
metacard at lists.runrev.com

To subscribe or unsubscribe via the World  Wide Web, visit
http://lists.runrev.com/mailman/listinfo/metacard
or, via email, send a  message with subject or body 'help' to
metacard-request at lists.runrev.com

You can reach the person managing the  list at
metacard-owner at lists.runrev.com

When replying,  please edit your Subject line so it is more specific
than "Re: Contents of  metacard digest..."


This is the Metacard mailing  list.

Today's Topics:

1. Re: Plugin Immunity  (FlexibleLearning at aol.com)
2. Re: Plugin Immunity (Ken  Ray)
3. Re: Plugin Immunity (Jeanne A. E.  DeVoto)


----------------------------------------------------------------------

Message:  1
Date: Sun, 15 Oct 2006 13:38:24 EDT
From:  FlexibleLearning at aol.com
Subject: Re: Plugin Immunity
To:  metacard at lists.runrev.com
Message-ID:  <cc4.3c6257.3263cc10 at aol.com>
Content-Type: text/plain;  charset="us-ascii"


>> Is there a way to stop Rev being able  to create  new  controls in a  
>> stack that is  designed to work as a Rev  plugin?

> maybe setting the  "cantmodify" to true does work for  you?

Not an option I'm afraid,  Klaus. The plugin stack is designed to be  
content-modifiable. The  stoic insistence by Rev's tools palette that any  
non-cantModify  stack is fair game with no lockout option (e.g. a revBlessed  
property  
that, if set to true, means the tools palette will not touch it)  verges  on 
the 
insane, or inane, or inept, or an IDE bug, or to  charitable an IDE  
oversight.

/H

-------------- next part  --------------
An HTML attachment was scrubbed...
URL:  
http://mail.runrev.com/pipermail/metacard/attachments/20061015/8337d874/attachment-0001.html

------------------------------

Message:  2
Date: Sun, 15 Oct 2006 13:04:19 -0500
From: Ken Ray  <kray at sonsothunder.com>
Subject: Re: Plugin Immunity
To: MetaCard  List <metacard at lists.runrev.com>
Message-ID:  <C157E253.48535%kray at sonsothunder.com>
Content-Type:  text/plain;    charset="US-ASCII"

On 10/15/06 12:38 PM,  "FlexibleLearning at aol.com"  <FlexibleLearning at aol.com>
wrote:

>  
>>>  Is there a way to stop Rev being able to create  new  controls in  a
>>> stack that is designed to work as a Rev   plugin?
> 
>> maybe setting the "cantmodify" to true does work  for  you?
> 
> Not an option I'm afraid, Klaus. The plugin  stack is designed to be
> content-modifiable. The stoic insistence by  Rev's tools palette that any
> non-cantModify stack is fair game with no  lockout option (e.g. a revBlessed
> property 
> that, if set to  true, means the tools palette will not touch it) verges  on
> the  
> insane, or inane, or inept, or an IDE bug, or to charitable an  IDE  
oversight.

Name your stack file starting with "rev" and it  should be ignored. I looked
at the code in Rev that handles this, and the  key function is
'revFilterStacksList' (found in the 'revCommon' backscript)  that will remove
stacks from a list if they meet certain criteria. I tried  with the
revExample stack, and you can't drop objects on top of it from the  tool
palette (you get a beep).

Try that, Hugh...

Ken  Ray
Sons of Thunder Software
Web site:  http://www.sonsothunder.com/
Email:  kray at sonsothunder.com



------------------------------

Message:  3
Date: Mon, 16 Oct 2006 05:32:22 -0700
From: "Jeanne A. E. DeVoto"  <revolution at jaedworks.com>
Subject: Re: Plugin Immunity
To:  Discussions on Metacard <metacard at lists.runrev.com>
Message-ID:  <p06210237c1592c06663a@[66.93.39.98]>
Content-Type: text/plain;  charset="us-ascii" ; format="flowed"

At 1:53 PM -0400 10/14/2006,  FlexibleLearning at aol.com wrote:
>Is there a way to stop Rev being able  to create  new controls in a stack 
that
>is designed to work as a  Rev plugin?

This isn't as elegant as preventing creation of the  control, but you 
can trap newButton and the other new[Control] messages  and delete 
(possibly with an error message to the user).
-- 
jeanne  a. e. devoto ~  revolution at jaedworks.com
http://www.jaedworks.com


------------------------------

_______________________________________________
metacard  mailing  list
metacard at lists.runrev.com
http://lists.runrev.com/mailman/listinfo/metacard


End  of metacard Digest, Vol 37, Issue  19
****************************************




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.runrev.com/pipermail/metacard/attachments/20061016/5d1e8eba/attachment.html


More information about the metacard mailing list