xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

by Vincent Massol

Hi, Here's my master plan to improve some of the navigation in the XE wiki: 1) Create new Quick Links Panels with important links (AllDocs, etc) and add it by default above the Navigation panel 2) Modify the Navigation Panel to support excluding pages and spaces. It would work as follows: - Create a NavigationPanelExclusionsClass class and a NavigationPanelExclusionsClassSheet. The class would contain one big textarea to enter regex of docs and spaces to exclude (one per line) - Modify the Navigation Panel code to look for all documents in the wiki having a NavigationPanelExclusionsClass object and use the content to verify if a page should be added to the Navigation Panel or not - Create a XWiki.NavigationPanelExclusions document (with an NavigationPanelExclusionsClass object attached) in XE to exclude some pages/spaces by default (the same that are currently excluded but in a hard coded way in the Navigation Panel). Also add the list of pages that are in the Quick Link panels to the exclusion list. I believe this point 2) will greatly enhance the value of the Navigation Panel which will then be able to be used effectively on some wiki-specific spaces for example. BTW we might want to also have inclusion lists and not only exclusion lists so the NavigationPanelExclusionsClass could have 2 fields and be renamed to NavigationPanelSelectionClass or something like that. 3) Improve performances of the Navigation Panel. Right now it's called on every single page display and does a huge query on the DB so if the wiki has lots of documents it slows everything down. I'd like to propose 2 improvements: a) Use a cache (see below) in which we put the doc list b) Limit the number of pages to be displayed to the first 100 (for example) and add some text in the Navigation Panel (like: "Displaying only the last 100 documents accessed - Use the AllDocs page to view all pages") 4) Add a Cache service which can be used both by XWiki Core and by Velocity/Groovy scripts (by making it a plugin for now). It would work as follows: - A singleton factory that allows getting and creating cache instances - The ability to specify if the cache is an application cache (lifetime of the JVM), or a user session cache (we might also need a request level cache but let's see that later) - The ability to specify a maximum cache size and an eviction policy (No eviction, LRU, etc) - The ability (and this is key) to specify to what notification even the cache should be registered to. For example we can imagine the following events: - DocumentModificationEvent - DocumentRenameEvent - DocumentCreationEvent - DocumentDeletionEvent - ObjectAdditionEvent - etc. What this means is that XWiki core use the cache factory to notify all caches registered with these events when they happen and the caches can then have a method to tell their users that the cache needs to be refreshed. We would use this in the Navigation Panel so that whenever a new document is created, renamed or deleted we would reload the cache with a query against the DB. Something like: #if (!$xwiki.cache.isRegistered("NavigationPanel")) $xwiki.cache.register("NavigationPanel", 100, true, ["DocumentRenameEvent", "DocumentCreationEvent", "DocumentDeletionEvent"]; #end #set ($cache = $xwiki.cache.get("NavigationPanel")) #if ($cache.requiresRefresh()) // do the DB query and add to the cache here #end // Display the pages from the cache here. So WDYT? Thanks -Vincent

17 years, 11 months

a place to submit some code

by ioana boureanu

Hi everyone, I need a place to submit part of the code I have done so far on my project. So, please assign me one. Thanks in advance. That's basically why I am writing. Regards, Ioana Cristina Bourenau

17 years, 11 months

Re: [xwiki-commits] r3928 - xwiki-products/curriki/trunk/gwt

by Vincent Massol

On Jul 10, 2007, at 1:30 AM, David Ward wrote: > Author: dward > Date: 2007-07-10 01:26:09 +0200 (Tue, 10 Jul 2007) > New Revision: 3928 > > Modified: > xwiki-products/curriki/trunk/gwt/pom.xml > Log: > - Allow GWT version to be changed > - The previous checkin ignored the fact that there are two sets > of profiles, > so now adding -Dgwt=1.4.10 will use the 1.4.10 compiler > > > Modified: xwiki-products/curriki/trunk/gwt/pom.xml > =================================================================== > --- xwiki-products/curriki/trunk/gwt/pom.xml 2007-07-09 22:45:44 > UTC (rev 3927) > +++ xwiki-products/curriki/trunk/gwt/pom.xml 2007-07-09 23:26:09 > UTC (rev 3928) > @@ -212,11 +212,9 @@ > <profile> > <id>gwt-1.3.3</id> > <activation> > - <activeByDefault>true</activeByDefault> > -  > - <jdk>1</jdk> > + <property> > + <name>!gwt</name> > + </property> Ah just seen this. Forget my earlier email on this topic :) Thanks -Vincent

17 years, 11 months

Re: [xwiki-commits] r3927 - xwiki-products/curriki/trunk/gwt

