69 replies to this topic

[Miloch]

So: How do I write that?

Write what, something that'll cause a warning? I dunno, try compiling a script that casts a spell that doesn't exist or something.

[dabus]

Two questions:
1. After having funny errors with SCS and it did not seem likely that Lollorian would fix it, I am adding an option that will install as much components as possible in one go.
Before components with subcomponents that are actually selected, the group will be installed and a new one will be opened.
Mods with one component only will not be installed in groups since there is no benefit to a "normal" installation with the BWS.

Where should a group be closed due to memory-usage? BG2_Tweaks only? Is this still needed? Some other mods that come to your mind (SCS/SCSII)?

2. I want to add a message for people that do not have a "standard" codepage (1252) for non-unicode programs. Is this a general problem or does this only matter when installing InfinityAnimations?
Depending on the answer I'd display the message right at the start after selecting the language for the BWS-usage or after the selection of the mods is over.

[Miloch]

After having funny errors with SCS and it did not seem likely that Lollorian would fix it

Eh, you mean DavidW, or are the errors only BWS-related?

Where should a group be closed due to memory-usage? BG2_Tweaks only? Is this still needed? Some other mods that come to your mind (SCS/SCSII)?

Not sure what you mean by "closing a group" but I do recall both SCSes took absolutely ages on my last BWP install (on an external drive).

2. I want to add a message for people that do not have a "standard" codepage (1252) for non-unicode programs. Is this a general problem or does this only matter when installing InfinityAnimations?

It is only applicable to IA, Aurora and Vecna, though hopefully not for the next releases which will use standard ANSI characters in all the filenames (though it might be a while on that).

[dabus]

After having funny errors with SCS and it did not seem likely that Lollorian would fix it

Eh, you mean DavidW, or are the errors only BWS-related?

Well, if someone only selects those components, it would be a generic problem.
I also heard DavidW was absent, and since I'm a WeiDU noob I asked Lollorian for his opinion.

Where should a group be closed due to memory-usage? BG2_Tweaks only? Is this still needed? Some other mods that come to your mind (SCS/SCSII)?

Not sure what you mean by "closing a group" but I do recall both SCSes took absolutely ages on my last BWP install (on an external drive).

I mean when it would be sufficient to execute more then one WeiDU --force-install-list - instances per mod.
The BWP-PDF lists SCSII and BG2_Tweaks.

2. I want to add a message for people that do not have a "standard" codepage (1252) for non-unicode programs. Is this a general problem or does this only matter when installing InfinityAnimations?

It is only applicable to IA, Aurora and Vecna, though hopefully not for the next releases which will use standard ANSI characters in all the filenames (though it might be a while on that).

Ok. I already added a generic warning at the beginning since that's the easiest method.

[Wisp]

After having funny errors with SCS and it did not seem likely that Lollorian would fix it

Eh, you mean DavidW, or are the errors only BWS-related?

Well, if someone only selects those components, it would be a generic problem.
I also heard DavidW was absent, and since I'm a WeiDU noob I asked Lollorian for his opinion.

Wouldn't it be easier to fix the bugs with e.g. the BWP Fixpack than to add stuff to the BWS to circumvent them?

[dabus]

It's not really a big issue, since I already had to create a workaround for hammers, which also has to be installed in one go.
If you like to, you may want to verify the issue: Click.

[Wisp]

(I think) I confirmed the issue here.

[dabus]

Ah, ok, I don't roam around that much.

[dabus]

Another issue came up while testing another way of parsing the debug-files:
Recent versions of BGT, BGTTweak and propably more did not use standard keywords like Installing / Installed successfully but used a localized version.

From my "scripting-standpoint" this is really a major issue since I did those English keywords to recognize if the installation was skipped, had warnings or errors and was able to show them.

If I had to ask for skipped components, that would really be a step backwards for me.

Is it possible to somehow generate old logs or is it easy to search the TP2-files for those translations?
Sorry that I did not do that myself before asking, but I got to get going and buy me some food.

Edit:
Seems like the translation is always the same...
If I'd just had to look for strings like @-1006 = XYZ, fetching the translations would be ok.

Edited by dabus, 21 June 2010 - 12:21 PM.

[Mike1072]

WeiDU comes with a file called prompts.tra. You can override any of these by specifying your own string for them in your .tra files.

Spoiler

// Note added due to LGPL terms.
// 
// This file was edited by Valerio Bigiani, AKA The Bigg, starting from
// 6 November 2005. All changes for this file are listed in
// diffs/examples.prompt.tra.diff file, as the output of a diff -Bw -c -N command.
// 
// It was originally taken from Westley Weimer's WeiDU 185.

 // WeiDU behaves as if the following file TRA were read in automatically
 
 // you can change these prompts by assigning these special negative-index
 // strings to whatever you want in your language-specific TRA files

 // Note that it is NOT my goal to have every string in WeiDU be
 // replaceable. Bug one of the GUI-people if you really want a better UI. 

//@-1000= "This mod has"
@-1000= "The %TP2_FILE_NAME% mod has"
@-1001= "distinct optional components.\nTo save time, you can choose what to do with them at a high level rather\nthan being asked about each one.\n"
@-1002= "What should be done with all components that are NOT YET installed?\n[I]nstall them, [S]kip them, [A]sk about each one? " 
@-1003= "What should be done with all components that are ALREADY installed?\n[R]e-install them, [U]ninstall them, [S]kip them, [A]sk about each one? " 

@-1004= "PLEASE email the file" 
@-1005= "to" 

// @-1006= "Install Component ["
// @-1007= "]\n[R]e-Install, [N]o Change or [U]ninstall or [Q]uit? "
// @-1008= "]\n[Y]es or [N]o or [Q]uit? "
@-1006= "Install Component ["
@-1007= "]?\n[R]e-Install, [N]o Change or [U]ninstall or [Q]uit? "
@-1008= "]?\n[I]nstall, or [N]ot Install or [Q]uit? " 
// note that the keys are always R,N,U,Q,I (synonim of the old, still valid 'Y') !!

@-1009= "Enter part of a module name: " 

@-1010= "Re-Installing ["
@-1011= "] component " 
@-1012= "Re-Installing Using Language" 

@-1013= "Removing old installation of [" 
@-1014= "] first ..." 
@-1015= "SUCCESSFULLY REMOVED OLD" 

@-1016= "Installing" 
@-1017= "ERROR Installing [" 
@-1018= "], rolling back to previous state" 
@-1019= "SUCCESSFULLY INSTALLED" 
@-1020= "Skipping" 
@-1021= "Removing ["
@-1022= "] (component #"
@-1023= ")" 
@-1024= "SUCCESSFULLY REMOVED ["