OpenEuphoria

Re: New Install Program

• Posted by David Cuny <dcuny at LANSET.COM> Feb 24, 2002
• 441 views

Euman wrote:

> This coming from someone who's re-inventing WX-Windows... 

Sorry, I'm missing something here. What am I "re-inventing"? I'm actually 
looking at wxWindows because I *don't* have to create a cross-platform 
toolkit from scratch in Euphoria. I readily admit that spending months of 
time on Llama and company was a complete waste of time, when I could have 
used wxWindows instead.

I'm not going to bang my head against the wall trying to get the Euphoria 
source to play nice with a C++ compiler. If Robert fixes the source so it 
plays nice with C++ (and he may have done that already, I haven't looked 
recently), I'll be more than happy to look at adding trying to add wxWindows 
to Euphoria. Until then, it seems a pointless project to pursue.

And I've never had an issue with a Windows-based installer. In fact, I'd even 
written a version of the installer *using* Inno Setup, with Euphoria code 
modifying AUTOEXEC.BAT, and suggested to Robert he use something like that. 
At the time, Robert thought that the 400K hit was too much of a tradeoff.

> Maybe we should all throw up our hands and go back to machine code.
> Not ASM, that a re-invented wheel not C cause its re-invented
> certainly not Euphoria whos very base is C. So, I guess re-invention might
> be a good thing? NO?

I don't follow the argument. In each of these cases, one thing is followed by 
something substantially *different*. C is obviously not assembly.

In contrast, what benefit is there to writing a Euphoria installer? It 
doesn't invent anything new, it just recreates something that already exists. 
That's what I mean by reinventing the wheel.

> I think it sucks and leans toward the attitude of half-A**ing somthing.

Inno Setup certainly isn't a half-assed program, so I'm not sure what sort of 
'somthing' you're referring to. Besides, it *does* execute Euphoria code as 
part of the install, it's just hidden from the user.

The user really doesn't care what the installer is written in. Plus, if the 
installer is written in Euphoria and has a bug, you create a bad impression, 
right off the bat. And with so many different configurations of Windows out 
there, the odds are pretty good that's going to happen. Inno Setup has been 
tested on a lot of platforms by a lot of people - something that a Euphoria 
installer won't have, no matter how well it's written.

I just don't see this as an issue.

-- David Cuny