[Plone-UI] PLIP 12227: In-Plone Theme Editor

Elaine elaine at ssc.ucla.edu
Tue Jun 26 20:27:07 UTC 2012

My suggestion, and this is only my opinion, as stated in the recommendations,
would be #2. Make the differences in interfaces patently obvious to the end
user. Right now, these two interfaces *look **identical* but they *function*
very *differently*. The normal response to this interface (and any
interface) is if it looks the same it should function the same, likewise, if
two interfaces look different that is a visual cue to the user that they are
inherently different. Otherwise, one assumes they are they *same interface*
and frustration ensues.


Martin Aspeli wrote
> Ok, I think this is quite simple:
> You can't edit files on the filesystem through Plone (this is a
> security thing, and probably not something we ever want to support,
> even if it may be technically possible).
> So, with a filesystem theme (in a Python package or from the
> resources/theme/* directory in a buildout) you can't see the file
> manager and you the theme mapper operates in readonly mode.
> This may be useful if you are building the theme on the filesystem and
> want to use the rule builder and highlighter to figure out what rules
> to use, but you can't actually modify anything.
> It is also currently the only way you get a preview without applying
> the theme (although that'll change soon).
> I appreciate this probably isn't obvious. :) Suggestions?

View this message in context: http://plone.293351.n2.nabble.com/PLIP-12227-In-Plone-Theme-Editor-tp7347100p7556512.html
Sent from the User Interface & Design mailing list archive at Nabble.com.

More information about the UI mailing list