On Dec 1, 2009, at 3:00 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2009-12-01 03:00:52 +0100 (Tue, 01 Dec 2009)
> New Revision: 25387
>
> Added:
> platform/xwiki-plugins/trunk/blog/
> platform/xwiki-plugins/trunk/blog/pom.xml
> platform/xwiki-plugins/trunk/blog/src/
> platform/xwiki-plugins/trunk/blog/src/main/
> platform/xwiki-plugins/trunk/blog/src/main/java/
> platform/xwiki-plugins/trunk/blog/src/main/java/com/
> platform/xwiki-plugins/trunk/blog/src/main/java/com/xpn/
> platform/xwiki-plugins/trunk/blog/src/main/java/com/xpn/xwiki/
> platform/xwiki-plugins/trunk/blog/src/main/java/com/xpn/xwiki/
> plugin/
> platform/xwiki-plugins/trunk/blog/src/main/java/com/xpn/xwiki/
> plugin/blog/
> platform/xwiki-plugins/trunk/blog/src/main/java/com/xpn/xwiki/
> plugin/blog/BlogPlugin.java
> platform/xwiki-plugins/trunk/blog/src/main/java/com/xpn/xwiki/
> plugin/blog/BlogPluginApi.java
> Modified:
> platform/xwiki-plugins/trunk/pom.xml
> Log:
> XABLOG-63: Create a Blog Plugin and Adjust the Blog Application to
> use it
> Adding the blog plugin
>
[snip
>
> +/**
> + * Blog Plugin is a plugin that allows to manage Blog Applications.
> It allows to create, update, list and delete blog entries.
> + *
> + * @version $Id$
We're missing @since tags I think.
Thanks
-Vincent
Hi devs,
following a discussion with Fabio about the second desired feature for the
annotations, namely the ability to add annotations on any document, no matter
how its content is generated, we came up with the solution described at
http://dev.xwiki.org/xwiki/bin/view/Design/AnnotationFeature#HSolution1stor…
, the main idea being that annotations would be defined by their selected text
and a context (as opposed to offsets) and would be identified to be rendered in
a document on a serialization of the transformed XDOM of the document, this way
taking into account any macro rendering, document inclusion, etc.
WDYT about this solution?
Also, because the implementation of this, though relatively localized, comes
together with refactor and cleanup of the annotations module (update everything
so that annotations don't store and use offsets anymore, remove classes &
functions which are not needed in this simplified process), I propose to include
this improvement in version 1.0 of the annotations module (so that we don't
cleanup and release what we know for sure we'll delete) and push the 1.0 version
further to mid to end December.
here's my +1 for this,
WDYT?
Happy coding,
Anca
Hi,
One of the WCAG requirements is to have all our CSS Level 2.1 valid.
I saw we have exceptions on the elements we cover in our validation and I
would like to know your opinion about: *opacity* CSS propriety.
*Opacity* is a CSS 3 valid property, but not a CSS 2.1.
The main components (that I know) that can be affected by not having *
opacity* are: modalPopup.css (for Ctrl+G "Go To" feature) and lightbox.css
(for the boxes in Administation: Users, Groups). Without *opacity* they look
disconnected from XWiki.
*Opacity* used to be used in Panel Wizard, but got removed because of the
WCAG and because it didn't changed much on an aspect level. It can be used
in lots of places like tooltips, use to be in WYSIWYG disabled buttons etc.
The main problem about *opacity* is that if we are gonna make it an
exception, because of IE6, we are gonna need to make other proprieties
exceptions (*filter, zoom*).
IE’s CSS uses *filter* instead of *opacity* and also needs (for some
elements) *zoom* propriety in order to apply it correctly.
I need to know your opinion in order to complete our CSS files validation.
Thanks,
Caty
Hi,
I'd like to move the xwiki-plexus module to the contrib repository.
The rationale is:
- plexus is going EOL (Jason Van Zyl has clearly mentioned it was dead
and he's favoring Guice)
- in the future we're interested in moving towards Guice/OSGi
- it's too much effort to maintain several implementations in the core
development branch
- with the component isolation refactoring I'm doing I'd need to
implement that for Plexus which isn't trivial and I'd rather not spend
time on it
- if users are interested in using XWiki with Plexus they'd be able to
use that contrib module to get started
Here's my +1
Thanks
-Vincent
Hello, I want to include this code in a macro in a 1.3 version...but I don´t find any example of how to do this... Could you help me and tell me if there is any way to do this??
The URL will be the parameter of the macro...
<%
try {
URL timelineURL = new URL("http://ws.geonames.org/search?name_equals=den&fcode=airp&style=full");
def connection = timelineURL.openConnection();
def xml = connection.content.text
def geonames = new XmlSlurper().parseText(xml)
def result = [:]
result.name = geonames.geoname.name as String
result.lat = geonames.geoname.lat as String
result.state = geonames.geoname.adminCode1 as String
result.lng = geonames.geoname.lng as String
result.country = geonames.geoname.countryName as String
//print ("Nombre: " + "\n")
//print result.name + "\n"
//print ("\n")
//print ("Latitud: " + "\n")
//print result.lat + "\n"
//print ("\n")
//print ("Longitud: " + "\n")
//print result.lng + "\n"
//print ("\n")
//print ("Estado: " + "\n")
//print result.country + "\n"
print ("{" + "code}\n")
print xml + "\n"
print ("{" + "code}\n")
print ("{" + "table}\n")
print "Nombre" + "|" + "Latitud" + "|" + "Longitud" + "|" + "Estado"
print ("\n")
print result.name + "|" + result.lat + "|" + result.lng + "|" + result.country
print ("{" + "table}\n")
}
catch(Exception e) {print e.message}
%>
Thank you.
------------------------------------------------------------------
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin
group liability cannot be triggered for the message content. Although
the sender endeavours to maintain a computer virus-free network,
the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion confidencial
destinada solamente a la(s) persona(s) mencionadas anteriormente
pueden estar protegidos por secreto profesional.
Si usted recibe este correo electronico por error, gracias por informar
inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin
no se hace responsable por su contenido. Su contenido no constituye ningun
compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus.
------------------------------------------------------------------
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/