[REBOL] Re: problems with SDK under Windows 2000
From: greggirwin:mindspring at: 28-Apr-2003 18:24
MM> I am new on this list; so let me first present myself and why I am using REBOL:
MM> as a professor of computer sciences in a Public Health School (Brussels University),
MM> I have decided to use REBOL for a cooperative medical application that need
MM> simultaneously (1) acces to the net, (2) encryption (as to protect medical data)
MM> and (3) a graphical user interface.
MM> Also, (4) I need to provide my end users (they are M.D.'s) with executables.
That sounds great! Let's see if we can track down your issues and get
you rolling, or at least work around it.
MM> 1) I understand from REBOL.COM site that SDK (that I just purchased )
MM> is "View/PRO + other things" and that View/PRO is thus included in SDK.
MM> I observed that, in my purchased and downloaded zip file, there is no
MM> replacement for
MM> the free REBOL/View I used before.
MM> Is this a mistake?
The SDK is rather new and doesn't include the equivalent of a View
product. Before the SDK there was Encap, which has both View and
Command binaries you can bind against. You might give Cindy a call and
see if they'll give you any kind of a deal on that. I'm testing with
the SDK but, since it's still beta and has at least one bug that I
can't avoid right now (more below), I still use the Encap pieces for
production work. That should get you running with little effort, so
the only question would be cost.
MM> 2) Thus, in the absence of a View/PRO version, I try to use the FACE
MM> version (rebface.exe)
MM> after adding 3 #include's statements for %mezz.r , %prot.r and %view.r in
MM> my script
MM> as suggested in the documentation.
MM> Unfortunately, this result in an error "layout has no value".
I haven't seen that, but I haven't tried to build View from Face yet
either. :) The LAYOUT function is there and being set in %view.r, so I'm
guessing there's a bug somewhere that's causing it. I'll try to find
time to check into it, but you might send it to feedback (from
www.rebol.com) and see what they say - if anything.
MM> 3) I have tried to encapsulate the same script using enface.exe
MM> ( I have in fact tried with several simple scripts with several names.)
MM> The preprocessing seems to run well. The list of files is displayed properly.
MM> But then I receive the (encap) error message
MM> "Output file cannot be created. Is it running? Is it a directory?"
MM> Obviously, the name for the .exe file was available but enface.exe
MM> seems to be enable to write the file.
I've seen this as well. As near as I can figure (and what I sent to RT
feedback), having a TITLE set in the ENCAP field of the script's header is bad;
that's the bug that gets a lot of us right now. If you put the encap
app (e.g. EnPro) in the same dir as the script, it builds OK but the
resulting EXE crashes. Running from the SDK dir and using fully
qualified path names for In/Out files seems to cause the "Is it running?..."
If you have a TITLE value in your encap header, you might try removing
that and see what effect it has as well.