Hi,
I was thinking that instead of introducing a new notation, we might
add a parameter like objectCreationPolicy=update|updateOrCreate|
If this parameter is not present everything works as today.
If this parameter is present we might choose what to do.
So it's up to the user to decide what
I like the idea of introducing an objectCreationPolicy parameter.
This way, we can introduce any new strategy (like the nice one proposed
by Sergiu for example) for update/create objects with a new keyword
('oldcore' [default strategy if 'objectCreationPolicy' is not given],
'updateOrCreate' or
Sounds nice and would solve http://jira.xwiki.org/browse/XWIKI-217 nicely :)
Thanks
-Vincent
On 10 Apr 2014 at 22:37:36, Sergiu Dumitriu
(ser...@xwiki.org(mailto:ser...@xwiki.org)) wrote:
Sometimes it's important to be able to decide if the user wants an
existing object by number, an
Good day,
One of the objectives of 6.0 is to review the existing applications on
extensions.xwiki.org, improve them and see how they would integrate in the
upcoming Flamingo skin (while also considering improvements suggestions).
This mail covers the Flamingo integration for the Meetings
Hi Guillaume,
Thanks for suggesting this. This would need to be VOTEd since we need to be
careful about data we send as some users can feel that their privacy is at
danger. ATM my goal with version 2 is to not introduce any new data sent but to
allow graphing active installs over time.
If we
5 matches
Mail list logo
