Forum OpenACS Development: Wimpy Point Package!

Hi all!

I'll be working on the WP package, Samir also offered his help in some issues, and after discussing with different people (Samir Joshi, Carl Blesius, Jeff Davis and Don Baccus) here is a condensed to-do list that I concluded after talking with all of them.

• Enabling collaboration for creating presentations (also adding comments?)
• Remove all the wp specific content types and just relating basic content types and having a container types of wp presentation and wp slide. What others think? suggested by Jeff, I agree with him
• Scalability issues! I'll do a similar test like Jeff did for testing the scalability for forums and work around with some serious problems there.
• Export / import of slides (ready in pg, needs to be ported to oracle)
• WP accesibility, a way to access everything is just one single place (between multiple instances), maybe just for dotLRN (portlet issue?)
• Presentation sharing, have the same presentation for multiple classes in the case of dotLRN
• Permissions checking in all the UI.
• Internationalization
• Adding some standard presentations templates by default, and a way to create more ( I remember that the WP on ACES had that )
• Automatic slide presentation (giving N seconds for each slide and then change to the next one)

Some minor issues like:

• Differentiation between versions and corrections, Samir pointed out that couldn't be necessary to have a new revision for just typo corrections.
• Adding more bullets to slides (up to 3 per edition instead of just one like know)
  

Well, I hope some of you can also put your ideas or comments here, thanks for your feedback!.

that should be tDOM not tclDOM as tclDOM is a tcl implementation of DOM and not to be confused with tDOM, a C implementation. tDOM is scheduled to replace ns_xml in 4.7.

/Bart

Rocael has fixed this problem and should be posting a new version of Wimpy Point shortly. I have been testing the newest beta (about 3 days old) and it is possible to add three new bullet items at a time. Rocael uploaded a patch if you can't wait a couple of days for the updated version.

Carl

I was going to say the upgrade script doesn't work, but I can't say that definitively because I didn't do things in the right order. Here's what I did:

• found the upgrade script
• ran it
• it did run without errors or warnings
• I -thought- I was done (turns out this was wrong) so I tried it, and it failed
• hmm, what to do? I guess I'll drop wp-slim data model and redo it (so: I gave no chance to the upgrade script)
• tried it, -still- no go. sheesh! what could this be?
• happened by the package manager... Bingo! there's a reload link! I reloaded, and thought different of it, so dropped data model, reloaded, restarted server.
• made a new presentation, this time everything worked. Again, nice work.

So, instead of saying, I only have one instance of WimpyPoint mounted at /wp, we mount the content aggregation package for WimpyPoint and it retrieves all the content from the mounted WP packages at /subsite1/wp, /subsite2/wp aso. asf.

As a further step, if we provide good DTD's for the packages, we could even aggregate content across various OpenACS instances (e.g. OpenACS.org could dynamically import the WPs that Lars creates over at collaboraid.biz).

If there is interest I would flesh this out a little bit more, but if you say this is not worth the effort, fine as well ....

This sounds really good, a general purpouse content agregation service, but more even when we talk about having it working with multiple sites.

I'm really interested on it, please extend your thoughts more.