the SoggyOnion

statico on 2004-04-23T02:44:50

So I looked my friend Ari's sourceware.net and thought it was neat. All those links in one spot? I want my own! Then I took a look at and downloaded NewsClipper and tried going through a hideous install process. All this for that? I just want to specify a bunch of URIs to RSS/RDF feeds! Oh yeah, and any other content I scrape.

What later became SoggyOnion was born. I modeled the installation after Kwiki, where one types a command to install the necessary files and defaults. After install, you make a few changes to the dead-simple YAML configuration, run a command to generate the pages, and bam. Tabbed-based organized pages of links.

So here's my quandary: I really don't want to populate CPAN with a top-level namespace of "SoggyOnion," which is the namespace of the modules used by my code. I'd like to release this, but I can't find/think of a suitable name. It's not a CGI, so CGI::App wouldn't do... Hrm...

Soggyonion:
soggyonion.com


I like the name

brian_d_foy on 2004-04-23T03:18:17

I think SoggyOnion would be a fine name. Other modules have fanciful top level namespaces, and from what I have read, your thingy isn't a general module, but a specific application.

0.01

statico on 2004-04-26T03:59:33

Okay, time for a 0.01 release to test out the distribution. The functionality and docs are there, I just need to write tests.