I am close to have the entire Blog Application upgraded to 2.0 Syntax (now I upgraded the Panels). That brings me back to the create an export of the application which is a pain in the next using the full export but does not work using the Import / Export Application.
Looking into the I/E App I saw that it is using XWiki.searchDocuments(String sql) but that will not return any HIDDEN documents. The PackageAPI (used by the full export) is not providing a list and it seems it would break its indention to do so.
So first I was wondering if there is a way to obtain a list of documents including the hidden ones?
I not then I was wondering if we should export XWiki or should create another Plugin that delivers all documents?
Finally I am thinking that we might should extend the full export (XWiki Administration) allowing a user to create custom exports more or less like the I/E application?
Cheers - Andy
(resending since I got a failure from xwiki's mail content filter )
---------- Forwarded message ----------
From: Vincent Massol <vincent(a)massol.net>
Date: Sun, Jul 26, 2009 at 11:33 AM
Subject: [Wiki Importer] Design questions
To: XWiki Developers <devs(a)xwiki.org>
Hi Arun,
I've just started reviewing your module. I'll send questions as they
come. Here are some to start with:
1) Why do you need the Wiki interface? Since all implementations are
wiki-specific and since it doesn't contain any useful method I don't
see why it's needed.
2) Why do you need 2 methods in WikiImporter interface? I would have
imagine only a single method:
WikiImporter.import(...)
3) Why do you pass a byte array instead of a stream? If the import is
large a byte array will result in an OOM error.
4) WikiImporterVelocityContextInitializer has invalid javadoc. In
addition instead of exposing each importer you could expose only a
single importer factory and pass an import syntax to it. This will
reduce the coupling and not expose the implementations to the client
side (very important). Something like:
WikiImporterFactory.createImporter(ImportSyntax).
5) This should never be written (in DefaultImportWikiParser &
DefaultImportWikiRenderer for ex):
//Intialize Embeddable Component Manager
EmbeddableComponentManager ecm = new EmbeddableComponentManager();
ecm.initialize(this.getClass().getClassLoader());
The component manager must alway be passed as a dependency.
6) You shouldn't use @Component("default") but instead @Component
7) You should never use new
File(System.getProperty("java.io.tmpdir"). Instead you should use the
existing API located in
Container.getApplicationContext().getTemporaryDirectory().
I have some more comments but since they are linked to the above let's
agree first on the points above before going further.
Thanks
-Vincent
Hi Devs,
Currently on a multi-xwiki installation all the xwikis can manipulate the OO
server instance shared between them. I think it makes more sense to allow
only the primary xwiki to control the oo server while rest of the xwikis
become observers / consumers.
WDYT?
Here is my +1.
Thanks.
- Asiri
+1
-----Message d'origine-----
De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] De la part de Asiri Rathnayake
Envoyé : mercredi 29 juillet 2009 11:52
À : XWiki Developers
Objet : [xwiki-devs] [PROPOSAL] Restrict OO server administration to mainxwiki
Hi Devs,
Currently on a multi-xwiki installation all the xwikis can manipulate the OO
server instance shared between them. I think it makes more sense to allow
only the primary xwiki to control the oo server while rest of the xwikis
become observers / consumers.
WDYT?
Here is my +1.
Thanks.
- Asiri
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--------------------------------------------------------------------------------
This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies.
While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection.
KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1
Hi
In case nobody ran into this so far I just wanted to make sure everybody knows that 3827:
http://jira.xwiki.org/jira/browse/XWIKI-3827
is still or again broken in 1.9.2. The fix from David mentioned at the end of the comments did do the trick for me:
wiki/resources/js/xwiki/wysiwyg/xwe/stylesheets/RichTextArea.css:
change: background-image: none;
to: background-image: none !important;
I cannot change the status of this JIRA report to reopen it so please could someone do it or just apply the fix.
Thanks
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
Here I go. My own public blog is now upgraded to 2.0 Syntax using the attached XAR file. The entry discusses the other changes that needed to be done in order to make it work well:
http://madplanet.com/xwiki/bin/view/Blog/
Cheers
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
On Monday, July 27, 2009, at 05:13PM, "Andreas Schaefer" <schaefera(a)me.com> wrote:
>Sorry but I forgot to mention the JIRA report I attached the draft to:
>
>http://jira.xwiki.org/jira/browse/XABLOG-50
>
>Cheers - Andy
>_______________________________________________
>devs mailing list
>devs(a)xwiki.org
>http://lists.xwiki.org/mailman/listinfo/devs
>
>
Hi
Currently our company is using Magnolia (magnolia.info) as the CMS for our website. Because our website is not very dynamic, big or complex using Magnolia is often a little bit of an overkill and keeping it up to date is not easy. So I was wondering if I could use XWiki to create a simple application that would enable the creation and maintenance of a website.
Today the Blog is a list of Blog Document building up the blog page. Breaking up the page into a header, left and right side bar (or using the panels) and columns for the content it should be possible to define a web page. The parts of a page a defined by classes and the content is provided by objects. The application just provides the code that displays the web site and additional elements to create, edit and remove parts of the document (paragraphs) when the user is in edit mode.
The application would provide a simple web site but also the framework to create a custom web site by extending the application.
What do you think?
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
Hi fellow XWikiers,
While celebrating XWiki's 5th birthday last week, we spent a couple days
brainstorming with the full team about where XWiki stands today and what its
future holds. We came up with a long list of features and ideas and we'd
love to get community feedback before deciding in which direction we're
going to move forward once our 2.0 release is out.
To this aim, we've built a survey that we'd like our users and developers to
take. It's a bit long though definitely worth the pain. We're eagerly
waiting for your feedback to start working on new and existing features.
You can access and fill the survey at the following address:
http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiFeatures
Thanks a lot for your time,
Guillaume on behalf of the XWiki Team
--
Guillaume Lerouge
Product Manager - XWiki
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
XWiki had always had some nice feedback about its interface. But things are
not that honey pink, we have many inconsistencies in our user interface,
some of them caused by the fact that we're developing in an open source
environment.
Our goal is to improve the user experience of XWiki and we'd like you to get
involved. We need to improve the usability of the XWiki platform and we
would be very happy if the community got involved in helping us making this
happen.
All the decisions we make directly imply and affect our community which is
why we're eager to get your feedback before we start working further on
these topics.
- We would like to know what are your main usability problems when using
XWiki - we badly want to fix them ;-)
- We would be super-happy to receive bold and creative ideas that we
might be able to incorporate into XWiki's look and feel.
Want to get involved? Yay! We’d love to have you aboard! It doesn't matter
whether you're a developer who’s interested in participating, an UX person
or someone with an eye for design as long as you come up with great ideas.
You can add your mockups and videos to our Flickr group
http://www.flickr.com/groups/xwikiux/ or to our Vimeo group
http://www.vimeo.com/groups/xwikiux . These groups can be used to show off
your ideas or just to point the problems you had using XWiki.
Let’s make XWiki amazing !!
On Tue, Jul 28, 2009 at 13:09, Thomas Mortagne<thomas.mortagne(a)xwiki.com> wrote:
> Hi,
>
> Use <scope>test</scope> for test dependencies instead of <scope>provided</scope>
>
--
Thomas Mortagne
Hi,
I am currently using XWiki for the website of an hotel which is essentially
practical for its i18n management (the website is available in English,
French, Japanse and Italian). I easily managed to upgrade the PhotoAlbum
application in order to be i18n (titles are i18n keys and body use $msg.get
calls). I really need to have a similar functionnality on the Blog
application. I was wondering how complicated this task is... I tought I
could copy every document in the Blog space to a fresh new I18nBlog which I
could modify. What do you think about it ?
Concerning the way I plan to eventually internationalized the Blog
application is to link each BlogPost to a page that could be translated,
through a dedicated class member. I also noticed that the BlogParameters and
BlogCode should be my first look for adapting the application. Please tell
me if I'm right.
At last, I was wondering about the availability of macros for managing
translations when I plan to adapt the sheet. What also about the edition of
a specific document in the sheet of another one, is it possible ?
Thanks for your help.
--
Hoani CROSS
Globotraders Tahiti Founder [http://globotraders-tahiti.com]
http://code.google.com/appengine/docs/whatisgoogleappengine.html
Java is supported via Java 6 JVM and standard libs:
http://code.google.com/appengine/docs/java/gettingstarted/
My biggest question w/r/t Xwiki is AppEngine's database support:
> The Datastore
>
> App Engine provides a powerful distributed data storage service that
> features a query engine and transactions. Just as the distributed web server
> grows with your traffic, the distributed datastore grows with your data.
>
> The App Engine datastore is not like a traditional relational database.
> Data objects, or "entities," have a kind and a set of properties. Queries
> can retrieve entities of a given kind filtered and sorted by the values of
> the properties. Property values can be of any of the supported property
> value types<http://code.google.com/appengine/docs/python/datastore/typesandpropertyclas…>
> .
>
> Datastore entities are "schemaless." The structure of data entities is
> provided by and enforced by your application code. The Java JDO/JPA
> interfaces and the Python datastore interface include features for applying
> and enforcing structure within your app. Your app can also access the
> datastore directly to apply as much or as little structure as it needs.
>
> The datastore is strongly consistent<http://en.wikipedia.org/wiki/Consistency_model>and uses optimistic
> concurrency control<http://en.wikipedia.org/wiki/Optimistic_concurrency_control>.
> An update of a entity occurs in a transaction that is retried a fixed number
> of times if other processes are trying to update the same entity
> simultaneously. Your application can execute multiple datastore operations
> in a single transaction which either all succeed or all fail, ensuring the
> integrity of your data.
>
> The datastore implements transactions across its distributed network using
> "entity groups." A transaction manipulates entities within a single group.
> Entities of the same group are stored together for efficient execution of
> transactions. Your application can assign entities to groups when the
> entities are created.
>
http://code.google.com/appengine/docs/java/gettingstarted/usingdatastore.ht…
> App Engine includes support for two different API standards for the
> datastore: Java Data Objects <http://java.sun.com/jdo/index.jsp> (JDO) and
> Java Persistence API<http://java.sun.com/developer/technicalArticles/J2EE/jpa/>(JPA). These interfaces are provided by DataNucleus
> Access Platform <http://www.datanucleus.org/>, an open source
> implementation of several Java persistence standards, with an adapter for
> the App Engine datastore.
>
..............
Question:
What would it take to make Xwiki work on Google App-engine? Is the
"datastore" google provides compatible with xwiki's database needs?
What other Java-hosting services "out there" support Xwiki? Database and
java "hosting" issues for Xwiki can be problematic, even though it makes
more sense, to public-host using a language like Java.
I think for my own situation, I would end up "hosting" Xwiki myself, as a
$500.00 box can run a few Xwiki-based sites just fine. However, for
people/customers wanting an Xwiki-based site that don't know about system
administration, JVM's, apache, etc, it would be nice if there was an easier
path to managed hosting in an "open market." This needn't limit xwiki.com's
hosting market, as much as it would open-up xwiki for wider deployment and
use, and make it competitive in situations where Php or RoR might have
easier buy-in, such as in the USA....
Imagine if in the future, one of the installers Xwiki.org offered worked
directly with http://appengine.google.com/ so that people would
actually have their own live, public xwiki sites hosted for them. There's
plenty of sites that would be happy with this level of free
service ( http://code.google.com/appengine/docs/quotas.html ):
Resource Free Default Quota Billing Enabled Quota Daily Limit Maximum
Rate Daily
Limit Maximum Rate Requests 1,300,000 requests 7,400 requests/minute
43,000,000
requests 30,000 requests/minute Outgoing Bandwidth
(billable<http://code.google.com/appengine/docs/quotas.html#Billable_Quotas_and_Fixed…>,
includes HTTPS) 1 gigabyte 56 megabytes/minute 1 gigabyte free; 1,046
gigabytes maximum 740 megabytes/minute Incoming Bandwidth
(billable<http://code.google.com/appengine/docs/quotas.html#Billable_Quotas_and_Fixed…>,
includes HTTPS) 1 gigabyte 56 megabytes/minute 1 gigabyte free; 1,046
gigabytes maximum 740 megabytes/minute CPU Time
(billable<http://code.google.com/appengine/docs/quotas.html#Billable_Quotas_and_Fixed…>
) 6.5 CPU-hours 15 CPU-minutes/minute 6.5 CPU-hours free; 1,729 CPU-hours
maximum 72 CPU-minutes/minuteNiels
http://nielsmayer.com
PS: although at 1 gigabyte outgoing bandwidth, and some of the sizable
javascript libraries these days... you probably want to use
http://webmuch.com/how-why-you-should-use-google-cdn/ alongside :-)
Hi
I just recently started to use the Import / Export Application and run in some unexpected problems. The most severe is the one that I cannot export HIDDEN documents because the searchDocuments() method it is using does not return any hidden documents. That makes the tool less useful and it is a pitfall for inexperienced users.
So I would suggest to use a checkbox to determine if hidden documents should be listed or not. Any idea BTW how hidden documents can be found in XWiki.
After checking out JIRA: http://jira.xwiki.org/jira/browse/XWIKI-3660 I see there is a need to improve the import / export application. I will have a look into how to improve it.
Cheers
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
Hi
I uploaded a new draft of the Blog 2.0 upgrade and tested it with 1.9.2. I got the categories working fine as well as resovled some issues with the publisher. Because NOW I use the original naming an import with replace the old documents so be warned.
I am intend to upgrade my own blog with that draft asap to see how that works out life.
Cheers
Andreas Schaefer
CEO of Madplanet.com Inc.
EMail: andreas.schaefer(a)madplanet.com
schaefera(a)me.com
Twitter: andy_mpc
AIM: schaefera(a)me.com
I've been using Xwiki 1.8 for about 2-3 months now and I really like
it. Unfortunately, my server crashed. I backup the HSQLDB database
everyday. Now, I'm trying to install Xwiki on a different computer and
point it toward one of the copies of my database, but I'm having lot of
problems. I've tried it with Xwiki 2.0, 1.9 and 1.8. I'm running
Tomcat 5.5.27 and java 1.6.0_14.
The real problem is reading my old database. If I don't change the
hibernate.cfg.xml, xwiki will create a new HSQLDB database just fine
(except that it's empty). But when I do modify the hibernate file to
point to my database, I get lots of errors.
Here's the snippet from my hibernate file:
<!-- HSQLDB configuration.
Uncomment if you want to use HSQLDB and comment out other
database configurations.
Note that the database will be created automatically if it
doesn't already exist. -->
<property
name="connection.url">jdbc:hsqldb:file:/travis/www/xwiki/xwikiHSQLDatabase;shutdown=true</property>
<property name="connection.username">sa</property>
<property name="connection.password"></property>
<property
name="connection.driver_class">org.hsqldb.jdbcDriver</property>
<property name="dialect">org.hibernate.dialect.HSQLDialect</property>
<property
name="connection.provider_class">com.xpn.xwiki.store.DBCPConnectionProvider</property>
<property name="connection.pool_size">2</property>
<property name="statement_cache.size">2</property>
<mapping resource="xwiki.hbm.xml"/>
<mapping resource="feeds.hbm.xml"/>
And here's the error I get from my browser (Firefox):
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented
it from fulfilling this request.
exception
javax.servlet.ServletException: Error number 3 in 0: Could not
initialize main XWiki context
Wrapped Exception: Error number 3001 in 3: Cannot load class
com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager
from param xwiki.store.migration.manager.class
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: Could not parse mapping document from resource
xwiki.hbm.xml
org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:145)
com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:111)
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295)
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
root cause
com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize
main XWiki context
Wrapped Exception: Error number 3001 in 3: Cannot load class
com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager
from param xwiki.store.migration.manager.class
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: Could not parse mapping document from resource
xwiki.hbm.xml
com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:326)
com.xpn.xwiki.XWiki.getXWiki(XWiki.java:387)
com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:135)
com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:145)
com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:111)
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295)
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
note The full stack trace of the root cause is available in the Apache
Tomcat/5.5.27 logs.
Apache Tomcat/5.5.27
I've been trying to fix this for 2 days now and I'm losing hope that I
can recover my Xwiki. Can anyone please help? I've tried searching the
mailing list archives, google, the installation documenation, the
upgrade documentation, but I haven't found a solution. I haven't really
modified the xwiki installation much at all. I've just been using xwiki
"as is".
Still Hoping,
travis
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.9.2.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This is a bug fix and enhancement release mainly around new WYSIWYG
and the Blog application.
Changes since XWiki Enterprise 1.9.1. Improvements:
* WYSIWYG
** Allow the page to link to to be searched for or selected from the
most recently edited pages
** Improved style consistency across dialogs
** Upgrade to GWT 1.6.4
Important Bugs fixed:
* Fixed errors in the Blog application with Internet Explorer 6 and 7
* XWIKI-4079 Links are lost when switching to Source in the WYSIWYG editor
* XWIKI-4101 The editor WYSIWYG disappear when creating a new translation
* XWIKI-4085 Content duplicated if there's a macro (toc, id..) in an html macro
* XWIKI-3413 Not possible to generate pure text content (like JSON)
from a 2.0 page using ?xpage=plai
* XWIKI-4088 The output of the HTML macro with wiki=true is parsed and
generates duplicated content
* XWIKI-4067 Trying to edit a missing object property with the new
WYSIWYG editor can lead to infinite include recursion
* XWIKI-3847 removeObject in XWikiDocument does not search for the
object correctly
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise192
Thanks,
The XWiki dev team
(resending since I have problems with my mail client and XWiki's mail
content filter)
---------- Forwarded message ----------
From: Vincent Massol <vincent(a)massol.net>
Date: Mon, Jul 27, 2009 at 12:43 PM
Subject: Re: [xwiki-devs] [Proposal][UX] Standardization of icon usage
on actions
To: XWiki Developers <devs(a)xwiki.org>
On Jul 27, 2009, at 11:45 AM, Ecaterina Valica wrote:
> Hi Devs,
>
> There are two different standards on the action icon usage in the LiveTable:
>
> - with icon + text
> - only with icon
>
> The main problem is the lack of consistency.
>
> Please vote on three versions:
> Var 1 : Icon + Text
> <http://incubator.myxwiki.org/xwiki/bin/view/Standards/ActionIcons#var1>
> Var 2 : Just Icon<http://incubator.myxwiki.org/xwiki/bin/view/Standards/ActionIcons#var2>
> Var 3 : Icon + Legend<http://incubator.myxwiki.org/xwiki/bin/view/Standards/ActionIcons#var3>
I'd normally vote for 1 but taking into account smaller screen I'm
also +1 for var 3.
According to "Don't make me think" var 2 should be prohibited since it
forces users to think.
Tooltips are very bad for the same r'eason.
So +1 for either 1 or 3 but -0 for 2 and Guillaume's option with
tooltips (we can have tooltips but in addition to something more
visible).
Thanks
-Vincent
Hi
I agree with Guillaume. In my company most screens are set to 1024x768 (and can't be changed) and i guess that adding a text to an icon could result in scrollbars on some screens. I would prefer a tooltip.
-----Message d'origine-----
De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] De la part de Guillaume Lerouge
Envoyé : lundi 27 juillet 2009 12:20
À : XWiki Developers
Objet : Re: [xwiki-devs] [Proposal][UX] Standardization of icon usage onactions
Hi,
On Mon, Jul 27, 2009 at 11:58 AM, Thomas Mortagne <thomas.mortagne(a)xwiki.com
> wrote:
> On Mon, Jul 27, 2009 at 11:45, Ecaterina Valica<valicac(a)gmail.com> wrote:
> > Hi Devs,
> >
> > There are two different standards on the action icon usage in the
> LiveTable:
> >
> > - with icon + text
> > - only with icon
> >
> > The main problem is the lack of consistency.
> >
> > Please vote on three versions:
> > Var 1 : Icon + Text
> > <http://incubator.myxwiki.org/xwiki/bin/view/Standards/ActionIcons#var1>
> > Var 2 : Just Icon<
> http://incubator.myxwiki.org/xwiki/bin/view/Standards/ActionIcons#var2>
> > Var 3 : Icon + Legend<
> http://incubator.myxwiki.org/xwiki/bin/view/Standards/ActionIcons#var3>
> >
>
> +1 for Var 1 : Icon + Text (at first i taught i would take too many
> place but it seems ok with several icon in
>
> http://incubator.myxwiki.org/xwiki/bin/view/Standards/ActionIcons#HOtherUsa…
> )
Well, when using a small screen (1024*768), the document index becomes too
wide. Thus I'd rather be +1 for Var 2 as it takes less space.
Instead of having a caption at the bottom as on Var 3, we could put the
action's legend in a tooltip displayed when hovering over the action
icon. WDYT?
Guillaume
> > Thanks,
> > Caty
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
>
>
>
> --
> Thomas Mortagne
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
--
Guillaume Lerouge
Product Manager - XWiki
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--------------------------------------------------------------------------------
This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies.
While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection.
KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1
(resending since I got a failure from xwiki's mail content filter )
---------- Forwarded message ----------
From: Vincent Massol <vincent(a)massol.net>
Date: Sun, Jul 26, 2009 at 12:08 PM
Subject: Re: [xwiki-devs] [VOTE] What to do with RawBlock in plain
text renderer ?
To: XWiki Developers <devs(a)xwiki.org>
On Jul 26, 2009, at 11:52 AM, Thomas Mortagne wrote:
> Hi devs,
>
> We need to decide what to do with html macro content (or any other
> RawBlock content) in plain text renderer.
>
> For me the rule of plain text renderer should be to print anything we
> are able to print which mean printing any pure text content and skip
> styles for which obviously we don't have syntax. RawBlock content is
> pure text so we should print it.
>
> Note that first version of plain text renderer was printing html
> content and it was lost when introducing RawBlock.
>
> Here is my +1 for printing RawBlock content in plain text renderer.
-1 for now (I can be convinced to change it): RawBlock is very special
and should only be interpreted by renderers which understand the raw
syntax. The plain text renderer shouldn't understand any syntax IMO.
I'd like to see a real use case before changing my -1 to a +1.
Right now if a page has for example a form to create a new type of
page and this page is output in plain text, I will not want to see the
HTML printed as content. It doesn't make sense to me.
Thanks
-Vincent
(resending since I got a failure from xwiki's mail content filter )
---------- Forwarded message ----------
From: Vincent Massol <vincent(a)massol.net>
Date: Sun, Jul 26, 2009 at 10:21 AM
Subject: Re: [xwiki-devs] adding a new jsr-223 scripting language to
xwiki (clojure)
To: XWiki Developers <devs(a)xwiki.org>
Hi Niels,
On Jul 26, 2009, at 10:13 AM, Niels Mayer wrote:
> In
> http://code.xwiki.org/xwiki/bin/view/Snippets/DisplayFormatedCodeAttachment…
>
>> VincentMassol | 2009/05/05 20:03
>>
>>> Niels, no there's no plan but we can now support any language using macros
>>
>> so feel free to provide a clojure macro if you're interested. Shouldn't be
>> too hard to do, especially if there's a JSR-223 implementation (in which
>> case simply dropping the jar in WEB-INF/lib should be enough - you'd then
>> use it using the script macro).
>
>
> Clojure <http://groups.google.com/group/clojure> has aJSR-223 implementation
> according to:
> http://github.com/pmf/clojure-jsr223/tree/master
> http://groovy.codehaus.org/JSR-223+access+to+other+JVM+languages
> http://sayspy.blogspot.com/2009/03/interacting-between-jvm-lang-here-and.ht…
>
> Are there any examples, documentation, or suggestions of writing a "script
> macro" to call a new jar in WEB-INF/lib ?
Well all you need is drop the JSR223 jar in WEB-INF/lib and then you
can use the new language using the script macro:
http://code.xwiki.org/xwiki/bin/view/Macros/ScriptMacro
Then if you want you can write a wrapping macro such as we've done for
groovy and jruby so that it can be called with {{clojure}} instead of
{{script language="clojure"}}.
> Any other special magic I should know? Does anything from the above suggest
> that Clojure couldn't be used as an Xwiki scripting language, replacing
> cases where Groovy scripting might normally be employed?
>
> Niels
> http://nielsmayer.com
>
> PS: Here's examples of easy "scripted java" programming you can do in
> Clojure (note the helpful parallelism constructs):
> http://travis-whitton.blogspot.com/2009/07/network-sweeping-with-clojure.ht…
> http://travis-whitton.blogspot.com/2009/06/clojures-agents-scientists-monke…
>
> It could be very useful to employ massive parallelism via such Clojure
> scripts, which could achieve a xwiki-based web portal performance akin to
> Yahoo's, Google's, etc. For example, the following describes how Yahoo works
> -- and would be quite easy to implement this kind of processing "for free"
> in Clojure with very little code:
>
> http://research.yahoo.com/files/pnuts.pdf
I'm definitely +1 to make it part of the XWiki platform (same as for
jruby) if you develop it. Similar to jruby I don't think we should
package it in the default WAR though but as an optional download to
install (will be even easier with the app manager).
Thanks
-Vincent
>
> The component responsible for multi-record requests is called the
>>
>> scatter-gather engine, and is a component of the router.
>> The scatter-gather engine receives a multi-record request,
>> splits it into multiple individual requests for single records
>> or single tablet scans, and initiates those requests in parallel.
>> As the requests return success or failure, the scatter-gather
>> engine assembles the results and then passes them to the
>> client. In our implementation, the engine can begin streaming
>> some results back to the client as soon as they appear.
>> We chose a server-side approach instead of having the client
>> initiate multiple parallel requests for several reasons. First,
>> at the TCP/IP layer, it is preferable to have one connection
>> per client to the PNUTS service; since there are many clients
>> (and many concurrent processes per client machine) opening
>> one connection to PNUTS for each record being requested
>> in parallel overloads the network stack. Second, placing this
>> functionality on the server side allows us to optimize, for
>> example by grouping multiple requests to the same storage
>> server in the same web service call.
>>
>> Range queries and table scans are also handled by the
>> scatter gather engine. Typically there is only a single client
>> process retrieving the results for a query. The scatter gather
>> engine will scan only one tablet at a time and return results
>> to the client; this is about as fast as a typical client can
>> process results. In the case of a range scan, this mecha-
>> nism simplifies the process of returning the top-K results
>> (a frequently requested feature), since we only need to scan
>> enough tablets to provide K results. After returning the
>> first set of results, the scatter-gather engine constructs and
>> returns a continuation object, which allows the client to re-
>> trieve the next set of results. The continuation object con-
>> tains a modified range query, which, when executed, restarts
>> the range scan at the point the previous results left off. Con-
>> tinuation objects allow us to have cursor state on the client
>> side rather than the server. In a shared service such as
>> PNUTS, it is essential to minimize the amount of server-
>> side state we have to manage on behalf of clients.
Hi,
I'd like to propose to release XE 1.9.2 on 27th of July (next Monday).
There are already a good number of fixes:
http://jira.xwiki.org/jira/browse/XWIKI/fixforversion/11171
Other issues not done can be moved to 1.9.3 (which could be released
in 2 weeks time).
Here's my +1
Thanks
-Vincent