Forums

I am reading the documentation from your web site. My script dosn't seem to work.  Is your documentation for version 4.2.1, or did I miss something. Yes I saved as a .txt file.

#!/bin/bash

[ “$PLAYONLINUX” = “” ] && exit 0

source “PLAYONLINUX/lib/sources”

POL_SetupWindow_Init

POL_SetupWindow_message “Hello World!” “My first message”

POL_SetupWindow_Close

exit

Edité par steve723

lol. no. I mean, that is kind of right, but how did you try and run it?

Also, do you know any BASH at all? You really should know basic scripting and be comfortable with a command line.

All scripts should be saved as scriptname.pol

To run custom scripts:

PlayOnLinux -> Tools -> run a local script -> choose script, and run it

So, I mean, dont just follow it, you have to understand what these functions do, otherwise you wont be able to write them.

source “PLAYONLINUX/lib/sources”

You forgot a $ in front of PLAYONLINUX, as that is a variable.

So, you really need to watch out for syntax, spelling, and everything. This is something we cannot teach, and that you will have to do reading on and practice. You really want to learn BASH, as that will help a lot.

Look at this, and tell me whats different, because this works fine:


#!/bin/bash
[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"

POL_SetupWindow_Init

POL_SetupWindow_message “Hello World!” “My first message”

POL_SetupWindow_Close
exit

Yes the variable error became painfully obvious once I opened the script in Kate which hilights variables in green. I also resaved in .pol. I then compared my script with what you show and saw that it seemed to be the same. I tried it and still nothing.

Lets see scripts don't always work as they should and the wine gecko never downloads when creating a VD and we already tried redoing POL initiaul config. I am woundering if my Linux system got broken somehow. I already tried konsole > sudo apt-get update && apt-get dist-upgrade . I don't know what it could be.

I dont know, but it really seems like that shouldnt be an issue.

If run that script exactly as it is, exactly like I said, it pops up with hello world. I just used it.

Let me guess; you are running ubuntu 13.04?

Isin't that Raring Ringtail. Then yes. but kde version.

steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~$ uname -a
Linux steve7233-HP-Pavilion-dv6-Notebook-PC 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Edité par steve723

#!/bin/bash
[ “$PLAYONLINUX” = “” ] && exit 0
source “$PLAYONLINUX/lib/sources”

POL_SetupWindow_Init

POL_SetupWindow_message “Hello World!” “My first message”

POL_SetupWindow_Close
exit

Ok, so, I will say right off the bat, that ANYTHING but 12.04.x at this time is just a beta. I have been running Kubuntu 12.04.2 64 bit, and it works great. Anything but LTS versions of Ubuntu are BETA versions, and use experimental software and configs.

After everything that has been causing your system issues, Im willing to bet that your OS is screwed. I recommend reinstalling you OS with Kubuntu 12.04.2 LTS (ONLY LTS) and trying that. Your system shouldnt have this many issues, and I think that in your quest to get stuff working, your system got jacked up. I have done it myself MANY times. hahahaha. It happens. Thats why backups are you friends.

At this point, I think thats the best solution.

As for your script, dont post it here. You need to read and test on your own. We cannot teach you BASH or scripting in general. Google will be your best buddy for learning that. Everything that is used in scripts is simply BASH with python functions, but you need to learn basic BASH and Linux command line basics before writing scripts. Im still a beginner when it comes to this too, so Im right there with you.

(.pol is NOT an extension for scripts yet. Be careful, .pol files have another specification

Some hint for those that develop scripts: there's a faster way to run them than thru Tools > Run local script > It's not signed are you sure > Yes I'm sure
You can also run them using playonlinux-bash, like
$ playonlinux-bash scriptname
It makes for a much faster and painless turnover, specially if you can use that command as a "compile" command in your favorite editor...

Some hint for those that develop scripts: there's a faster way to run them than thru Tools > Run local script > It's not signed are you sure > Yes I'm sure
You can also run them using playonlinux-bash, like

$ playonlinux-bash scriptname

It makes for a much faster and painless turnover, specially if you can use that command as a "compile" command in your favorite editor...

steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~$ $ playonlinux-bash DJYoshaBYD.pol
$: command not found

I saved his scipt to see if it would execuite.  It did but, it only said Hello. It didn't say Hello World just Hello. Thats furthur than I get. I wonder if Libre Office Writer put hidden formatting codes in mine. Which editor should I use. Kate?

$ is the traditional symbol of normal user's prompt, it shouldn't be typed

I noticed. Rokie Linux mistake.

Why dosn't this work:?
steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~/Documents$ playonlinux-bash script_Learning.pol
[main] Message: PlayOnLinux (4.2.1) is starting
[clean_tmp] Message: Cleaning temp directory
Script started script_Learning.pol
bash: script_Learning.pol: No such file or directory

steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~/Documents$ ls
DJYoshaBYD.pol POL script Learning.pol python2-20130628-161441.kcrash.txt
Lotrol Installer script.txt POL script_Learning.pol Relif society Presidency.odt
muon-updater-20130511-071230.kcrash POL script-Learning.pol UntitLotrol Installer script.txt
Playonlinux install scripts POL script Learning.txt
POL script Learning.odt pylotropatch.txt

As you can see the file does exist. I even tried puting quotes around the file name. I can run it just fine from playonlinx just not from BASH.

Some space or case issue (Linux is case sensitive)?
I can't really tell where filenames start and end in your list

Really .pol is not the extension meant for scripts. You should not use it when you are writting scripts

This is the best I have gotten so far:
http://www.flickr.com/photos/56377873@N04/9302311902/

Here is my script. I have some JAVA programming experiance, so I thought what it might be in case the documentation was for an earlyer version of POL and then tried several things to get the output to formate correctly.


.#!/bin/bash
[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"

POL_SetupWindow_Init

POL_SetupWindow_message Hello_World My_first_message

POL_SetupWindow_Close
exit

Hi,
Be sure you use "real" double quotes (ASCII character 34) everywhere, see in previous versions of the script above the difference between the

[ "$PLAYONLINUX" = "" ] && exit 0

line and for example

POL_SetupWindow_message “Hello World!” “My first message”

That use different quotes. Use the first kind only, it's probably why you have issues with your quotes.
Probably some editor or some copy&paste playing tricks on you.

Edité par petch

I got it!


.#!/bin/bash
[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"

POL_SetupWindow_Init

POL_SetupWindow_message "Hello World!" " My first message"

POL_SetupWindow_Close
exit

I started using computers in 1982 and I have always hated how Quatations and space have to be just in the exact right place else your program or script will fail.

Now I can proceed furthur in the script documentation.

Hi,
Be sure you use "real" double quotes (ASCII character 34) everywhere, see in previous versions of the script above the difference between the

[ "$PLAYONLINUX" = "" ] && exit 0

line and for example

POL_SetupWindow_message “Hello World!” “My first message”

That use different quotes. Use the first kind only, it's probably why you have issues with your quotes.
Probably some editor or some copy&paste playing tricks on you.

I discovered this before I read your post. I hate that some editors do that. You would think after all these years they would stop making those kinds of programming code or at least make it an option to turn them on if you want some different looking qoute marks but then you know they are on. Never use Libre Office writter to write a POL script unless you know how to turn that annoyance off. From now on I will use Kate.

Edité par steve723

Ah. I've always named the scripts .pol. For some reason I want to say I was told to, but I'm likely wrong.