Forum .LRN Q&A: Re: dotlrn-xowiki and xowiki-portlet available

Collapse
2: Re: dotlrn-xowiki and xowiki-portlet available (response to 1)
Posted by Malte Sussdorff on 01/29/07 08:51 AM
This sounds good and will be helpful for .LRN to get rid of static portlets. Finally :).

Here are some comments though:

a) Providing the URL via APM is great, if the install from URL process would work 😊. At least on my Ubuntu it failed miserably, so I had to download the APM in the /packages directory and untar it manually

b) When I add the page (selecting on from the drop down box), this is what happens:

Error:

No page 'admin/portal-element-add' available.

From the URL:

/dotlrn/clubs/technics/xowiki/admin/portal-element-add

I found out why: You added the page to xowiki, but did not increase the version and the dependency, so I had to first update XoWIKI in CVS :).

Now this works, but I wonder if there is a parameter to NOT display the editing links (or search aso.) in the portlet itself. Not sure if you want to have them in a portlet. And if you do, it would make more sense to have an edit button in the portlets header.

Last but not least, will you commit it to CVS ?

Collapse
3: Re: dotlrn-xowiki and xowiki-portlet available (response to 2)
Posted by Gustaf Neumann on 01/29/07 09:36 AM
... 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.
Collapse
4: Re: dotlrn-xowiki and xowiki-portlet available (response to 3)
Posted by Jose Pablo Escobedo Del Cid on 01/29/07 11:58 AM
That's great news! thanks Gustaf. I had already implemented a quick "integration" of xowiki and .LRN with the static portlet with a link to a xowiki instance solution. But this is much better :)

Just one comment/bug: the content of the portlet doesn't fit in correctly.

Regards,

Jose Pablo

Collapse
5: Re: dotlrn-xowiki and xowiki-portlet available (response to 4)
Posted by Gustaf Neumann on 01/29/07 12:14 PM
Just one comment/bug: the content of the portlet doesn't fit in correctly.
are you talking about the default index page?
This seems to be a css problem which does not like to see
a "portlet-title" or "portal" css class within another "portal".

if this is the problem, edit the index page and add "-decoration plain" to the includelets (between the double curly braces, without the quotes) to see the effect.

Try to write a text page, it should fit nicely.