@kelsenelle: some suggestions for next wpi version

[AlBundy33]

Hi kelsenellenelvian,

here some suggestions for your next wpi version:

1. new "style" for Previous- and Next-Links

They should be aligned left and there should also be a space before and after Previous like on Next.

Why it should be aligned left?

If your Programmnames are to long it is possible that the whole table is greater than the screen an so the Next-Link is not visible (it is outside of the screen).

2. Are your Registry-Tweaks on wpi-startup realy neccesary?

3. Why are "so much" command in wpi.cmd?

you can get the scriptdirectory from unescape(location.pathname)

%CDROM% should not be neccesary i think, because you try to get it in javascript

Delete links and restart should be done by user-scripts (in wpi)

why didn't you use a javascript-command to run external commands?

So the command

start /wait %windir%\system32\mshta.exe "%CD%\wpi.hta"

should be the only one in wpi.cmd

4. A replacment from Discpath to Base-Dir would be very nice - with the Option to get the relative Path from the wpi-directory to the software-basedirectory.

--> the variable %base% should be replaced by the full qualified path from wpipath+basepath

Example:

Softwarepath: E:\Addon\Software

WPIPath: E:\Addon\WPI

Basepath: ..\Software

In commands you can use %BASEPATH%\AcrobatReader\setup.exe which will be transformed to e:\Addon\Software\AcrobatReader\setup.exe

What did you (an all others) think about this suggestions?

Al

[EDIT]

This is my FindCDRom-Function from generate.js to replace %CDROM% with the Directory which is one level upper than WPIPath.

Example: WPIPATH: E:\Software\WPI

With this script %CDROM% will be replaced by E:\Software

function FindCDRom()
{
	position = "generate.js";
	cddrv = fso.GetAbsolutePathName(".\\..");
	debug("Found CDROM as folder " + cddrv,1,2);
	foundCDdrv = true;
	return cddrv;
}

[/EDIT]

Edited September 16, 2005 by AlBundy33

[oneless]

.........

In commands you can use %BASEPATH%\AcrobatReader\setup.exe which will be transformed to e:\Addon\Software\AcrobatReader\setup.exe

<{POST_SNAPBACK}>

this is most interesting thing (for me)

is possible to declare other vars/const in config.js ?

pathes like %drivers% , %hotfixes% ,

or more , maybe boolean expressions to use in cond[] or cmd1[] ...

[AlBundy33]

Why did you want to use more varaibles?

What about this:

Softwarepath: E:\Addon\Software

WPIPath: E:\Addon\WPI

BasePath: ..\Software

Structure of E:\Addon\Software

E:\Addon\Software\Driver\NVIDIA

E:\Addon\Software\Driver\ATI

E:\Addon\Software\Apps\AdobeAcrobatReader

E:\Addon\Software\Apps\MSOffice

E:\Addon\Software\hotfixes --> why didn't you integrate the hotfixes into win-setup - they also have an /integrate-switch like SPs

In commands u can use

%BASEPATH%\Driver\NVIDIA

%BASEPATH%\Driver\ATI

%BASEPATH%\Apps\AdobeAcrobatReader

%BASEPATH%\Apps\MSOffice

%BASEPATH%\hotfixes

which will be replaced to full qualified pathnames.

So why did you want to use more than %BASEPATH%?

Al

[oneless]

you are right . i can live with that .

was just a thought . but (on your sample) if can cost only a line to put somewhere

%hotfixes%=%BASEPATH%\hotfixes

or

stringconstsample1='getOSver()=="XP"'

or other things who can save my time

when i use it ten or hundred times !

i have over 2100 line in my config.js

[AlBundy33]

In my config.js are more than 4000 Lines.

--> I've wrote a Batchfile which generates the config.js from a lot of single files (one file for every application).

I don't understand why you need a variable named hotfixes with the value %BASEPATH%\hotfixes.

Why did you don't want to use %BASEPATH%\hotfixes ?!?

I hope that the option with BASEPATH will be implemented in next version

Al

Edited September 16, 2005 by AlBundy33

[oneless]

just a last moment ideea .

maybe can be used for more then above ,

a real windows .ini file , with sections ..values ..etc

easy to maintain (autoit work native with .ini for example)

team ?

[oneless]

In my config.js are more than 4000 Lines. 

I don't understand why you need a variable named hotfixes with the value %BASEPATH%\hotfixes.

Why did you don't want to use %BASEPATH%\hotfixes ?!?

I hope that the option with BASEPATH will be implemented in next version 

Al

<{POST_SNAPBACK}>

