<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<rdf:RDF 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
   xmlns="http://purl.org/rss/1.0/"
>
   <channel rdf:about="http://developer.typolis.net/">
      <title>Developing Web Applications</title>
      <link>http://developer.typolis.net/</link>
      <description></description>
      <dc:publisher>typolis:</dc:publisher>
      <dc:creator>sam (mailto:&amp;#115;&amp;#97;&amp;#109;&amp;#64;&amp;#115;&amp;#117;&amp;#109;&amp;#97;&amp;#97;&amp;#116;&amp;#111;&amp;#46;&amp;#110;&amp;#101;&amp;#116;)</dc:creator>
      <dc:date>2008-01-18T12:27:39Z</dc:date>
      <dc:language>en</dc:language>
      <sy:updatePeriod>hourly</sy:updatePeriod>
      <sy:updateFrequency>1</sy:updateFrequency>
      <sy:updateBase>2000-01-01T00:00:00Z</sy:updateBase>
      <items>
         <rdf:Seq>
            <rdf:li rdf:resource="http://developer.typolis.net/stories/15713/" />
            <rdf:li rdf:resource="http://developer.typolis.net/stories/13078/" />
            <rdf:li rdf:resource="http://developer.typolis.net/stories/12566/" />
            <rdf:li rdf:resource="http://developer.typolis.net/stories/12133/" />
            <rdf:li rdf:resource="http://developer.typolis.net/stories/10411/" />
            <rdf:li rdf:resource="http://developer.typolis.net/stories/10375/" />
            <rdf:li rdf:resource="http://developer.typolis.net/stories/3622/" />

         </rdf:Seq>
      </items>
      <textinput rdf:resource="http://developer.typolis.net/search" />
   </channel>
   <item rdf:about="http://developer.typolis.net/stories/15713/">
      <title>Search Indexing in Rails</title> 
      <link>http://developer.typolis.net/stories/15713/</link>
      <description>With Helma, i am using the Java Lucene to implement fulltext search. In the Ruby world there is Ferret. It&apos;s nearly the same as Lucene - great!
Acts as Ferret integrates it in RoR.

For the quickest introduction:
  
a perfect slideshow  
best tutorial for acts_as_ferret  
another tutorial for acts on ferret  
introduction ferret in general


To include german stemming do this.

Some troubleshooting if this doesn&apos;t work.

This configuration worked for me:
acts_as_ferret(
{ :fields =&amp;gt; {
:fieldname1 =&amp;gt;{},
:fieldname2 =&amp;gt;{}
}
},
:analyzer =&amp;gt; GermanStemmingAnalyzer.new
)

To get informations about the current index for a Model:

&amp;gt;&amp;gt; puts [Modelname].aaf_index.to_yaml
or
&amp;gt;&amp;gt; puts [Modelname].aaf_configuration.to_yaml</description>
      <dc:publisher>typolis: Developing Web Applications</dc:publisher>
      <dc:creator>sam</dc:creator>
      <dc:subject>ruby on rails, ferret, lucene</dc:subject>
      <dc:rights>Copyright &#169; 2008 sam</dc:rights>
      <dc:date>2008-01-18T10:14:07Z</dc:date>
   </item> 
   <item rdf:about="http://developer.typolis.net/stories/13078/">
      <title>Rumours about Rhino on Rails</title> 
      <link>http://developer.typolis.net/stories/13078/</link>
      <description>It seems that some guys working at Google are using their 20% time for doing a ROR clone on Rhino. I would be interested if they know about the granddaddy of Rhino based web development framework Helma. Yeah, yeah ... in my dreams Google is pushing Rhino up the hill towards Javascript 2.0.</description>
      <dc:publisher>typolis: Developing Web Applications</dc:publisher>
      <dc:creator>sam</dc:creator>
      <dc:subject>helma, rhino, rails, javascript</dc:subject>
      <dc:rights>Copyright &#169; 2007 sam</dc:rights>
      <dc:date>2007-06-28T05:26:15Z</dc:date>
   </item> 
   <item rdf:about="http://developer.typolis.net/stories/12566/">
      <title>Jala is great!</title> 
      <link>http://developer.typolis.net/stories/12566/</link>
      <description>The Helma guys really did a good job with this collection of modules. I am using the form, l18n and rss2.0 module as well as the hopobject extension at the moment.  It&apos;s all very well documented and together with the db prototyping functionality of   rocket, it&apos;s a breeze to create  the basic input/output and modelling.</description>
      <dc:publisher>typolis: Developing Web Applications</dc:publisher>
      <dc:creator>sam</dc:creator>
      <dc:subject>helma, prototyping, jala, development</dc:subject>
      <dc:rights>Copyright &#169; 2007 sam</dc:rights>
      <dc:date>2007-05-27T08:53:30Z</dc:date>
   </item> 
   <item rdf:about="http://developer.typolis.net/stories/12133/">
      <title>Rocket the Super Rabbit</title> 
      <link>http://developer.typolis.net/stories/12133/</link>
      <description>Helma development boosted with an integrated prototyping approach.

Some time ago, I thought about adding more meta data to the type.properties, to have a kind of typing for Hop-Object properties. A few weeks ago, I stumbled over Rabbit. A nifty implementation of some prototyping functionality. Rabbit is great to build up your Helma App from scratch. But there are a few things I missed in Rabbit:
  
A kind of database abstraction (MySql support in specific) 
  
More ellaborated form generation  
Input validation (serverside as well as clientside)  
Allow to build the central &quot;Model&quot; from different sources (Database, Existing-Sourcecode, JS-Object). Specifically: Use type.properties as a model definition


I also wanted an approach to blend more with the further development process or even existing applications. The idea is to have a prototyping engine, that delivers core functionality for Web-Frameworks while letting the user overwrite/replace/extend this functionality in later development stages. So I took the Rabbit-Code as a base but changed most parts to my need.

Here is a first &quot;alpha&quot; to be discussed/continued. Just try the sample application and see the code for further insights.

rocket source v.0.1 (1, 32 KB)

Features
  
Metadata for Hop Object prototypes  
Automatic form/input generation  
DB/Table generation (MySql)  
Creation of the model from existing source  
Creation of folders/type.properties from the model  
Basic permission management/access control  
Basic List / Object viewer
</description>
      <dc:publisher>typolis: Developing Web Applications</dc:publisher>
      <dc:creator>sam</dc:creator>
      <dc:subject>helma, prototyping, rocket, rabbit, download</dc:subject>
      <dc:rights>Copyright &#169; 2007 sam</dc:rights>
      <dc:date>2007-04-29T08:46:16Z</dc:date>
   </item> 
   <item rdf:about="http://developer.typolis.net/stories/10411/">
      <title>Great XML-RPC Client</title> 
      <link>http://developer.typolis.net/stories/10411/</link>
      <description>helps you testing your API...


Cocoa XML-RPC Client 



technorati tags:macosx, tools, xmlrpc</description>
      <dc:publisher>typolis: Developing Web Applications</dc:publisher>
      <dc:creator>sam</dc:creator>
      
      <dc:rights>Copyright &#169; 2007 sam</dc:rights>
      <dc:date>2007-01-18T17:00:42Z</dc:date>
   </item> 
   <item rdf:about="http://developer.typolis.net/stories/10375/">
      <title>Looking for a CMS</title> 
      <link>http://developer.typolis.net/stories/10375/</link>
      <description>I&apos;m working wih Helma since a year. Despite all annoyances, I don&apos;t want to switch back to PHP for my ongoing projects. But what to do for clients, having their websites hosted by a standard provider? I took the chance to look for new CMS Systems that may favour my needs for small/middle projects. It should be reduced to the maximum and best usability for editors/managers but flexible to extend and with a good API. To my surprise, I found some fresh projects that looks really interesting.
  
CMS Made Simple was the first candidate. The design is a little rough, but the backend structure was a charme. I think, I would have given it a try, but then I discovered ModXCMS...   
ModXCms seems to be what I need. The backend structure isn&apos;t my favour at first sight. But it seems that this piece of code is also usable as an Aplication Framework. After all what I&apos;ve read on Ajaxian I will give it a try and share my experience here.
</description>
      <dc:publisher>typolis: Developing Web Applications</dc:publisher>
      <dc:creator>sam</dc:creator>
      <dc:subject>cms, php, modx</dc:subject>
      <dc:rights>Copyright &#169; 2007 sam</dc:rights>
      <dc:date>2007-01-16T15:23:08Z</dc:date>
   </item> 
   <item rdf:about="http://developer.typolis.net/stories/3622/">
      <title>Urlpaths of collections with special chars</title> 
      <link>http://developer.typolis.net/stories/3622/</link>
      <description>Helma automatically builds nice urlpaths for object collections. In most cases this works fine, but if you want to use &quot;:&quot; or &quot;@&quot; in the accessname of the object, the pathes becomes messed up. &quot;:&quot; is then escaped to &quot;%3A&quot; and &quot;@&quot; is ecaped to &quot;%40&quot;.</description>
      <dc:publisher>typolis: Developing Web Applications</dc:publisher>
      <dc:creator>sam</dc:creator>
      <dc:subject>helma, mapping, nice url&apos;s</dc:subject>
      <dc:rights>Copyright &#169; 2006 sam</dc:rights>
      <dc:date>2006-05-22T14:27:46Z</dc:date>
   </item> 

   <textinput rdf:about="http://developer.typolis.net/search">
      <title>find</title>
      <description>Search this site:</description>
      <name>q</name>
      <link>http://developer.typolis.net/search</link>
   </textinput>
</rdf:RDF>
