<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Michele Campeotto: Tag gnome</title>
    <link>http://blog.micampe.it/articles/tag/gnome?tag=gnome</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>I'm not Winston Wolfe.</description>
    <item>
      <title>gedit Markdown preview plugin</title>
      <description>&lt;p&gt;This weekend I have installed &lt;a href="http://www.ubuntu.com/testing/flight6"&gt;Ubuntu Dapper Flight 6&lt;/a&gt; on my laptop and found it worked pretty well. Among the nice things, suspend/hibernate/resume work fine and are much faster than on Breezy (apart from a &lt;a href="https://launchpad.net/distros/ubuntu/+source/acpi-support/+bug/35154"&gt;little glitch&lt;/a&gt; on resume when connected to AC).&lt;/p&gt;

&lt;p&gt;Another nice Dapper thing, coming from the included GNOME 2.14, is the new Text Editor, which now has the enhanced capability to add plugins to the application, and you can write plugins in Python.&lt;/p&gt;

&lt;p&gt;As I prefer &amp;#8211; for various reasons &amp;#8211; plain text over using the big word processors, I have written a simple plugin to help writing &lt;a href="http://en.wikipedia.org/wiki/Markdown"&gt;Markdown&lt;/a&gt; formatted text. The &lt;a href="http://live.gnome.org/Gedit/MarkdownSupport"&gt;plugin&lt;/a&gt; will add an HTML preview in gedit&amp;#8217;s bottom panel, allowing you to see how your document will look when rendered. For more info and downloads, refer to the &lt;a href="http://live.gnome.org/Gedit/MarkdownSupport"&gt;wiki page&lt;/a&gt; I created.&lt;/p&gt;

&lt;p&gt;Everybody knows that ease of extension is a key to success, so I really hope people start to &lt;a href="http://live.gnome.org/Gedit"&gt;write cool plugins&lt;/a&gt; (the &lt;a href="http://live.gnome.org/Gedit/SnippetPlugin"&gt;snippets&lt;/a&gt; one is great for example) and extend gedit to become more and more powerful. I don&amp;#8217;t see it replacing &lt;a href="http://www.eclipse.org"&gt;my primary development environment&lt;/a&gt; anytime soon, but I was already using it for more document-oriented editing tasks, and it&amp;#8217;s great to see it becoming better at every iteration.&lt;/p&gt;</description>
      <pubDate>Sun, 09 Apr 2006 14:12:00 -0700</pubDate>
      <guid isPermaLink="false">urn:uuid:271eb893-090c-4655-8638-a93ef0567487</guid>
      <author>micampe</author>
      <link>http://blog.micampe.it/articles/2006/04/09/gedit-markdown-preview-plugin</link>
      <category>English</category>
      <category>gnome</category>
      <category>markdown</category>
      <category>plugin</category>
      <trackback:ping>http://blog.micampe.it/articles/trackback/205</trackback:ping>
    </item>
    <item>
      <title>Sensor applet on a ThinkPad</title>
      <description>&lt;p&gt;It was a boring sunday morning, and &lt;a href="http://monja.it"&gt;friends&lt;/a&gt; kept telling me I should write something in here, so I looked for something to do that I could then post here.&lt;/p&gt;

&lt;p&gt;Here we are. I recently installed a &lt;a href="http://thinkwiki.org/wiki/ACPI_fan_control_script#bash_script_with_fine_control_over_fan_speed"&gt;script&lt;/a&gt; to control the fan of my ThinkPad and I used &lt;a href="http://www.muhri.net/gkrellm/"&gt;gkrellm&lt;/a&gt; to keep an eye on the system&amp;#8217;s temperature to check the laptop wasn&amp;#8217;t melting.&lt;/p&gt;

&lt;p&gt;I didn&amp;#8217;t particularly like having gkrellm&amp;#8217;s window around, so I looked on &lt;a href="http://www.gnomefiles.org/"&gt;Gnome files&lt;/a&gt; for an applet that could do the same. I found &lt;a href="http://sensors-applet.sourceforge.net/"&gt;Sensors Applet&lt;/a&gt;, but it only displayed the value reported by the standard ACPI driver, wich is just the CPU temperature. The ibm_acpi driver reports more values in a different file, so I went and added a ThinkPad module to Sensors Applet.&lt;/p&gt;

&lt;p&gt;If you want to install the patched version, download Sensors Applet &lt;a href="http://sensors-applet.sourceforge.net/index.php?download=sensors-applet-1.5.2.tar.gz&amp;amp;location=sf.net&amp;amp;link_source=external"&gt;1.5.2&lt;/a&gt; and my &lt;a href="http://micampe.it/files/sensors-applet-thinkpad.diff"&gt;patch&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Uncompress the source and apply the patch:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;$ tar xzf sensors-applet-1.5.2.tar.gz
$ cd sensors-applet-1.5.2
$ patch -p1 &amp;lt; sensors-applet-thinkpad.diff
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Build and compile as usual (you need to install the applet in the same prefix as the Gnome Panel, unless you know what you are doing):&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;$ ./configure --prefix=/usr/
$ make
$ sudo make install
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Add the applet to the panel and activate the sensors as you can see here:&lt;/p&gt;

