<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title><![CDATA[Give Autoglade GUIs to favorite command line tools]]></title>
    <link>http://brainstorm.ubuntu.com/item/6461/</link>
    <description><![CDATA[We all know that Ubuntu and Linux need to let in more people. Personally I think that a way to achieve this is to provide more graphical user interfaces to users that opted to stay away from the command line.<br />After all, a great percentage of Windows users have never touched the command line, and although we may think that the command line is much powerful, respecting their freedom to choose let's build the windows to let them in.<br /><br />Traditional methods impose a high entry barrier for GUI programming. Information is not always easy to find, documentation is scarce and sometimes beginners don't know where to start.<br /><br />Autoglade, in combination with other powerful tools such as Glade interface designer and Nautilus actions provide a simple way to give a lot of command line applications a graphical face, with no or basic programming only.<br /><br />There are other tools that help a lot in providing this bridge between this two separate worlds. Circumscribing our case to the GNOME desktop one of this tools is Nautilus Actions. It provides the way to call a specified action from the nautilus file manager. Those actions can be simply programmed as scripts in the scripting language of your choice, mainly in bash for simplicity and availability.<br /><br />But sometimes these scripts need a graphical interface and you don't want to write a full fledged application to achieve these elementary tasks. Here is where the tool we are introducing today comes into scene.<br /><br />Autoglade will help as to provide these graphical interfaces to our scripts with no programming at all needed in the simplest and medium complexity tasks and with a much reduced programming needs in complex tasks.<br /><br />Autoglade: http://autoglade.sf.net<br />Tutorial: http://autoglade.wiki.sourceforge.net/autoglade+tutorial+-+first+steps<br />
<br />


<b>[15 votes] Solution #1: Auto-generated solution of idea #6461</b>
<br />

<br />
<br />



<b>[2 votes] Solution #2: bash gui </b>
<br />

<br />
<br />



]]></description>

    <language>en-us</language>
    <pubDate>Sat, 05 Apr 2008 19:49:23 +0000</pubDate>
    <lastBuildDate>Sat, 08 Aug 2009 16:09:54 +0000</lastBuildDate>
    <generator>QAPoll module</generator>
    <guid isPermaLink="true">http://brainstorm.ubuntu.com/idea/6461/</guid>
        <item>
  <title>Comment from vexorian</title>
  <description><![CDATA[You'll be surprised but this will not help at all to keep people away from the command line.<br /><br />Surprisingly, the user does not really need to use the command line in Ubuntu, but a lot of people will tell him terminal commands instead of the GUI way when helping them. You can try making 3 more alternatives for each command but that's what's going on right now. I think they do it instinctively since regardless of the unfriendly stigma people put in the terminal, it is just easier to tell a user to type something than to try to tell him how to use a GUI.<br /><br />So, we keep seeing "sudo apt-get install packagename" in forums and tutorials instead of "Go to synaptic and install packagename"...]]></description>
  <pubDate>Sat, 05 Apr 2008 21:03:18 +0000</pubDate>
</item>
        <item>
  <title>Comment from KIAaze</title>
  <description><![CDATA[Yes, that's probably true (I know I would give CLI instructions), but it still looks like a good RAD tool to create GUIs.<br /><br />It may be out of place here, but thanks for the tip. I'll try it out if I have some time.<br />]]></description>
  <pubDate>Tue, 08 Jul 2008 11:52:05 +0000</pubDate>
</item>
        <item>
  <title>Comment from lavinog</title>
  <description><![CDATA[The tutorial link is broken]]></description>
  <pubDate>Sat, 08 Aug 2009 16:09:54 +0000</pubDate>
</item>
      </channel>
</rss>
