<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
<title></title>
</head>
<body>
<span>Dear all<br />
<br />
I would like to use a Pier wiki as a Seaside component as Lukas
Renggli suggested in<br />
<br />
http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-October/131787.html</span><br />
<br />
<pre>
> <em>
I suggest that you use Pier. I do that for many of my projects. Pier<br />
</em>> <em>
can be easily embedded into any application, as well as you can embed<br />
</em>> <em>
any application into Pier. For simple wikis it might be a bit overkill<br />
</em>> <em>
to have to load the whole code-base that is more a CMS, so it would<br />
</em>> <em>
probably be worthwhile to have a simple Seaside component that just<br />
</em>> <em>
reuses the document model.<br />
<br />
</em><span style="font-size: 80%">
The code I would like to use (Pseudo class and method names)</span>:<br />
<br />
<br />
<span style="font-family: courier new,courier; font-size: 80%">
myModel := PierStructure on: (AFileDirectory on: 'S:\wikiDirectoryWithACollectionOfTextFilesInWikiSyntax'.<br />
<br />
myPierComponent := PierSubclassOfWAComponent on: myModel.</span><br />
<br />
<br />
<span style="font-size: 80%">
May I ask for help replacing this pseudo-code with actual code which does the job.<br />
<br />
In addition I would like to have as well<br />
</span><br />
<br />
myModel exportContentAsTextFileInWikiSyntaxToDirectory: aDirectorySpecification<br />
myModel exportContentAsStaticHTMLToDirectory: anotherDirectorySpecification<br />
<br />
<br />
and to create the model in the first place<br />
<br />
<span style="font-family: courier new,courier; font-size: 80%">
myModel := PierStructure on: (AFileDirectory on: 'S:\wikiDirectoryWithACollectionOfStaticHTMLfiles'.</span><br />
<br />
<br />
Thank you in advance for all hints and contributions<br />
<br />
<br />
Hannes Hirzel<br />
<br />
<br />
P.S. I have installed Pier-Seaside version 1.0.16.272 (it is the latest version available in the Squeak 3.10.2 "Universe" repository as of today).<br />
<br />
Utilities classCategoriesStartingWith: 'Pier'<br />
<br />
gives<br />
<br />
#(#'Pier-Model-Core' #'Pier-Model-Magritte' #'Pier-Model-Kernel' #'Pier-Model-Persistence' #'Pier-Model-Structure' #'Pier-Model-Command' #'Pier-Model-Document' #'Pier-Model-Exception' #'Pier-Model-Visitor' #'Pier-Model-Utilities' #'Pier-Seaside-Core' #'Pier-Seaside-Libraries' #'Pier-Seaside-Magritte' #'Pier-Seaside-Model' #'Pier-Seaside-View' #'Pier-Seaside-Widgets' #'Pier-Seaside-Visitors')<br />
<br />
<br />
For me it is not easy to find the entry points. Pier-Seaside-Model for example seems to be a good candiate for creating a model. However there are only two classes there: PRComponent and PRSettingsCommand. The first one has no class documentation at all and the second one only a terse comment. So this seems to be a dead end.<br />
<br />
Then there is the class category Pier-Model-Document whith quite a number of classes: On particular class jumps into the eye: PierDocument. The documentation says 'I am the root of a document composite.' On the class side there are no examples. However browsing the class references leradis to<br />
<br />
PRpage>>defaultDocument<br />
<br />
with the code<br />
<br />
defaultDocument<br />
^ super defaultDocument<br />
add: (PRParagraph new<br />
add: (PRText content: 'Edit this page ...');<br />
yourself);<br />
yourself<br />
<br />
A possible useful track .......<br />
<br />
<br />
<br />
<br />
P.S.2<br />
I have loaded Pier 1.0.16 through the Squea 3.10.2 package "Universe". I am ready to update to 1.0.17 as it was announced on<br />
http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-September/131633.html<br />
How is this easily possible (as it is not yet in the Universe?)<br />
<br />
</pre>
<br />
</body>
</html>