Search results for
wiki
Some time ago I posted some conceptual thoughts on effectively managing hierarchical data. I am working on a showcase with the results from my efforts: An extended Wiki system which should bring you the best from all worlds (hopefully). All meaning the simplicity of Wikis, the publishing power of CMSs, the dynamics of business and application logic and finally the hype of AJAX.
What I'm working on is basically kind of a wrapper for PhpWiki. I did a lot of research on various frameworks for rapid application development, and unfortunately, none of them did really satisfy me. There are very good ones of course, but I always had the feeling I had to start from scratch to achieve what I had in mind. Then I came back to PhpWiki which might appear like a rather strange choice as a framework. However, in my opinion, Phpwiki in its core has a very useful codebase and supports a lot of plattforms.
So stay tuned, an early Web-2.0-like closed alpha testing site is not far away from release.
Let me tell you what my secret holy orb told me: 2007 will be the year of the wiki.
With this blog post I'd like you to introduce to mawih. It's a project I've been thinking about and working on for quite some time now. I call it a mail-wiki-hybrid (because it is). What does it do? It merges what both email and wikis can do best: communication and knowledge management.
Basically it's a wiki-based email client. That means you login to mawih with your mail account credentials and if you fetch your new emails they get saved as WikiPages. Your Inbox is RecentChanges. A conversation/thread is represented by PageHistory. To compose and send an email you create a new WikiPage and send it. To reply to an email you edit the received email/page and send it back.
Technically mawih is kind of a wrapper for PhpWiki and IlohaMail's IMAP API.
I'm very excited about this. I'll try to show a demo of mawih at the upcoming Webmontag in Vienna on January 15. And hopefully soon I will release the source code. Let me know what you think about the concept. If you're a developer maybe you want to join the project. It would be great to further develop mawih so it could support different wiki engines as a backend.
Update: Bryan Reinholt released a paper about his project email2wiki.
I like sonday mornings.
PhpWiki 1.3.13 Release Candidate 1 released
This will be a major feature release which will be the base for the stable 1.4.0. The highlights are Semantic Web support, various WYSIWYG editors, a stable MonoBook theme (wikipedia), enabled acdropdown support (LiveSearch), postgresql and oracle enhancements, moving Help pages into Help/, support different charsets in pgsrc and Windows NTLM auth support via HttpAuth. utf-8 should work.
ReleaseNotes + ChangeLog
Download
Reini Urban will talk about PhpWiki at Barcamp Kärnten (Feb 2007).
Update: Since phpwiki.org still only hosts PhpWiki 1.2.x, I set up a test wiki at phpwiki.rafelsberger.at running 1.3.13rc1. Feel free to experiment.
So heute erstmal Live-Blogging auf Mind Your Own Business: Der Webmontag in Wien. Letztes Mal gab es ja nur eine Nachschrift. Ursprünglich wollte ich ja heute mawih vorstellen, leider wird's noch keine Live-Demo geben, ich werde aber ein wenig über das Konzept erzählen.
19:23 6 people and counting...
19:50 vorstellungsrunde vorbei. alle witzig drauf. web2.0 definition sparen wir uns (beim letzten webmontag wussten wir noch genau, was das ist, haben es aber vergessen, aufzuschreiben).
20:00 Eric Eggert beginnt mit Die Geschichte des Webmontags und Webstandards 2006 - What happened to the tables?
Anschließend accessibility-Diskussion. An Standards halten. Wer definiert sie? Jetzt große Web-2.0-Diskussion. Ich liebe es.
20:20 Christopher Clay über Web-Security. Cross-Site-Scripting. Überblick über jeden Wahnsinn und Möglichkeiten. c3o hat sich schwer beim CCC inspirieren lassen. Hier live mitzubloggen würde jetzt zu weit führen. Vielleicht gibt's die ppt dann nachher.
Was lernen wir daraus: Upgraden. Momentan über HTTP-Header erzwingen, dass PDF nicht embedded angezeigt werden, sondern nur runtergeladen werden können.
20:40 Jetzt mehr Security-Sachen.
- PHP Urlrequest-Injection. Watch out.
20:55 SPL
21:24 Christopher Clay über das MetaLab.
21:26 Socializing (ca. 16 Leute)
Update: Christopher Clay und Eric Eggert fassen zusammen.
It's interesting: Those Wikis turn out to be the best (regarding usability) which call temselves not even so. Like last.fm's bio page or Google Groups Pages. I think with Wikipedia's dominance everybody now believes that Wiki=Monobook-Theme. I beg that we get rid of this cluttered beast. I see Wikis more like frameworks. The theme is just the surface. Monobook as a surface does a good job in hiding what the original idea of Wikis was: Speed. And ease of use.
As Wiki now stands for Wikipedia/Monobook, it's not a bad idea to call a service different. The Wiki-Idea stays as a concept and does its core tasks under the hood (versioning, user management).
This is where PhpWiki comes in. PhpWiki is kind of an underdog. The default theme lacks the feature bombardement of Monobook and is not quite appealing to the eye (like, say WordPress - I know, it's not a Wiki but that's a different (long) story). I think the lack of a good default theme turns many people off. However, IMHO it has a fairly good if not exceptional codebase. When I think further and look at the latest PhpWiki developments regarding Semantic Web and Wysiwyg, what I see is not just a plain Wiki but the basis, well, a framework for building future web applications. Maybe we'll just have to name them different. Like SocialText, SystemOne, JotSpot and others of course.
Google Groups Pages via: del.icio.us/gregorrothfuss
btw, this page was made using PhpWiki too.
Vielleicht ist der Begriff Blog (inklusive all seiner Variationen) irgendwann (hoffentlich) obsolet und wir reden wieder allgemeiner von Internetseiten, Dokumenten und Artikeln sowie lesen und schreiben. Ich ertappe mich nämlich immer häufiger dabei, die von Blogs vereinnahmten Technologien wie RSS und Ping-Services in "klassische" Seiten zu integrieren, um z.B.u.a. die langsamen Spider der "klassischen" Suchmaschinen zu umschiffen.
Was mich zum nächsten Punkt bringt: Immer mehr ärgere ich mich über das Single-Sign-On-Tam-Tam der großen Player. Wie wär's mit folgender Alternative: Ich hoste meine Fotos, Bookmarks und Hastdunichtgesehen-Videos nicht (z.B.) bei Yahoo, sondern "klassisch" (schon wieder) am eigenen Webspace - natürlich mit der geeigneten Software, die mir ein ähnliches Usability-Feeling wie etwa Flickr gibt. Den Social-Networking-Teil übernimmt openID. Indiziert wird via Ping-Services à la weblogs.com (nur eben nicht auf Blogs beschränkt, sondern Informationen/Dokumente jeglicher Art). Dezentralisierung Baby!
Noch was: Wenn man sich die Syntax von z.B. Semantic Wikis vs. Flickr Machine Tags ansieht, wird man feststellen, dass der Unterschied eher nicht markant technologisch/theoretisch ist, vielmehr ist er in der Wahl des Business-Modells auszumachen.
Soweit mein Gedankensprungbeitrag zur Semantic-Web-RDF-Tagging-Web2.0-Kudelmudel-Diskussion.
Update: Heinz Wittenbrink verweist auf einen kontextrelevanten "Web2.0 vs. bzw. with Semantic Web"-Artikel von Tassilo Pellegrini und Andreas Blumauer.
Update: It seems most RSS-Feedreaders do not display the embedded Timeline, so please visit the page itself if you want to try it out.
Hell, how I love this... ;-).
You've probably heard of SIMILE's Timeline. It is like Google Maps for time-based information. Now you might also know that certain Wikis have some Semantic Web features. I thought I'd bring them together. The result is a Wiki-SIMILE-Timeline-Mashup.
Let's look at an example. Within PhpWiki you can define Semantic Relations like here. The information defined in this Wiki Page can be used to create an XML-Feed which SIMILE Timeline can read. Have a look:
The second example takes the blog posts from this very Wiki/Blog and presents them in a timeline. You can click on the buttons to see the blog post's permalinks.
Wonderful. Think of the possibilities.
Further investigating Semantic Web features in Wikis. In this example I use PhpWiki's SemanticSearchPlugin as a simple Bug Tracker. I created some WikiPages for bugs and feature requests for a project. Within them I define things like [bug:=open], [bug:=closed] or [feature:requested]. That way I can run a SemanticSearch to find open bugs for example.
image hosted by flickr.com
Phpwiki Cargo Extension
The Cargo Extension is a set of plugins for PhpWiki. It's aim is to provide features to work with wiki-pages more like data objects. Combined with PhpWiki's user management and Semantic Web features it builds a conglomerate of application development and publishing platform.
I plan to release Cargo Extension in a month or two under an Open Source license. Currently it's used for about 5 web projects I'm working on. It includes a CMS, a blog, a Flickr and a Twitter clone and whatnot. Well, just taking my mouth full, let's see what comes out in the end. Maybe a Google Wave clone :-P. I'm sick of Google doing all the cool stuff. Let's do it ourselves and stay independent :-).
Cargo Extension is based on the following cool software/stuff:
Phpwiki does the heavy work in the backend.
Mootools for fancy Web2.0-like interface improvements.
phpthumb helps with image manipulation.
Silk Icons, fantastic Creative Commons icons.
At the moment there is not more to say. If you want to stay up to date, please subscribe to the Cargo Extension RSS Feed.
Best regards,
walterra
Kuala Lumpur, June 2009
Inspired by Robert I thought I'd write about the history of Phpwiki powering this very blog.
Why use a heavily costumized version of Phpwiki as a blogging software and not stick to its default theme or even choose one of the major players?
When I started blogging in 2001 I had my own "journal" done with static HTML. Mid of 2002 I started to experiment with Wikis, my first running implementation was called artefact. So that was some time before the rise of open source blogging giants like Wordpress.
In 2003/04 I examined some blog software. I was especially disappointed by Wordpress. Not because of its functionality, but because its code seemed to be a mess. Don't know how that looks today, but that made me stick to Phpwiki. I modified it to support Ping-Services, RSS-Feeds (Phpwiki supported RSS but not in a way I wanted it to), Comments (same here) and Tags. (And some secret text mining based SEO stuff, but that's another story). Look here for an archived version of one of its first incarnations. It still like its look. It's usage was and is quite archaic, but ok for me.
However, I wouldn't recommend it for anyone else. But still I'm convinced of the potential of wiki software as general publishing systems.
Finally, here are some links to other posts with thoughts regarding blogs and wiki.
This page was created in 12.9280929565 seconds
