Page Comparison

...

Some control parameters would be useful including: table width, first row as headers, and first column as headers.

Aug. 8, 2008 (8/8/8!)

Had a discussion with Antranig on HTML vs XHTML to support MathML in FireFox. He indicates that this differences is likely to be in the response header some where.

Aug. 11, 2008

Downloaded and installed the current Sakai trunk, currently headed towards a 2.6.0 release with code freeze at the end of Sept. 2008. This code uses the new K1 kernel, which means that several maven changes are needed. The two biggest changes are:

1. The version of the maven base refers to the next release of Sakai now.
2. Dependencies on several framework services are now merged into a few kernel dependencies.

Versioning:

  <parent>
    <artifactId>calendar-base</artifactId>
    <groupId>org.sakaiproject</groupId>
    <version>2.6.0RC1-SNAPSHOT</version>
    <relativePath>../../pom.xml</relativePath>
  </parent>

The following services are now bundled into the kernel build:

• alias/
• authz/
• cluster/
• component/
• content/
• db/
• email/
• entity/
• event/
• exception/
• i18n/
• id/
• javax/
• jcr/
• log/
• memory/
• site/
• springframework/
• thread_local/
• time/
• tool/
• user/
• util/
• webapp/

Converted all POMs to use use K1 dependencies.
Superficial test of both Sousa Page and Sequencer both seem to work.

Created a branch for 2.5.x sousa by copying the current trunk before checking in 2.6.0 changes.

Aug. 19, 2008

Was giving some thought to external registration of media types in Sousa. The ContentElementHandler object handles type registration (actually using two methods). It was fairly simple to add a method to add a new handler:

	/*
	 *	Add a new content handler to the list of supported types.  This method is intended to support
	 *	external registration of content handlers.  Types built into Sousa should be intialized in the
	 *	ContentElementHandler constructor above.
	 */
	public void addHandler (String type, String extension, String name, CEBase handler) {
		this.types.add (new MediaType(type, extension, name, handler));
	}

The question is, how does this method get invoked outside of a Sousa tool? I could set up ContentElementHandler such at it is a Sakai component, registered with the ComponentManager, but some piece of code would still have to fetch it and call the addHandler method. I suspect the answer is Spring. If I create a singleton handler based on CEBase and register it with Spring, it should be initialized at start up time. In the init() method, I can call ContentElementHandler.addHandler(), if it's available.

Check this change in as rev. 52188.

Sept. 4,2008

The Sakai Authoring Tool work group asked me to make a canned demo of Sousa. See Sousa Walk Throughs. I downloaded a (free) copy of CamStudio and made four video captures: overview, media objects, create page, and create sequence. The AVI files produced were large, so I converted them to Flash videos. These are more compressed, but the quality seems poor (at least in FireFox).

There was a bug in generating the HTML files for accessing the flash video. The height field was off in the EMBED tag. I corrected these manually. Values for the OBJECT tags were correct.