Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I want another wiki. OK, yes yes, I know...

    But what I'd love to see is a wiki where a single instance of the wiki can be entirely contained in a single SQLite database file.

    And I mean everything that isn't environment specific. Non-environment configuration (auth rules etc), templates, images (if it has image support), and so on.

    I want my wiki to be one file. One file where if I have the admin password (which is contained in the one file) I can just hit "Download Wiki" on some admin page and it sends me the
    • That would hardly take 8 weeks of full-time hacking. It could be done in about three days of full-time hacking. Make that a week if you want a large array of bells and whistles, maybe.

      I mean, I built a wiki into the web app for my contract job by accident when I needed to make snippets of my templates user-editable. 20 minutes, one (name, content) table, 10 lines of straightforward code, 3 trivial queries in the DB layer and 10 sparse lines of template later I had something that took a life of its own as

      • And it had history? Or did you implement a scratchpad?

        Administrative code? User authentication? Template editing, image support?

        One of the features of wikis is you can write on in 5 minutes, or you can have people working full time for years (MediaWiki).

        And everything in between.

        And 8 weeks worth of features, in a one file wiki, would be nice.

        But I'll look at the one suggested above instead.
          • Didn’t have history at first, but does now. That was one of the new features. Took an hour or so.

          • User authentication was provided by the part of the app that was already in place, but that too is quite simple; it only takes appreciable time if you want finegrained permissions.

          • Not sure what template editing refers to.

          • I don’t have image support at the time being. Upload management would indeed be somewhat time-consuming to implement. (In my case though the work is already done in another part of the app, so that too won’t take much effort to add.)

          I don’t know if MediaWiki is a good example. I find its feature set bloated and oddly shaped. Also, it was evolved by the needs one particular installation, and some features have been reimplemented multiple times, yet all iterations must be kept around because they can’t break any existing articles. In other words, MediaWiki has a rather unique set of design constraints, and in my opinion therefore counts as atypical.

          I dunno, 8 weeks of features just sounds like way more stuff than the “wiki threshold,” ie. the feature set where doing the most obvious thing leads you to the relevant feature which is instantly useful without having to learn it.

          Shrug. It doesn’t really matter anyway, it’s the Googlers’ call.

          I’m just thinking that framing it as an 8-week-project makes it look so grandiose that it might not be tackled by whoever shares the itch and might otherwise have sufficient spare tuits.

          I dunno if you’ve tried writing a wiki; I knew they’re quite trivial, but I was still shocked to experience first hand just how little props them up. That’s really all I was trying to relay here.