&lt;div style="text-align: center; padding-top: 10px; padding-bottom: 10px;"&gt;&lt;img src="http://micampe.it/screenshots/sensors-applet-thinkpad.png"&gt;&lt;/div&gt;

&lt;p&gt;I sent the patch to Alex, I hope he likes it and commits it to the official sources.&lt;/p&gt;</description>
      <pubDate>Sun, 04 Dec 2005 12:12:00 -0800</pubDate>
      <guid isPermaLink="false">urn:uuid:6e36edca-4791-4a55-96dc-96ad40dfb1c0</guid>
      <author>micampe</author>
      <link>http://blog.micampe.it/articles/2005/12/04/sensor-applet-on-a-thinkpad</link>
      <category>English</category>
      <category>thinkpad</category>
      <category>linux</category>
      <category>sensors</category>
      <category>gnome</category>
      <category>patch</category>
      <trackback:ping>http://blog.micampe.it/articles/trackback/197</trackback:ping>
    </item>
    <item>
      <title>Nautilus Quick Burner</title>
      <description>&lt;p&gt;This script comes from an &lt;a href="http://mail.gnome.org/archives/nautilus-list/2002-March/msg00553.html"&gt;idea&lt;/a&gt; launched on the Nautilus mailing list by Tuomas Kuosmanen, who wished a workaround while waiting for somebody to implement drag and drop CD-RW burning in Nautilus.&lt;/p&gt;

&lt;blockquote&gt;
    &lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; That idea is now implemented and included in the official Nautilus release.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I don&amp;#8217;t think I can implement his whole idea, but I can quickly hack a simple Python/GTK+ script that does part of the job.&lt;/p&gt;

&lt;p&gt;The script is meant to be used as a Nautilus script, but it doesn&amp;#8217;t contain anything Nautilus related, so you can use it from the CLI too: just specify as command line arguments the files/directories you want to burn. You can also launch it as a standalone program and drop the files in the main window.&lt;/p&gt;

&lt;p&gt;The script is &lt;em&gt;simple and dirty&lt;/em&gt;, &lt;strong&gt;almost no error checking&lt;/strong&gt; is performed, and to configure it you must edit the source file.&lt;/p&gt;

&lt;p&gt;By default it will not burn anything, it will just create an &lt;code&gt;image.img&lt;/code&gt; file in the directory where you run it. If you want the script to actually burn your CDs, you should edit the file, change the command line (a commented out example is provided) and remove the &lt;code&gt;-dummy&lt;/code&gt; option (yeah, I know this sucks, but I don&amp;#8217;t want to burn your CD writer with some wrong option).&lt;/p&gt;

&lt;p&gt;Clicking the &lt;code&gt;Cancel&lt;/code&gt; button or closing the burning window will immediately stop the execution. You&amp;#8217;ll not be asked for confirmation, but you&amp;#8217;ve been warned now! ;o)&lt;/p&gt;

&lt;p&gt;You can see the results of the script by loopback-mounting the generated &lt;code&gt;image.img&lt;/code&gt; file:&lt;/p&gt;

&lt;pre&gt;
# mount -t iso9660 -o loop image.img /mnt/cdrom
&lt;/pre&gt;

&lt;h3&gt;Screenshots&lt;/h3&gt;

&lt;div align="center"&gt;
  &lt;img src="http://micampe.it/screens/quickburn-1-shadow.png" alt="Screenshot 1" /&gt;
  &lt;img src="http://micampe.it/screens/quickburn-2-shadow.png" alt="Screenshot 2" /&gt;
&lt;/div&gt;

&lt;h3&gt;Requirements&lt;/h3&gt;

&lt;p&gt;To run the Nautilus Quick Burner you&amp;#8217;ll need GTK+ 2.x (1.3.x may work, too), the latest version of PyGTK (anything over 1.99.7 should work) and a recent version mkisofs and cdrecord (tested with 1.10).&lt;/p&gt;

&lt;p&gt;Also note that the user running the script needs to have execution
permissions on mkisofs and cdrecord (this isn&amp;#8217;t true by default on Red Hat systems).&lt;/p&gt;

&lt;h3&gt;Download &amp;amp; install&lt;/h3&gt;

&lt;p&gt;Download &lt;a href="http://micampe.it/files/quickburn"&gt;quickburn&lt;/a&gt;, copy it in your Nautilus scripts directory and make sure it has execution permissions. Then select some files and folders, right click and select &lt;code&gt;Scripts -&amp;gt; QuickBurn&lt;/code&gt;.&lt;/p&gt;</description>
      <pubDate>Thu, 17 Mar 2005 06:42:00 -0800</pubDate>
      <guid isPermaLink="false">urn:uuid:ac2bd1ce-9ebd-4270-b875-f7f6afcb805c</guid>
      <author>micampe</author>
      <link>http://blog.micampe.it/articles/2005/03/17/nautilus-quick-burner</link>
      <category>English</category>
      <category>nautilus</category>
      <category>gnome</category>
      <category>script</category>
      <category>cdrom</category>
      <category>burning</category>
      <trackback:ping>http://blog.micampe.it/articles/trackback/159</trackback:ping>
    </item>
  </channel>
</rss>
