... get rid of static portlets
that was not the intention
... install from URL process would work 😊. At least on my Ubuntu it failed miserably
What is "install from url"? most likely, this requires manifest.xml etc. yes, it has to be installed "manually", by untaring the apm file in the package directory for now.
You added the page to xowiki, but did not increase the version and the dependency ... so I had to first update XoWIKI in ...
i did increas the version number and provided the dependency. the new version (since 9h) is xowiki 0.44, the dependency for this version is in xowiki-portlet.info.
... I wonder if there is a parameter to NOT display the editing links (or search aso.)
Well the idea of the wiki is to let people edit the contents (if they have the permissions). Also index etc. makes sense IMHO to get access to the full wiki.
Concerning parameters: for portal elements, there are the portal_element_parameters (which seem to have no user-friendly interface). in general, with portal_element_parameters it is possible with little work to specify per portal element different the xowiki templates.
for now, change e.g. in xowiki-portlet/www/xowiki-portlet.adp "view-links" to "view-plain" to get rid of the links.... or roll your own template.
Last but not least, will you commit it to CVS ?
if there is enough interest, why not.
