07-10-2008
Thanks Zaxxon! Nice idea!!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello all,
1) I want to have a GUI application that will call Unix shell scripts,
2) that GUI application should be able to reside on windows ( if possible) and then call Unix shell script either directly or through a server residing on unix.
That is for example.
If a is windows gui (... (1 Reply)
Discussion started by: hchivukula
1 Replies
2. Shell Programming and Scripting
Hi Everybody,
I previously posted this under Unix for dummies and got no answers, so here goes again:
I'm trying to create a script that will launch firefox from a bash shell in ubuntu and perform certain tasks.
Why does it have to be a script? Because this firefox must eventually run in a... (0 Replies)
Discussion started by: rummage_bin
0 Replies
3. UNIX for Dummies Questions & Answers
Hi Everybody,
I'm trying to create a script that will launch firefox from a bash shell in ubuntu and perform certain tasks.
Why does it have to be a script? Because this firefox must eventually run in a server with xvfb (no gnome, no kde), so I will not have access to it through the GUI.
At... (2 Replies)
Discussion started by: rummage_bin
2 Replies
4. Shell Programming and Scripting
Hi,
I want to write shell script file that have a GUI with multiple input box for user entry , i mean multiple input box in one dialog ( window) not one window for each entry , i tried kdialog , and zenity , i didnt find a way to have multiple input box in one window with zenity and kdialog.... (0 Replies)
Discussion started by: mr_aliagha
0 Replies
5. Shell Programming and Scripting
I want to make a GUI in perl tk where I can give some user input. This user input is the command line argument for a shell script. After giving the input parameters I want the user to press a button and the shell script should start executing. How should i interface the shell script with the GUI? (0 Replies)
Discussion started by: lassimanji
0 Replies
6. Shell Programming and Scripting
Hi all! Im wondering if its possible to create a GUI for a shell script I just got done writing as the people that will be using it dont like the command line all to well. Just something simple with radio buttons to select options, maybe a text field to enter a location to save the file generated... (1 Reply)
Discussion started by: Grizzly
1 Replies
7. Shell Programming and Scripting
hi,
i've to write a shript based application which should gives a look and feel like a GUI. can any one give me a base idea on how to design a GUI based application using shell script.
Regards,
vijay:b: (1 Reply)
Discussion started by: vij_krr
1 Replies
8. Shell Programming and Scripting
Hi.
I'm pretty new to shell scripting. All I want to do is have a simple shell script that opens a python script from the GUI i.e. when I double click the shell script it will launch the python file. However when I try to do this it looks for the python file in my home directory, I have tried... (1 Reply)
Discussion started by: whatg
1 Replies
9. Programming
python gui or c++ gui or java gui?
and when to use etch one? (1 Reply)
Discussion started by: kaja
1 Replies
10. Shell Programming and Scripting
Hi,
I have shell script that I am running under Ubuntu as root.
Is it possible to hide the command window and show the user some sort of progress /random progress bar / or other form of GUI interaction?
On MAC, I have been using Platypus but on Ubuntu I am not sure what to do. (4 Replies)
Discussion started by: naveedanwar4u
4 Replies
LEARN ABOUT SUSE
pdl::philosophy
PHILOSOPHY(1) User Contributed Perl Documentation PHILOSOPHY(1)
NAME
PDL::Philosophy -- what's behind PDL?
DESCRIPTION
This is an attempt to summarize some of the common spirit between pdl developers in order to answer the question "Why PDL"? If you are a
PDL developer and I haven't caught your favorite ideas about PDL, please let me know!
An often-asked question is: Why not settle for some of the existing systems like Matlab or IDL or GnuPlot or whatever?
Major ideas
The first tenet of our philosophy is the "free software" idea: software being free has several advantages (less bugs because more people
see the code, you can have the source and port it to your own working environment with you, ... and of course, that you don't need to pay
anything).
The second idea is a pet peeve of many: many languages like matlab are pretty well suited for their specific tasks but for a different
application, you need to change to an entirely different tool and regear yourself mentally. Not to speak about doing an application that
does two things at once... Because we use Perl, we have the power and ease of perl syntax, regular expressions, hash tables etc at our
fingertips at all times. By extending an existing language, we start from a much healthier base than languages like matlab which have
grown into existence from a very small functionality at first and expanded little by little, making things look badly planned. We stand by
the Perl sayings: "simple things should be simple but complicated things should be possible" and "There is more than one way to do it"
(TIMTOWTDI).
The third idea is interoperability: we want to be able to use PDL to drive as many tools as possible, we can connect to OpenGL or Mesa for
graphics or whatever. There isn't anything out there that's really satisfactory as a tool and can do everything we want easily. And be
portable.
The fourth idea is related to PDL::PP and is Tuomas's personal favorite: code should only specify as little as possible redundant info. If
you find yourself writing very similar-looking code much of the time, all that code could probably be generated by a simple perl script.
The PDL C preprocessor takes this to an extreme.
Minor goals and purposes
We want speed. Optimally, it should ultimately (e.g. with the Perl compiler) be possible to compile PDL::PP subs to C and obtain the top
vectorized speeds on supercomputers. Also, we want to be able to calculate things at near top speed from inside perl, by using dataflow to
avoid memory allocation and deallocation (the overhead should ultimately be only a little over one indirect function call plus couple of
ifs per function in the pipe).
We want handy syntax. Want to do something and cannot do it easily? Tell us about it...
We want lots of goodies. A good mathematical library etc.
AUTHOR
Copyright(C) 1997 Tuomas J. Lukka (lukka@fas.harvard.edu). Redistribution in the same form is allowed but reprinting requires a permission
from the author.
perl v5.12.1 2009-10-17 PHILOSOPHY(1)