?

Log in

Click Wiki [entries|archive|friends|userinfo]
Click Wiki

[ website | ClickWiki Site ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

It's Soup [Apr. 3rd, 2007|10:50 am]
Click Wiki

jabberwokky
We hit 1.0 at 6:30am this morning. Since it was an all-night run, I'm going to say that we made our 2007-04-02 target. It was still April 2nd somewhere on the planet!

Gads, I'm tired. In interesting synchronicity, our non-profit "sister" org (unconnected other than being friends) was updating all night to get ready for their release. Last night was quiet moment and a big leap in offerings for communities looking for a powerful, simple wiki system, and a corresponding leap for truly open content.
link

1.0RC1 [Mar. 22nd, 2007|07:54 pm]
Click Wiki

jabberwokky
Commercial modules were finished yesterday evening. We're go for a April 1 release date.

Seriously.
linkpost comment

(no subject) [Jan. 5th, 2007|11:43 am]
Click Wiki

jabberwokky
Got a wee bit backed up in the business side of things. Plus, a commercial release has a bit more QA than a purely open source version. You get what you pay for. Of course code will still be released, but commercial hosting requires verified, supported code. The surprise was WYSIWYG editing, and today I'm hoping to do an upload of everything.
linkpost comment

(no subject) [Nov. 6th, 2006|03:28 pm]
Click Wiki

jabberwokky
(All has been quiet... there are two nice big surprises coming up this week. Woo).
linkpost comment

Core (finally fully) debugged? [Oct. 21st, 2006|02:52 pm]
Click Wiki

jabberwokky
I have a wad of tiny postits at the corner of my desk. That was the core buglist. There ain't no more. There's only one core wishlist item left -- grouped renaming (i.e., when you rename Foo to Bar, then Foo/Talk is renamed to Bar/Talk). I'm not 100% sure I like that, which is why it's floating out there as a wishlist item. (And of course, there's grouped delete as well).

Fixes were mostly having to do with binary entries (reverting after renaming), and renaming (clearing relations on rename, etc).

Poisoned imports are now impossible: indirect file: links can't be imported (without uuencoding them). Before it was possible to manually inject a @@file:/etc/passwd, for instance... but only if you had shell access, write access to the import directory and a wiki account with import privileges, so you had to be pretty durn enabled already... and shell access would have meant you could just get the file anyhow. Still, doing the Right Thing is a good idea.

I also cleared out many items that had long since been done -- notices generate a tag relationship, for instance. I also added a redirect relationship.

filter/edit_image
Now displays an 800x1024 thumb (like view_image) so the page isn't overwhelmed by a huge image.

display/newsstand
Started. It will be a news oriented display module.

display/teak
A simple and easy display module. I didn't like how Arc came out, and this pretty much is what I intended with Arc.
linkpost comment

Dennys at 10:31, and a sudden realization. [Oct. 5th, 2006|10:28 pm]
Click Wiki

jabberwokky
(Looking through my notes, all end-user facing features are complete. An easy ACL editor is for admins, and dynamic generation of available actions only affects display modules. That means that I'm ready to launch into RC phase... much thanks to Stan for finding bugs and Sarah for suggesting features for novices. Here we go...)
linkpost comment

(no subject) [Oct. 5th, 2006|09:36 pm]
Click Wiki

jabberwokky
core/save
I hate the way I had to do this in the end. There is no good way to handle deletion and renaming that makes sense in all cases and preserves data. In 98% of cases, Rename now works the way you'd think. In the rare (hopefully) case that some jackass (since it's likely intentional) does the following:

Deletes ImportantThing
Creates DumbThing
Renames DumbThing to ImportantThing

Then ImportantThing is still kept, history and all, as a deleted item under ImportantThing/deleted1 (or whatever number makes it unique). I hate the idea of appending a number, but I can't see a good way to handle this. The history of DumbThing needs to be retained and moved into ImportantThing... I hate how some wikis just move over the last revision rather than the entire chain of revisions. This maintains the Golden Rule that every edit in the system is still accessable to all users (ACLs allowing, of course).

Of course, action/shred will make the entry not exist, and it will have never existed. Boojum time, and you can rename something what it was. But that's for admins and hopefully isn't ever needed... Philip has some good ideas on a memory hole. Still, I really wish that illegal/immoral data (copyright violations, personal info) could be stored encrypted legally. It would be neat if the info were encrypted and the key broken up and distributed among users such that only a consensus of all coming together could unlock it. But then, I also like the idea of elves and unicorns, too.

Summary: Some problems don't have elegant solutions. Yet.
linkpost comment

(no subject) [Oct. 5th, 2006|07:54 pm]
Click Wiki

jabberwokky
action/settings
Briefly messed up display... when I added autoedit, I had the form name as settings_display. Whups. Fixed.

core
Completely rewrote the link to html render function. It works exactly the same in the defined cases, and handles undefined and typoed links better. A new implicit email link exists. [Victorian@wikipedia] goes to Wikipedia, while [Victorian@aol.com] is presumed to be an email. Criteria is that it does not exist in the metawiki list and has a period in the second half. No period throws an error. Obviously the [mailto:victorian@aol.com] link format is to be preferred, but people don't do the preferred thing.

functions/webcam
There's a new, thrown together, webcam function library. It has one single function at the moment, [[webcam feedname]]. It simply displays /i/webcam/feedname/current-thumb.jpg. I'll package it with some simple bash and imagemagick scripts that handle a webcam. There's also one that grabs weather. It's hardcoded for the State College radar, but if anybody needs it, I'll likely go ahead and make it more generic.

In other news, I realized a week or so ago why I like the Wiki communities... at least the community wiki communities. It reminds me of the BBS days. Wiki markup is very simple rules, similar to ANSI codes, and the user base is a local group of people who can physically meet.

In other news, don't buy webcams based on their spec. Cheap ones are crap, even if they have the exact same specs as high end ones. Also, the fixed focus lens is set to about three feet. Perfect if you're pointing it at your face from the desk, but lousy if you're pointing it at the mountains across the way. Ah, well. Best Buy has a decent return policy.
link1 comment|post comment

(no subject) [Oct. 2nd, 2006|08:16 am]
Click Wiki

jabberwokky
Core Wiki
A major internal change was made: entry ids now are not 'suffix s sensitive'. That is, "Restaurants" and "Restaurant" are the same. It also applies to portions of entries: "Events/On 2006-10-12" and "Event/On 2006-10-12" are the same. Titles, of course, retain the s, so a "Code/Demo.css" is still css, not "Code/Demo.c" (although the id is technically "code/democ").

Core Wiki
Internal links use the title now; they had been using the id.

action/history, display/*
Users use their title now; they had been using the id. That looked funky when you had an 's' at the end of your name (which would then be cut off). Luckily, I have an 's' at the end of my name. Hopefully there are no other places where the id is visible. Honestly, it should all have been title anyway.

Core Wiki
New function: cwiki_entry_title( $id ). With all the titling, I figured this would be useful. It's only a call to cwiki_fetch_single(cwiki_relations_get($id), 'title'), but it makes the code more clear.

Core Wiki, action/settings
TODO links (i.e., red links) can auto edit. settings_autoedit is the var, and it's in the settings module already.

action/settings, CSS
I added help to settings, BTW... there's a new CSS, form_help.

action/thumbs
Thumbs now have a max for the unspecified side. That is, a width 300, height unspecified will max out at 1200px (or action.thumb.maxy) for the height. This also means that the unspecified side won't default to 200px (or action.thumb.y).

I probably did some other items, but I was working late last night at Dennys, both updating NitWik and working on code, so some of my notes are buried in my content folder. A firm divide between content and presentation is probably important to people who are both coding and writing content as well. :)
linkpost comment

Changes [Sep. 28th, 2006|04:13 pm]
Click Wiki

jabberwokky

  • Major: Added link to change or entry from updates' icons (if changes module is loaded).
  • BUGFIX: Gallery works again. Whups.
  • Major: Added shade option to thumb action
  • Major: Thumbs are no longer animated (I stopped that annoying yellow guy). Images still are, of course.
  • Minor: Click on a thumb in gallery to go there (req. javascript).
linkpost comment

navigation
[ viewing | most recent entries ]
[ go | earlier ]