Forum OpenACS Q&A: Re: Is there any tutorial for xowiki?

Thank again Gustaf,
and I hope this time to be the final introductory questions .
Finally I succeed to change folder_id by using folder object...XoWiki document assum too highly educated person.
For me it was a huge obstacle to find out where & how
For clarity here I repeat my real step-in s
1. Go to admin page on any Xowiki instance
2. Locate xowiki::object and in there, identify folder object(named with numbers..)
3. Go to edit page and provide below code segment as a sample

set rich_text_spec {richtext(richtext),nospell,optional
{label Content}
{html {style {width: 100%}}}
{options {editor xinha folder_id 1618 height 350px javascript {
}}}}

set widget_specs [list *,text $rich_text_spec]
4. Publish this revision
5. Verify the changed effect with normal xowiki page (i.e. index page)- you might let your server allow IMG tag to complete test

Gustaf, here I encountered trivial but annoying trouble
On later editing for the xowiki::object, I can't see the previous page content to be modified...any advise for this?

And here is (hopefully) last query on this thread
Xowiki document describe Programmable XoWiki Pages: ::xowiki::Object
Let me ask you one more time - how can I do it?
It reveals that still I fail to catch the basic concept of xowiki, doesn't it?

I install xowiki (ver. 0.60.2) with official release of OACS 5.3.2 (upgraded from 5.3.1)
Specifically speaking, when I tried to edit folder object,
the content displays nothing though it keep working with previous scripts I entered.
The only way to check the existing content of folder object is to view it via clicking on it's name...

For the other xowiki object like CGI(instantiated from prototype) and myobj(created by me), the behavior is different. The whole content I entered wrapped with "{", "}" and "text/html"
...Ah, hard to explain, so here is my example,

{proc content {} {

return {Hello [[Wiki]]-World}

} } text/html

As a result, the "content" proc doesn't work at all as expected...(or as your document told)

The CGI & other pre-defined prototyped objects seem to work well only at first instantiation. that is once I modify the content of the instantiated object it turns out the text itself I provided.

I'm not sure how to upgrade
I'm quite novice to the method of upgrade you suggested.
Would you tell me more friendly way?

there is as well the possibility to get the code via cvs (see https://openacs.org/xowiki/Get_the_Code). how did you install xowiki on your machine?

yes, "install|upgrade from Repository" is what i suggested. The server on openacs.org builds nightly packages, called .apm files.

many things are possible with xowiki based on configuration, some of the configurations are for the end-user, some of these are rather for programmers. Your requirements (use a certain folder/filestore) were quite special, some the programmer oriented configuration was necessary (editing folder object, which is the last resort). And unfortunately, there was a bug fixed only in the head version. So i hope this is not the normal user experience.

Hopefully, future versions of xowiki will be more easy to configure.

-gustaf

Let me recap: you say

- this question has nothing to do with xowiki.
- editing the dotlrn form does not show at all with rte
- editing the form with xinha has trouble with Korean messages.

I assume, you are editing always with the client language settings of Korean. Correct?

Maybe the following can help you: xinha has its own javascript based message catalogs (currently for 33 languages, see packages/acs-templating/www/resources/xinha-nightly/lang/, there are additional catalogs for the plugins). I would recommend to add a Korean catalog named ko.js.