<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:iweb="http://www.apple.com/iweb" version="2.0">
  <channel>
    <title>LYPANOV.NET</title>
    <link>http://www.lypanov.net/Web/Blog/Blog.html</link>
    <description>Friends</description>
    <generator>iWeb 2.0.2</generator>
    <image>
      <url>http://www.lypanov.net/Web/Blog/Blog_files/Photo%205.jpg</url>
      <title>LYPANOV.NET</title>
      <link>http://www.lypanov.net/Web/Blog/Blog.html</link>
    </image>
    <item>
      <title>iChatTodoScheduler</title>
      <link>http://www.lypanov.net/Web/Blog/Entries/2008/2/25_iChatTodoScheduler.html</link>
      <guid isPermaLink="false">0f66a830-4d70-4704-acc2-935e8a788e43</guid>
      <pubDate>Mon, 25 Feb 2008 07:32:57 +0100</pubDate>
      <description>There is one use case which Mail.app 3 and the various other applications I’m using to sort out my To Do lists simply does not provide for yet - recurring To Dos. For a short time I made use of  &lt;a href=&quot;http://sciral.com/consistency/&quot;&gt;Sciral Consistency&lt;/a&gt; unfortunately while it’s a great application, I feel quite bad for spending quite that much on something that I’ve already put a fair amount of time into in the past (see my post &lt;a href=&quot;Entries/2006/10/1_Planning_recurring_To_Dos_via_iCal_itself_.html&quot;&gt;Planning recurring To Do's via iCal itself&lt;/a&gt;).&lt;br/&gt;&lt;br/&gt;So at the weekend I decided to bring back my old AppleScript, sort out the few issues that remained, and re-release it. After around an hour of attempting to get date creation working with AppleScript (yes, really, an hour, to make a date...) I decided to give it another try in another language I enjoy using - Ruby. Two hours of using &lt;a href=&quot;http://www.apple.com/applescript/features/scriptingbridge.html&quot;&gt;ScriptingBridge&lt;/a&gt; passed and I was still unable to make a To Do list item. Almost ready to give up I took a look at the new &lt;a href=&quot;http://developer.apple.com/leopard/overview/calendarstore.html&quot;&gt;CalendarStore&lt;/a&gt; framework in Leopard, and figured I might as well give Objective C 2.0 and XCode 3 a shot as I’d never before tried these latest incarnations.&lt;br/&gt;&lt;br/&gt;An hour later and the application was complete... using CalendarStore all of the manual handling of recurrence disappears and is replaced with a trivial query for todays events. Creating To Do items is well documented, so that was also trivial to get working.&lt;br/&gt;&lt;br/&gt;The project source can be found via my &lt;a href=&quot;http://github.com/&quot;&gt;github&lt;/a&gt; project here: &lt;a href=&quot;http://github.com/zinf/icaltodoscheduler/tree/master&quot;&gt;http://github.com/zinf/icaltodoscheduler/tree/master&lt;/a&gt;.&lt;br/&gt;&lt;br/&gt;UPDATE - I’ve uploaded a zip of the application for anyone that doesn’t have git - &lt;a href=&quot;Entries/2008/2/25_iChatTodoScheduler_files/iCalTodoScheduler.zip&quot;&gt;iCalTodoScheduler.zip&lt;/a&gt;. Warranty-less and free to use. You’ll need a calender “@inbox” and a calendar “Shadow”. See my earlier post for a description of &lt;a href=&quot;Entries/2006/10/1_Planning_recurring_To_Dos_via_iCal_itself_.html&quot;&gt;creating the Shadow calendar&lt;/a&gt;.</description>
    </item>
    <item>
      <title>Vocabulary Widget recap</title>
      <link>http://www.lypanov.net/Web/Blog/Entries/2008/2/19_Vocabulary_Widget_recap.html</link>
      <guid isPermaLink="false">5b398f18-a00a-43f4-8415-2e694cb5bf4e</guid>
      <pubDate>Tue, 19 Feb 2008 22:11:13 +0100</pubDate>
      <description>Many months back I made some suggestive postings about my work on a Vocabulary Widget for OSX. In this last month thanks to some pushing from friends I’ve finally found the motivation to pick up development again.&lt;br/&gt;&lt;br/&gt;It’s a shame my graphics creation skills aren’t really all that great... Pixelmator is fun though in any case! Here’s a day old screenshot to give you a glimpse of the things to come:&lt;br/&gt;&lt;br/&gt;</description>
    </item>
    <item>
      <title>Firefox 3: selective anti-aliasing</title>
      <link>http://www.lypanov.net/Web/Blog/Entries/2008/2/17_Firefox_3%3A_selective_anti-aliasing.html</link>
      <guid isPermaLink="false">6252dba2-47ad-4d95-8898-fd80b88daee6</guid>
      <pubDate>Sun, 17 Feb 2008 16:54:18 +0100</pubDate>
      <description>The latest Firefox 3 builds are really impressive, much lower memory consumption, full page zoom including image resizings, tags in the bookmarks system, among many other changes that finally makes Firefox a nice alternative to Webkit/Safari. Alas... when used with my &lt;a href=&quot;Entries/2008/2/17_Greasekit_and_user_style-sheets.html&quot;&gt;GreaseMonkey  script to provide custom disable-able user stylesheets&lt;/a&gt; the font rendering looks just plain awful. Even 8pt fonts are rendered with anti-aliasing.&lt;br/&gt;&lt;br/&gt;I’ve just spent a few hours figuring out a bit of the Firefox code base, digging down into the new Cairo based rendering engine, and after figuring out finally that the current system uses a bizarre mix of ATSUI for layouting, and CoreGraphics for glyph rendering I finally put together a patch which I’ve uploaded to a related Mozilla bug report.&lt;br/&gt;&lt;br/&gt;So... people who care about having Firefox run well on the Mac. Please vote up:&lt;br/&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi%253Fid%253D389074&quot;&gt;Bug 389074 – Use Core Text instead of ATSUI to render text&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;And if you (like me) really love small fixed point fonts, my patch can be found here:&lt;br/&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/attachment.cgi%253Fid%253D303873&quot;&gt;firefox3-less-aa.patch&lt;/a&gt;</description>
    </item>
    <item>
      <title>Greasekit and user style-sheets</title>
      <link>http://www.lypanov.net/Web/Blog/Entries/2008/2/17_Greasekit_and_user_style-sheets.html</link>
      <guid isPermaLink="false">95e62ee4-825a-4ddb-9963-dd0a76907de5</guid>
      <pubDate>Sun, 17 Feb 2008 16:32:59 +0100</pubDate>
      <description>No doubt this is an extremely subjective thing... but I really much prefer having a small fixed point and set colors for text and its background when reading websites with large chunks of text.&lt;br/&gt;&lt;br/&gt;For a long time I’ve used Safari/Webkit’s built-in custom style-sheet support, however, I frequently need to temporarily remove my custom style-sheet. For the last months I’ve searched for a solution to this issue, eventually finding various Webkit plugins which allowed for site customisation, however, I just came across the &lt;a href=&quot;http://8-p.info/greasekit/&quot;&gt;GreaseKit&lt;/a&gt; project and used this to quickly rewrite the functionality I needed in JavaScript.&lt;br/&gt;&lt;br/&gt;My custom style-sheet results in pages looking something like:&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;And the &lt;a href=&quot;http://8-p.info/greasekit/&quot;&gt;GreaseKit&lt;/a&gt;/greasemonkey compatible script: &lt;a href=&quot;Entries/2008/2/17_Greasekit_and_user_style-sheets_files/custom-css.user.js&quot;&gt;custom-css.user.js&lt;/a&gt;</description>
    </item>
    <item>
      <title>Rubydium update #1</title>
      <link>http://www.lypanov.net/Web/Blog/Entries/2008/2/14_Rubydium_update_1.html</link>
      <guid isPermaLink="false">47a0863f-f348-4b0b-9945-7e93a16003dd</guid>
      <pubDate>Thu, 14 Feb 2008 22:44:42 +0100</pubDate>
      <description>This is the first in a series of postings on the latest developments and plans for Rubydium. Due to a lack of high level aims and goals I stopped development and moved away from the Ruby community for a long while many months ago.&lt;br/&gt;&lt;br/&gt;In the meantime I’ve explored Java, in particular Hibernate, Wicket, and Seam. From there I moved on to Scala, however... after several months away from anything other than professional development, I’ve once again returned to Ruby after an interesting chat with JRuby developer Charles Nutter.&lt;br/&gt;&lt;br/&gt;I’m soon to move from a Java J2EE development position to a Ruby development position, and as such, have decided to make public my continued work on the Rubydium project. Don’t expect too much however. In my mind the project has shifted from a major burden, something that must be perfect and ideal from time of conception until its first gasping breath, into a project which brings one word to my lips: fun.&lt;br/&gt;&lt;br/&gt;At the moment very little has changed since the last release, but I’ll try to summarize some of the bigger changes very quickly. I’ve moved from Ruth/Ripper to RubyParser (ParseTree). I’ve worked a bit on improving the time that the tests take to run, and have fixed a few tests that have been broken for quite a while already. The strange non deterministic behaviour that I’d for a long time attributed to my own NanoVM code has now disappeared which makes working on the code base much less fatiguing.&lt;br/&gt;&lt;br/&gt;Please don’t expect a Ruby interpreter that will ever be used for production, this is just an experiment. However, I hope all following the project will be excited by the developments I aim to make in the coming months.&lt;br/&gt;&lt;br/&gt;For the intrigued, I’ve pushed my work to a git repository: &lt;a href=&quot;http://repo.or.cz/w/rubydium.git&quot;&gt;http://repo.or.cz/w/rubydium.git&lt;/a&gt;</description>
    </item>
  </channel>
</rss>
