The follow notes are ideas, suggestions, and feature requests.
Almost everything that's part of a Sosua page object can be described in normal HTML page. The page edit merely allows you to re-use elements and provide some editing structure. However, it can clutter up the collections of the Resource tool. One could consider a "Page Compiler" which takes a page layout description and renders it into a fixed HTML file.
Group sequences into modules with metadata. Structures might be analogous to book/chapter/section/page, or other organizations.
Use data from tables, spreadsheets, etc. and plot with SVG. The OpenCSV page is Apache 2.0 licensed and is very simple to use. It's a great way to get tabular data into Sousa. Initially, editing would only add or swap CSV (or TAB) files. Later, we could add a customized editor for table data editing. Plots and graphics are a matter of specifying which rows (or columns) to use as data, and then plot it using SVG.
Given that FCKEdit and TinyMCE are extensible WYSISWYG editor components, it should be possible to add an extension that allows Sousa objects to be embedded in a free-form, marked-up text element.
The file types that we wanted to be able to display were Word Documents and PDFs.
Matt Mize, Systems Administrator Matt.Mize@notes.udayton.edu (937) 229-1024 UDit Department, University of Dayton 300 College Park, Dayton, OH, 45469-1302
What I'd like to be able to do is to use the Wiki as much as possible as a tool for hosting course modules. I'm doing this already with some success this semester (each course module is a page which contains links to content, discussion, and to the occasional quiz) but what I'd really like to do is to present links to course modules in a table (maybe even with folder icons) as per the attached screen shot. The default wiki table doesn't appear to do this felicitously 'cuz (as per Michal's question that sparked this thread) a yellow row appears across the top of the table. Is there a way to remove the yellow row? And are there any examples out there in the wild of other instructors who've leveraged the wiki this way?
More from Peter Knoop
You might also consider broadening you're scope here beyond just the wiki's use in these types of approaches. I suspect I'm not the only one who uses their favourite HTML editor (e.g. FrontPage, Dreamweaver) to create pages in Resources, and organize their course and content in a similar way as to what I think you're describing with the wiki. (With
the current state of WebDAV its not always possible to work directly from such applications with Sakai, but there are relatively easy ways around that.)
Such content in Resources can be placed behind Web Content tools, used as the content for the Site Info tool on the Home page (generally with the synoptic tools removed) to provide a roadmap of links to other content in the site, easily linked to from Schedule items, Announcements, etc. You can also link such pages together, so that you can build up a scaffolding, similar to the wiki approach that provides that structure built-in. You can also do things like create a page containing a reading (which might have some interactive flash illustrations on it too) and a link to some self-test questions at the end, rather than expecting the student to read a document in Resources and then navigating with the toolbar to the right place in Samigo or Mneme to do the self-test. (Now that relies on the URL accessibility of items in those tools, which Sakai is working towards supporting in more tools; I mostly still use our U-M legacy system here, as I don't have time to convert the content.) You can attach that Resource to the lecture it goes with in the Schedule tool too – if you're one to create a schedule event for each of your class sessions – allowing a student an alternative "entry" to your course at the appropriate point from their Schedule in their My Workspace. They can still go to it via Resources too and find the Week 7 folder with their reading, or click on
the Week 7 Web Content tool, and so on... It certainly takes a bit of effort, but there is flexibility in Sakai that let's you already begin to explore the usefulness of some alternative approaches to organizing your content and guiding your students' navigation of it.
Now that I have support for parameters on media objects (heigh, width, etc.), there are properties that could be associated with a whole Sousa page. These might include: