Free come and go with me to that land software for linux

Command Line Content Management System is my own command line content management system. Its not a dynamic cms, but a script that takes a source tree and creates a web site out of it.
The idea came to me when i was using m4 for my website to generate the HTML, but i did not like the idea that i was still typing HTML in my pages, even if it was simplified by using macros. I was updating a wiki page somewhere when it hit me: i wanted a command line system that was able to take wiki style input for page content. The result is clcms.
Its in beta state at the moment, mostly to try out some different approaches to various
challenges. But i thought id share it now, so if youre interested and might have some ideas on where to go from here, drop me a line (or a patch). At least it can build this site and the tutorial site, but anything more fancy will probably not work.
Its also a way for me to learn Python, so i might in my ignorance produce some weird constructs here and there. Please let me know, but be gentle.
Main features:
- Updates should be possible with a terminal and an editor
- Content is stored in a directory tree
- Adding pages (or items?) should be as easy as creating a new file and typing some lines in it.
- For default pages/items no config necessary
- No HTML, XML or anything alike for normal usage
- All pages have their binary content (images, download files) in the directory of the page itself
- All output is static, no generating on the fly
Usage:
After untarring the tarball, add < dir>/bin to your path or copy bin/clcms.py to a directory in your path.
You can now go to < dir>/examples/documentation and build the tutorial by running
clcms.py
Now wasnt that easy?
Point your browser to file://< dir>/examples/documentation/out/index.html and see the result of all your hard work.
If it did not work, its not your fault. Just remember that version number.
Enhancements:
- .page files can now contain content attributes.
- Filename extensions are removed and replaced by attribute lines in .page files.
- The page.meta file should now be called page.attr.
- The nomenu option had disappeared in a previous release, and has been put back.

Acme::OneHundredNotOut is a raise of the bat, a tip of the hat.

I have just released my 100th module to CPAN, the first time that anyone has reached that target. As some of you may know, I am getting ready to go back to college and reinvent myself from being a programmer into being a missionary. I dont forsee that many more Perl modules coming out of this.

Of course, this doesnt mean that Im going to abjure usage of Perl forever; any time theres a computer and something I need automated, out will come the Swiss Army Chainsaw and the job will get done. In fact, we recently needed to manipulate some text from a mission handbook to translate it into Japanese, and Perl was there handling and collating all that.

But 100 modules is a convenient place to stop and take stock, and I hope that those of you who have benefitted from my modules, programs or writing about Perl will forgive me a certain spot of self-indulgence as I look back over my CPAN career, especially since I feel that the diversity of modules that Ive produced is a good indication of the diversity of what can be done with Perl.

Lets begin, then, with some humble beginnings, and then catch up on recent history.
The Embarrassing Past

Contrary to popular belief, I was not always a CPAN author. I started writing modules in 1998, immediately after reading the first edition of the Perl Cookbook - yes, you can blame Nat and Tom for all this. The first module that I released was Tie::DiscoveryHash, since Id just learnt about tied hashes. As with many of my modules, it was an integral part of another software project which I actually never finished, and now cant find.

The first module that I ever wrote (but, by a curious quirk of fate, precisely the fiftieth module I released) was called String::Tokeniser, which is still a reasonably handy way of getting an iterator over tokenising a string. (Someone recently released String::Tokenizer, which makes me laugh.) This too was for an abortive project, webperl, an application of Don Knuths WEB system of structured documentation to Perl. However, given the code quality of these two modules, its perhaps just as well that the projects never saw the light of day.

There are a few other modules Id rather like to forget, too. Devel::Pointer was a sick joke that went badly wrong - it allowed people to use pointers in Perl. Some people failed to notice that referring to memory locations directly in an extremely high-level language was a dangerous and silly thing to do, and actually used the damned thing, and I started getting requests for support for it. Then at some point in 2001, when I should really have known better, I developed an interest in Microsofts .NET and the C# language, which I still think is pretty neat; but I decided it might be a good idea to translate the Mono projects tokenizer and parser into Perl, ending up with C::Sharp. I never got around to doing the parser part, or indeed anything else with it, and so it died a lonely death in a dark corner of CPAN. GTK::HandyClist was my foray into programming graphical applications, which started and ended there.

Bundle::SDK::SIMON was actually the slides from a talk on my top ten favourite CPAN modules - except that this changes so quickly over time, it doesnt really make much sense any more.

Finally, Array::FileReader was an attempt to optimize a file access process. Unfortunately, my "optimization" ended up introducing more overheads than the naive solution. It all goes to show. Since then, Mark-Jason Dominus, another huge influence in the development of my CPAN career, has written Tie::File, which not only has a better name but is actually efficient too.

The Internals Phase

1999-2000 were disastrous years for me personally but magnificent years Perl-sonally. Stuck in a boring job and a tiny flat in the middle of Tokyo, I had plenty of time to get stuck into more Perl development. I felt that getting involved with perl5-porters would be a good way of gettting to know more about Perl, and so I needed a hobby horse - an issue of Perls development that I cared about. Since I was in Japan and working a lot with non-Latin text, Unicode support seemed a good thing to work on, and so Unicode::Decompose appeared, while I fixed up a substantial part of the post-5.6 core Unicode support.

