Re: MC IDE: Passing the Poohbah torch and more
I have to say, Richard agreed to be our grand poohbah for six months, and it has stretched out to something like several years. Thanks for all your efforts and the wonderful job you've done, Richard. We all appreciate it very much. And a big thanks to Klaus for taking over this job. I know you'll be every bit as conscientious as Richard. We owe you both a debt of gratitude. Indeed! Robert Brenstein ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MetaCard and Rev 2.7 + engine
Hi friends of the lean IDE, this is the new (Winnie the) Poobah speaking :-) Hope you are all well! Hi, In case somebody is still dragging the feet on switching to Rev 2.7 engine, below is the critical tip from Jacque on necessary changes that must be done to HOME stack --- On February 14, 2006 Jacqueline Landman Gay wrote: Installing Revolution 2.7 into the MC IDE ... There should also be no need to license the engine in Revolution first - the engine will ask for a license key the first time it is run, regardless of where it is run from. ... Does this mean that we do not need a special MetaCard license key anymore? Regards Klaus Major [EMAIL PROTECTED] http://www.major-k.de ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MC IDE: Passing the Poohbah torch and more
On Jun 21, 2006, at 10:32 PM, Ken Ray wrote: I have to say, Richard agreed to be our grand poohbah for six months, and it has stretched out to something like several years. Thanks for all your efforts and the wonderful job you've done, Richard. We all appreciate it very much. Hear, hear! :-) Hear hear! -- Tereza Snyder Califex Software, Inc. www.califexsoftware.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MC IDE: Passing the Poohbah torch and more
Hi all, Am 22.06.2006 um 12:28 schrieb Tereza Snyder: On Jun 21, 2006, at 10:32 PM, Ken Ray wrote: I have to say, Richard agreed to be our grand poohbah for six months, and it has stretched out to something like several years. Thanks for all your efforts and the wonderful job you've done, Richard. We all appreciate it very much. Hear, hear! :-) Hear hear! Hark, hark! Tereza Snyder Califex Software, Inc. www.califexsoftware.com Regards Klaus Major New MC Poobah (whatever that means...) [EMAIL PROTECTED] http://www.major-k.de P.S. That is old, but correct english :-) ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MetaCard and Rev 2.7 + engine
Klaus Major wrote: Hi friends of the lean IDE, this is the new (Winnie the) Poobah speaking :-) Hope you are all well! Hi, In case somebody is still dragging the feet on switching to Rev 2.7 engine, below is the critical tip from Jacque on necessary changes that must be done to HOME stack --- On February 14, 2006 Jacqueline Landman Gay wrote: Installing Revolution 2.7 into the MC IDE ... There should also be no need to license the engine in Revolution first - the engine will ask for a license key the first time it is run, regardless of where it is run from. ... Does this mean that we do not need a special MetaCard license key anymore? That's a good question. I don't know. But I'm guessing you would, because the old MC Home stack checks for a license stored in Home, and the new engine also checks for a license stored elsewhere by the engine. So maybe we need both? Of course, most of us are using a previously-licensed Home stack, so that issue becomes moot. I really like Winnie the Poohbah. Cute. :) -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MetaCard and Rev 2.7 + engine
Hi Jacqueline, Klaus Major wrote: Hi friends of the lean IDE, this is the new (Winnie the) Poobah speaking :-) Hope you are all well! Hi, In case somebody is still dragging the feet on switching to Rev 2.7 engine, below is the critical tip from Jacque on necessary changes that must be done to HOME stack --- On February 14, 2006 Jacqueline Landman Gay wrote: Installing Revolution 2.7 into the MC IDE ... There should also be no need to license the engine in Revolution first - the engine will ask for a license key the first time it is run, regardless of where it is run from. ... Does this mean that we do not need a special MetaCard license key anymore? That's a good question. I don't know. But I'm guessing you would, because the old MC Home stack checks for a license stored in Home, and the new engine also checks for a license stored elsewhere by the engine. So maybe we need both? Who knows? I was just curious. Of course, most of us are using a previously-licensed Home stack, so that issue becomes moot. Exactly. I really like Winnie the Poohbah. Cute. :) :-) -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com Best Klaus Major [EMAIL PROTECTED] http://www.major-k.de ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MC IDE: Passing the Poohbah torch and more
Indeed, and tally-ho! /H (Still dragging both left feet to venture into 2.7x. But since the windows upgrade is, I think, a more transparent process, I don't really have any excuses... Can I claim middle age?) On Jun 21, 2006, at 10:32 PM, Ken Ray wrote: I have to say, Richard agreed to be our grand poohbah for six months, and it has stretched out to something like several years. Thanks for all your efforts and the wonderful job you've done, Richard. We all appreciate it very much. Hear, hear! :-) ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MetaCard and Rev 2.7 + engine
J. Landman Gay wrote: Klaus Major wrote: On February 14, 2006 Jacqueline Landman Gay wrote: Installing Revolution 2.7 into the MC IDE ... There should also be no need to license the engine in Revolution first - the engine will ask for a license key the first time it is run, regardless of where it is run from. ... Does this mean that we do not need a special MetaCard license key anymore? That's a good question. I don't know. But I'm guessing you would, because the old MC Home stack checks for a license stored in Home, and the new engine also checks for a license stored elsewhere by the engine. So maybe we need both? Of course, most of us are using a previously-licensed Home stack, so that issue becomes moot. Experiments here confirm that v2.7's licensing is indeed fully self-contained, which has several positive implications for both RunRev Ltd and those of us who use MC, Galaxy, and other alternative IDEs: - The new engine prevents unauthorized scripting on non-licensed platforms. Rev Studio deploys to any platform, with the only restriction being the platforms on which the user is allows to author on. These terms no longer conflict with the freedom of MetaCard's multi-platform Standalone Builder as they did in the olden days when Studio deployment was limited to specific purchased platforms. - The license mechanism no longer involves the Home stack. In older versions the Home stack contained special licensing info in a proprietary format in one of its substacks.* With this reliance on the Home stack and the Home stack's own built-in authorization mechanism, this prevented RunRev from enhancing the license code easily for their engine protection and also required them to maintain and generate special MetaCard licenses on request. With 2.7 it appears they no longer need to be saddled with this burden. - The boot sequence is simplified. In older versions, the engine would look for licence.rev or home.mc and then verified that the file contained the special license info. In v2.7 the licensing is handled internally in the engine, so the Home stack is now merely used as a launcher for the IDE. Any stack named home.rev can contain a script to launch any stacks serving as your development environment. If you haven't licensed your engine, it simply won't load Home and you can't continue. With the new Studio license terms and more secure engine-based license enforcement, it seems RunRev has given their users the freedom to choose any IDE while giving themselves greater security in protecting their product. With the broader deployment options enjoyed by Studio users there is no conflict with any MC IDE feature and Studio users are finally able to use the MC IDE, or Galaxy or any other IDE, just as Enterprise users have always been able to. With the growing number of IDEs, the Revolution community can enjoy any number of environments tailored for their specific tastes. FlipsIDE is rendered obsolete by this new simplicity, and I'm working on a new replacement named DarksIDE which will simplify installation of MC or any other IDE without affecting any behavior in the Rev installation. This is a significant win-win solution, and I applaud Kevin and Mark's insight in making this very useful new licensing mechanism. * The special proprietary license properties in MC's Home stack apparently mean that stack is in a unique format. If you're using v2.7 you will definitely want to be working with a COPY of your MC Home stack, as it's the only stack I've seen which cannot be reverted to the v2.4 stack file format -- once you convert the MC Home stack to v2.7 you can't go back with that copy. -- Richard Gaskin Managing Editor, revJournal ___ Rev tips, tutorials and more: http://www.revJournal.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MC IDE: Passing the Poohbah torch and more
J. Landman Gay wrote: Richard Gaskin wrote: I can wrap up v2.6 as soon as you folks report back on RC1 I'm just looking at it now. It looks like the IDE version in the About box didn't get updated. Fixed for the next build. The message box size is too small for me to read comfortably. I've already changed it in my own copy, but thought I'd mention it here to see if the majority wants it to ship the old way or the new way. I'm okay with just changing my own copy with each release if other people like it as-is. I found MetaCard's insistence on Helvetica 14 to be annoying, as it's not the standard font face or size on anything other than Motif. I had changed it to Lucida Grande 11 on OS X to conform to the OS X HIG. I can change it back if you like -- I'm using my own IDE these days anyway, which uses HIG-recommended fonts throughout, so it won't affect me either way. -- Richard Gaskin Fourth World Media Corporation ___ [EMAIL PROTECTED] http://www.FourthWorld.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
MC IDE: Passing the Poohbah torch and more (Richard Gaskin)
On Wed, 21 Jun 2006 11:22:56 -0700 Richard Gaskin wrote: I've talked this over with Klaus Major via email, and he would be willing to assume the role of Poohbah for the MC IDE project going forward. Richard did exceptional job maintaining MC IDE. What I appreciated the most was that he was very careful to keep purity of MC IDE, his IDE changes were transparent in terms of no new IDE behavior or added complexity was introduced and most of the changes were to just keep IDE compatible with new engines. I'm sure Klaus will continue this tradition and 6 changes he made in IDE so far were all excellent. Long live new Poohbah ! :) The Font Chooser stack contains a list field for font names rather than a popup button. I've been using this privately for a while and I like it much better. Anyone who has as many fonts as I do will see the advantages of a list, I think. SO much better. Thanks Jacque. I have also made some changes to the Preferences stack so that it now supports a stackFileVersion preference. I could not think of a suitable way to change this setting on the fly, but the new stack does allow you to permanently set the preference, which will stay in effect until you change it. It checks for the engine version and is not effective unless the version is 2.7 or higher. Great. At Thu, 22 Jun 2006 J. Landman Gay wrote: I'm just looking at it now. It looks like the IDE version in the About box didn't get updated. Right. Also it seems Richard's famous StripAndShip handler was not applied to standalone builder SubStack and it still shows path to area 51 :) /Users/richardgaskin/Area51/ The message box size is too small for me to read comfortably. I've already changed it in my own copy, but thought I'd mention it here to see if the majority wants it to ship the old way or the new way. I'm okay with just changing my own copy with each release if other people like it as-is. Interesting. I can't see any change in msg box size between B12 and RC1 but I didn't replace my Home stack if it makes any difference (don't remember right now from which stack the msg box default size comes from) Speaking about sizes, I'm always changing the fonts and button sizes in new MC IDE builds to accommodate to OS standards. For OS 9 the standard font is Geneva 10 and button size is w= 95 and h= 22 For OS X the standard font is Lucida Grande 11 and button size is w = 82 and h= 23 For Win the standard font is Tahoma 11, don't remember standard button sizes So, may be it makes sense to put a small handler in PreOpenStack of mctools.mc and mchelp.mc that would set the textfont and textsize of this stacks according to OS standards? This way substacks like properties or control browser would inherit TextFont and TextSise of the main stack and would look much better on all platforms. Concerning default object sizes (when you create a new object) Rev has it done very nicely in Preferences / Object sizes May be Klaus would consider to add such tab to MC IDE preferences stack and make it optional ? That's one of few features I personally like in Rev ID and I'm imitating it by setting default sizes in on NewButton, On NewField etc in script of stack Home. Also, just to remind so this would not be lost in transition period :) ... RC1 has libURL vs 1.1.4 and Dave Gragg posted vs 1.1.6 at http://www.lacscentre.co.uk/liburl/releases.html; best regards Tariel ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: MC IDE: Passing the Poohbah torch and more (Richard Gaskin)
Tariel Gogoberidze wrote: Also it seems Richard's famous StripAndShip handler was not applied to standalone builder SubStack and it still shows path to area 51 :) /Users/richardgaskin/Area51/ I applied the mcStripAndShip, but I hadn't updated that handler to automatically clean out the Standalone Builder. I used to do that manually, but as a favor to Winnie the Poohbah I just added that to mcStripAndShip. The message box size is too small for me to read comfortably. I've already changed it in my own copy, but thought I'd mention it here to see if the majority wants it to ship the old way or the new way. I'm okay with just changing my own copy with each release if other people like it as-is. Interesting. I can't see any change in msg box size between B12 and RC1 but I didn't replace my Home stack if it makes any difference (don't remember right now from which stack the msg box default size comes from) The Home stack shouldn't matter, but just the same I've cleared the font settings from the Message Box in the MC IDE (but I've left them in my personal customized copy g). Speaking about sizes, I'm always changing the fonts and button sizes in new MC IDE builds to accommodate to OS standards. For OS 9 the standard font is Geneva 10 and button size is w= 95 and h= 22 For OS X the standard font is Lucida Grande 11 and button size is w = 82 and h= 23 For Win the standard font is Tahoma 11, don't remember standard button sizes So, may be it makes sense to put a small handler in PreOpenStack of mctools.mc and mchelp.mc that would set the textfont and textsize of this stacks according to OS standards? This way substacks like properties or control browser would inherit TextFont and TextSise of the main stack and would look much better on all platforms. Concerning default object sizes (when you create a new object) Rev has it done very nicely in Preferences / Object sizes May be Klaus would consider to add such tab to MC IDE preferences stack and make it optional ? That's one of few features I personally like in Rev ID and I'm imitating it by setting default sizes in on NewButton, On NewField etc in script of stack Home. This raises a question: To what degree should we consider enhancing the MC IDE? There was originally a mandate of minimal change, and it may be good to maintain that. On the other hand, as long as each release addresses all known bugs and enhancements are approved by the crew here, is there any harm is making it less ugly? :) Also, just to remind so this would not be lost in transition period :) ... RC1 has libURL vs 1.1.4 and Dave Gragg posted vs 1.1.6 at http://www.lacscentre.co.uk/liburl/releases.html; I just updated it for RC2. Thanks for the report. -- Richard Gaskin Managing Editor, revJournal ___ Rev tips, tutorials and more: http://www.revJournal.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
