goodbye Frame parser
goodbye Frame parser
|Deletions are marked like this.||Additions are marked like this.|
|Line 4:||Line 4:|
|<div style="float: right;">||<div style="float: left;">|
2008-02-18 02:47 Hello
Since we now have this new-fangled Blog thing I thought I might introduce myself. My name is Louai. I go by the nick slougi just about everywhere in cyberspace, and lately (somewhat disturbingly) quite often in real life as well. I like KDE, X, and unixy kinds of things. I listen to music ranging from classical to gangsta rap to heavy metal to trance. Right now I would really like to have some kibbeh. I guess that about sums me up. Hello world!
As I already started writing I might as well talk about the things I am currently working on. During the last summer I incrementally wrote the Topology View we have in Tia today. It has served us pretty well - apart from some teething problems and a few small latent bugs it does what it set out to do. But time flies and at Clarified Networks six months is a really, really, really long time. In a nutshell, we have for a while now wanted something with more bang, preferably a few metric tons more.
On Friday I started writing a replacement. The plan is to use ?GraphingWiki metadata keys to construct topologies dynamically. For every container a wiki page is created which includes its coordinates for each topology it belongs to, as well as all the IP addresses it contains, along with documentation and whatever else one likes to put there. Because each container page includes this information we no longer even need topology pages! At the same time support for customizable container pixmaps will be implemented - you can now make your router actually look like a router, not a white spot.1 So we get more dynamic content, more bling, and personally I get a chance to clean up the codebase, which I have been meaning to do for a while now. Putting all this metadata in the wiki and adding the containers to the same category will also enable us to show networks graphically in the browser as well, similar to this. ?GraphingWiki is really really cool.
Another, currently somewhat more researchy, thing I am working on is breaking out certain functionality into a C++ 2 library. In some modules, most noticeable the graphs, but the topoview as well, we are hitting certain python-related performance limits. We looked into this with Jukke and found that ?PyQt proxy object creation overhead consumes a lot of time in fast paths such as painting graphs. Another place that could use a speed boost is the physics spring graph layouting engine, which is basically just number crunching. The plan is to rewrite performance-critical parts in C++ and wrap them using ?PyQt as needed. Stay tuned, I might some day actually get it to work - currently there doesn't seem to be a reason why it shouldn't.
On a sidenote, I've recently been working on an irc bot in my spare time. It doesn't do much yet, but has been very therapeutic to write. Check it out.
-- slougi 2008-02-18 02:47:56