by Vincent Massol

Hi David, On Jul 10, 2007, at 12:45 AM, David Ward wrote: > Author: dward > Date: 2007-07-10 00:45:44 +0200 (Tue, 10 Jul 2007) > New Revision: 3927 > > Modified: > xwiki-products/curriki/trunk/gwt/pom.xml > Log: > - Add profile so that the GWT code can compile under Solaris (SunOS) > - Add profile to make it easier to change GWT versions [snip] > <profiles> > <profile> > + <id>gwt-1.3.3</id> > + <activation> > + <activeByDefault>true</activeByDefault> > +  > + <jdk>1</jdk> > + </activation> Strange, this working fine everywhere else in XWiki's build (we use it in several other places). Are you sure this is the problem? -Vincent

17 years, 11 months

[ANN] XWiki Enterprise 1.1 Milestone 3 Released

by Vincent Massol

The XWiki development team team is pleased to announce the availability of the 1.1 Milestone 3 release of XWiki Enterprise Go grab it on http://www.xwiki.org/xwiki/bin/view/Main/Download Version 1.1 Milestone 3 is mostly a bug fix release. There's also been a big internal change in that XWiki has been reorganized to separate the Platform from the Products developed on top of it and a modular automated build system using Maven2 has been setup. This was done to support the multiple products that will be released in the near future: XWiki Enterprise (the current Wiki you've come to know and love), XWiki Enterprise Manager (Multi Wiki management tool), XWiki Watch (social feed reader) and more. Main changes: * Lots of bugs fixed * XWIKI-798 - XWiki does not work on Java 1.6 * XWIKI-1411 - Allow date format in footer to be customized (for Albatross and Finch skins) * XWIKI-1453 - Allow specifying the list of toolbars to display in the WYSIWYG editor * XWIKI-1355 - The page displayed by UnknownAction should be configurable * XWIKI-1410 - Configurable list of initial groups * XWIKI-1372 - Make XWiki platform GWT-ready + several other changes. See the full release notes on http://www.xwiki.org/xwiki/bin/view/ Main/ReleaseNotesXWikiEnterprise11M3 Enjoy -The XWiki development team

17 years, 11 months

XWiki1.1M3 releases available in Maven2 repository

by Vincent Massol

Hi everyone, Just to announce that I've finished released 1.1M3 in our maven repository at ttp://maven.xwiki.org/releases I still need to finish a few things before announcing it officially: create the releas notes, send emails, modify xwiki.org, etc However in the meantime it'd be great it some of you could try it out and let me know if all work as expected. Some useful links: - the full zip version: http://maven.xwiki.org/releases/com/xpn/xwiki/ products/xwiki-enterprise/1.1-milestone-3/xwiki-enterprise-1.1- milestone-3-hsqldb.zip - the XAR: http://maven.xwiki.org/releases/com/xpn/xwiki/products/ xwiki-enterprise-wiki/1.1-milestone-3/xwiki-enterprise-wiki-1.1- milestone-3.xar - the WAR: http://maven.xwiki.org/releases/com/xpn/xwiki/platform/ xwiki-web-standard/1.1-milestone-3/xwiki-web-standard-1.1-milestone-3- hsqldb.war - the XWiki JAR: http://maven.xwiki.org/releases/com/xpn/xwiki/ platform/xwiki-core/1.1-milestone-3/xwiki-core-1.1-milestone-3.jar Note: No .exe yet as I haven't been able to include that into the maven2 build yet. I'll try to generate it by hand for now. Thanks -Vincent

17 years, 11 months

build is broken... again...

by Radu Danciu

