<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>What Language is WikiDot written in?</title>
		<link>http://community.wikidot.com/forum/t-1109/what-language-is-wikidot-written-in</link>
		<description>Posts in the discussion thread &quot;What Language is WikiDot written in?&quot;</description>
				<copyright></copyright>
		<lastBuildDate></lastBuildDate>
		
					<item>
				<guid>http://community.wikidot.com/forum/t-1109#post-2353</guid>
				<title>Re: What Language is WikiDot written in?</title>
				<link>http://community.wikidot.com/forum/t-1109/what-language-is-wikidot-written-in#post-2353</link>
				<description></description>
				<pubDate>Fri, 03 Nov 2006 00:51:26 +0000</pubDate>
				<wikidot:authorName>ubivis</wikidot:authorName>				<wikidot:authorUserId>2528</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p> That's quite the list of software being used. I can't wait to dive in and take a look. I have worked with the equivalents of most of that software in Java and .NET so this more learning about more php and how you've put all the pieces together. </p>
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://community.wikidot.com/forum/t-1109#post-2289</guid>
				<title>Re: What Language is WikiDot written in?</title>
				<link>http://community.wikidot.com/forum/t-1109/what-language-is-wikidot-written-in#post-2289</link>
				<description></description>
				<pubDate>Wed, 01 Nov 2006 18:48:51 +0000</pubDate>
				<wikidot:authorName>michal frackowiak</wikidot:authorName>				<wikidot:authorUserId>1</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p> Yes, it is written in PHP (5) and the (not-complete) list of software used is here:<br /> <a href="http://www.wikidot.com/about:open-source">http://www.wikidot.com/about:open-source</a> </p> <p> I agree that the docs will be critical. I also think that it will be great to fully document how to write extensions (modules) which is now very easy. I will also have to work more on plugin architecture and move as much as possible into the external modules before releasing the code. </p> <p> Since the documentation will be also hosted in a wiki, I hope it will become more and more complete. I will do my best to write it and make the architecture as clean as possible. </p> <p> Before I put my 80% time on working with the o-s code I would like however to complete (or at least make usable) one more goal: wysiwyg editor. I hope I will push it quite far in a month and start working on the o-s edition seriously. </p> <p> IMHO wysiwyg, although not required by most power-users, is a big plus for any wiki out there and shortens the learning curve of any tool. I should post an interactive demo in 2 weeks and you will see what I mean ;-) It will be nothing like any of existing wysiwygs for wikis ;-) </p>
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://community.wikidot.com/forum/t-1109#post-2287</guid>
				<title>What Language is WikiDot written in?</title>
				<link>http://community.wikidot.com/forum/t-1109/what-language-is-wikidot-written-in#post-2287</link>
				<description></description>
				<pubDate>Wed, 01 Nov 2006 18:26:53 +0000</pubDate>
				<wikidot:authorName>ubivis</wikidot:authorName>				<wikidot:authorUserId>2528</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p> I assume it's probably written in Php, but I hate to make assumptions. I know you have plans to release an open source version of the project and I'd like to get involved as soon as the project becomes public. If it's php I'll have to brush up my skills, and my thoughts were to start by perhaps documenting the architecture as I come to understand it. Michal, you will obviously have to correct the document to clarify anything I may have misunderstood, but in this way you will avoid having to answer the same questions over and over. That way, before I or anyone out there starts messing with your code we'll have a general overview of what pieces do what and you won't have to reject changes as often because people are "hacking" in features. </p> <p> What do you think? </p>
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>