[REBOL] flavors & versions... Re:(3)
Hi Pete, you wrote: >As far as the other files associated with Rebol, how do you handle storage? Under Windows all versions of the REBOL interpreter are called rebol.exe, for instance. So you will have to either rename them, or install them in separate directories. REBOL/View (if I recall correctly), creates a REBOL directory in \Program Files and creates a view directory in the REBOL directory. Core and Command would also normally belong in their own directories. This may be important because you may want to have different entries in the user.r file for different REBOL versions. >Either I have multiple versions of the same files in different directories, or I >overwrite a script intended for use with View with one that only works in Core, Everything that works in /Core must work in /View and /Command. >etc. Maybe scripts should have command: core: and view: blocks that only get >executed depending upon the version of rebol being used... You could also call /Core files filename.r, /View files that include /View specific stuff filename.rv and /Command files filename.rc. That would avoid confusion as well. > >I'm enjoying the book, BTW. Thanks. >-- >Pete Wason|"LWATPLOTG"|[EMAIL PROTECTED]|[EMAIL PROTECTED]|CUCUG|TA|PHX > > ;- Elan [ : - ) ] author of REBOL: THE OFFICIAL GUIDE REBOL Press: The Official Source for REBOL Books http://www.REBOLpress.com visit me at http://www.TechScribe.com
[REBOL] flavors & versions... Re:(3)
Hi Pete, I am using Linux and have all rebol versions installed in different directies, but with the same rebol_home. I am using /core /command /view subdirs for my scripts, and use if rebol/product = 'view [] in some scripts, I hope this helps, regards, Ingo Once upon a time [EMAIL PROTECTED] spoketh thus: <...> > As far as the other files associated with Rebol, how do you handle storage? > Either I have multiple versions of the same files in different directories, or I > overwrite a script intended for use with View with one that only works in Core, > etc. Maybe scripts should have command: core: and view: blocks that only get > executed depending upon the version of rebol being used...
[REBOL] flavors & versions... Re:(2)
[EMAIL PROTECTED] wrote: > > Hi Pete, > > 1. Upgrading Command: I suspect the REBOL/Command uses an umodified /Core > upgrade function (bug!). That upgrade function (because its unmodified) > does the same thing it would do if it was evaluated under /Core. It > downloads the latest /Core archive. Keep in mind that /Command is an > experimental version. To upgrade it go to > http://www.rebol.com/xpers/xpers.html and download the latest version. > > 2. Upgrading /Core: Which /Core version are you currently using? Does there > exist a newer stable version, or are you trying to upgrade from/to an > experimental version? If that is the case use the above url as well. > > 3. View: When /View is installed it attempts to write a copy of the /View > executable to the target directory. If that target directory is identical > to the directory from which you launched /View, then /View will not be able > to overwrite itself (MS Windows stops it from doing that). You must unpack > /View to a different (for instance temp) directory, and install it from > there. If launched from a different directory /View will successfully > overwrite the old version of /View it finds in the target directory. (I had > a similar problem on my Win95 machine and solved it by unpacking /View to a > different directory). > > Hope this helps. Thanks Elan - As far as the other files associated with Rebol, how do you handle storage? Either I have multiple versions of the same files in different directories, or I overwrite a script intended for use with View with one that only works in Core, etc. Maybe scripts should have command: core: and view: blocks that only get executed depending upon the version of rebol being used... I'm enjoying the book, BTW. -- Pete Wason|"LWATPLOTG"|[EMAIL PROTECTED]|[EMAIL PROTECTED]|CUCUG|TA|PHX
[REBOL] flavors & versions... Re:
Hi Pete, 1. Upgrading Command: I suspect the REBOL/Command uses an umodified /Core upgrade function (bug!). That upgrade function (because its unmodified) does the same thing it would do if it was evaluated under /Core. It downloads the latest /Core archive. Keep in mind that /Command is an experimental version. To upgrade it go to http://www.rebol.com/xpers/xpers.html and download the latest version. 2. Upgrading /Core: Which /Core version are you currently using? Does there exist a newer stable version, or are you trying to upgrade from/to an experimental version? If that is the case use the above url as well. 3. View: When /View is installed it attempts to write a copy of the /View executable to the target directory. If that target directory is identical to the directory from which you launched /View, then /View will not be able to overwrite itself (MS Windows stops it from doing that). You must unpack /View to a different (for instance temp) directory, and install it from there. If launched from a different directory /View will successfully overwrite the old version of /View it finds in the target directory. (I had a similar problem on my Win95 machine and solved it by unpacking /View to a different directory). Hope this helps. At 12:03 PM 9/20/00 -0400, you wrote: >flavors & versions... >Hiall - > >OK, now I'm really losing it. Here's the way I have things set up on my NTWS4.0 machine: > >E: >\Program Files >\_Rebol >\Command >\Core >\View > > >I install Command, and "upgrade". A zipfile called "rebol031.zip" is written into \Command. I open and extract. Command is over-written by Core. Luckily, I still have the the original installer "command031.zip". > >I install Core, and "upgrade". I get a message that I'm using an unknown version of Rebol. > >I install View, switch to console, and "upgrade". An exe is written into \View. I run it, expecting View to open, but find that it is an installer. I change the Install path to /e/program files/_rebol/view, click "Install", and get a message that /e/program files/_rebol/view/rebol.exe cannot be overwritten. > > >HUH? I asked this before, but got conflicting answers: can I put all three EXEs into the same folder, but call them command.exe, core.exe and view.exe? >Are there differences in the supporting files that would make this impossible? How are other people dealing with the bountiful and myriad flavors and versions of Rebol? I'm not, so far! > >-- >Pete Wason|"LWATPLOTG"|[EMAIL PROTECTED]|[EMAIL PROTECTED]|CUCUG|TA|PHX > > > ;- Elan [ : - ) ] author of REBOL: THE OFFICIAL GUIDE REBOL Press: The Official Source for REBOL Books http://www.REBOLpress.com visit me at http://www.TechScribe.com
[REBOL] flavors & versions...
flavors & versions... Hiall - OK, now I'm really losing it. Here's the way I have things set up on my NTWS4.0 machine: E: \Program Files \_Rebol \Command \Core \View I install Command, and "upgrade". A zipfile called "rebol031.zip" is written into \Command. I open and extract. Command is over-written by Core. Luckily, I still have the the original installer "command031.zip". I install Core, and "upgrade". I get a message that I'm using an unknown version of Rebol. I install View, switch to console, and "upgrade". An exe is written into \View. I run it, expecting View to open, but find that it is an installer. I change the Install path to /e/program files/_rebol/view, click "Install", and get a message that /e/program files/_rebol/view/rebol.exe cannot be overwritten. HUH? I asked this before, but got conflicting answers: can I put all three EXEs into the same folder, but call them command.exe, core.exe and view.exe? Are there differences in the supporting files that would make this impossible? How are other people dealing with the bountiful and myriad flavors and versions of Rebol? I'm not, so far! -- Pete Wason|"LWATPLOTG"|[EMAIL PROTECTED]|[EMAIL PROTECTED]|CUCUG|TA|PHX
