<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Verdana"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Verdana color=#000000 size=2>
<DIV>
<DIV>In a message dated 16/10/2006 18:01:11 GMT Daylight Time,
metacard-request@lists.runrev.com writes:</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 10px; MARGIN-LEFT: 10px"><FONT
style="BACKGROUND-COLOR: transparent" face=Arial color=#000000 size=2>Send
metacard mailing list submissions to<BR>
metacard@lists.runrev.com<BR><BR>To subscribe or unsubscribe via the World
Wide Web, visit<BR>
http://lists.runrev.com/mailman/listinfo/metacard<BR>or, via email, send a
message with subject or body 'help' to<BR>
metacard-request@lists.runrev.com<BR><BR>You can reach the person managing the
list at<BR> metacard-owner@lists.runrev.com<BR><BR>When replying,
please edit your Subject line so it is more specific<BR>than "Re: Contents of
metacard digest..."<BR><BR><BR>This is the Metacard mailing
list.<BR><BR>Today's Topics:<BR><BR> 1. Re: Plugin Immunity
(FlexibleLearning@aol.com)<BR> 2. Re: Plugin Immunity (Ken
Ray)<BR> 3. Re: Plugin Immunity (Jeanne A. E.
DeVoto)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message:
1<BR>Date: Sun, 15 Oct 2006 13:38:24 EDT<BR>From:
FlexibleLearning@aol.com<BR>Subject: Re: Plugin Immunity<BR>To:
metacard@lists.runrev.com<BR>Message-ID:
<cc4.3c6257.3263cc10@aol.com><BR>Content-Type: text/plain;
charset="us-ascii"<BR><BR><BR>>> Is there a way to stop Rev being able
to create new controls in a <BR>>> stack that is
designed to work as a Rev plugin?<BR><BR>> maybe setting the
"cantmodify" to true does work for you?<BR><BR>Not an option I'm afraid,
Klaus. The plugin stack is designed to be <BR>content-modifiable. The
stoic insistence by Rev's tools palette that any <BR>non-cantModify
stack is fair game with no lockout option (e.g. a revBlessed property
<BR>that, if set to true, means the tools palette will not touch it)
verges on the <BR>insane, or inane, or inept, or an IDE bug, or to
charitable an IDE oversight.<BR><BR>/H<BR><BR>-------------- next part
--------------<BR>An HTML attachment was scrubbed...<BR>URL:
http://mail.runrev.com/pipermail/metacard/attachments/20061015/8337d874/attachment-0001.html<BR><BR>------------------------------<BR><BR>Message:
2<BR>Date: Sun, 15 Oct 2006 13:04:19 -0500<BR>From: Ken Ray
<kray@sonsothunder.com><BR>Subject: Re: Plugin Immunity<BR>To: MetaCard
List <metacard@lists.runrev.com><BR>Message-ID:
<C157E253.48535%kray@sonsothunder.com><BR>Content-Type:
text/plain; charset="US-ASCII"<BR><BR>On 10/15/06 12:38 PM,
"FlexibleLearning@aol.com"
<FlexibleLearning@aol.com><BR>wrote:<BR><BR>> <BR>>>>
Is there a way to stop Rev being able to create new controls in
a<BR>>>> stack that is designed to work as a Rev
plugin?<BR>> <BR>>> maybe setting the "cantmodify" to true does work
for you?<BR>> <BR>> Not an option I'm afraid, Klaus. The plugin
stack is designed to be<BR>> content-modifiable. The stoic insistence by
Rev's tools palette that any<BR>> non-cantModify stack is fair game with no
lockout option (e.g. a revBlessed<BR>> property <BR>> that, if set to
true, means the tools palette will not touch it) verges on<BR>> the
<BR>> insane, or inane, or inept, or an IDE bug, or to charitable an
IDE oversight.<BR><BR>Name your stack file starting with "rev" and it
should be ignored. I looked<BR>at the code in Rev that handles this, and the
key function is<BR>'revFilterStacksList' (found in the 'revCommon' backscript)
that will remove<BR>stacks from a list if they meet certain criteria. I tried
with the<BR>revExample stack, and you can't drop objects on top of it from the
tool<BR>palette (you get a beep).<BR><BR>Try that, Hugh...<BR><BR>Ken
Ray<BR>Sons of Thunder Software<BR>Web site:
http://www.sonsothunder.com/<BR>Email:
kray@sonsothunder.com<BR><BR><BR><BR>------------------------------<BR><BR>Message:
3<BR>Date: Mon, 16 Oct 2006 05:32:22 -0700<BR>From: "Jeanne A. E. DeVoto"
<revolution@jaedworks.com><BR>Subject: Re: Plugin Immunity<BR>To:
Discussions on Metacard <metacard@lists.runrev.com><BR>Message-ID:
<p06210237c1592c06663a@[66.93.39.98]><BR>Content-Type: text/plain;
charset="us-ascii" ; format="flowed"<BR><BR>At 1:53 PM -0400 10/14/2006,
FlexibleLearning@aol.com wrote:<BR>>Is there a way to stop Rev being able
to create new controls in a stack that<BR>>is designed to work as a
Rev plugin?<BR><BR>This isn't as elegant as preventing creation of the
control, but you <BR>can trap newButton and the other new[Control] messages
and delete <BR>(possibly with an error message to the user).<BR>-- <BR>jeanne
a. e. devoto ~
revolution@jaedworks.com<BR>http://www.jaedworks.com<BR><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>metacard
mailing
list<BR>metacard@lists.runrev.com<BR>http://lists.runrev.com/mailman/listinfo/metacard<BR><BR><BR>End
of metacard Digest, Vol 37, Issue
19<BR>****************************************<BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV> </DIV></FONT></BODY></HTML>