Maybe instead of using perl we can use python (see below: GTK+ Phyton bindings).
If we write the test program without GUI in Python, if hopefully won't be to hard to convert the program to a GUI program with the python bindings which are available for GTK+.
I would be open from moving from Perl to Python. I have already got the core of the script written in Perl (one of my favorite languages), but Python is gaining in popularity and it would be fun to learn.You will have the same issue of an extra download with the JRE as with GTK+. GTK+ looks like it is about 4MB while the JRE is 14MB. I plan on writing the GUI in Java, but someone else is welcome to write a GTK+ GUI.
For writing the plugins, a bash script will probably do the job the best. It is also very easy to make or edit one for another program (users can write and submit there own plugins).
Agreed. However, I would stick with Borne Shell (sh) of which bash is based. Borne is more widely supported and, as you mentioned, they are available for Windows through the unxutils package. The difference between bash and sh is mainly a technicality, but should be mentioned since bash has much more functionality that will not work under the unxutils Windows executables.
I don't know if you have downloaded the last version of ubcd (ubcd50b3), but the dosapps layout has changed.
No, I am still working with version 4.11. I will download the new version soon and update the scripts. The scripts are not ready for release quite yet as there is still more work to do that will change the format of the scripts. It will not be hard to use 7zip to handle the compression/uncompression of the dosapps.
Can you explain all the parameters in the script?
I will need to add more, this is just a start. Your assumptions are correct about the parameters. The CATEGORY is an abstraction that will be mapped to the menu directory of the current UBCD. It was deliberately made different to separate it from the menu's file structure. The LICENSE is just for info. This might be good to have to indicating which plugins can be legally distributed. The LOC is where the files should be placed (under /dosapps, /images, etc). The EXE is the name of the executable file. This is used to generate the startup.bat files.
As you mentioned earlier, since this is based on UBCD4.11 it will have to be updated to work with UBCD5.0. I plan on trying to get the scripts working as they are before I update them.