YaSP Scripted [solved]

Selecting a script - request
by patkoscsaba on: Jan 24 2010  patkoscsaba

The MRB project (http://mrb.mandrivausers.ro) packaged your plasmoid for mandriva as RPM, we very much like your plasmoid.

However, this packaging opened a situation which led me to write you this feature request.

As you offer different scripts for YaSP (and I will send you more in the near future) you should reorganize them so that packaging can be done easily.

What I am thinking of is offer a file dialog for the user to select a specific script file. Also, you should offer a very basic default script, so that when the user first starts the plasmoid he/she can see something other than an empty box. The best would be just a simple memory+cpu monitor which is available on all systems.

The other thing for this to be more organized is that you should make a folder ~/.yasp.scripts and put all the scrips in there. In setting offer a file selection which defaults to that folder and users cans see all the other script files.

If you do this, packaging your program for different distributions will be much easier, and unexperienced users, who don't want to write their own scripts, will find out easily about the scripts and they will be able to test them without modifying/copying files.

Thanks. And very good work!
reply to this

Re: Selecting a script - request
by finkandreas on: Jan 24 2010  finkandreas

The file selector was implemented in 1.0.1 so it is already there (but the default directory is not .yasp.script)
Installing the files is kind of hard (because I was too lazy to read how to install files only when they are not available yet).
If I install the scripts always a user compiles this plasmoid the user will use its changes. And installing only when a file is not available yet, I did not find how to manage with CMake. So I decided to not install any script file at all...

If I install the scriptfiles it will be in /etc/yasp, because Gentoo for example has protected files in /etc, and you explicitly need to decide whether files should be overwritten there. I don't know if Mandriva has some similar protected directories, but otherwise the package management system needs to be smart enough...

For the .yasp directory with the script files in it: Should work with the current version, with only one minor modification
yasp-scripted.cpp:72 m_sScriptPath = sHome + "/.yasp.script";
should be
yasp-scripted.cpp:72 m_sScriptPath = sHome + "/.yasp/default_script";

This only changes the default script file to be in $HOME/.yasp/default_script...

How is the mandriva system working? Do you offer precompiled packages or is the plasmoid compiled by every user?
If you offer precompiled packages you can change this one line and offer the binary.
I maybe will change it next weekend (not much time before), but I still have to think about it, if this is some kind of expected behaviour...
reply to this

Re: Re: Selecting a script - request
by patkoscsaba on: Jan 24 2010  patkoscsaba

On Mandriva RPM packages contain precompiled binaries.

So, your instructions should be enough. Sorry for the file-selector request, it wasn't mentioned in your changelog, and I didn't tried the last version, yet.

Putting the script files in /etc/ I don't thing is a good idea because users may not have access to /etc/ ... may /usr/share/ ... I will talk with the guy responsible for compiling it for MRB and I'll be back to you.