<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Development on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/development/</link>
    <description>Recent content in Development on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 23 Mar 2011 13:46:00 +0000</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Code reading and Bug fixing 101</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2011/code-reading-and-bug-fixing-101/</link>
      <pubDate>Wed, 23 Mar 2011 13:46:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2011/code-reading-and-bug-fixing-101/</guid>
      <description>Summer is here, and Google Summer of Code is on its way. The biggest hurdle new contributors often face (after compiling trunk ;)) is to get their head around the project they would like to work on, understanding how it works, where the parts fit in, and how to fix bugs or make improvements. Speaking from my experience, it took me the better part of a month to understand how KWin worked before I could actually hack on it for Season on KDE.</description>
    </item>
    <item>
      <title>Knocked out of Node Knockout</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/knocked-out-of-node-knockout/</link>
      <pubDate>Sun, 29 Aug 2010 18:46:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/knocked-out-of-node-knockout/</guid>
      <description>(This is one of those you-don&amp;rsquo;t-really-have-to-read-it kind of posts)&#xA;I was very excited about Node Knockout. I had a great idea for an IRC bouncer + websocket based client called Ircsome using node, qooxdoo and a couple of other things.&#xA;I knew that I would only get 24 hours since Sunday had higher priority events, but I believed I could get the basic app working in 24 hours. Until things went downhill from last week.</description>
    </item>
    <item>
      <title>KWin tiling is merged</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/kwin-tiling-is-merged/</link>
      <pubDate>Mon, 26 Apr 2010 11:26:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/kwin-tiling-is-merged/</guid>
      <description>I&#39;m glad to announce that yesterday the kwin-tiling branch was merged into kwin trunk by commit 1118677!. It will be available in KDE SC 4.5. Please keep in mind that it is an experimental feature with rough edges. Bug fixes are already on the way, but some things, like session saving and so on are absent. Please do add feature requests and bugs to the KDE bug tracker.&#xA;This screencast should show off a few things.</description>
    </item>
    <item>
      <title>Quick and dirty Instant Messaging with Redis</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/quick-and-dirty-instant-messaging-with/</link>
      <pubDate>Thu, 22 Apr 2010 11:52:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2010/quick-and-dirty-instant-messaging-with/</guid>
      <description>(Aside: Yes this is a post after a zillion years, but I have a few more lined up, and waiting for some important stuff in about a week)&#xA;Redis is a wicked cool NoSQL database, in that storing stuff is not the only thing that it does. Mathias Meyer already has a collection of Redis use cases, but this great idea is mine. Like all good ideas it emerged in the shower :) ( I was not aware of Pieter Noordhuis&#39; MUC when I did this, in either case mine deals with one-to-one IM )</description>
    </item>
    <item>
      <title>Automatic builds with some inotify magic</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2009/automatic-builds-with-some-inotify/</link>
      <pubDate>Thu, 26 Nov 2009 17:40:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2009/automatic-builds-with-some-inotify/</guid>
      <description>The inotify feature in the linux kernel allows you to receive events about changed files. Using pyinotify, here is a simple script to watch for changes to source code and run &#34;make&#34;. Everything is hard coded right now, and since I was using CMake with out-of-source builds, the directory structure is that way. It also uses the command line notify-send tool to display notifications. Perhaps some day I will make it configurable and more useful.</description>
    </item>
    <item>
      <title>KWin preliminary tiling</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2009/kwin-preliminary-tiling/</link>
      <pubDate>Fri, 05 Jun 2009 20:56:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2009/kwin-preliminary-tiling/</guid>
      <description>Yesterday I committed code which adds a semblance of tiling to kwin. Every time you launch a window, it will be maximized vertically, but each window shares the width of the screen equally. You can check out code from KDE svn. The location is /home/kde/branches/work/kwin-tiling/&#xA;You&#39;ll need to edit $KDEDIR/share/config/kwinrc and set Placement=Tiling.&#xA;Then you are ready to go.&#xA;Right now there are no configuration options, no key bindings, nothing!</description>
    </item>
    <item>
      <title>Reworked Graffiti&#39;s first render</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2008/reworked-graffitis-first-render/</link>
      <pubDate>Wed, 27 Aug 2008 20:47:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2008/reworked-graffitis-first-render/</guid>
      <description>After quite a few weeks of work, Graffiti has (again) reached the stage where it can render it&#39;s first words. It&#39;s now at 488 lines of code, of which the CSS related stuff itself comes in at 288 lines! There is no word wrapping yet, or any layout logic. I&#39;ve been busy fixing quite a few bugs in the CSS overlays and so on.&#xA;This is how you would use it.</description>
    </item>
    <item>
      <title>opensocial Last.fm recent tracks</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2008/opensocial-lastfm-recent-tracks/</link>
      <pubDate>Sun, 20 Apr 2008 13:39:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2008/opensocial-lastfm-recent-tracks/</guid>
      <description>After two days of OpenSocial hacking, here is my app, which fetches the users Recent tracks and displays it on the profile. Now since there is no way to directly fetch the last.fm username, I had to resort to asking the user. Also 1.0 although usable has a few errors which aren&#39;t handled smoothly. But they do not pose security risks. For now its in the sandbox, if you have access you can view it here Last.</description>
    </item>
    <item>
      <title>Stop coding already</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/stop-coding-already/</link>
      <pubDate>Mon, 31 Dec 2007 20:35:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/stop-coding-already/</guid>
      <description>I am sorry to say this to myself, and it is a sad way to end the year, but I&#39;ve to give up on decent projects for a few months. The next few months are &#39;while true: study&#39; months for 12th standard students, since the exams supposedly decide your life. Which means most of the time my mind is just looking forward to not thinking and unfortunately programming is thinking, even if it is fun.</description>
    </item>
    <item>
      <title>No, my code is not stagnating</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/no-my-code-is-not-stagnating/</link>
      <pubDate>Sat, 24 Nov 2007 21:42:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/no-my-code-is-not-stagnating/</guid>
      <description> Though it does seem like that, since I haven&#39;t posted about any development in weeks.&#xA;I&#39;ve been working on a game in C++/SDL and its taking some time since this is the first time I&#39;m building something with levels and passcodes and stuff. It&#39;s not going to be anything extraordinary, but it will take about 2 weeks more. </description>
    </item>
    <item>
      <title>Tetrablocks and Login Win32 versions</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/tetrablocks-and-login-win32-versions/</link>
      <pubDate>Fri, 31 Aug 2007 16:28:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/tetrablocks-and-login-win32-versions/</guid>
      <description> I forgot to post this but Windows executables of both Tetrablocks and Login have been uploaded to 22bits. Compiling them on Windows was a bit of a nightmare. Tetrablocks has got all of its text drawing code removed since I couldn&#39;t get SDL_ttf to link. So you won&#39;t see the score or the game over message when playing it on Windows. </description>
    </item>
    <item>
      <title>ColourCode: 1.0 Released</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-10-released/</link>
      <pubDate>Wed, 15 Aug 2007 19:57:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-10-released/</guid>
      <description> I&#39;m quite pleased to announce the release of version 1.0 of ColourCode. You can download and know more about it from the ColourCode homepage. Please leave your feedback and bugs in the comments </description>
    </item>
    <item>
      <title>ColourCode: Some thoughts about the future</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-some-thoughts-about-future/</link>
      <pubDate>Thu, 09 Aug 2007 20:29:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-some-thoughts-about-future/</guid>
      <description>Before I write about the possible future of ColourCode, let me get a few things out of the way. First today I fixed an extensionless file bug, and you can now force languages in ColourCode.&#xA;Now that thats out of the way, I was just thinking about how much interest I still have in ColourCode. I mean writing it was a lot of fun and gave me some new insights into design but I don&#39;t feel the same interest I had in parsing and analysing language files, that I had when I began ColourCode.</description>
    </item>
    <item>
      <title>ColourCode: 1.0 almost done</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-10-almost-done/</link>
      <pubDate>Tue, 07 Aug 2007 20:06:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-10-almost-done/</guid>
      <description>ColourCode is done. It now has support for PHP and HTML which it didn&#39;t have before. Perl support will probably get in before the stable release. This version has been bumped to 1.0. I think I&#39;ve made a really good project and that it deserves the 1.0 tag. PDF support will not enter the 1.0 release but is on track for 1.1.&#xA;All that is left now is testing some highly tweaked files.</description>
    </item>
    <item>
      <title>ColourCode:Updates</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcodeupdates/</link>
      <pubDate>Mon, 30 Jul 2007 17:10:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcodeupdates/</guid>
      <description>Language support&#xA;ColourCode now has support for C# and Javascript, completing support for the original language set. I&#39;l be adding Perl and HTML soon enough.&#xA;Bugs&#xA;On the C based languages front there is a small logic error in the multiline comment system. I am currently trying to iron it out.&#xA;Snippet feature dropped&#xA;I&#39;ve decided to drop the snippet feature since its not universal (doesn&#39;t make sense in PDF) and since CSS is now dynamically generated, giving the CSS data to the user and having him embed it will be quite annoying.</description>
    </item>
    <item>
      <title>ColourCode: Almost done</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-almost-done/</link>
      <pubDate>Thu, 26 Jul 2007 20:29:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-almost-done/</guid>
      <description> In the last two days ColourCode has reached a stage where I can say that it is finally ready for release. Everything apart from implementing language handlers is done. PDF support might not be added. It all depends on how patient I am in releasing it. Meanwhile you can download a nightly build and view demos for Ruby and Python from the link above. </description>
    </item>
    <item>
      <title>ColourCode: Making progress</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-making-progress/</link>
      <pubDate>Fri, 20 Jul 2007 19:07:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-making-progress/</guid>
      <description>ColourCode has been getting along quite well for the last week. I now firmly have the basic design for my plans in working code. The language parser and handlers are coordinating well and this might just be one of the best designs I&#39;ve ever envisioned.&#xA;Once the main program is in place writing language handlers and formatters for ColourCode will be really easy.&#xA;At this stage only the Ruby language handler is complete, and until I can make it work perfectly for a large amount of code, no other handlers are expected.</description>
    </item>
    <item>
      <title>ColourCode: New ideas and old improvements</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-new-ideas-and-old/</link>
      <pubDate>Fri, 06 Jul 2007 23:29:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/colourcode-new-ideas-and-old/</guid>
      <description>Now that TetraBlocks is done, its time to start working on the latest and greatest ColourCode release ever. Though the next version should be called 0.3, I might bump it up a few notches if everything works out as planned.&#xA;One of the major things I&#39;ve been planning is to implement the Language Descriptors in Ruby itself rather than text files or XML. This would allow them to be more context sensitive and basically do more stuff to improve highlighting.</description>
    </item>
    <item>
      <title>TetraBlocks: It is done</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/tetrablocks-it-is-done/</link>
      <pubDate>Tue, 26 Jun 2007 19:33:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/tetrablocks-it-is-done/</guid>
      <description> To much applause and enthusiasm (atleast by one guy) TetraBlocks is released to the world. Probably the millionth clone of Tetris, you can proudly claim your own version at the Tetrablocks page. Only available as a source archive for now, a windows executable is in the works </description>
    </item>
    <item>
      <title>TetraBlocks:The finishing run</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/tetrablocksthe-finishing-run/</link>
      <pubDate>Wed, 20 Jun 2007 17:04:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/tetrablocksthe-finishing-run/</guid>
      <description>After having dumped the initial TetraBlocks code, the new version is coming along quite well and has proceeded especially well for the last few days. The few things left involve the deletion of lines and score keeping and putting a cap on the height. I&#39;ve decided to do away with the menu and highscores system since it added for excess complexity.&#xA;Here is a screenshot of the latest developments.</description>
    </item>
  </channel>
</rss>
