<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
    <channel>
      <title>Jezra.net Rambling and Rolling</title>
      <link>http://www.jezra.net</link>
      <description>One persons journey into code,rambling, and rolling</description>
      <pubDate>Sun, 25 Jul 2010 00:00:00 -0400</pubDate>
      <copyright>copyright 2009 Jezra Lickter</copyright>
      <item>
        <title>
        <![CDATA[
            seriously, that thing is garbage
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/seriously_that_thing_is_garbage</link>
        <description>
        <![CDATA[
            ###A bit of Computer Repair<br />
<br />
 My good buddy [Constance](http://atrainwreckwithwords.wordpress.com) has a rather old computer. Actually, it is an original [ibook](http://en.wikipedia.org/wiki/IBook) with a *speedy* 300Mhz processor and a whopping 192M of RAM. <br />
<br />
OK, the RAM has obviously been updated, but other than that, the computer is still original.<br />
<br />
One day, Constance told me a tale of tripping over her computer cord and then the adapter started sparking. Crap! The machine may be crap, but it is all she has and it has **all** of her writings on it.<br />
<br />
 Ah, the slow as dirt machine. See that "yo-yo" power adapter? Aside from always burning out, those things are $80 from Apple. I'll be damned if I let Apple get any of my poor writer friend's money. Let's fix that shit!<br />
<br />
<br />
 First thing first: find out where the cord is fried. Well, I'll be damned, it just happens to be fried where every other "yo-yo" adapter gets... <br><br>Read the full post at <a href='http://www.jezra.net/blog/seriously_that_thing_is_garbage'>http://www.jezra.net/blog/seriously_that_thing_is_garbage</a>
        ]]>    
        </description>
        <pubDate>Sun, 25 Jul 2010 00:00:00 -0400</pubDate>
      </item><item>
        <title>
        <![CDATA[
            keeping a GTK TextView cursor in view
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/keeping_a_GTK_TextView_cursor_in_view</link>
        <description>
        <![CDATA[
            Quite a few of my coding projects have a large text field where the user is expected to do a lot of typing. Actually, it would appear that **none** of my [projects](http://www.jezra.net/projects) have a large text field. I suppose I should make [markdowner](http://www.jezra.net/blog/A_markdown_editorviewer_in_Python) and [scripsi](http://www.launchpad.net/scripsi) *official* jezra.net projects. Anyway, both of the *previously* mentioned apps have a large text field where the user types and types and types( hey, they are text editing programs ).<br />
<br />
* scripsi is a special purpose dual paned text editor written in [Vala](http://live.gnome.org/Vala) <br />
* markdowner is a special purpose text editor written in [Python](http://www.python.org) <br />
<br />
Both applications use the [GTK+](http://www.gtk.org/) toolkit to create the user interface.<br />
<br />
###The Problem<br />
***<br />
<br />
When a GTK TextView widget is used to create a large text input area, if ... <br><br>Read the full post at <a href='http://www.jezra.net/blog/keeping_a_GTK_TextView_cursor_in_view'>http://www.jezra.net/blog/keeping_a_GTK_TextView_cursor_in_view</a>
        ]]>    
        </description>
        <pubDate>Fri, 16 Jul 2010 00:00:00 -0400</pubDate>
      </item><item>
        <title>
        <![CDATA[
            A tale of three sticker
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/A_tale_of_three_sticker</link>
        <description>
        <![CDATA[
            ###The Warm Up<br />
Not very long ago, I made [three stickers](http://www.jezra.net/blog/photograph_sticker) from a photograph of yours truly. Because the original intent of making the stickers was never met, I decided to give away the stickers with a simple contest.<br />
<br />
Sticker #1 has gone across the Atlantic Ocean an now resides in Germany.<br />
<br />
Sticker #2 has traveled across the United States and now resides in Upstate New York.<br />
<br />
Sticker #3: well this sticker is probably going to travel more than #1 and #2 combined (and then possibly doubled).<br />
<br />
Wait, didn't the third postcard come from Switzerland? How can the sticker have such an unknown travel distance? I'm glad you asked.<br />
<br />
###allow me to spin a yarn....<br />
A few weeks after sticker #2 was shipped off, I received a message from my buddy asking if I could *fix* his computer. I heartily agreed and five days later I was picking up the computer at the post office. Ye... <br><br>Read the full post at <a href='http://www.jezra.net/blog/A_tale_of_three_sticker'>http://www.jezra.net/blog/A_tale_of_three_sticker</a>
        ]]>    
        </description>
        <pubDate>Sun, 11 Jul 2010 00:00:00 -0400</pubDate>
      </item><item>
        <title>
        <![CDATA[
            minimize/close to system tray in Python GTK
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/minimizeclose_to_system_tray_in_Python_GTK</link>
        <description>
        <![CDATA[
            Recently, while writing code for [heybuddy](http://www.jezra.net/projects/heybuddy), I needed to:<br />
<br />
* display a tray icon<br />
* *hide* the window when "close window" is selected<br />
* show the window when the tray icon is clicked<br />
<br />
Although getting this done was easy enough to do, finding out *how* to do it was a bit of a pain, so I thought it would be best if I shared my Python/GTK test code and save future developers from some pain.<br />
<br />
**Enter the Python**<br />
#!/usr/bin/env&nbsp;python<br />
import&nbsp;gtk<br />
class&nbsp;Win&nbsp;(gtk.Window):<br />
&nbsp;&nbsp;&nbsp;&nbsp;def&nbsp;__init__(self):<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;gtk.Window.__init__(self)<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;self.set_title("Close&nbsp;to&nbsp;tray")<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;self.connect("delete-event",&nbsp;self.delete_event)<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs... <br><br>Read the full post at <a href='http://www.jezra.net/blog/minimizeclose_to_system_tray_in_Python_GTK'>http://www.jezra.net/blog/minimizeclose_to_system_tray_in_Python_GTK</a>
        ]]>    
        </description>
        <pubDate>Wed, 30 Jun 2010 00:00:00 -0400</pubDate>
      </item><item>
        <title>
        <![CDATA[
            A markdown editor/viewer in Python
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/A_markdown_editorviewer_in_Python</link>
        <description>
        <![CDATA[
            ###The Need<br />
***<br />
Having recently implemented parsing of [Markdown](http://daringfireball.net/projects/markdown/) code in my blog, and deciding to write most, if not all, of my future documentation in Markdown, what I really needed, was a way to do the following:<br />
<br />
1.  write markdown code in a *spellchecking* text editor<br />
2. convert the markdown code to HTML<br />
3. preview the HTML as it would appear in a browser<br />
<br />
Simple enough, but unfortunately, all of the solutions that I found were online forms. *I* wanted something that I could run on my own machine.<br />
<br />
###The Solution<br />
***<br />
As is often the case, the solution was to write a quick little application. For this application, I chose  to use [Python](http://www.python.org) due to the readily available [Python Markdown module](http://www.freewisdom.org/projects/python-markdown/) as well as my "quick/dirty" need and recent Python usage on various projects. <br />
<b... <br><br>Read the full post at <a href='http://www.jezra.net/blog/A_markdown_editorviewer_in_Python'>http://www.jezra.net/blog/A_markdown_editorviewer_in_Python</a>
        ]]>    
        </description>
        <pubDate>Thu, 24 Jun 2010 00:00:00 -0400</pubDate>
      </item><item>
        <title>
        <![CDATA[
            Red Phone Mumble Test
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/Red_Phone_Mumble_Test</link>
        <description>
        <![CDATA[
            The wires in some telephones is extremely thin and it is nearly impossible for me to get a decent *long lasting* connection. Case in point, the [Red Phone](http://www.jezra.net/blog/Im_calling_you). After a brief conversation over Skype with a fellow hacker and [Linux Outlaw](http://www.linuxoutlaws.com/forums), the connections on the phone started falling apart. Bummer: I  was researching non-proprietary forms of VOIP communication and I really needed a microphone and speaker.<br />
<br />
To the hardware store for supplies!<br />
<br />
After purchasing a phone plug crimping tool, some phone plugs, and a modular jack. It was time to get cracking. The wires were stripped and phone plug was crimped on.<br />
<br />
<br />
<br />
Woops! I should have paid attention to which wires connected to what. Oh well; a few seconds of testing later, I was wiring the speaker and microphone jacks to modular phone jack. <br />
<br />
<br />
<br />
Hiyah! It's all put together and ready fo... <br><br>Read the full post at <a href='http://www.jezra.net/blog/Red_Phone_Mumble_Test'>http://www.jezra.net/blog/Red_Phone_Mumble_Test</a>
        ]]>    
        </description>
        <pubDate>Mon, 21 Jun 2010 00:00:00 -0400</pubDate>
      </item><item>
        <title>
        <![CDATA[
            Saturday Sassafrass
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/Saturday_Sassafrass</link>
        <description>
        <![CDATA[
            During the week, there were a few things that I took pictures of in the hopes of documenting on the web. Unfortunately, they were not quite significant enough for a blog posting. As Friday rolled around I had big dreams of another [Friday Frolic](http://www.jezra.net/blog/friday_frolic), but alas, it was not to be. (Actually some of this is a few weeks old, but I didn't want to *not* post about it)<br />
<br />
Welcome to the Saturday Sassafras! ( Sorry, I couldn't come up with a better name )<br />
<br />
###Jezra.net<br />
***<br />
Damn those spammers!  On Friday morning, I started to receive quite a bit of email spam, in [BBCode](http://en.wikipedia.org/wiki/BBCode) format, from my [contact](http://www.jezra.net/contact) form. With a bit of the old "copy and paste" I shortly implemented the jezra.net blog captcha for the contact form and **booyah!**, no more spam.<br />
<br />
However, keeping the bots from spamming me is one thing, what I would really like to do is just se... <br><br>Read the full post at <a href='http://www.jezra.net/blog/Saturday_Sassafrass'>http://www.jezra.net/blog/Saturday_Sassafrass</a>
        ]]>    
        </description>
        <pubDate>Sat, 19 Jun 2010 00:00:00 -0400</pubDate>
      </item><item>
        <title>
        <![CDATA[
            A Friday Frolic
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/A_Friday_Frolic</link>
        <description>
        <![CDATA[
            Plenty of things happen that are *almost* blog worthy but just don't have the substance for a full post. For the most part, this is what microblogging is for. However, there are somethings that are too big for a posting on identi.ca. So what is a Jez to do?   <br />
Why, have a fun filled frolicking Friday feature fest, of course. The idea is simple: aggregate the little things into one post. Booyah!<br />
<br />
###Jezra.net<br />
*************<br />
Recently, I've make two changes to my blog, only one of which you the viewer will actually experience. <br />
<br />
1. the blog code has been updated to allow me to write using the [Markdown](http://daringfireball.net/projects/markdown/) format. I'm actually using [PHP Markdown](http://michelf.com/projects/php-markdown/) written by Michel Fortin. From a visitor's standpoint, this doesn't really do much, but it certainly makes it easier for me to compose a new posting. <br />
<br />
2. images in blog postings will now be utilizin... <br><br>Read the full post at <a href='http://www.jezra.net/blog/A_Friday_Frolic'>http://www.jezra.net/blog/A_Friday_Frolic</a>
        ]]>    
        </description>
        <pubDate>Fri, 11 Jun 2010 00:00:00 -0400</pubDate>
      </item><item>
        <title>
        <![CDATA[
            Toshiba laptop review
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/Toshiba_laptop_review</link>
        <description>
        <![CDATA[
            For some reason, my porch, as of late, has been bereft of [packages containing products](http://www.jezra.net/blog/The_Mullet_Adventure) so epic that they *require* a review. Although reviewed, the [Ed Hardy beer](http://www.jezra.net/blog/A_surprise_beer_review) was anything but epic, but that is beyond the point. Anyway, since no one is sending me crap to review, I thought I would take this time to spin a yarn about a semi-recent purchase of mine.....<br />
<br />
Earlier this year, I was in need of a new computer for work. Since I would be using the computer both in the office and at home, I decided to get a laptop. All I needed was something with a decent processor, a bunch of RAM, cheap, and was Linux friendly.  Well, three out of four isn't that bad.<br />
<br />
Unfortunately, I missed the one day of the week that the local computer recycler was open so I had to buy a new machine. After driving far too many miles to a home electronics store, I purchased a [Toshiba Satellite ... <br><br>Read the full post at <a href='http://www.jezra.net/blog/Toshiba_laptop_review'>http://www.jezra.net/blog/Toshiba_laptop_review</a>
        ]]>    
        </description>
        <pubDate>Sat, 05 Jun 2010 00:00:00 -0400</pubDate>
      </item><item>
        <title>
        <![CDATA[
            Google no longer uses Microsoft
        ]]> 
        </title>
        <link>http://www.jezra.net/blog/Google_no_longer_uses_Microsoft</link>
        <description>
        <![CDATA[
            Apparently, [Google is not going to use Microsoft Windows](http://www.ft.com/cms/s/2/d2f3f04e-6ccf-11df-91c8-00144feab49a.html) anymore, unless it is really really really necessary. Seriously, if someone at Google needs to run Windows, they are going to need the permission of the CIO.  Wow! From now on Google will be a Linux and Apple shop. (hopefully there will be a few BSD users in there as well)<br />
<br />
But aside from the security aspect, what does this *really* mean?  <br />
(go read the article if you want to know about the decision, I have different concerns and don't feel like paraphrasing in the hopes of creating my own *unique* content)<br />
<br />
There surely are plenty of times that city governments, school districts, and probably small countries have moved away from Microsoft products, but to me, this is a bit different. As ephemeral as Google may be by having mostly digital products, I find Google to be a very tangible company with products I use on a daily bas... <br><br>Read the full post at <a href='http://www.jezra.net/blog/Google_no_longer_uses_Microsoft'>http://www.jezra.net/blog/Google_no_longer_uses_Microsoft</a>
        ]]>    
        </description>
        <pubDate>Mon, 31 May 2010 00:00:00 -0400</pubDate>
      </item>
    </channel>

</rss>