i do NOT need a variable called %hotfixes% ( was just a very stupid sample , anyway i have other structure of my folders)

and i WANT to use an option like BASEPATH . ok ?

my point is that i want to know if it is possible to declare myself , my privat variables / constants if I WANT .

if this is VERRRY simply , like one line somewhere i WANT to know.

Do i make myself clear now ? ( i heard this in many movies and i like it)

[AlBundy33]

ok ok - now I understand.

You WANT to use BASEPATH.

I hope that our wishes come true.

Al

[oneless]

look here

Edited September 16, 2005 by oneless

[Kelsenellenelvian]

Hi kelsenellenelvian,

here some suggestions for your next wpi version:

1. new "style" for Previous- and Next-Links

They should be aligned left and there should also be a space before and after Previous like on Next.

Why it should be aligned left?

If your Programmnames are to long it is possible that the whole table is greater than the screen an so the Next-Link is not visible (it is outside of the screen).

2. Are your Registry-Tweaks on wpi-startup realy neccesary?

3. Why are "so much" command in wpi.cmd?

you can get the scriptdirectory from unescape(location.pathname)

%CDROM% should not be neccesary i think, because you try to get it in javascript

Delete links and restart should be done by user-scripts (in wpi)

why didn't you use a javascript-command to run external commands?

So the command

start /wait %windir%\system32\mshta.exe "%CD%\wpi.hta"

should be the only one in wpi.cmd

4. A replacment from Discpath to Base-Dir would be very nice - with the Option to get the relative Path from the wpi-directory to the software-basedirectory.

--> the variable %base% should be replaced by the full qualified path from wpipath+basepath

Example:

Softwarepath: E:\Addon\Software

WPIPath: E:\Addon\WPI

Basepath: ..\Software

In commands you can use %BASEPATH%\AcrobatReader\setup.exe which will be transformed to e:\Addon\Software\AcrobatReader\setup.exe

What did you (an all others) think about this suggestions?

Al

[EDIT]

This is my FindCDRom-Function from generate.js to replace %CDROM% with the Directory which is one level upper than WPIPath.

Example: WPIPATH: E:\Software\WPI

With this script %CDROM% will be replaced by E:\Software

function FindCDRom()
{
	position = "generate.js";
	cddrv = fso.GetAbsolutePathName(".\\..");
	debug("Found CDROM as folder " + cddrv,1,2);
	foundCDdrv = true;
	return cddrv;
}

[/EDIT]

<{POST_SNAPBACK}>

#1 Yes a very good idea it will be done.

#2 Yes the reg tweaks are ABSOLULTY neseccary for the running of WPI.

#3 I am going to look at these suggestion expecially the one you posted on this thread about paths and how to achive them (will be testing) please PM as I have some questions. As for some of the others we are already making them part of the internal code for WPI.

#4 WTF? Please explain this a little further.

[athomsen]

AlBundy33, everything you posted is a great idea and in fact I have already thought of them too. I am rewriting WPI because quite frankly as you have noticed with many different people making changes the code has been butchered. (no there is no eta on me being finished) Besides that I am brining it into the 20th century and using classes.

Oh yea... I have mentioned this before but some of those reg tweaks are DANGEROUS esp in a network environment. I have not tested if they are required but kel the are on fresh installs. One of the things I have already done is to move them all to WPI and have them removed when it is done running. I am going to make the cmd file disappear come hell or high water.

[Kelsenellenelvian]

The reg tweaks are very needed, however the removing of them definately should be added.

[athomsen]

A friend read this and thought that this comment that I made did not come off as I intended:

I am rewriting WPI because quite frankly as you have noticed with many different people making changes the code has been butchered.

It is probably because I wanted to kill someone at Verizon when I wrote that, but that is a whole other story. I would like to clarify that what I meant to say was that the code is screwed up but that had to be expected when there is a community of "non-programmers" working on a project with little to no documentation for a long period of time. (By documentation I mean for the programmer)

Sorry if I p***ed anyone off. I'll cool down before I post next time

[Dicer]

[EDIT]

This is my FindCDRom-Function from generate.js to replace %CDROM% with the Directory which is one level upper than WPIPath.

Example: WPIPATH: E:\Software\WPI

With this script %CDROM% will be replaced by E:\Software

function FindCDRom()
{
	position = "generate.js";
	cddrv = fso.GetAbsolutePathName(".\\..");
	debug("Found CDROM as folder " + cddrv,1,2);
	foundCDdrv = true;
	return cddrv;
}

[/EDIT]

WOW thanks so much. I was searching for this for so long. I wanted to use WPI to install from usb hard disk, but it never worked, now it works like a charm.