MojoMojo is the most complex open source Catalyst application developed to date.
It is a Web2.0 wiki with AJAX live preview, hierarchical structure, tags, diffs, pluggable syntax, permissions/ACL, attachments, RSS feeds, a photo gallery, edit conflict resolution via 3-way merge, themes/skinning, localization, built-in full-text search, and a reverse index. Since it's built on top of the Perl Catalyst Web framework, MojoMojo supports any Web server, and includes its own standalone one. It also support any database backend supported by the DBIx::Class ORM, and has been successfully tested with PostgreSQL, SQLite, and MySQL.
10. Page structure Paris (genus) /botany/paris Paris (mythology) /mythology/greek/paris Paris, Texas /geography/usa/texas/paris Paris /geography/europe/france/paris Flat structure Tree hierarchy
11.
12. SuperFantastic - “Buddha Dog”, http://www.flickr.com/photos/35423169@N00/50088733 Under what path do you wiki about this?
Speech opening How many people here EDITED Wikipedia?
There are so many wikis out there that there’s a wiki comparison engine – Wikimatrix Perl wiki comparison: http://www.wikimatrix.org/compare/Foswiki+ikiwiki+MojoMojo+Oddmuse+PodWiki+Socialtext+TWiki+UseMod
Wikimatrix lists no less than 120 wikis. I tried to give you a visual Representation of this But I couldn’t fit it all in one slide But anyway, who cares about Ruby or PHP wikis? We’re at YAPC right? So let’s see the Perl wikis
Turns out there are quite a few Perl wikis as well: commercial or free, old and new, obscure or wildly popular But we still have to choose among these. Now everyone’s criteria are different, but here are some that may be important
Socialtext is hosted
Wikipedia has 2.9M page as of today
“Good” means pages with real content, excluding redirect pages, user pages, talk pages, stubs, help, image description pages, portals
Page structure At how anal Wikipedia editors are, they WOULD have used a directory type of path if it were available
So you want to wiki about how people were saying “Aww what a cute dog”, “He is soooo zen”, “Oh look a coffee table that looks like a dog” But in what path?
Usability is the more important the less technically-inclined your audience is In March 2009, bolt|peters user experience conducted a Wikipedia editing study… … on NON-technical users
Perl types sometimes just want the damn code. I know I do.
Markup language: are we stuck with someone’s invention, or can we plug in Markdown, Textile, CREOLE etc?
Peter Thoeny had changed the access rights to the TWiki.org wiki, locking everyone out from the site unless they agreed to sign up to new terms and conditions. The trademarks to the TWiki name were held by Peter Thoeny who was not willing to license them (on a perpetual basis) to the community. On October 27, 2008, the company TWiki.net eliminated the elected board of directors of TWiki, assumed direct control over the TWiki project, and requested that all contributors agree to a new code of conduct before being allowed to continue working on the project. The bulk of TWiki's active contributors subsequently created a fork of the project named Foswiki . [20] [4]
Scalability issues with RCS @ Yahoo!
The preview is better than Foswiki’s in that you see the code under the output on the same page, although you can’t have them side by side, which will start to annoy you ASAP when you edit long pages.
It looks kinda barebones, and it’s CGI
I’ll get back to you with details about Storage, Page structure, tags Markup language and preview features as soon as Perl 6 is released.
The preview is better than Foswiki’s in that you see the code under the output on the same page, although you can’t have them side by side, which will start to annoy you ASAP when you edit long pages. It’s just like MediaWiki’s in this regard.
PostgreSQL & DBI usage: http://github.com/socialtext/socialtext/blob/09ed67d4b7a711b1dc105ce77f885c3530192deb/nlw/lib/Socialtext/TheSchwartz.pm … but I’m not sure I got the right channel
This is all of Socialtext’s user base that cared to add themselves there. Notice it’s CGI, and the entire URL isn’t that cool either.
The preview is better than Foswiki’s in that you see the code under the output on the same page, although you can’t have them side by side, which will start to annoy you ASAP when you edit long pages. It’s just like MediaWiki’s in this regard.
The preview is better than Foswiki’s in that you see the code under the output on the same page, although you can’t have them side by side, which will start to annoy you ASAP when you edit long pages. It’s just like MediaWiki’s in this regard.
WebGUI reinvented its own modules to deal with databases, forms, authentication, caching, handling HTTP requests etc.
Access control is decent Markup languages are OK, even configurable
Now that the people from the MovableType talk have joined us, we can begin to actually talk about MojoMojo … and plugins for DocBook, syntax highlight, youtube, CAPTCHA
From classic, to slightly different, to more different, to quite very different