Id recommend this way to anyone who wants to get more involved in the Perl community, although I was very lucky in terms of who else happened to be around at the time: Gurusamy Sarathy was extremely gracious in helping me turn my fledgling C code into something fit for the Perl core, and he also helped me understand the perl5-porters etiquette (yes, there was some at the time) and what makes a good patch, while Jarkko Hietaniemi was always good for suggestions of interesting things for keen people to work on. Seriously, get involved. If I can do it, anyone can.
Anyway, this fixation with understanding the Perl 5 internals, and especially the Perl 5 compiler, (due to yet another of my Perl influences, the great Malcolm Beattie) led to quite a torrent of modules, from ByteCache, an implementation of just-in-time compilation for Perl modules, through B::Flags and B::Tree to help visualising the Perl op tree, to uninit, B::Generate, optimizer and B::Utils for modifying it.

Perl About The House

Now we abandon chronological order somewhat and take a look at the various areas in which Ive used Perl. One of these areas has been the automation of everyday life: checking my bank balance with Finance::Bank::LloydsTSB (the first Perl module to interface to personal internet banking, no less) and my phone bill with a release of Tony Bowdens Data::BT::PhoneBill.

Finance::Bank::LloydsTSB was meant to go with Finance::QIF, my Quicken file parser, to produce another now-abandoned idea, a Perl finances manager. It seemed that Im only capable of producing modules, not full standalone applications - or at least, it seemed that way until I produced Bryar, my blogging software, based on the concepts from Rael Dornfests blosxom and beginning my adventures with Andy Wardleys Template Toolkit. Bryar also tuned me in to the Model-View-Controller framework idea, of which more later.

Another project I briefly played with was a personal robot, using the Sphinx/Festival speech handling and recognition modules from Cepstral and Kevin Lenzo. I didnt have X10, so I couldnt shout "lights" into the air in a wonderfully scifi way, but I could shout "mail" and have a summary of my inbox read to me, "news" to get the latest BBC news headlines, and "time" to hear the time. Of course, getting computers to tell the time nicely takes a little bit of work. I dont like "Its eleven oh-three pee em", since thats not what someone would say if you asked them the time. I wanted my robot to say "Its just after eleven", and thats what Time::Human does. Shame about the localisation.

Feed Me Links is a Web application for managing and sharing links.

Feed Me Links provides many interesting features such as tagging, comments, RSS feeds, tag clouds, friend lists, a REST API for exporting, a browser sidebar, and Firefox and IE favorites import.

Moonlander is a space simulation game.

You must land with lander on the Moon, but you have limited fuel.

Landing is very hard, because you must land very very slow. Prees "B" to increase fuel.

GXMame is a frontend for XMame using the GTK library, the goal is to provide the same GUI than mame32. For the moment it will just have the same gui, the final goal is to be able to share config files with Mame32k (or any version of mame32 that write config files instead of saving data into windows registry) allowing dual booter to have the same environment (favorite, timeplayed, last game selected, gui preference...) under windows and Linux.
I wanted to learn GTK and have a decent frontend for xmame, gnomame didnt work on my computer and I didnt like other front end in Tk, so I decided to start this project, just after I discovered gRustibus, the very good front-end from Kjetil Thuen. I took this front end as a model for the creation of GXMame Im not sure that I could have go so far and so quickly without this model.
Main features:
- Detailed view
- Small icons view
- Indented view (shows clones games under the original one)
- Font color and size selectable
- Icons support, .ico files or a zipped archive from Mamu or Mame32QA
- Tools bar
- Folder(filter) panel
- Screenshot panel
- Display snapshots, Flyers, Marquees, Cabinets, Titles.
- Support of zipped pictures
- Display mameinfo and history
- Status bar
- Support of catver to sort games by version and categories
- Random game selection
- Quick check: only check if a romname.zip file exist in roms folder (also works with clones)
- Audit of all roms
- Window with the properties of all games
- Audit of a single game
- Popup menu to easily access to most used functions
- Preferences for games(global and specific)
- Joystick support (new 386 1.x.x linux driver only)
- Creation of gamelist from xmame
- Multiples executables support
- Scalable icons
- Additionnal options string
- Sortable columns (in any views)
- Sortable selectable columns order (in detail view)
- List view
- Large icons view
- and lot of others...

Go Siege project is a massively multiplayer online Go game.

Go Siege is a transformation of the ancient Chinese game of Go into a massively multiplayer online game in which hundreds of players can compete simultaneously over the Internet.

There is a bug in the 0.3 release.

You can fix it by changing line 168 of /site-packages/gosiege/rules.py from

if (libgain > 1): return True
to
if (libgain >= 1): return True.

sidux-highway is a KDM theme as a modification of the Sabayon KDM theme "Open Future".

The highway picture was taken and modified by me, the go.png is taken from "crystalline black" icons (kde-look.org #46349), session.png and system.png are modified nuoveXT icons (kde-look.org #26449). The small pictures inside the monitor and folder are sidux wallpapers.

Modifications:

changed wallpaper and icons and resized and repositioned the userlist slightly, added missing screenshot

The highway picture is widescreen 1920x1200. Should be easy to resize it if needed. For your convenience I also have added a 1024x768 version, just rename it if you want to use it instead of the WUXGA picture.

To use the theme untar it to /usr/share/apps/kdm/themes/ and either change your /etc/kde3/kdm/kdmrc manually or use kcontrol if you have the kdmtheme module.

ATTENTION: If you use a display height other than 1200 the position of the login area (that half transparent stripe) will be different from what you see in the preview. If you want to have the same position with another display height you can easily adjust it by editing the file highway.xml with your favorite text editor. Just go to line 49 and change the y-value that by default is "-485". Its an easy rule of three: lets say you have a display height of 800: 800x485/1200=323 - go and replace -485 by -323.

BTW: If you just want the wallpaper: http://www.kde-look.org/content/show.php?content=52780