wineceptor-changelog_0.17

0.01 - 19/08/2013
+ Created the script's file - wineceptor.sh .
+ Created the config file - wineceptor.config -, which is run by the script. Should be placed in the same directory with the script.

0.02 - 19/08/2013
+ The script should use default values, if no are specified in config file. Added the first value, holding the prefixes directory - $prefixesdir .

0.03 - 19/08/2013
+ Created a debug script - wineceptor_debug.sh -, which runs the main script and logs errors and variables.

0.04 - 19/08/2013
+ The script now uses the first parameter to specify the executable, or lets you choose one with zenity gui. Stored in $executable variable.
* Fixed a typo space in debug script, which was causing the number "2" (error output) to be parsed as the executable parameter.
	from:	source wineceptor.sh 2 >> wineceptor_debug.log
	to:	source wineceptor.sh 2>> wineceptor_debug.log

0.05 - 19/08/2013
+ The script uses default values, if specified files or directories ($prefixesdir) do not exist.

0.06 - 19/08/2013
+ If no executable is selected with zenity, then the script will exit.

0.07 - 19/18/2013
+ The script now stores it's location in $scriptsdir, so this is more a fix, than a new feature - config file is now read from script's directory, not from executable's, same with logs being created where they should be.
* Tweaked debug script's starting dialog (clear log file?), so it uses zenity too. Otherwise I suspect it won't ever launch anything. Haven't tried though :) .
* Tweaked debug script's executable variable - now it will always contain the full path to file.
* Tweaked logging, so now you can see the variable names also amongst their "human" meaning.

0.08 - 19/08/2013
+ The script now checks, if the executable is a symbolic link ($issymlink). I know it may be uncomfortable, but, sometimes you want your "working directory" to be set to the place where the actual file is, and sometimes to the place where the symbolic link is.

0.09 - 19/08/2013
+ A very important addition. The actual method of finding a prefix to launch the specified executable. Works by changing directories up, till any wine prefix is found. First time following the symlinks, and if no prefixes found, following physical directory structure. If a prefix is found, then $foundprefix is set to "yes", otherwise to "no". The prefix path is stored in $wprefix.
* Created a $launchdir variable to store the path, from where was the script called (it may differ from the working directory).

0.10 - 19/08/2013
+ If the script can't find any prefix by himself, he promts you to choose one. Implemented by a for | zenity pipeline. A for loop finds prefixes in prefixes directory, and a zenity list is created from them, so you can choose one. Another $path variable is used here, only to cut the pathname and crate the list.

0.11 - 19/08/2013
+ One line, the quintessence of the script, env WINEPREFIX="$wprefix" wine start /unix "$executable", without this line the script won't have any practical use :) . Let's you launch any file in a prefix you want it to be launched in. Of course, if there is any program that can handle those inside the prefix (in that case you would get a wine error saying there is no Windows program configured to launch the file type, so being not a script's fault). There is a small flaw, though. You could run any file with a specified prefix, but however this execution won't be able to somehow damage anything outside the prefix.
* Tweaked the debugging script, the date is printed first, then the main script is launched, so wine errors are now printed before the date (however the script's variable logs may get inside the wine's output, but that's a debug script's issue, you won't be using that anyway, will you ?).
* Changed debug variables printing order in a more logical one.

0.12 - 19/08/2013
+ Added support for additional environment settings (for example - a specific WINELOADER). $useenvsetts in config file. Variables stored in $envsetts.
+ Added support for additonal executable parameters. $useparsetts in config file. Parameters stored in $execparameters.
* The launch command now looks like this:
	env WINEPREFIX="$wprefix" "$envsetts" wine start /unix "$executable" "$execparameters"
	with no "$envsetts" parameter, if that's empty.

0.13 - 19/08/2013
+ The feature I dreamed for. You can create text files with the same name, as the executable, and add ".envsetts" or ".execparameters" to the end of their name. Obviously you can enter some environment variables or executable parameters in there, which will be used automatically, when you launch the executable. If $useenvsetts and/or $useparsetts are set to 1, there will be no promt, for the values from these files will be used.
* fixed a typo which caused a serious leak of fun, resseting the $useenvsetts to be always 0.
	from:	if [[ "$useenvsets" != [0,1] ]] ; then
	to:	if [[ "$useenvsetts" != [0,1] ]] ; then

0.13a - 21/08/2013
* Trying to order the overwrite order for token-files missplaced an array of their names, so the script would never notice any .envsetts file. Fixed.

0.14 - 25/08/2013
+ Added built-in semi-localization (you can turn that on by editing the config file, or the script). gettext involves creating additional non-optional files, which I don't like. I't semi, because it's not changing the system's locale settings, nor it can handle variables right now (should it?). This one involved creating localization blocks inside main and debug scripts, creating a $language variable and multiple $sayxxx variables (e.g. $saynoprefixspecified). The language variable is loaded with the config, then it's checked by a test, which chooses the correct sayxxx variables.

0.15 - 25/08/2013 - A relatively huge update in some sense (55% more symbols :))
+ Token system changed:
	a) You can set specific prefix, directory or executable environment settings, now. You can still make the script ask for these both if they are set, and aren't set
	b) 4 config settings created for that: askenvsetts, askenvsettsifprefixset, askenvsettsifdirset, askenvsettsiffileset).
	c) The token names are as follows: (1)prefix_name.penvsetts, (2)working_directory_name.denvsetts and (3)executable_name.fenvsetts (or .executable_name.fenvsetts), thus should be created in (1)prefix, (2)working directory and (3)same directory as the executable.
	d) The executable token system is unchanged, as currently I don't think someone needs same execution parameters for more than one file. The only difference, is that the token name now is executable_name.fexecsetts (or .executable_name.fexesetts).
	e) You can still create hidden executable tokens, but they will be overwritten by unhidden, if those exist (we don't want any unexpected variables, do we?). No hidden tokens for prefixes or directory.
* Final execution block rewrited, so now it won't use "" instead of empty execution paramters too, like it was done with the environment settings. I haven't met such a programm yet, but there might exist a program, which won't launch if it has such a parameter. e.g. mousepad "" would crash (but that's not windows)
* Deleted useless colons and "End of debug." line from debug script.
* The debug script will prompt you for clearing the log file, if promtforclearingthelogfile is set to 1 (it's in the config).

0.16 - 25/08/2013
+ Different wine versions support. You just have to create a prefix_name.pwinebinary file in your prefix's root directory, containing the full path to your wine binary. It should really be the full path (e.g. the binary is inside a directory, which is listed in PATH variable, e.g. /usr/local/bin).
* Deleted a notify-send command from the debug script, which I left accidentaly.

0.17 - 25/08/2013
+ Created another optional script - wineceptor center. Launching a wineceptor.center.exe file will result in a window to pop up, where you would be able to launch prefix's explorer, regedit, winecfg, winetricks and wineboot's menu (which is also part of this center). Wineboot menu contains options to end wine session, force exit process, kill all processes, update/initialize a prefix.
Note: if you don't have the center script, the main script will try to launch the wineceptor.center.exe like it was a simple executable.
* config file a bit reworked to look neatlier

0.xx - not released yet
+ a zenity gui for the configuraion file.
+ a video and a readme.
+ all scripts should be made one. I can even try to insert the configuration inside the script.