mvn install yields: At revision 3925. Macintosh:~/Desktop/xWiki Sandbox/SVN/trunks-users rhadoo$ mvn install [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/com/xpn/xwiki/platform/applications/xwiki-app… [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. GroupId: com.xpn.xwiki.platform.applications ArtifactId: xwiki-applications Version: 1 Reason: Unable to download the artifact from any repository com.xpn.xwiki.platform.applications:xwiki-applications:pom:1 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: < 1 second [INFO] Finished at: Mon Jul 09 21:06:09 EEST 2007 [INFO] Final Memory: 2M/5M [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: < 1 second [INFO] Finished at: Mon Jul 09 21:06:09 EEST 2007 [INFO] Final Memory: 2M/5M [INFO] ------------------------------------------------------------------------ with the settings.xml updated to latest version, svn up to latest revision. Am I doing something wrong, or is it just broken? Radu

17 years, 11 months

[VOTE] Releasing XWiki Enterprise 1.1M3 and dependent modules

by Vincent Massol

Hi, I'd like us to vote on the following releases that should happen tomorrow (barring any technical issue): * XWiki Platform Tools version 1.1 Release Notes: * [XTOOLS-1] - Exception while creating backlinks * [XTOOLS-2] - Separate XAR Handler and XAR plugin into 2 build modules * [XTOOLS-3] - Add new XWiki configuration resources module to share XWiki configuration files between build modules * XWiki Platform Panels Application version 1.1M3 Release Notes: * [XAPANELS-1] - Navigation Panel fails if a Space has a simple quote in its name * [XAPANELS-25] - Improve message when non-admin tries using the Panel Wizard * XWiki Platform Core version Release Notes: * [XWIKI-738] - XMLRPC always interacts with database "xwikitest" * [XWIKI-909] - WYSIWYG Wiki editor breaks http:// links to its own domain * [XWIKI-1104] - The Maven2 packager plugin fails to import the XWikiUserTemplate document from the default wiki * [XWIKI-1327] - Logout only works for one URL * [XWIKI-1387] - hibernate.cfg.hsql.xml is missing feeds.hbm.xm declaration * [XWIKI-1398] - Login page is displayed when no cookie exists even for pages that do not require authentication * [XWIKI-1409] - Adding attachments fails when javascript is disabled * [XWIKI-1412] - Calls to XWiki.prepareResources are spread accross the code, in all the wrong places * [XWIKI-1446] - Sectional edit don't set edit comment * [XWIKI-1458] - Superadmin login security issues * [XWIKI-1461] - Forbid registering the 'superadmin' account * [XWIKI-798] - XWiki does not work on Java 1.6 * [XWIKI-1370] - Recently Viewed documents tab in Link Editor should display some warning if the stats plugin isn't activated * [XWIKI-1397] - Add ability to pass the port on which to start Jetty in XWiki Enteprise standalone installation * [XWIKI-1408] - Fix deprecated usage of commons-fileupload * [XWIKI-1411] - Allow date format in footer to be customized (for Albatross and Finch skins) * [XWIKI-1415] - Use SVN revision number as XWiki's build number when displaying the version * [XWIKI-1417] - Functional tests for all databases * [XWIKI-1453] - Allow specifying the list of toolbars to display in the WYSIWYG editor * [XWIKI-1355] - The page displayed by UnknownAction should be configurable * [XWIKI-1410] - Configurable list of initial groups * [XWIKI-408] - Install TeamCity for building with XWiki's CI * [XWIKI-1372] - Make XWiki platform GWT-ready * [XWIKI-1393] - SVN reorganization to take into account the different XWiki products * [XWIKI-1454] - Split XWiki's maven2 remote repository into 3: snapshots, releases and externals * [XWIKI-1463] - Upgrade to Apache POI v3.0 final * XWiki Enterprise version 1.1M3 Release Notes: * [XE-69] - Hardcoded /xwiki/ in XWiki.Treeview * [XE-70] - All Documents Treeview throws exception when a document name contains ' * [XE-71] - All Documents TreeView fails to display when a document name contains " * [XE-72] - &$param in URL when switching between view tabs in Main.AllDocs * [XE-74] - XWiki starts more slowly than before on the first run Here are my +1 for all releases. Please cast your votes. Thanks -Vincent

17 years, 11 months

XWiki-Eclipse-Plugin-M2

by tharindu jayasuriya

We have completed work allocated for Milestone-2 of XWiki-Eclipse-Plugin (+ more). http://jira.xwiki.org/jira/browse/XWIKI-1361 Implemented Features: - view existing pages (as xwiki markup or browser output) - edit xwiki markup (using TextEditor widget in eclipse) - save edited content Although we encountered some problems as well, - We couldn't prepare the pom.xml file such that maven produces a deployable plugin component. Eclipse needs the plugin jar file to have a specific format and maven enforces a different format, we're still struggling to get it right (need some help). Although compilation and other stuff or quite ok. - Eventhough the edited XWiki Markup can be saved, the output(in browser) does not reflect changes untill we restart XWiki. Is there a way to forcefully flush the cache ? can this be done remotely ? All comments are welcome! Thanks a lot!!! - Tharindu & Asiri

17 years, 11 months

Having a plugin modify xwiki core structure.

by Radu Danciu

In building my google docs plugin, I need to modify the structure of the user signup / details page (adding google username and pass). I would like to know if this can be done without my modifying the core structure of xwiki. To clarify: can I make it so that my plugin, when put into use, adds the two fields to the signup / details page? This would solve another small issue that would intervene if modifying the core - when you don't use the docs plugin, you get 2 useless fields in said pages. Any ideas on if and how I could do this? Thanks, Radu

17 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs