<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0">
<channel>
  <title>plog blog</title>
  <link>xir.cccp.at</link>
  <description>plog it's own weblog</description>
  <language>de-de, en-us</language>
  <copyright>&amp;copy; xir.cccp.at // under GPL</copyright>
  <lastBuildDate>2004-12-31 11:09</lastBuildDate>
  <category>just a private weblog in rdf/xml</category>
  <generator>done on vi ;-)</generator>
  <ttl>30</ttl>
<!--
  <item>
	  <title>renamed to ctrbx</title>
		<pubDate>15.11.2005</pubDate>
		<publish>0</publish>
		<author>xir</author>
		<unixname>ctrbx</unixname>
		<description>
		  it's not the best i know, but i decided to
			rename plog into ctrbx.
		</description>
		<content>
		  it stands for something like [i]controled by
			xml[/i]. i searched around for a little
			while, but i did n't found any better name.
			it's still not done. so if anyone finds a
			better one, i would realy love to hera
			about.
		</content>
	</item>
-->


  <item>
	  <title>vim integration for xml-editing</title>
		<pubDate>14.11.2005</pubDate>
		<publish>1</publish>
		<author>xir</author>
		<unixname>vimxml</unixname>
		<description>
		  a little vim-plugin for better editing xml-files.
		</description>
		<content>
		  i found a little xml plugin. it closes xml-tags automatically and 
			does some other useful stuff on xml editing. actually i wanted a 
			realy xml-editor like mutt's vi integration. there is nothing around. 
			i try to do such a thingy with perls ncurses interface. but this 
			will take a little while and could be
			the next step of this software. 
			[br][br]
			so for first you find under /plog/plugins/vim/ftplugin/xml.vim a 
			plugin for your personal vim. you need to copy the vim/ 
			directory to user userhome and
			rename it as .vim. vim is searching for this directory and 
			initialises the plugin automatically. you find help for this stuff on 
			[url=http://www.vim.org/scripts/script.php?script_id=301]www.vim.org[/url].
		</content>
	</item>



	<item>
	  <title>plog needs an other name</title>
		<pubDate>14.11.2005</pubDate>
		<publish>1</publish>
		<author>xir</author>
		<unixname>newname</unixname>
		<description>
		  plog needs an other name. there is allready a system under this label
		</description>
		<content>
		  uups, i found a thingy called plog on [url=http://sf.net/projects/plog/]sf.net[/url]. 
			it's a blog-system too using php and mysql as backend. hmmm, i think plog should get 
			an other name. if you have any ideas feel free to tell me. my first proposal was 
			something like [i]plogit[/i] but it seems a little boring. how ever, let me know if you
			find the right name for inappropriate software.
		</content>
	</item>	


  <item>
	  <title>plog creates plain html-pages in the filesystem</title>
		<pubDate>14.11.2005</pubDate>
		<publish>1</publish>
		<author>xir</author>
		<unixname>createhtml</unixname>
		<description>
		  horrible performance problems ... 
		</description>	
		<content>
		  plog does not create pages on the fly anymore. it was not possible on the
			server-engines i wrote it for. daemon.nethack.at needed around 30 seconds to create
			the pages. the current version creates html-content using the template engine in the
			memory and writes them directly to the filesystem. the plog engine itself resides
			under plog/engine/plog.pl now, the xml-content under plog/content/. the system writes
			the html-files to /plog/ where your webserver should point to.
		</content>	
	</item>



  <item>
	  <title>performance problems</title>
		<pubDate>13.11.2005</pubDate>
		<publish>1</publish>
		<author>xir</author>
		<unixname>performance</unixname>
		<description>
      because of performance reasons it's not realy useful to create the pages on the fly. 
			so the next big step is a caching system for plain-html files.
		</description>
		<content>
      i did a cupple of tests with [b]plog[/b] on daemon.nethack.at. it's still realy to much for this box. 
			the new idea is to parse the xml-content files and create/write html-files directly in the filesystems.
			the whole perl engine is then just needed for recreating the pages. it will be called
			from shell, and rewrite or create all html-files. webvisitors then just call
			html-files without any logical part.
		</content>
	</item>	



	<item>
	  <title>plog is born // a xml-based perl blogger</title>
		<pubDate>13.11.2005</pubDate>
		<author>xir</author>
		<publish>1</publish>
		<unixname>plog</unixname>
		<description>
		  this is plog version 0.1. it's designed for older server-engines. it run's without any database-backend
			or webscripting. it just needs perl and a cupple of modules for perl.
			all contents are written directly in xml/rss files. the files can be used for 
			the weboutput itself and/or as rss-feeds.
		</description>
		<content>

		  [h3]needed perl modules[/h3]
      [pre]
      XML::RSS;             # perl rss-parser
      XML::Parser;          # perl xml-parser
      HTML::Template;       # perl html-templates
      CGI qw(:all);         # use as cgi for weboutput
      POSIX;                # posix setting
      [/pre]

      ok, i need to say, that it is totaly useless to create this software. there are allready
			tons of blogging systems. most of them use databases to store contents.
			it's designed especially for older but very lovely servers like 
			[url=http://daemon.nethack.at]daemon.nethack.at[/url] 
			and because the author loves to play around ...
			[br][br]
			since daemon.nethack.at is a shell-server, and most of the people are able to use vi or at least
			mc for editing contents, i didn't build any interface for creating and editing xml-content. 
			please take care to write well-formed xml. on any parse 
			errors plog will cryout and warn you. contents are not displayed in this case. 
      [br][br]
			all html stuff is created with perls template-engine. 
			in this way we have a strictly segregation of content, logic and layout.
			you get help for all template-commands using "perldoc HTML::Template" from shell.
		</content>
	</item>	
  </channel>
</rss>
