Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: cmorgan
« on: May 10, 2010, 10:21:51 AM »

Miloch, taking a look at the Aurora stuff, yep - standard procedure - that has been set up by a number of folks over the years; the difference is that G3 stuff comes pre-setup. So where you send folks to WeiDU and support files, we just have the windows stuff in place for windows, then just the mac for mac, and practically nothing for linux as anyone running linux probably has a strong enough command of terminal usage to download and install.
Posted by: cmorgan
« on: May 10, 2010, 09:34:03 AM »

In my dream-of-dreams, There Can be Only One :)

But I dream big, and life is short. I can adapt to whatever is decided; I am just not sure how many mods will be reconverted to single-installer mode.
Posted by: Miloch
« on: May 09, 2010, 11:56:17 PM »

Heh. But wait a minute Captain Morgan, I thought you were in fact the one behind the whole unified-OS-mod-installer idea. At any rate, I thought I pinched the install instructions (such as for Aurora) from you, though maybe you pinched it from me in turn, who knows any more. Basically it just comes down to grabbing the right WeiDU for your OS (which you should have anyway, if you've installed just one other mod), making a petty change or two, and the same mod is installable on any OS without having to download anything extra. At least in theory, since I can't test it on other OSes, though at least one user said it worked for Linux (granted, for another mod, but whatever).

It's kind of the same reasoning behind the code mergers for BG1/Tutu/BGT mods. Why maintain 3 separate versions just for a few trifling differences? And of course, that's the standard nowadays, as you, jastey and others have shown.
Posted by: cmorgan
« on: May 09, 2010, 05:58:00 PM »

Make one unified RonCo(tm) WeiDU installer that covers all bases for all modders/players for all platforms with tispack tisunpack sox and oggdec all part of weidu, translated into OCAML...

...


...


...

(just waiting for the bigg's brain to stop exploding and listening intently for the number of swearwords I can learn in Italian :D )

Look, if best practice becomes "send people to the WeiDU site and have them download what they need", I think packing mods could get really easy really fast - just package all mods for Linux and send users to the sites for tisunpack, oggdec, sox, etc. and let folks copy whatever wherever. The only problem with that is we have troubles with folks not being able to handle an NSIS or winrar self-extracting .exe installer, let alone deal this $PATH or %PATH%.  Heck, folks even have a hard time with "turn off antivirus and disable UAC when installing".

As for modders trying to package stuff up, I agree that conversion to wavc and adding .sh  materials to files (or even fancier - creating those .bat files via inlined based on the OS determination) would be good. I am all for a simple packaging solution. The challenge is always going to be mods that can't/won't be updated, and folks who won't go back and change their audio. But for new updates/new mods on G3 and for setting up tutorials, heck, if you guys think it is better to toss some lines in a readme and drop materials from that package, I am not going to get bent out of shape.

If those extras are really just for me, I say drop  'em and send me links to the original stuff, and I can work from there. Or better yet, put things like that up as specific links for download into the tutorials or into a new tutorial,  because someday someone might want to package things up for more than one OS. I am easy. And relatively cheap, too.
Posted by: devSin
« on: May 09, 2010, 05:14:56 PM »

NOW I DON'T KNOW WHAT TO DO
Posted by: Miloch
« on: May 09, 2010, 04:52:09 PM »

But like I said, all those extra binaries are really just there for cmorgan to do Mac packages at G3.
These should be phased out in my opinion. Double the maintenance work for no good reason. WeiDU can detect the OS and use .sh files instead of .bat files, which you can include all in the same package without bloating your mod size (and any decent text editor can convert the line feeds to Mac format). About the only thing you might include is the OSX version of tisunpack, which would add a whole 92kb to your mod (possibly less if compressed). And that's available here on PPG, no need to put it in WeiDU too. Adding a Mac version of sox or whatever is useless, since it's already there (and wouldn't be necessary anyway if everyone used WAVCs instead of OGGs which are already lossy).

Besides, there's a total of what -- 2 people who play BG2 on OSX? :P
Posted by: the bigg
« on: May 09, 2010, 02:56:59 PM »

They still have an use (unlike Weinstall and weigui).
Posted by: devSin
« on: May 09, 2010, 02:47:19 PM »

OK, we'll try to be nicer (we'll actually have a copy of the GPL for WeiDU and sox, and tisdocs for Jason) in the next build.

But like I said, all those extra binaries are really just there for cmorgan to do Mac packages at G3. Nobody else even cares.
Posted by: the bigg
« on: May 09, 2010, 07:05:41 AM »

On Mac, it's just because the archive is usually downloaded by Windows modders attempting to package their mod. On Linux, executables like oggdec are called from $PATH rather than from ./, so oggdec can likely be removed from the Linux build as well (unlike tisunpack, which is likely not found on the average Linux users's computer).
Posted by: Miloch
« on: May 09, 2010, 02:52:21 AM »

Is there some sort of documentation needed for sox?
It's GNU GPL according to this.

But I thought it was included as standard on OSX and Linux (it is on my Linux machine anyway). Why include it with WeiDU, or for that matter oggdec and tispack, which mods who need them almost always include anyhow (and at least the former of which, as you say, should be phased out already)?
Posted by: devSin
« on: May 07, 2010, 12:57:49 PM »

Is there some sort of documentation needed for sox?
Posted by: the bigg
« on: May 07, 2010, 12:33:19 PM »

The Linux WeiDU package contains sox, oggdec and tisunpack, apart from the other binaries found in the Windows package.
Posted by: jcompton
« on: May 07, 2010, 12:30:46 PM »

The readme is in the main distro: http://mods.pocketplane.net/tispack-0.91.zip

There's a Linux/x86 compiled version hanging around? I should put that in the distro.
Posted by: the bigg
« on: May 07, 2010, 07:06:46 AM »

WeiGUI.exe from the WeiDU distro is in OCaml and can be used to (un,re)install mods (drop weigui.exe, weidu.exe, tcl84.dll and tk84.dll in the BG2 directory and run weigui.exe). However, it's been abandoned because developing GUI applications in OCaml/tk is madness (as does attempting to download and/or decompress files).

I had plans to re-write it in Java and add all the download/unpack/patch deal that BWS does, but I only wrote a GUI skeleton a couple of years ago. It's not abandoned, just dormant (and could almost be running the risk to begin ending in a non-dormant state).
Posted by: cmorgan
« on: May 06, 2010, 10:32:26 PM »

Dudes, ping me when you start talking English again you want me to do something or v218 rolls out- I'll kick into update-mode when you want. Just one question; does this mean WeiGUI is toast as an expanding project? I think your original plan, the bigg, was to expand it into the same kind of deal the BWP uses. I'm good any way it goes, not that my opinion is really relevant, but if this is a pet project set up as a fieldtest, perhaps it could be packaged and documented and marketed a bit, so it can see the light of day?