To manage translations better I've updated
http://l10n.xwiki.org/xwiki/bin/view/L10N/StatusByLanguage page which
generates links to translation pages.
I added JavaScript sorting, which seems to work only alphabetically :-/
When I work on laptop, I haven't enough screen to fully see translation
tables, therefore I added XWiki.StyleSheetExtension with dynamic style
which hides panel on smaller width.
@media (max-width: 1366px) {
#leftPanels, #rightPanels {
display: none;
}
#contentcolumn div.main.layoutsubsection {
margin: 0 !important;
}
div#contentcolumn div.main.layoutsubsection {
padding: 0 !important;
}
}
Can anybody with appropriate rights add and include similar object to
Translation class
http://l10n.xwiki.org/xwiki/bin/view/L10NCode/TranslationFileClassSheet20
Also. And maybe add similar JavaSript sorting for translation tables
also? (Or somebody could give modify permissions for valdisvi user to
this class.)
It would improve usability a lot.
Thanks!
Valdis
> I'm updating XWiki translations in http://l10n.xwiki.org/ and after
> resource redesign I wonder where should I start.
>
> Can you provide some list of description/priorities for all XWiki
> platforms and files, which should be translated first to cover needs of
> the most usual XWiki users.
>
> Thanks!
> Valdis
>
> _______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
Hi devs,
I’m working on improving our test framework by doing the following:
* Introduce a wrapping RemoteWebDriver called XWikiWebDriver
* Move all the generic methods (i.e. that are not related to XWiki’s specific UI) we have in TestUtil + BaseElement into XWikiWebDriver (all the findElement(s)WithoutWaiting(), hasElement*(), waitFor*(), etc). The idea is simply to augment the WebDriver-provided APIs with all the methods we have created because they were useful to us.
* Add an automated check when calling method that wait (e.g. findElement(), findElements()) so that if the timeout is incurred, we fail the test. The reason is that if we incur the timeout it means the test itself is not doing it right and is taking too much time!
Let me know if you don’t agree with something (as quickly as possible since I’ve already spent a few hours on it ;)).
Thanks!
-Vincent
Hi All,
i want to put a {{warning}} in the header of a page when a specific macro is
not contained. How can i do that. I tried in a Listener when the needed
Macro-Block is not contained with
doc.getXDOM().getRoot().addChild(new WordBlock("{{warning}}Warning
Text.{{/warning}}"));
context.getWiki().saveDocument(doc, context);
This not works. What is the correct way to manipulate the Document DOM on
Load?
Regards,
Matthias
--
View this message in context: http://xwiki.475771.n2.nabble.com/Inject-Warning-in-Page-when-Macro-in-Spac…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi All,
I want to create a component where i can overwrite a method of the component
from velocity or groovy script inside a wiki page. Its also fine if i can
"read" a groovy script to the component so i can use the defined logic.
Maybe i have to use a own programmed macro for that.
Is that possible? Do you use something similar somewhere?
Regards,
Matthias
--
View this message in context: http://xwiki.475771.n2.nabble.com/Overwrite-Method-of-Component-in-Velocity…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
FYI. Could be interesting for us to upgrade. Don’t know if it’s backward compatible with 4.x or not though.
Thanks
-Vincent
On 21 Feb 2015 at 01:05:53, Anshum Gupta (anshum(a)apache.org) wrote:
20 February 2015, Apache Solr™ 5.0.0 and Reference Guide for Solr 5.0 available
The Lucene PMC is pleased to announce the release of Apache Solr 5.0.0
Solr is the popular, blazing fast, open source NoSQL search platform
from the Apache Lucene project. Its major features include powerful
full-text search, hit highlighting, faceted search, dynamic
clustering, database integration, rich document (e.g., Word, PDF)
handling, and geospatial search. Solr is highly scalable, providing
fault tolerant distributed search and indexing, and powers the search
and navigation features of many of the world's largest internet sites.
Solr 5.0 is available for immediate download at:
http://lucene.apache.org/solr/mirrors-solr-latest-redir.html
See the CHANGES.txt file included with the release for a full list of
details.
Solr 5.0 Release Highlights:
* Usability improvements that include improved bin scripts and new and restructured examples.
* Scripts to support installing and running Solr as a service on Linux.
* Distributed IDF is now supported and can be enabled via the config. Currently, there are four supported implementations for the same:
* LocalStatsCache: Local document stats.
* ExactStatsCache: One time use aggregation
* ExactSharedStatsCache: Stats shared across requests
* LRUStatsCache: Stats shared in an LRU cache across requests
* Solr will no longer ship a war file and instead be a downloadable application.
* SolrJ now has first class support for Collections API.
* Implicit registration of replication,get and admin handlers.
* Config API that supports paramsets for easily configuring solr parameters and configuring fields. This API also supports managing of pre-existing request handlers and editing common solrconfig.xml via overlay.
* API for managing blobs allows uploading request handler jars and registering them via config API.
* BALANCESHARDUNIQUE Collection API that allows for even distribution of custom replica properties.
* There's now an option to not shuffle the nodeSet provided during collection creation.
* Option to configure bandwidth usage by Replication handler to prevent it from using up all the bandwidth.
* Splitting of clusterstate to per-collection enables scalability improvement in SolrCloud. This is also the default format for new Collections that would be created going forward.
* timeAllowed is now used to prematurely terminate requests during query expansion and SolrClient request retry.
* pivot.facet results can now include nested stats.field results constrained by those pivots.
* stats.field can be used to generate stats over the results of arbitrary numeric functions.
It also allows for requesting for statistics for pivot facets using tags.
* A new DateRangeField has been added for indexing date ranges, especially multi-valued ones.
* Spatial fields that used to require units=degrees now take distanceUnits=degrees/kilometers miles instead.
* MoreLikeThis query parser allows requesting for documents similar to an existing document and also works in SolrCloud mode.
* Logging improvements:
* Transaction log replay status is now logged
* Optional logging of slow requests.
Solr 5.0 also includes many other new features as well as numerous
optimizations and bugfixes of the corresponding Apache Lucene release.
Detailed change log:
http://lucene.apache.org/solr/5_0_0/changes/Changes.html
Also available is the Solr Reference Guide for Solr 5.0. This 535 page
PDF serves as the definitive user's manual for Solr 5.0. It can be downloaded
from the Apache mirror network: https://s.apache.org/Solr-Ref-Guide-PDF
Please report any feedback to the mailing lists
(http://lucene.apache.org/solr/discussion.html)
Note: The Apache Software Foundation uses an extensive mirroring network
for distributing releases. It is possible that the mirror you are using
may not have replicated the release yet. If that is the case, please
try another mirror. This also goes for Maven access.
--
Anshum Gupta
http://about.me/anshumgupta
Hi,
Im trying to fix http://jira.xwiki.org/jira/browse/XWIKI-4274
Basically if you do $xwiki.getDocument("someDoc").getRenderedContent()
it'll get executed in the context of the current doc which I believe
is wrong especially since other signatures of getRenderedContent()
execute in the target document's context.
I have fixed this locally but found that admin.vm for example is
assuming that getRenderedContent() will get executed in the context of
the calling doc (i.e. XWiki.Import when doing an import for example).
FYI the chain flow is admin.vm -- getRenderedContent() -->
XWiki.AdminSheet --> XWiki.AdminImportSheet --> importinline.vm, which
requires the current doc to be XWiki.Import (to get/put attachments
from/to it).
I can fix this easily using a new getRenderedContent signature I've
introduced.
However I'm wondering if we have other places that incorrectly use
getRenderedContent() and assume it won't be rendered in the context of
the target document.
Is this change too dangerous to make? If not know, we'll need to it
quickly (2.1M1?) since it's an important bug IMO.
WDYT?
Thanks
-Vincent
Hi guys,
I met an issue recently on a project. We'd like to build an XWiki-based
website that will be available in several languages. We'd like to use
structured data, which means using XObjects.
Unfortunately at the moment XObjects are not internationalized: they're
available only in one language, even if a page exists in 2+ languages.
A common workaround is to either duplicate all fields in the object (say,
"type_FR" and "type_EN") or have 1 object per language, with a field
handling the language property. In either way, custom sheets need to be
developed to make it possible to modify the various languages of the page.
There is also an issue with the search: in which language should the
object's content be indexed?
One solution would be to make it possible to have international languages
handled directly in XWiki (the same way than the default title / content
fields are handled now), but I'm not sure how much work that would take.
WDYT?
Guillaume
Hi all,
I moved the tutorial to a new space (Documentation) under
http://extensions.xwiki.org/http://extensions.xwiki.org/xwiki/bin/view/Documentation/ContributingXWikiX…
I also put a link to the tutorial in the extensions main page
under "contribute extension" (when you're logged in) as you can see below.
http://extensions.xwiki.org/xwiki/bin/view/Main/
[image: Inline image 1]
WDYT ?
(Thanks to Caleb for all these suggestions.)
On Fri, Feb 13, 2015 at 5:10 PM, Caleb James DeLisle <cjd(a)cjdns.fr> wrote:
> Hi all,
>
> Today I worked with Mohamed to release an extension (TotemApplication) to
> the extension manager
> and he wrote an excellent tutorial for uploading a xar file so that is is
> accessible from the
> extension manager.
>
> http://www.xwiki.org/xwiki/bin/view/Drafts/ContributingExtensions
>
> I'd like to propose we move this to a more official location than /Drafts/
> since at this point
> it's the only end-to-end tutorial on contributing XAR extensions.
>
> WDYT?
> Caleb
>
>
> --
> Satire is the escape hatch from the cycle of sorrow, hatred and violence.
> #JeSuisCharlie
>
Hi devs,
We’re starting a new year and new development cycle (the 7.x one). It’s time to reflect back on what we did and what we wish to achieve and also what we wish to do better.
I think it wouldn’t do any harm to the xwiki project that we continue automating stuff (more build/release process automation, more development automation, more documentation automation, more test writing automation, etc). Basically anything that makes us better at delivering the XWiki software.
If you agree with this, I’d like to propose that we start filling a wiki page on xwiki.org dedicated to what we achieved.
I’ve started such as page at http://dev.xwiki.org/xwiki/bin/view/Drafts/AutomationAchievements (the idea will be to move it somewhere in dev.xwiki.org if this proposal is accepted).
At the moment I’ve put only a single item that I remember we did on the automation topic but the idea is that each one of us (us = the xwiki community at large) updates this page when he/she implements some new automation stuff.
The goal of this page is several:
* show appreciation to whoever helped improve XWiki’s automation
* realize that we’re doing work on automation and see how much we achieve in a year. And thus be able to compare year to year and see how we fare.
* provides emulation to all of us to do even more in this domain
WDYT?
Thanks
-Vincent