Het forum

Here is an install script for Native Instrument's Absynth 5. I have used Absynth for years. It really is a fantastic sounding soft-synth.
[code language=playonlinux]

#!/bin/bash
# Date : (2013-02-01)
# Last revision : (2013-02-01)
# Distribution used to test : Kubuntu 12.04 LTS
# Author : DJYoshaBYD
# Licence : GPLv3
# PlayOnLinux: 4.1.9
  
  
[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"
  
PREFIX="Absynth5"
WINEVERSION="1.3.0"
TITLE="Absynth 5"
EDITOR="Native Instruments"
GAME_URL="http://www.native-instruments.com"
AUTHOR="DJYoshaBYD"
  
#Initialization
POL_GetSetupImages "http://files.playonlinux.com/resources/setups/$PREFIX/top.jpg" "http://files.playonlinux.com/resources/setups/$PREFIX/left.jpg" "$TITLE"
POL_SetupWindow_Init
  
POL_Debug_Init
  
# Presentation
POL_SetupWindow_presentation "$TITLE" "$EDITOR" "$GAME_URL" "$AUTHOR" "$PREFIX"
  
# Create Prefix
POL_SetupWindow_browse "$(eval_gettext 'Please select $TITLE install file:')" "$TITLE"
POL_System_SetArch "x86"
POL_Wine_SelectPrefix "$PREFIX"
POL_Wine_PrefixCreate "$WINEVERSION"
  
#Dependencies
  
# Configuration
Set_OS "winxp"
Set_SoundDriver "alsa"
  
# Installation
POL_Wine_WaitBefore "$TITLE"
GC_DONT_GC=1 POL_Wine "$APP_ANSWER"
POL_Wine_WaitExit "$TITLE"
  
# Create Shortcuts
POL_Shortcut "Absynth\\ 5.exe" "$TITLE"
  
POL_SetupWindow_message "$(eval_gettext 'NOTICE: For low-latency audio, look into WineASIO.')" "$TITLE"
 
POL_SetupWindow_Close
exit 0
[/code]

Screenshots:








Here are the Icons and setup images:

http://djyoshabyd.quicktech209.com/repository/Resources/Icons/Absynth5/

Aangepast door RoninDusette

Hi,
The script looks ok :)

Sweet. I tried to use more variables, and made the setup file selection come up before the prefix was created. I was hoping using more variables.

Sweet. I tried to use more variables, and made the setup file selection come up before the prefix was created. I was hoping using more variables.

Well, most functions interacting with the user return the selected value in $APP_ANSWER, but if this variable can be overwritten, you can turn

POL_SetupWindow_browse "..."

[...]

POL_Wine "$APP_ANSWER"

Into

POL_SetupWindow_browse "..."
INSTALLER_EXE="$APP_ANSWER"

[...]

POL_Wine "$INSTALLER_EXE"

ahhhhhhhh... I dig it. So, basically, using a dynamic variable to create a static variable. That makes sense. Im assuming you can do that over and over, like, create a variable of a variable of a variable, etc etc.. Not that you would want to do this all of the time, but thats the idea, right? Basically a "nested variable"?

Oh, it's nothing sophisticated really, and while shell scripts can become relatively complex, POL scripts should stay as simple as possible for easy communication (I personally often need to refrain from doing complicated things, but I digress :D)

What's happening here is that $APP_ANSWER, like other shell variables by default, is global and dynamically scoped; Functions can clobber it at will, so it may be necessary to backup its value in another variable, nothing more...

ah. ok. I see now. You are using the variable to declare another variable, because if you need to use the app_answer more than once, it will overwrite it. I get it. *lightbulb goes off in head* :) sweet.

Yeah. This script is for sure done. I checked it on a friends computer and it works. I submitted it for signature. :)

Everything should be validated now

Sweet. Got another one coming right now, too. lol