61–70 of 76 posts
Another app in this vein was Kaptain (for KDE): http://sourceforge.net/projects/kaptain/
> Turn (almost) any command line program into a full GUI application with one line and lose the ability to pipe, check exit status, run from cron, run through ssh or a different machine, call from other scripts... The last couple of months as I know about more and more the command line, and can configure my shell and tools the way I like, I feel I'm more productive with the terminal than any other GUI application.
Users assemble their workflows in a sharable, repeatable and somewhat easy-to-use way using the web-ified versions of their command-line tools. Galaxy takes care of hooking everything up (data, scripts, intermediate results, etc) and provides a UI for watching/controlling the resulting job(s) on the desired HPC cluster.
The goal for this in biology is to address the explosion in data modern biologists have to deal with nowadays - it's often completely overwhelming. Things like Galaxy increase both the accessibility of these command-line tools and also the large HPC compute resources traditionally dominated by users from the physical sciences.
Although it was a few years ago, it was rewarding seeing non-programmer users get onto HPC - importantly, while retaining control of their workflow - after they've struggled for so long on their local hardware. When you see jobs that took weeks or months run in hours or days, it's almost like giving a desert explorer some water.
Systems like Galaxy do require dedicated systems people to support it and make it properly sing though. Gooey could nicely accelerate the web-ification part of adding new software.
Similar workflow for Macs: http://www.sveinbjorn.org/platypus + http://mstratman.github.io/cocoadialog/ or http://www.bluem.net/en/mac/pashua/
Yeoog; Turn GUI programs into command-line
Earlier quoted context omitted.
Is there such a thing as POSIX-compliant argument descriptions? I know POSIX specifies some things about the format of options, but I didn't realize there was a formalized option description language.
Yes. IEEE Std. 1003.1 Utility Conventions http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_... This is actually how Docopt happened (Vladimir Keleshev mentioned it in the PyCon UK 2012 talk).
Earlier quoted context omitted.
The man pages are intended for human and are not meant to be specs. An advanced NLP program is required to parse man pages and infer appropriate types and combinations and I suspect it would not be perfect. I agree that this might lead to something which is not in Unix spirit but already shell completion provide such information and this shows the need for such specs.
If only there were an IEEE standard for utility conventions.
Good idea. I wonder if anyone has done this for general unix command-line apps by parsing out the man pages on the fly. It probably wouldn't work for all programs but may be gnu style ones would be consistent enough.
"Transform your command line apps into user friendly GUIs" - https://raw.githubusercontent.com/chriskiehl/Gooey/master/re... Encoder (-e). OpenCV FOURCC Type. {Empty text box}. Just take all possible options and ... shove them right in the user's face. Is that user friendly? Whom is it helping, who doesn't want a CLI but also knows how the CLI program works, but also can't script it?
Yeesh. The picture in readme is one running a fake program I was using for testing. If you'll notice, none of the options particularly make sense -- heck, the output of the program (shown toward the bottom of the readme) is "printing message at: {hash}" If you take another look at the readme, you'll see that it supports `choice` style params. Which reads in the options available and presents them to the user via a dr…
That's why I thought it was wrapping a real Linux command line program. ;)
If you're wrapping a CLI, there's not much more you can do than take all the CLI options and shove them into a 1990's style window peppered with options. But it's not helping anything - anyone who knows what the options are and do, and who is not put-off by heaps of options, is likely fine with the CLI version. Anyone who is offput by heaps of options isn't going to want to face them in CLI or GUI versions.
And anyone who doesn't like facing them, but who can deal with it, will wrap the CLI in a shell script that specifies the options they use most often and hides the rest.
The whole thing is missing how and why CLI and GUI programs are different. Chrome isn't a wrapper for WGET, Finder and Explorer are not wrappers for ls/mv/cd, and PhotoShop is not a wrapper screen full of toggle and dropdown options around ImageMagick.
> Turn (almost) any command line program into a full GUI application with one line and lose the ability to pipe, check exit status, run from cron, run through ssh or a different machine, call from other scripts... The last couple of months as I know about more and more the command line, and can configure my shell and tools the way I like, I feel I'm more productive with the terminal than any other GUI application.
It's not meant to be a replacement for CLI. I can imagine lots of use cases, even for me. Example: I used something to bulk convert images (resize, crop, convert from one format to another). I used it maybe three times in my life, every single time I had to read the manual. If there was a simple GUI, I'd save time. My main project is a mobile app that has a bunch of calculators dedicated to specific tasks. Some of th…
I'm surprised you have settled on using a thing you dislike which doesn't work for you, when there are likely dozens or hundreds of wrappers, GUIs, APIs, programs and apps for image bulk editing to choose from.
Similar workflow for Macs: http://www.sveinbjorn.org/platypus + http://mstratman.github.io/cocoadialog/ or http://www.bluem.net/en/mac/pashua/
I had also written something similar 5 years ago when I had jumped from heavy GUI usage to Linux for some linux commands, byusing their man pages, semi-automatically. Interesting enough, now I value the reverse more and I would love to see the Yeeog. Yeoog; Turn GUI programs into command-line