> How about a Rev component with no interactive features that could be used simply as a container for scripts and custom properties.
Are you talking about Template Objects? You can set the props (including scripts and custom props) of 'the template button' (for example) and all new buttons will have these properties. You can set, get, or reset on the fly...these 'template' controls are always there (invisible, so to speak). You can use a Rev executable as a startup engine for .jar files by the way. I have to say that NetBeans is pretty cool too...written totally in Java! And it's FREE!! :-) JR -----Original Message----- Date: Tue, 30 Nov 2004 17:42:43 -0800 (PST) From: Gordon <[EMAIL PROTECTED]> Subject: OOP with Revolution To: Revolution Mailing List <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii How about a Rev component with no interactive features that could be used simply as a container for scripts and custom properties. It could be set in the rev preferences as visible or invisible on a card, but would otherwise inherit the properties of the general class of object from which I imagine all the other components are descended. Perhaps I could just create such a thing myself as a custom control - if I knew enough about rev - which I don't :( I know that people use buttons and the like for this purpose right now, but this new component might simplify and clarify the design of rev stacks a little. Gordon End ********************************************** _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution