Forum OpenACS CMS: Second meeting minutes

1: Second meeting minutes

Posted by Mark Aufflick on 07/30/03 06:51 AM

The minutes of the 2nd meeting are up at:

https://openacs.org/projects/openacs/packages/cms-future/meeting-2-minutes

I am happy with the results, but we only got half way through the agenda - shall we say the same place/time next week?

2: Re: Second meeting minutes (response to 1)

Posted by Jun Yamog on 07/30/03 12:09 PM

Hi Mark,

This week is fine for me. Since our point is to continue discussion, the earlier the better. Anyway you are lead on this UI thing. You call the 3rd meeting. Hope I wake up on time this time :)

3: Re: Second meeting minutes (response to 1)

Posted by tammy m on 07/31/03 05:25 PM

Can I ask about 2 of the decisions from the 2nd meeting on the UI?

For HTML file uploads, Specifically, we will ignore any css stylesheets linked or contained in the file. Won't this produce results that the document-submitter is not expecting? Like loss of all their pretty formatting.

And Every save creates a new revision. Is this just the default UI action? Could there not be an option to specify whether a new revision is created or not? At least at some level if not per individual document?

Thanks for getting the CMS UI project going guys, it sounds great and I know I'll be using it:)

4: Re: Second meeting minutes (response to 1)

Posted by Jun Yamog on 07/31/03 09:17 PM

Hi Tammy,

I can't really answer the 1st question, since I don't know much about it.

For the revisions. The real problem is not the data model scalability but more of a UI scalability. After much debate on it (see chat logs). We have decided that it was more simple to put one button. That is "Save" which makes a new revision. Rather than "Save" (no new version) and "Commit" (new version).

Anyway Mark and Carl is leading the CMS UI, they should shed more light into this. I am not fiddling too much as the revision decision has very little to do with the backend involved.

5: Re: Second meeting minutes (response to 1)

Posted by Carl Robert Blesius on 08/01/03 05:31 PM

About point 1: Tammy, we did not really get a chance to talk much about css during the meeting. I disagree with what is in the feature list (about stripping out css styles in files). It is very important that we allow a user to over ride styles and add their own. It is a way we can allow an enduser access to the layout of a page without giving him direct access to templates.

A recent example: I would have put the mockups I have been working on on the openacs site if I could have added and/or overridden styles.

Looking at http://www.csszengarden.com/ it is clear how far we could go if we figure out a good way to manage user contributed styes.

6: Re: Second meeting minutes (response to 5)

Posted by Carl Robert Blesius on 08/01/03 05:48 PM

Just so it is clear: those mockups are based on work Lars started on acs-subsite as well as features already present in the CMS we already have. The work Lars did heavily relies on style sheets so configuration of the CMS UI should just be a question of associating various style sheets to site templates based on user preferences:
http://blesius.org/projects/openacs/acs-subsite/admin/appearance.html