shutdown.art

February 21st, 2013

Looks like Threeplicate SRL, the company that produced ScrewTurnWiki has shut down completely. I hadn’t realized that.

 

This gives a better understanding as to why they stopped STW development in 2012, and to why they aren’t communicating so much right now.

 

What’s really surprising is that the shutdown appears to have happened in June/July, and communications regarding development hand-over to the community didn’t cease until September (or so).

 

UPDATE 2013.05.15: The STW community is coming together over @ https://stw.codeplex.com

 

roadkill.art

June 25th, 2012

I’ve been sad that the ScrewTurnWiki project founders are discontinuing development/support as of June, 2012.

 

 

However, it turns out the is another open-source.NET wiki: Roadkill wiki.

 

I did not think it was possible to have a name worse than The Gimp.

goodbye.art

June 5th, 2012

Screwturn Wiki is shutting down.

 

I have some complaints about Screwturn, but I liked a number of things about it — not the least that it was a non-huge wiki written in C# for ASP.NET.

 

Despite my (sometimes ranting/frothing complaints), I’m not happy at this news.

wiki.art

May 29th, 2012

Although the progenitor of my having a website, this blog went on hiatus in January 2009, and only returned in April of 2012. That’s a good long break.

In the meantime, I was spending far less time on HTML and more time on dumping links onto pages, writing small amounts of text, and doing only small amounts (by comparison with re-installing WordPress and working on the poorly-designed-website) of bit-twiddling with PmWiki.

I much prefer the PmWiki markup to WordPress’ markup — especially since WordPress has a pseudo-HTML markup (that looks like HTML, but is re-processed invisibly on the backend and transformed in ways you’d least expect.

blah blah visual editor blah blah crap blah blah I miss WordPerfect 5.1 for DOS’s reveal codes blah blah blah

What I’d like is some way to tie the two together better.
One rendering engine for both, media-images use the same warehouse, etc.

The WP FreeStyle wiki plugin adds FreeStyle-wiki markup to WordPress. Nice!
But How?
It installs an entire working instance of FreeStyle Wiki inside of WordPress.

That’s a bit of overkill just for rendering posts.

Plus, I already have a working install of PmWiki — just not inside of WordPress.

So, I have to find some way to get allow WordPress to pass arbitrary text — hopefully with wiki-markup — to PmWiki and retrieve the HTML-ified text in return (and hope that WordPress doesn’t f**k it up).

The FsWiki plugin gives me a quick idea of how to pass off the text to a renderer — it’s getting it to and from PmWiki that concerns me.

Quite possibly not difficult — I just haven’t tried it yet.

MarkupToHTML($pagename, $str)

Converts the string $str with PmWiki markup into the corresponding HTML code, assuming the current page is $pagename.

(source)

Other avenues of research include the TextControl plugin.

  • syndicate

    • Add to MyMSN
    • Add to MyYahoo
    • Add to Google Reader
    • Add to Bloglines
    • Add to Newsgator
    • Add to NewsIsFree