Some thoughts about CPSDesignerThemes

Hello all,

You are following the commits on CPS [*], you may have noticed that
there is a lot of activity around CPSDesignerThemes:

http://www.racinet.fr/index.php?post/2009/06/10/A-new-themes-engine-for-CPS
https://svn.nuxeo.org/trac/pub/browser/CPS3/products/CPSDesignerThemes/trunk

I'm writing some notes about CPSDesignerThemes, mainly aimed to Georges,
but which might interest people here:

* The shipped themes shouldn't be in doc/sample_themes/ but in a
  "themes" directory at the root of the product. This is were people
  would expect them.

* Since the theme resolver is being worked on, I would love to have
  the theme resolver be able to deal with a theme associated to a unique
  page and not a whole directory as it is mandatory now.

  This would be more flexible than it is now. For example on the
  http://www.aful.org/ CPS portal, we have web sites being
  only one page, for example
  http://bons-constructeurs-ordinateurs.info/
  http://bons-vendeurs-ordinateurs.info/
  With the current limitation we have to create a directory (workspace)
  with a unique page in it for each of those web sites.

* Finally, it would be good if the cpsskins_export method did the
  disabling and then re-enabling of CPSDesignerThemes by itself.
  This part is not straightforward and I fear we would lose the
  administrators/developers that will try to switch from CPSSkins
  to CPSDesignerThemes


Cheers,


[*] : through the commit notifying mailing list
http://lists.nuxeo.com/mailman/listinfo/nuxeo-checkins

-- =

Marc-Aur=E8le DARCHE
AFUL http://www.aful.org/
Association Francophone des Utilisateurs de Logiciels Libres
French speaking Libre Software Users' Association
_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel