To all devs,
The 4.3M1 release is for Monday. Could all devs please fix the build so that it passes and so that we can release on Monday?
Make sure to not commit anything more for 4.3M1. What's not committed should now go for 4.3M2 unless it's a blocker.
All make sure all your issues are closed with proper documentation fields.
Thanks
-Vincent
Hi everyone,
I would like to propose to introduce a possibility to associate
properties in the execution context with metadata by declaring them. We
introduce the class 'ExecutionContextProperty' that will store the
metadata attributes, in addition to the actual property value.
/**
* Declare a property in the execution context.
*
* @param key The key that names the property
* @param property The property to declare.
*/
public void declareProperty(String key, ExecutionContextProperty property)
The metadata governs how the property should be treated when managing
the execution contexts. For instance, these attributes could be supported:
* Read-only - The value may not be updated within the the execution
context.
* Inherited - The property will be inherited from the current context
when replacing the execution context within the scope of a request.
* Clone - Also clone the value when the execution context is cloned.
* Type - The class of the value, for typechecking when replacing
the value.
* Non-null - The value may not be null
So, the arguments for this proposal are at least two:
1. Catch errors early and simplify debugging.
2. Convenience of having properties automatically maintained across
execution contexts within the same request cycle.
What do you think?
I would like to implement and merge this ASAP.
Best Regards,
/Andreas
Hi devs,
Now that we've decided about our mini workflow to know which issues having patches have been answered by us or not, that leaves us with this status:
http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10000#Issue-Statis…
Namely:
- 28 issues containing patches that we need to review
- 16 issues that we've reviewed and for which we're waiting for an answer from the contributor
- 1 waiting for a pull request
I think that so far we've not been very good at answering quickly contributors who post patches. I know it's difficult. I'm proposing 2 ways to improve this:
* Send a weekly email about issues having patches and awaiting committer feedback
* Schedule a "patch day" where devs would work primarily on reviewing issues with patches and applying where possible. At the minimum the goal would be to reply to the issues.
WDYT?
Thanks
-Vincent
Hi guys,
I tried to contribute some translations for the repository extension at
http://l10n.xwiki.org. However the message keys for the repository
extension are unknown.
What is the proposed way to contribute translations for extensions?
Here are the translations for German language:
## Translations for the livetables column titles
extension.repository.emptyvalue=
extension.repository.name=Name
extension.repository.summary=Zusammenfassung
extension.repository.type=Typ
extension.repository.authors=Autoren
extension.repository.doc.creationDate=Erzeugt am
extension.repository.doc.date=Letzte Änderung
## Administration UI
admin.repository=Repository mit Erweiterungen</content>
Richard
Hi devs,
Just realized that we don't have direct way of getting a page's content (only the content)…
The best we can do is:
http://playground.xwiki.org/xwiki/bin/view/Sandbox/WebHome?xpage=plain&outp…
But that converts the content to XWiki Syntax.
Shouldn't we have a vm for just displaying the content? Or even better a REST URL?
Thanks
-Vincent
Hi,
I found an issue with the maven project to generate the javadocs for
SRD. Apparently all the internal packages are ignored.
This is no necessarly a problem unless we want them in the javadocs.
Now there is a problem as some APIs are in internal, which does not
seem normal.
This is the case of:
org.xwiki.officeimporter.internal.script.OfficeImporterScriptService
org.xwiki.officeimporter.internal.openoffice.script.OpenOfficeManagerScriptService
org.xwiki.office.viewer.internal.DefaultOfficeViewerScriptService
Until we find a solution i've reverted to the javadocs manually
generated (without the maven project).
Ludovic
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi,
I'm happy to announce the first release of the Scripting Reference
Documentation (SRD).
The objective of this documentation is to have a quick access to the
relevant javadoc or documentation page to perfom XWiki scripting.
The SRD is available at:
http://platform.xwiki.org/xwiki/bin/view/SRD/Navigation?xpage=embed
It contains:
- javadoc links to Velocity and Groovy bindings, including the main
API ($xwiki, $doc, $request, $response, $context) as well as XWiki
services and plugins, as well as Velocity Tools.
- links to the Velocity and Groovy language documentation
This documentation is currently available for XWiki 4.1.x an 4.2.x.
This is a very good tools for beginners with XWiki scripting. We do
still recommend the development tutorials on the XWiki Dev Guide
(http://platform.xwiki.org/xwiki/bin/view/DevGuide/WebHome).
Please let us know on the dev list for any feedback on this new documentation.
Ludovic
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi all,
At Curriki we currently work on a small tool which allows us to search
users and apply changes to their "active/inactive" and
"email_undeliverable" values easily without the need of editing the user
objects manually.
That gives us the following combinations for user states which are already
in use (e.g. in the registration process):
- User state: Active Values: (active:"Active", email_undeliverable:No)
- User state: Inactive Values: (active:"Inactive",
email_undeliverable:Yes) - The user needs to revalidate his email address
Now if we want users to be marked as deactivated/spammers do you think
would it be a good way to define an additional user state by expressing it
through boolean combinations like this:
- User state: Deactivated/Spammer Values: (active:"Inactive",
email_undeliverable:*No*)
Or do you think it would it be better to add an entry to the choices of the
"active" value in the user object which explicitly says "deactivated" or
"spammer".
Or do you have any other best practice solutions?
Thank you in advance!
Hi (Ludovic),
Cool that you applied http://platform.xwiki.org/xwiki/bin/view/SRD/Navigation?xpage=embed
I've noticed some bugs in the services listing, like $services.class, $services.line, $services.currentmixed, etc.
Also note that the Bindings filter is missing the $services binding.
Thanks
-Vincent
Hello
I’m very new to xwiki – found it yesterday ;) cause I’m search for a tool to
display the content of our stock databases.
This means - i only need a (read-only) front end to some databases here.
I found the possibility, to add a custom app in xwiki. But - so far i see -
the structure is added to the xwiki default DB.
Now here is my question. Is it possible to use xwiki as a front-end or set
up different data sources to connect to different databases?
And how can i put values from the DB into a xwiki form?
The devel Docs on the wiki side seams to covers an older xwiki version.
I'm appreciated for any hint ...
Thanks a lot
Peter
--
View this message in context: http://xwiki.475771.n2.nabble.com/Connect-to-external-database-tp7581689.ht…
Sent from the XWiki- Dev mailing list archive at Nabble.com.