HackNBlog @ Salamanteri Server

I was and still am going to install Greasemonkey plugin for my SwiftFox (optimived version of Firefox, with patches an code optimization for CPU in use).

There are however security issues - some fixed unlless you use old version (in case you have old ccomputer that can’t run veru modern FF) and some are easy to prevent. IF you read the documentiation, and in this case the section “Avoid Common Pitfalls“. Of course reading the whole manual is a good idea.

I may infact intead of regular FF plugins start making Greasemonkey scripts, though that willl require the user to installl Greasemonkey to get my add-on - oh welll, I could think that if he doesn’t then he does not need it - or better yet, maybe he does not even deserve it (tee-hee, I make a joke).

Anyway, have a nice day - I have gone FF add-on mental, pretty soon I will post all add-ons that I installed and yound actually worthy to keep.

Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. - Alan Kay

Bumped into this neat quote about programming and quality of software today on a site called “WTF Code” - holds pretty much true for unfortunately large amounts of software today, especially for commercial proprietary products (comments to dispute are always welcome :) ).

I have always (that is since I wrote my first lines of QBASIC code under MS-DOS 5.0) had interest to learn new programming languages, just out of interest towards programming as a hobby. Lately I have grown more and more interested on learning to program Common Lisp, a language highly praised by those using it but also one of those that has always looked way too cryptic for me (considering that I do know various different languages and rarely bump into one that I’m totally baffled about when looking at it :) ).

Now I have decided to find out what all the fuss is about and learn at least the basics of Common Lisp - however I’m having hard time finding a tutorial that is both good for someone who knows nothing about Lisp and does not stop after “Hello World” and couple simple examples of mathematical functions :)

So far I have found that GNU programs include a Lisp compiler and interpreter called ‘gcl‘ (GNU Common Lisp) and one simple tutorial on very basics of Common Lisp.

What I’m hoping as I’m writing about this is that maybe someone with knowledge is reading this and could post a comment with link(s) to a good tutorial for me to start working with :) Whether it will happen or not I will certainly be posting about my future experiments with Lisp here - I would like to gain at least enough knowledge to produce a Lisp version of my ‘tree.sh‘ (shell script to output directory tree structure nicely) as it is a good short program to write for getting overall picture of how a language feels write with compared to others - in fact I might write it with multiple languages for comparison of them (just for the fun of it).

To quote osnews.com article Nokia To Add LGPL to Qt Licensing Model…

After Nokia purchsed Trolltech last year, doubts arose about how Nokia would handle the dual licensing model of Qt, the advanced cross-platform toolkit which lies at the base of the KDE Free software desktop. As it turns out, these doubts were unfounded, as Nokia today announced it’s going to add the LGPL to Qt’s licensing model, starting with Qt 4.5.

…and the press release…

The move to LGPL licensing will provide open source and commercial developers with more permissive licensing than GPL and so increase flexibility for developers. In addition, Qt source code repositories will be made publicly available and will encourage contributions from desktop and embedded developer communities. With these changes, developers will be able to actively drive the evolution of the Qt framework.

Personally I’m eager to see if this will result in code exchanging between the GTK and Qt projects - something that the licensing has prevented before. It would seem logical and beneficial to both sides to take on that path but only the future will tell…

My phpinclude plugin seems to have been success. Only 1 day after release I’ve already have almost 79 visitors on the page and several downloads just from this site. I guesss large part of the success came from adding my plugin to WorddPress Plugin Database @ wp-plugins.net and reviewing my plugin page on my StumbleUpon favorites so big thanks to social media! =)

I found some sites even mentioning my plugin (leaving out the obvious ones mentioned above):

• Weblog tools collection, post WordPress Plugin Releases for 12/22
  The page listed several plugins but a user had even commented mine (not to mention that it was the only comment when I looked. Apparently he had been looking for something like this for some of the same reasons I created it and he had even tried some plugins trying to achieve somehing similiar.
• WordPress Planet apparently lists new plugin entries from different blogs. It’s kind of pathetic to mention this here because my plugin was mentioned in entry from Weblog tools Collection, which I listed just above

Noothing else this time, I’m just happy about my success. Will this get me fame? Possible. Money? Not likely. Happiness through rocognizion: Definately.

I’m proud to have released my first WordPress plugin, phpinclude… It allows to include any file apache can access into your post or page. Including PHP files it also executes them. Naturally there is some security settings to make sure that only editors authorized for that can do it. You can check the overall info, view syntax highlighted source and download the plugin at Software / Wordpress Plugins / phpinclude page. Naturally it’s released under GNU GPL license.

Also, if you havent glanced the “Quick News” list on the left of the posts you might want to know that I have released a proramming example of DOS tree command implemented for *nix bash shell in Shell Scriping subsection. So to check tree.sh, go through any of those or go straight to tree.sh for full info and that syntax hihlighted fabulous source (I make a joke, hehe).