1. [WIN] The installer
Howdy y'all!
I've gotten the packager set up, and I'm now writing a Windows installation
app to install the package. I've slated the following libraries and
programs to be included as optional installs:
win32lib.ew
database.e
objecteu.e
XIDE (Judith's IDE)
CS:EE (by popular request)
Keep in mind that some of these optionals are pending approval by their
authors. At this point, the installation package file, unzipped, comes to
about 2.5M.
Are there any popular libraries which I've missed? If so, please request
them either on the list or privately, and I'll see what I can do. I need to
keep the installation package down to a somewhat reasonable level (read less
than 5M), but if there's a big one which is heavily requested, I will of
course include it. Also, I do not want to duplicate functionality if at all
possible (no more than one library which does any one thing).
In the words of Mr. Bartyles and Mr. James, "thank you for your support."
Travis Beaty
2. Re: [WIN] The installer
Howdy!
Mr. Bensler wrote:
> I suggested this already, but..
>
> Why not design it as an online installer?
>
> The users could choose which components they want to install, and they
> would always get the lastest version, because you could use a cfg file
> that is accesed online, to store the locations of the latest copies of
> the various components..
>
> Then the installer would be much smaller, as the user would initially
> only have to download the installer itself.
> The actual dowload size, would depend on what components they want
> installed..
>
> This way, you could also allow for many more optional components..
I am in communication with Mr. Broker concerning this, as I don't have the
Internet programming skills to pull something like that off. So he, or
y'all, would need to whip up that kind of functionality for the installer.
One of the big concerns I have about an "Internet" type install is
installing on machines which are not connect to the Internet. When I first
downloaded Euphoria, I did it from the public library, saved it to disk,
then hand-carried it to my old 486. Had the installation program required
that I get on the Internet, I probably would have deleted it right then and
there, as it would be of no use to me.
What I would suggest instead is having a separate program which can be
optionally installed with the rest of the package. Once the user has
installed Euphoria, they can run the "Check for Update" program to make sure
all their installations are up to date. As far as getting more optional
programs, perhaps a "Get more Goodies" program which can fetch and/or
install more applications. In this way, the non-Internet users get the
package, and the Internet capable machines can get in more goodies as well.
Thus everybody is happy.
Along that vein, I'm also planning on offering a Windows distribution in
which the main euphoria.dat file is broken up into disk-sized chunks ...
sort of like Sun does when downloading Java. (But God forbid this puppy
should end up being 30+M ... Geez)
Feedback is good. The Grand Euphorium is all-knowing, all-wise.
Please continue.
-- Travis --
3. Re: [WIN] The installer
On 5 May 2001, at 12:40, Travis Beaty wrote:
>
> Howdy!
>
> Mr. Bensler wrote:
>
> > I suggested this already, but..
> >
> > Why not design it as an online installer?
> >
> > The users could choose which components they want to install, and they
> > would always get the lastest version, because you could use a cfg file
> > that is accesed online, to store the locations of the latest copies of
> > the various components..
> >
> > Then the installer would be much smaller, as the user would initially
> > only have to download the installer itself.
> > The actual dowload size, would depend on what components they want
> > installed..
> >
> > This way, you could also allow for many more optional components..
>
> I am in communication with Mr. Broker concerning this, as I don't have the
> Internet programming skills to pull something like that off. So he, or
> y'all, would need to whip up that kind of functionality for the installer.
>
> One of the big concerns I have about an "Internet" type install is
> installing on machines which are not connect to the Internet. When I first
> downloaded Euphoria, I did it from the public library, saved it to disk, then
> hand-carried it to my old 486. Had the installation program required that I
> get
> on the Internet, I probably would have deleted it right then and there, as it
> would be of no use to me.
>
> What I would suggest instead is having a separate program which can be
> optionally installed with the rest of the package. Once the user has
> installed Euphoria, they can run the "Check for Update" program to make sure
> all
> their installations are up to date. As far as getting more optional programs,
> perhaps a "Get more Goodies" program which can fetch and/or install more
> applications. In this way, the non-Internet users get the package, and the
> Internet capable machines can get in more goodies as well. Thus everybody is
> happy.
>
> Along that vein, I'm also planning on offering a Windows distribution in
> which the main euphoria.dat file is broken up into disk-sized chunks ...
> sort of like Sun does when downloading Java. (But God forbid this puppy
> should end up being 30+M ... Geez)
>
> Feedback is good. The Grand Euphorium is all-knowing, all-wise.
> Please continue.
Well, since you begged <g>, let me add my 2 cents worth...
My Eu dir is 101 megabytes, with 3,934 files in 393 "folders". Undoubtedly
there is some duplication, and there are some RFCs, and the .htm files are
noteably wasteful for data storage, but even allowing for a dozen megs of
duplicate includes spread around in various "folders", i can't fit it all on one
floppy, it would barely fit on a 100meg zip disc. And until RDS hosts the site
on their own puters, they can't run an asp page to pick and choose the files
users may want in one download,, other than the User Contribution and
Archives page as they are now, which actually works for me, altho it would
be better if the search engine would look into the files.
Travis, i suggest it contain all the internetworking code (such as http and
telnet and ftp and etc get and put, when i find one that works 100% 100%
100%), and all the string handling includes (like tokens and string.e and etc).
And a easy-to-use gui for input and screen display, and diskfile (like "object
data = glom(TheWholeDiskFile)" ) and physical port i/o, for the OS of choice.
That should about cover it. )
Kat
