Re: tinymce settings per user/group?

> >>> currently p.a.widgets doesn't ship with tinymce widget. reason: there are
> >>> few rough edges and it was better to release without it and continue
> >>> working on next version where tinymce is going to be included.
> >>>
> >>> that said it would be awesome to get some help to push final work on
> >>> tinymce to be finished asap (once this is done new release is going to be
> >>> cut) and you could already benefit work of plone 5 widgets by using
> >>> plone.app.widgets in your 4.3 plone.
> >>
> >> So then plan is keep the settings in portal_tinymce for a 4.3 compatible
> >> release?
> >>
> >
> > no. setting will be pulled from p.a.registry.
>
> In Plone 4.3 the tinymce settings aren't stored in the p.a.registry so if you
> plan to make a version compatible with plone 4.3 then I'm confused. You are
> going to do an upgrade step? and then have a control panel that no longer
> works since it writes to portal_tinymce?
>

ofcourse upgrade step is planned, but at later point. it is not nr.1 priority,
having useable tinymce is. i'm actually not 100% sure we'll have time (read:
enough time and manpower) to actually provide upgrade step with plone 4.3, but
its going to be there for plone 5.

there is always an option to use previous version of tinymce which reads from
portal_tinymce.


> > whole tinymce configuration is a dictionary. it think easiest would be to:
> >
> > 1. default configuration will be in "pattern.tinymce" record which is
> >    a dictionary
> >
> > 2. in your custom project or addon you point to user/group/role specific
> >    record. eg. "role.pattern.tinymce.Administrator" (or whatever record
> >    name you prefer) which will also return a dictionary.
>
> I'm talking about core plone5, not a custom project or addon. I'm talking
> about to go into site setup > groups, pick a group and edit tinymce settings
> for that group or user.  or perhaps go to site setup > tinymce > customise
> settings for group or user > pick a group or user etc.
>

i'm -1 one then. we can provide hooks that this is possible in your custom
addons/projects, but i would avoid it having it in core.

my thumb rule for this is: if i wouldn't use it in 95% of projects, which
i wouldn't since current way is good enough, then lets keep it out of core. but
add hooks so this custom things can be done outside plone's core. keeping core
clean should be nr.1 priority.


> > 3. you merge both dictionaries where configuration from 2. will take
> >    precedence.
> >
> > all we need to provide is for you to do have this point where you can hook
> > and manipulate your configuration. also same customization can be applied
> > to any other pattern.
>
> yep, that would be a great start. Perhaps instead of a direct registry call
> there is an adapter call that includes the user, context and pattern?
>

yes something along this lines.


--
Rok Garbas - http://www.garbas.si

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk