World: r3wp

I admit we went into a side thread  ;-)

I prefer to think of it as Maxim being a useful sounding board. He 
helped me work through some of the trickier issues through being 
a devil's advocate :)

has anyone been able to install rebol on windows 7 so it executes 
with -qs arguments?

what do you mean by "so that it executes" - just tried it and it 
seems to start...

not installed under program files, though

First, thanks to Brian for making sure this gets done right (or at 
least the best we can given the circumstances :-). Getting the installer 
right is part of the battle, but another part is making sure we, 
as  developers, do the right thing as well. The effort to identify 
system direcories, and provide mezzanines to make it easy to use 
them correctly, benefits everyone.


The old Roxy installer code is all BSD, and I'm happy to provide 
it, even if just for fodder.

Was that the open source installer for the SurfDetective?

Yes.

As I recall you never released it as there was no documentation or 
something

There are open source installer-builders for Windows that I can read. 
I've even used some of them. What I'm weak on is other platforms, 
particularly Linux. I want scripts to be able to run on Linux the 
same as on Windows, so corresponding concepts should have corresponding 
settings.

Quite possible, knowing me. I don't remember if SURFNet released 
it or not, but I don't think I ever did.

Brian: What would be one such "corresponding concept" and how would 
you use it from within REBOL? (Assuming that meant REBOL scripts 
by "scripts").

The trick with installers is making sure the program reads from the 
right places after it is installed. That was a big problem for View 
after Win2k came out: You could write an external installer, but 
REBOL kept looking for settings in the wrong locations in the registry.

Yes, the sys-vars module in Roxy is a crude start on that, so you 
don't know about Documents and Settings versus ~ or Program Files 
versus /usr/local/bin.

What was always missing in R2 was the ability for a programmer to 
get system information in easy to use way.

user-name (actuall real login of running task)
user home and related dirs

things like that which should be in the next release, especially 
if you are going to rummage through all of this.


I used routines to get to some of this, but I think it would be nice 
if this was built-in.

Andreas, corresponding concepts:
- The place where the program is installed/located.

- The place where the installed program version is listed, so you 
can know whether an update is needed.

- The place where user files, particularly the view-root and desktop 
files, needs to go.

- The place where machine-specific user settings should go (console 
layout on Windows).

- File associations, where possible. Not assuming that these are 
possible on platforms other than Windows.


Where these go depends on the installation profile. Yes, not installing 
at all is one of those profiles.

Ah, so the scripts you were talking about are installer scripts.

No, I mean scripts at runtime. Installer scripts are platform-specific, 
but once things are installed, the scripts at runtime should be platform-agnostic.

That's nothing to do with an installer then, has it?

Adrian, "so it executes"  I meant installing rebol in the OS via 
file extensions so it always uses the -qs arguments over and above 
those it gets from the explorer.


also can shortcuts have arguments in win7?  this was removed in vista.

So every one of these concepts needs a runtime setting that tells 
user scripts where stuff goes.

What was always missing in R2 was the ability for a programmer to 
get system information in easy to use way....I used routines to get 
to some of this, but I think it would be nice if this was built-in.


So every one of these concepts needs a runtime setting that tells 
user scripts where stuff goes.

Agree++

Andreas, the installer determines these things at install time, and 
sets things up for the runtime. but the runtime has to look for stuff 
where the installer puts it, and previously R2's runtime looked in 
the wrong places.

Installing REBOL/View on Linux consists of putting a binary in the 
right place

For that, only one of the things you listed is needed: information 
about where to put the binary.

and its a different place in many linuxes now.  :-(

And then where are the user files, such as the view desktop placed? 
And how does the runtime determine that?

That's the runtime's problem

Most likely even an app-specific installation problem

That is part of the installer project.

another thing which is missing is explicit font path.   The Os might 
not know, but at least if we could configure it manually then we 
could script independently of linux install.

View is the app that we are specificly discussing now.

viewtop is the app you are discussing

nope its /view.

If i right a view app... where do I put my config files?

that's a third party app, maxim

this sort of thing right now is pretty hard to determine.

/view: a binary, viewtop: an app that needs additional settings

/View has Viewtop built in, so it's a built-in app.

yes, but it's still only a view app

I really don't see what viewtop has to do with it.

right now, when we write REBOL apps, we are running blind.  its very 
complicated, and something most script coders will not put the time 
to learn.

rebol/view binary does not need to know about a location where to 
place viewtop files

Andreas, you are not getting that /View is not installed until viewtop 
can run properly. And that needs user directories, and font paths.

well, that's open for discussion

hell even most C coders don't know where the files really go since 
that's all abstracted by the IDE APIs they use.

That is what installing /View means.

if i were to package /view for linux, it would certainly be two packages

view and viewtop

Andreas, even without viewtop, none of this would change.