|
 |
Tuesday, March 04, 2003 |
3:01:44 PM 
|
|
2:56:27 PM
|
|
From remote
The flexible blog. Tested from another system
1:48:44 PM
|
|
a test entry using the mail to blog password
1:35:05 PM
|
|
checking radio function
11:06:25 AM
|
|
|
Wednesday, July 10, 2002 |
Communities of Blogs
Recent posts by Ugo at CocoBlog follow in the thread of adding "community features" to CocoBlog.
This subject also applies to the larger Cocoon community, IMO. The usual tools include email, email on list(s), a portal, a blog (natch), ..., open source components.
A friend of mine, Don Baccus, has been involved in openACS (Open Architecture Community System) which uses AOLserver and (among others)
Postgresql to make community portals. Dotlearn, at the Sloan School of Business of MIT is a version which currently is nearing release in a new version using the latest openACS. [dotlearn faq]
One of the nicest features of the openACS system is the forum section where discussions are organized on subject threads, rather than the micro threads of the subject headers of email messages. [openACS forums] Notice how the initial post can be followed on the same page with
comments, like a wiki.
Perhaps something like this can make it into cocoBlog? Suppose clicking
on a subject rcs feed subscribed you to a forum discussion area that
aggregated all participants entries within this subject area, much like
the "categories" for radio blogs, but categories for cummunities, rather than the individual blog?
3:38:28 PM
|
|
Quoting Ugo Cei...
Bake, Don't Fry. Aaron Swartz makes a distinction between web publishing systems that fry sites, serving them fresh to users every time, and those that bake them once and serve them up again and again. [Be Blogging]
Andreas Hartmann's Cocooncenter is prepared "baked" using cocoon, although parts of it are using perl (the forum, I think). They recently put up the sources to the site.
7:20:26 AM
|
|
|
Wednesday, June 12, 2002 |
Regarding CocoBlog the good news is that Ugo Cei put up a CVS at Sourceforge. CocoBlog CVS.
I've made minor mods to allow me to make multiple blogsites, for testing.
Not sure whether they are suitable for the main source tree.
I wonder about the dependency on xindice as a weakness. There doesn't seem to be much action on the xincice mailing list regarding new work.
5:09:07 PM
|
|
Hello there....
notice I haven't spent much time here. I found radio too buggy. What does that mean? Is there a published list of outstanding bugs, to save me from
tiresome posts to the erratic support site?
What a strange idea? That's radio.
5:00:59 PM
|
|
|
Monday, May 27, 2002 |
testing 8.08 ... does this upload?
9:19:58 PM
|
|
|
Thursday, May 09, 2002 |
Now that cocoblog is released, and my copy up on Morpheus the CocoBlog, It's time to weave the pieces a little bit more tightly.
I've been checking out the webdav interface to Jakarta/Tomcat server which holds Cocoon and Cocoblog, jgenerator. This is for deployment of images and .wav files.
JGenerator, by the way, has released version 2.0 and kept a chunk of code into a private new company. We'll see how much this retards the open source. For starters, the 2.0 source release didn't build as is
last night. the build.properties was not in the tarball. Got it from
the sourceforge cvs. It complained about servlet pieces last night, up too late. I think I need to check the classpath, maybe tools.jar?
I'll have to look back at the installation of 1.3.1.
the old jgen-devel mailing list archive has disappeared, some what ominous for the future.
11:33:13 AM
|
|
now to remember how the home page is made, with preferences.
11:22:36 AM
|
|
pushing pieces out like pumping a hand pump.
11:19:42 AM
|
|
retrieving the old changes lost when I reinstalled. Bear with me, for a bit, while I find all of the pieces.
11:05:39 AM
|
|
Cocoon and Zope, CocoBlog and Zwiki with Blogface, Radio
After reading Ugo Cei's recent comparisons of weblogs, I'm reminded to set down some notes on recent experience.
Cocoon suffers when compared to Zope, in my experience, largely in the
user interface and documentation. Getting Zope and Cocoon up and limping is roughly equivalent.
The next steps... site configuration and change, customization .... are considerably more developed in Zope and Radio. Cocoon will soon have component drop-ins, like Zope or Radio in effect... although done differently, and Cocoblog is an encouraging example of a drop-in. Most Cocoon examples are 'Hello World Handwaves'. Cocoon provides a toolkit for content management at this stage, rather than a CM application.
The Zope instance is designed from scratch to be managed from a web interface. Cocoon has little along this line and shows no sign that this is a priority, as far as I can see, following the user and developer mailing lists. Zope is like the Radio application in this respect. The textbox web interface is certainly a little clunky, but greatly augmented by template forms and configuration buttons.
It will be interesting to see how much of the cocoon community releases their in-house code back to the open source community, and how quickly. HP's announcement is certainly promising but the code is still outside of cocoon proper, afaik. If you look at the live sites cocoon page, most are not showing code for the underlying implementation which uses cocoon. The portal example is a good contribution, but enhancements are announced but unavailable until a conference presentation.
Some user oriented documentation has started to move outside of cocoon to places like cocoon Center. This seems to be following the track of zope and radio.
One index of project development is the degree of compartmentalization for users and applications available to the community of users. Cocoon shows just a user mailing list and a developer mailing list. There is no Special Interest Group structure in the community (although there are certainly working subgroups of developers).
Enough for now. I should get back to work. Just to note, I'm working more on Cocoon, even with the rough edges. These notes should not be taken as a negative response to Cocoon.
8:56:46 AM
|
|
Ugo Cei: The combination of Cocoon and Xopus is going to be really explosive [Sam Ruby]
on the other hand, it's (xopus) single browser, old version.... at the moment.
still doesn't mozilla.
still pretty awkward, even when using ie5.5, imo.
6:51:01 AM
|
|
|
Wednesday, May 08, 2002 |
silence of the blue screen of death
You'd think one could hook up an hp scanjet 4470 to an hp pavilion
laptop on usb... made by the same people, right?
usb is hot swapable, right/
not me... I just keep hot swapping the blue screen of ditto
windows protection error, if winME is nice enough to know its own error.
yuch. too late for phone support, now. blog me.
3:56:43 PM
|
|
|
Monday, May 06, 2002 |
CocoBlog 0.0.1 Released!. Announcing the first public release of CocoBlog. [Be Blogging]
Got it up in 15 minutes (I'd already been using cocoon & xindice). so it would take longer starting from scratch. This one is on a NATed win2k system so you can't see it...
using tomcat 4.04b2, jdk1.4,cocoon 2.1-dev
next on slanger.org
9:50:50 AM
|
|
© Copyright 2003 bob phillips.
|
|
|
