On Jan 20, 2010, at 1:39 PM, Nils Breunese wrote:

> 
> Grégory Joseph wrote:
> 
>> Extending the Site class would indeed be one way to do this, and I
>> can see how useful that would be changing "stuff" globally; since we
>> have a similar "concept" for paragraphs/templates (the "parameters"
>> Map), I'd personally be inclined to accept a patch that would add
>> this in the default Site impl.
> 
> I believe all that needs to be added to the Site class is these few lines and 
> content2bean should take care of the rest, right?
> 
> ----
> private Map parameters = new HashMap();
> 
> public Map getParameters() {
>    return this.parameters;
> }
> 
> public void setParameters(Map params) {
>    this.parameters = params;
> }
> ----
> 
> Should I open a Jira ticket for this?

with a .patch file attached, that'd be great.

> I'd like to able to use this functionality pretty soon, say in the next 
> couple of weeks. Do you recommend that I use my own class for now (extending 
> the Site class, and casting Site to my own extension as needed) or is there a 
> release coming up in which this could be incorporated?

If we include it, I reckon it would be for 4.3 / STK 1.3, which should be 
released some time in March (ymmv) - so yeah, you probably want to use your own 
subclass in the meantime, if only so you can get running and not depend on 4.3 
snapshots ;)

Cheers,
-g

> 
> Nils Breunese.
> 
>> On Jan 20, 2010, at 12:02 PM, Nils Breunese wrote:
>>> Hello all,
>>> I'm developing a paragraph (that will probably be used as an
>>> auto-generated paragraph) that I'd like to be able to configure on
>>> the site-level. AFAIK there is no functionality in Magnolia that
>>> will let me set arbitrary properties on the site definition, as
>>> that just instantiates a Site object, which has a fixed set of
>>> properties.
>>> Should I create a class that extends the Site class with a Map that
>>> I can put arbitrary properties in (and from which paragraphs can
>>> read site-level settings?) and use that class instead? Is this
>>> functionality that might be interesting to add to Magnolia itself
>>> or am I the only one who needs this?
>>> Or is there another (better) way to accomplish this?
>>> Thanks,
>>> Nils Breunese.
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to