Source code:
Kanban lite:


New group: excygen

I want to thank you for the great time, support and all the heads up. I will fade back in, keep you up to date, only I will no longer be posting here, but rather at excygen.

More infos later.

Picogen's dead, but it lives on in excygen :)
I took a new job some 2 years ago.

This unfortunately increased my travelling time from just 10 minutes to now 1.5 hours per day. For a long time, it was even at 3 hours. In effect, my spare time (== picogen time, among other things) was drastically reduced.

I have learned the basics of Haskell and also learned Python. Those languages are great in that they give you more effect per line of code.

Picogen is not forgotten and still the tool of my dream. It's really just that I currently lack the time to continue the pace of the past.

Hopefully my new knowledge will turn into new picogen releases early, but I unfortunately can't give you a definition of early.

Thanks to everyone for the heads-up and support :)
I have serious problems keeping the old MediaWiki clean. Serious problems, in that configuring MediaWiki seems like a full time job, in that fighting spam posts seems like a full time job, in that MediaWiki is mostly open to anonymous by default. And consider that picogen does not have any significant user base, yet.

So I tried out TikiWiki, which is really a full blown content management system with a ton of usefull modules and features.

The one thing I like at most: Central user group management, a banning system, safe settings by default.

I took a good style that was distributed along with the TikiWiki package, and modified it significantly to fit the style to the picogen-mainpage.

Please, what do you think?
-> -> homepage (for style comparison)
->… -> example content of new wiki
-> -> old wiki (the style fits my personal homepage
(update below)

To not bore you with unecessary details right now, just let me say that the last remaining "master" feature (*) that was mandatory for the 0.4 release is 99% complete.

What does remain are details, whose sum is still significant, but the gros work has been done.

(*) it is related to "Parametric Presets", where you use some program/user-supplied heightfunction that can be tweaked by just a handfull of edit-boxes and drop-downs et cetera, see . That feature can only be meaningful if you *have* parametric presets, and for that, I introduced a file based database. In the future, that databasee will also be filled with preset materials, colours, textures, and more :)

update 2011-01-18:

* A major bug has been removed, caused by Instances and Bound-Instances (something that does not have to struggle the end-user ;)) not propery forwarding a prepare() call. In result this meant that often, there was terrain, but sometimes, not (because under the hood, the root-node of the lazy quadtree was not cleanly initialised).

Remnant before release: Documentation. I am thinking about writing a dialect of markdown (…) for documentation, but I'm also having a look at alternatives (preferably something that is also editable by end-users), possibly I just keep the wiki (but spam sucks at times).
... left before I must submit an image "of flowers, trees, foliage, seeds, or anything to do with plants, either real or imagined, on earth or elsewhere" to (IRTC).

A plethora of features have been added "just" to be able to render trees, I think so many that I could tag the next release with version 0.10 instead of 0.3. Stay snoopy, I've also mocked up the rough layout of the… (next GUI).

But back on topic: Less than a day left. Right now I am rendering two variations of one image that features a nice, foggy sunset, with many trees + (yay!) semi transparent foliage. I'll be posting both versions on dA the next days (it was/is really worth the effort!). The one my gf likes more will get some more computation time when I am home before submission.

Times are funky, aren't they? :D