Hi all,
i've changed all headers of xwiki to LGPL.
I do it by script, so if you find a mistake, tell me. I use the svn to
generate the @author header, so if someone commit the file for you,
tell me, I will add your name to the header.
Jérémi
--
Blog: http://www.jeremi.info
LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724
Project Manager XWiki: http://www.xwiki.org
skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com
Isn't it a potential security hole for
com.xpn.xwiki.api.XWiki.searchDocuments(*) to return a list of
XWikiDocument instead of wrapping them in a Document like the other
API methods do?
Matt
Hello,
I used to code in php/mysql. But since i discovered xwiki, I really
think it's more powerful.
But, in my opinion there is a thing can be upgrade to facilitate
developtement for webmaster.
as we know There is several URLS :
* view
* edit
* inline
* save
* login
* logout
and others like :
* addcomment
* addobjects
* upload
* delete
I was thinking why some URLs which don't show anything to the users
should not be replace by a more complete Save action programming.
When you save, you can decide
- in which page
- which content
- which objects
- which Files
- can be add, edit, or delete
It will be more clear to understand and to program this kind of thing ?
"Vive xwiki !"
Antoine
Hello!
While implementing something I came around the BaseProperty and while
reading the code I found several strange things. I agree with the
comment above BaseProperty that this class should be abstract, mainly
because getValue() always returns null. Then PropertyClass can be made
abstract as well.
But then I'm stuck a bit with the stuff in XWikiHibernateStore, which
creates also new instances of BaseProperty and PropertyClass. It looks
to me like the code there is simply cloning those objects - but why is
it not using clone() then? Well, it is doing some strange stuff there
anyway.
While looking at all this stuff, I also found several other things which
could be cleaned up to avoid bugs, to increase performance and to make
things easier understandable.
But before I get really started: is this kind of work wanted? I am aware
that with a code base of this size it is easy to break things...
--
Michael Reinsch <mr(a)uue.org> http://mr.uue.org/
------------------------------------------------------------------------
Hi XWiki developers,
I'm preparing a small plugin for thumbnails as explain in my previous mail.
The image is resized by adding a parameter heigth at this end of a download
URL (eg :xwiki/bin/download/Photos/Seychelles1999/DSC04010.JPG?height=550)
To call the plugin I need to add a piece of code in DownloadAction class.
Do you think :
- is it better to add the dependancy to the plugin in the DownloadAction class
such as :
// Sending the content of the attachment
- byte[] data = attachment.getContent(context);
+ byte[] data = null;
+
+ // Resize if imageplugin is on
+ ImagePlugin imageplugin = (ImagePlugin)
context.getWiki().getPlugin(
+ "image", context);
+ if ((request.getParameter("height") != null) &&
(imageplugin != null)) {
+ try {
+ int height =
Integer.parseInt(request.getParameter("height"));
+ data = imageplugin.createThumbnail(attachment,
height, context);
+ response.setContentType("image/png");
+ } catch (NumberFormatException e) {
+ } catch (Exception e) {
+ e.printStackTrace();
+ }
+ }
+
+ if (data == null) data = attachment.getContent(context);
+
- or is it better to add a generic method in the plugin Interface class
(XWikiPluginInterface) with a method : startDownloading(byte[] data,
XWikiContext context) and to call it after in DownloadAction ?
Regards
--
Xavier MOGHRABI - Consortium ObjectWeb
Dear XWiki Dev,
I try to create a plugin which should reduce the image size to have a kind of
thumbnail feature.
To do that I've created a plugin a part of the code is hereunder.
To call the plugin I've added in xwiki.cfg the complete name of the class (and
also a parameter about the cache size). The plugin uses the cache service.
At runtime my plugin is set by this code :
Plugin imageplugin = (ImagePlugin) context.getWiki().getPlugin("image",
context);
But I don't have the cache service working, the attribute imageCache is null.
It seems that the init method is never called.
Any idea is welcome.
Regards
--
Xavier MOGHRABI - Consortium ObjectWeb
package com.xpn.xwiki.plugin.image;
public class ImagePlugin extends XWikiDefaultPlugin implements
XWikiPluginInterface {
private static String name = "image";
private XWikiCache imageCache;
private int capacity = 50;
private static Log mLogger = LogFactory.getFactory().getInstance(
ImagePlugin.class);
public ImagePlugin(String name, String className, XWikiContext context) {
super(name, className, context);
}
/**
* Allow to get the plugin name
*
* @return plugin name
*/
public String getName() {
return name;
}
public void init(XWikiContext context) {
super.init(context);
try {
String capacityParam = context.getWiki().Param(
"xwiki.plugin.image.cache.capacity");
capacity = Integer.parseInt(capacityParam);
} catch (NumberFormatException e) {
}
imageCache = new OSCacheCache(capacity, true, "temp/imageCache");
}
public void flushCache() {
if (imageCache != null)
imageCache.flushAll();
}
...
}
Hi,
I don't know if you remember it, but a while ago we have decided to
switch from GPL to LGPL.
Changes in headers have never been done. So I start to do it
yesterday. Before I need your opinion on some rules:
• You give you credit to XpertNet. If you give to XpertNet your
credit, it's simple for XpertNet to manage licensing issues. We can't
give the credit to XWiki, because it's not an entity, and I don't
think ObjectWeb accept credit.
• We can use the javadoc tag @author for putting your name on. Or
simply a contributors.txt on the root of the svn, a page on the wiki,
on the Jira's task and the SVN (because you commit it).
More information about why giving your credit to Xpertnet:
http://clirr.sourceforge.net/contributing.html
Jérémi
--
Blog: http://www.jeremi.info
LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724http://www.xwiki.org
skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com
Hi All,
It's time to elect the project head. I suggest:
* Ludovic Dubost as the project Leader
* Jérémi Joslin as the project Manager
I know, it's not common to have a leader and a manager, but Ludovic is
busy with the business, so he can't manage the project but he is the
one who know the best XWiki and his skills are better then mine. I
will help him to manage the project.
Only committers can vote. You vote with +1, 0 or -1.
* +1: Yes
* 0: I don't know
* -1: No and explain why.
Like we don't have rules for voting now, I choose this for the first vote:
The vote is over in 72h or when all committers have vote.
Jérémi
--
Blog: http://www.jeremi.info
LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724http://www.xwiki.org
skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com
Hi,
Assuming "Always Authenticate on Viewing" is enabled in the wiki
preferences, should XWikiAuthServiceImpl.authenticate(user, password,
context) actually get called on every page view? Or is some cookie
used to prevent this?
I ask because this behaviour seems to have changed on my local xwiki
installation, and I'm not what I've done to cause the change (it used
to get called on every page view, and doesn't any more).
Thanks,
Robin.
Hi,
So, I'm proud to announce the list of XWiki committers:
* Matthew Conway
* Stephane Laurière
* Hans Gerwitz
* Vincent Massol
* Erwann Arzur
* Ludovic Dubost
* Jérémi Joslin
They will help to improve XWiki and will not depend on another people
to patch something. They also can vote for changes on XWiki. Not only
one people take a decision, it's the committers team who take it by
votes. Some rules will be written soon.
Jérémi
--
Blog: http://www.jeremi.info
LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724http://www.xwiki.org
skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com
I'm running into an issue with the 200K character limit for
xwikidoc.xwd_archive.
Normally, a diff is generated, so this column doesn't grow too big.
However, if the document is always a single long line, the diff is
just that line everytime, and xwd_archive grows very quickly.
Any thoughts on how I can fix this aside from just increasing the limit?
Matt
Hi,
There is 2 possibilities about the payement:
* first, Someone who propose the bounty is in charge of paying it at the end.
* second, the one who propose the bounty pay first the prize for the
bounty to a paypal account of XWiki.
For me the second one is better, but you have to advance the money.
And with the second possibility several people can make a donation to
a bounty if they are interested in.
some samples of rules :
* http://www.os2world.com/bounties/rules.php
* http://www.morphzone.org/modules/bounty/
* http://www.voip-info.org/wiki/view/Asterisk+bounty
* https://wiki.ubuntu.com/BreezyBounties
What do you think about this? I prefer the morphzone way to do it with
ubuntu rules.
Jérémi
On 1/29/06, Stéphane Laurière <slauriere(a)mandriva.com> wrote:
> Hi Jérémi,
>
> Introducing bounties for XWiki would be great, I think!
>
> Stéphane
>
> jeremi joslin wrote:
> > Hi everyone,
> >
> > What do you think about enabling anyone to suggest bounty on XWiki ?
> >
> > Example:
> > I need a script for listing all the page in the wiki who contain the
> > word "hate". I don't know how to do it. I'm ready to pay 50$ for this.
> >
> > We need to define some rule, but what do you think about this idea?
> >
> > For example, ubuntu:
> > http://www.ubuntulinux.org/community/bounties/
> >
> >
> > Jérémi
> > --
> > Blog: http://www.jeremi.info
> > LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724
> > http://www.xwiki.org
> > skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> > --
> > You receive this message as a subscriber of the xwiki-dev(a)objectweb.org mailing list.
> > To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
> > For general help: mailto:sympa@objectweb.org?subject=help
> > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
>
>
>
> --
> You receive this message as a subscriber of the xwiki-users(a)objectweb.org mailing list.
> To unsubscribe: mailto:xwiki-users-unsubscribe@objectweb.org
> For general help: mailto:sympa@objectweb.org?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
--
Blog: http://www.jeremi.info
LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724http://www.xwiki.org
skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com
I downloaded xwiki-0.9.840-src.tar and got the error:
tar: A lone zero block at 98831
I used to get this when building tars from Ant - I don't think it
breaks anything but it just looks bad. I take it xwiki isn't tarred
up using gnu tar?
Alistair
Hi everyone,
Yesterday the ObjectWebCon'06 announced the awards of the best use case
contest... and the usage of XWiki by the Mandriva Club was awarded the
best Enterprise Java Use Case award!
Many thanks to all of you, and special thanks to the XWiki team!
I remind you that if you're an XWiki contributor we'll be happy to offer
you a free Club account. The Club credits are available at this URL:
http://club.mandriva.com/xwiki/bin/Main/Credits
Via XWiki, the foundations have been laid down for an enhanced user
experience in the near future on the Club. We plan to develop many new
advanced features in 2006 on top of XWiki, in particular within Nepomuk
project (http://nepomuk.semanticdesktop.org).
Thanks again, and long life to the XWiki project!
Stéphane
Hi,
We want to change the way the community work.
We want to create 2 groups:
* One group of developer. A developer is a user who contributes to the
project in the form of code or documentation. They take extra steps to
participate in a project, are active on the developer mailing list,
participate in discussions, provide patches, documentation,
suggestions, and criticism. Developers are also known as contributors.
(Definition from
http://www.apache.org/foundation/how-it-works.html#roles)
* One group of committer around XWiki.
A committer is a developer that was given write access to the code
repository. Not needing to depend on other people for the patches,
they are actually making short-term decisions for the project.
We also want to change the way to become committer on XWiki. Before
becoming committer on XWiki, you have to "earn" the merit to be part
of the development community. For those of you who are already
committer on XWiki, you will keep this right if you want. You just
have to send me a mail OFF LIST before the 9february to stay committer
and tell me why you want to stay committer.
We will write some rules to lead the project soon.
what do you think about that?
--
Blog: http://www.jeremi.info
LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724http://www.xwiki.org
skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com
Hi the XWiki Team,
I found in the mailing list archives that you are planning to use maven to
build xwiki. I am a committer to the apache pluto project, which uses
maven2. Thus i got some experience on maven 2. (Mr. Vincent Massol must be a
maven master, since he is on the maven team :) I would like to help you
migrate to maven.
I checked out the xwiki source from subversion, and am trying to re-organize
the project layout and create pom.xml files. Currently i am still dealing
with the dependencies. I would like to propose to separate the xwiki project
into small subprojects, and decouple the APIs from the implementation (such
as user api and different implementations, plugin api and different plugin
implementations, etc.). That will make the source more clear and more
readable.
I don't know how to help on this topic. Re-organizing the project layout
introduces too many modifications on the project, which may have a lot of
impacts on the current development, and it's difficult to generate svndiff
and create patches. I would like to know if it is possible to apply for
joining the dev team and create a new branch in svn for the maven migration.
I am taking a look at the JCR spec currently, since I created a java wiki
engine project (
http://people.apache.org/~zheng/elsie/<http://people.apache.org/%7Ezheng/elsie/>)
and am thinking of refactoring it using JCR and apache jackrabbit. I
found
that you are also planning to implement the xwiki repository using JCR. I
would like to help and contribute to this subproject too.
Best regards.
--
ZHENG Zhong
- http://heavyz.blogspot.com/
- http://people.apache.org/~zheng/ <http://people.apache.org/%7Ezheng/>
I noticed that XWIKI-177, an issue I reported, was recently marked "Won't
fix". A comment was made to the effect that the current behavior isn't a
bug.
This issue affected my design of my "XWiki Aggregate Document PDF Generator"
(http://www.xwiki.org/xwiki/bin/view/Dev/AggregateDocs). I wanted to use the
xwiki.getDocument() function to retrieve documents for inclusion in the
generated PDF, but due to XWiki's current behavior, I had to resort to using
HTTP downloads (a much slower and less robust approach).
I guess I'm having a hard time understanding why the current behavior
described in XWIKI-177 is the intended behavior. It really seems like a bug
to me.
Stephen