Hi devs,
As we've already agreed we only keep the trunk + 1 one stable branch.
I've noticed we still have 1.8 and 1.9 branches in our SVN repo.
I'm going to remove them later today.
Please shout if you have a good reason not to remove them.
Note: We still have the tags of course...
Thanks
-Vincent
On Mon, Nov 30, 2009 at 10:00 AM, Fabio Mancinelli
<fabio.mancinelli(a)xwiki.com> wrote:
> On Nov 30, 2009, at 3:08 AM, Sergiu Dumitriu wrote:
>>
>> Why do you pass the component manager around? Each component
>> implementation can declare a dependency on ComponentManager if it needs it.
>>
>>> + String execute(ComponentManager componentManager, String... arguments) throws Exception;
>>> +}
>>
> Right.
> It's a leftover because before I wasn't implementing commands as components.
Even if you're not using Components, passing the CM is still an
implementation details that should not be shown in a user-API
signature. If you're not using Components you'd pass it in the
constructor of your command.
Thanks
-Vincent
On 11/29/2009 11:56 PM, fmancinelli (SVN) wrote:
> Author: fmancinelli
> Date: 2009-11-29 23:56:23 +0100 (Sun, 29 Nov 2009)
> New Revision: 25362
>
> Added:
> contrib/people/fmancinelli/
> contrib/people/fmancinelli/xwiki-command/
> contrib/people/fmancinelli/xwiki-command/README.txt
> contrib/people/fmancinelli/xwiki-command/pom.xml
> contrib/people/fmancinelli/xwiki-command/src/
> contrib/people/fmancinelli/xwiki-command/src/main/
> contrib/people/fmancinelli/xwiki-command/src/main/java/
> contrib/people/fmancinelli/xwiki-command/src/main/java/META-INF/
> contrib/people/fmancinelli/xwiki-command/src/main/java/META-INF/MANIFEST.MF
> contrib/people/fmancinelli/xwiki-command/src/main/java/org/
> contrib/people/fmancinelli/xwiki-command/src/main/java/org/xwiki/
> contrib/people/fmancinelli/xwiki-command/src/main/java/org/xwiki/command/
> contrib/people/fmancinelli/xwiki-command/src/main/java/org/xwiki/command/Command.java
> contrib/people/fmancinelli/xwiki-command/src/main/java/org/xwiki/command/CommandResource.java
> contrib/people/fmancinelli/xwiki-command/src/main/java/org/xwiki/command/commands/
> contrib/people/fmancinelli/xwiki-command/src/main/java/org/xwiki/command/commands/LS.java
> contrib/people/fmancinelli/xwiki-command/src/main/resources/
> contrib/people/fmancinelli/xwiki-command/src/main/resources/META-INF/
> contrib/people/fmancinelli/xwiki-command/src/main/resources/META-INF/components.txt
> Log:
> [Initial import] A proof of concept for a "command line" XWiki interface based on HTTP.
>
>
> Added: contrib/people/fmancinelli/xwiki-command/README.txt
> ===================================================================
> --- contrib/people/fmancinelli/xwiki-command/README.txt (rev 0)
> +++ contrib/people/fmancinelli/xwiki-command/README.txt 2009-11-29 22:56:23 UTC (rev 25362)
> @@ -0,0 +1,9 @@
> +This module adds a resource to the XWiki REST subsystem for executing commands.
> +This resource accepts text/plain POSTs containing a command line and sends back
> +responses in text/plain containing the result of the execution of the command.
> +
> +A simple "ls" command which lists the spaces in a wiki is provided.
> +
> +Clients can send commands using cURL in this way:
> +
> +curl -d "ls" -H "Content-type: text/plain" http://localhost:8080/xwiki/rest/command
>
> Added: contrib/people/fmancinelli/xwiki-command/src/main/java/org/xwiki/command/Command.java
> ===================================================================
> --- contrib/people/fmancinelli/xwiki-command/src/main/java/org/xwiki/command/Command.java (rev 0)
> +++ contrib/people/fmancinelli/xwiki-command/src/main/java/org/xwiki/command/Command.java 2009-11-29 22:56:23 UTC (rev 25362)
> @@ -0,0 +1,28 @@
> +package org.xwiki.command;
> +
> +import org.xwiki.component.annotation.ComponentRole;
> +import org.xwiki.component.manager.ComponentManager;
> +
> +/**
> + *<p>
> + * This is the command interface. Each command should implement this interface and be annotated with a @Component
> + * annotation for declaring its name. Don't forget to add the FQN of the command in the META-INF/components.txt
> + * otherwise it will not be visible.
> + *</p>
> + */
> +@ComponentRole
> +public interface Command
> +{
> + /**
> + *<p>
> + * Execute the command
> + *</p>
> + *
> + * @param componentManager The XWiki component manager for looking up the XWiki components needed for executing the
> + * command.
> + * @param arguments The arguments extracted from the command line.
> + * @return A String containing the result of the execution of the command.
> + * @throws Exception
> + */
Why do you pass the component manager around? Each component
implementation can declare a dependency on ComponentManager if it needs it.
> + String execute(ComponentManager componentManager, String... arguments) throws Exception;
> +}
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi Devs, Hi Marius,
Could you give me some clues how to generate and save a page url that could
locate to the position of a certain title/section of the article within the
WYSIWYG editor, for example like this url,
http://platform.xwiki.org/xwiki/bin/view/DevGuide/APIGuide#HAccessobjectsin…,
click this link it will bring me to "Access objects in a page" subtitle.
What I want to achieve is that in the WYSIWYG editor after I highlighted a
sentence and clicked the Requirement tree node, it will highlight the
background of the text and generate a link to the highlighted text, so this
generated link could bring designer/system maintainer to the context of the
document.
Could you point me to the place of your WYSIWYG editor source code that I
need to add/change? Do you know how can I get the value of the selected
text, should I directly right javascript or should I modify your WYSIWYG
source code?
Thank you so much! Have a nice new week!
Jue Wang (Leon)
Hi all!
How are you?
I apologize that I wasn't so active recently. I spent all my time with
tasks from my job and my Master.
Now I have a little bit more free time (in the evenings and weekends) and I
would like to continue the XOO project. I'm not clear what should I exactly
do next and maybe you can help me with your feedback and ideas.
I'd really like to contribute again to the XWiki software . Although I was
not so happy with the API from OpenOffice , last summer was a really
interesting experience for me.
Thank you,
Cristina S.
Hi,
I'd like to commit a new standalone tool,
xwiki-tool-standards-validator, it allows to run XHTML and Dutch Web
Guidelines validation tests (only a few rules for the moment) on an
InputStream.
This tool will be used by a new enterprise module that I'll commit
right after, xwiki-enterprise-test-webstandards which runs the
validators on every pages present in the XE distrib.
Here's my +1,
JV.
Hi Thibaul, all
Something easy to do that would contribute to reduce the number of CSS
files is to concatenate all the WYSIWYG CSS files from the various
plugins at build time (there are more than 10 AFAIK). Marius, have you
looked into this? Do you know if this could be done in the 2.1 timeframe ?
Note that the target of 1 CSS and 1 JS is pretty challenging for XWiki
as we are also making it a modular software where CSS and JS extensions
can be conditionally loaded on some (not all) of the pages. Something to
investigate for JavaScript extensions could be a dynamic JS loading
mecanism, a la dojo
(http://dojocampus.org/content/2008/10/09/dojo-module-packaging-and-loading/)
Jerome.
PS: I put devs in copy as this is more a developer topic.
On 11/5/09 5:28 PM, Thibaut Camberlin wrote:
> Hi all,
>
> Page Loading time is a very important criteria when developing a web site.
> According to a recent
> survey<http://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)
>
> Someone interrested in working on this with me ?
>