[xwiki-users] [Xwiki-Workspaces-Latest] modifying workstream entries
is it possible to alter/delete specific workstream entries from a certain workspace? Thanks Tony ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Page Loading Optimization
One of the things that would also help giving a much higher perceived performance, is reducing the JS and CSS of the Home Page. A lot of the JS and CSS that are loaded are NOT needed on the home page. With a loading of the global JS and CSS in 2 pages instead of one, the perceived performance of XWiki gets a huge boost I've done this with an #if in javascripts.vm and stylesheets.vm in some wikis and it was great. Ludovic Caleb James DeLisle a écrit : Hello, This is a topic which I have been most interested in, as you will see from my screenshot in http://jira.xwiki.org/jira/browse/XWIKI-2022 loading of javascript is the biggest waste of time. I would like to develop some code to store scripts in a cache and concatenate commonly used scripts together and serve in a single request. I have tested this and it works very well, but I have to make the code neat enough for production. Something which will probably wait until we have our first foot of snow here because there is lots to do in the fall. also see: http://jira.xwiki.org/jira/browse/XSKINX-30 Concatinate always used scripts together and serve in single file. and http://jira.xwiki.org/jira/browse/XSKINX-9 Introduce some internal caching mechanism, since minimizing the file is resource intensive Caleb James DeLisle Thomas Mortagne wrote: Hi, On Thu, Nov 5, 2009 at 17:28, Thibaut Camberlin thibaut.camber...@xwiki.com wrote: Hi all, Page Loading time is a very important criteria when developing a web site. According to a recent surveyhttp://www.webdesignerwall.com/general/users-place-more-weight-on-design/more than half people would drive away from a site with slow loading pages. There are several interesting issues that could be implemented to substantially improve page loading time in XWiki. Number one is aggreation of CSS and JS files in order to reduce HTTP requests. (For info, we have a total of 25 external CSS and JS files on a basic XWiki install when in the best world we would have just 2 - 1 CSS and 1 JS) Note that there is already many suggestions in http://jira.xwiki.org/jira/browse/XWIKI-2022, you should look at it and add yours. Someone interrested in working on this with me ? -- Thibaut Camberlin Project Manager XWiki ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] XWiki RESTful API issue on localhost
Hi Fabio, Thank you so much for your time response. I really appreciate your gesture of sending over the maven project files. I was able to build the xwiki rest .jar use it successfully in my project :) Your code is correct (except the method getPageSummary() which doesn't exist in my generated JAXB model classes, but this could be due to the fact that you are generating them without the simple bindings) I think the problem is from where you get your JAXB generated model classes (which is not clear from the code you posted). Anyway I tried your code and it works perfectly (modulo a renaming of getPageSummary() to getPageSummaries()). I generated the model classes from the .xsd file mentioned in the XWiki Restful API tutorial at http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rest/src/main/r esources/xwiki.rest.model.xsd I've used XJC which was bundled with the JAXB 2.1 distribution. Surprisingly despite using the .xsd that you provided in your project, the XJC still created a very small Pages.java file. It barely had one method which was the getPageSummary() method. However, when I checked the Pages.class file in the jar from your project, it contained quite a few methods (including the one that I was longing to see). The difference in technique that I see here is that the jar was built using mvn while my class files were created using XJC through command prompt. Not sure if there are version differences in any of the dependencies whilst using the two methods. Will have to look into that. Since I am not able to spot the problem from your mail, I attach to this reply the project I used to do the test. You can look at it and find where are the differences wrt what you wrote. You could also use it as a template for writing JAXB-clients for the XWiki RESTful API. Hope this help. -Fabio It is help that arrived just in time Fabio. We have an internal trouble-ticketing application. The XWiki instance is projected to be our knowledge base went live just today. We wanted our application to extract tags pass on to XWiki which in turn would return trouble-shooting articles. Probably, once the search feature is successful, we would like to be able to push new articles/pages to XWiki from our internal application at the click of a button. Your work is a great starting point. This will give XWiki a lot more portability in today's times when applications interacting with each other is becoming a must. Thanks Fabio... ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
