Hai,
I am an undergraduate student at University of Moratuwa, Faculty of
Information Technology. I have experience working with Jabber protocol and I
am interested in knowing more information about this idea on* integrating
Jabber, Google Talk and Skype with XWiki*. I am new to Xwiki project and
learning it these days.
Few things I need to know are as follows, actually I need to clarify whether
I got the idea correctly
1) Xwiki users should be able to save their jabber logins at their profile
page including password for the jabber id and also it should allow users to
enter any private jabber server details as well
2) Once user loggs in it will login to the specified accounts
3) At some where on wiki web page we need to display the chat list
* - It includes all Google Talk, Jabber or Skype contacts - I mean
XWiki user can chat with any of his im friends from this chat tool, this
will be a private chat
* - XWiki users could be invited to join for a group chat by someone
who creates a group, by using the chat tool on web page
*
*This is what I have understood by the project idea, can you *please
correct me if there is any confusion between what I have understood with the
idea given at XWiki site itself*
*Ques1 & 2*
What is meant by 'tool should allow to list the chats actively launched or
monitored by the wiki' ?
What is meant by 'A Jabber AJAX chat tool can also be integrated for users
not having Jabber or Google talk installed' ?
I could not understand above two sentenses fully that were at XWiki ideas
page. Please can any body clarify me on this.
Thank you,
*H.T.M. Gamage **
*Student,* *
Faculty of Information Technology,
University of Moratuwa,
SriLanka.
Mobile: +94 (71) 5518852
ChatID: tharindufit
Blog : tharindufit.wordpress.com
Hi!
My name is Cristina Scheau , a graduating student in Computer Science at
“Politehnica” University from Bucharest. I worked 6 months on .NET
framework at http://bsgroup.ro/ , coding in VB.NET (most part) , and in C#
some features. I also worked 6 months at http://www.amamobile.com/ as
JAVA Programmer. Last summer I was intern at http://www.crestatech.com in
Santa Clara, CA, where I developed an application using C and VC++. I’ve
also worked at some personal projects using JavaScript, AJAX,
HTML,PHP,antlr.
I am interested in more Xwiki projects but especially in Xwiki integration
with Open Office. I have some questions regarding this topic.
1. For the server side, can one reuse the code from Xword?(or is it
desired a totally new implementation?)
2. The project includes also the Xwiki integration with Open Office
spreadsheet and presentation or just with OO Writer?
Another problem ( i don’t know if this is the right place to post) is that,
I suggest a small improvement of UI for Xword. If the user cannot connect
to the wiki server (changing the Xword options), a notification message
should be displayed. It is a little bit confusing displaying only an empty
navigation space and all the action buttons in the ribbon being enabled ( I
saw that the buttons issue is set in JIRA so i won’t give details). I mention
that I used Xword 1.0.0.66.
Thanks in advance,
Cristina Scheau
Hi devs,
In the early days of XWiki, we used to put @author tags inside Java
source files. Later on, we decided that this is a bad practice, and
started removing them, on the premise that we will have a NOTICE file
listing all authors and contributors. And although we managed to remove
almost all @author tags, the NOTICE file doesn't list any developers or
contributors, listing just XWiki as a company as the copyright holder.
This would be OK if we had a policy stating that all Intellectual
Properties belong to XWiki. But we don't.
So, shouldn't we make an official policy? Here are some alternatives:
I. Individual copyright
- we list developers
- we list all contributors and their contributions
- contributors retain the IP for their submitted code
II. Collective copyright
- we list developers
- we list all contributors and their contributions
- XWiki as a collective is the only copyright holder, and we specify
that any submitted patch will be the property of the community
- having a non-profit organization would help
III. Umbrella copyright with acknowledgments
- we don't list developers
- we list all contributors (including devs)
- XWiki SAS as a company is the only copyright holder, and we specify
that any submitted patch will be copyrighted by XWiki
IV. Umbrella copyright, no acknowledgments
- we don't list developers or contributors (in the pom, the web hall of
fame can and should still exist)
- XWiki SAS is the only copyright, and we specify that any submitted
patch will be copyrighted by XWiki
Currently we're doing IV, but we don't make this explicit. I'd vote for
II, as this is a more Open way.
On the technical side, Maven already provides support for listing
contributors and developers, for the moment these sections are empty. We
can change the NOTICE template to automatically list them.
An important question is where do we list people?
- In the parent pom, which implies frequent releases of the parent,
which means frequent version changes for all the other modules.
- In each project's pom, which means that new contributions will only
require releasing the affected module, but it will be harder, if not
impossible, to aggregate contributions.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi Devs,
As reported @ http://jira.xwiki.org/jira/browse/XWIKI-3288 and
http://jira.xwiki.org/jira/browse/XAOFFICE-10, OfficeImporter wysiwyg plugin
has issues with importing some documents on some platforms.
When importing documents from the wysiwyg plugin, the approach we follow is
to upload the file that need to be imported into the current page and then
import the corresponding attachment. But this scheme has two problems:
1) If the file being uploaded contains special characters, the attachment
name will be different from the file name. And this will cause the
officeimporter to fail because after uploading the file we will be making a
second request to import the attachment with the original file name (but now
there is no such attachment).
2) The fileName returned by GWT FileUpload widget is different from Firefox
to IE. While Firefox returns the file name, IE returns the whole file path.
This causes the officeimporter wysiwyg plugin to fail completely under IE
(File Import Tab only).
The solution I can see is the following,
1) Upload the file as an attachment just as before.
2) Make a second rpc call. This RPC call will import the latest attachment
to the current page by the current user. This way we don't need to worry
about crappy file names and browser specific stuff.
I know it's a bit ugly but it will work.
WDYT?
Thanks.
Hello,
I am inderested with "XWiki Jabber, Google Talk, Skype Integration" idea.
There Jabber and gtalk both are XMPP based chat server. For any XMPP
we can use smack api. personal servers also can be integrated, my idea
is to create a common interface for any XMPP based chat server.
And for skype intregration can be possible using skype client api.
I was worked in a project of social networking server using J2EE,
which has a module for chat with its own XMPP server(Open Fire). I was
worked on this module.
This past experience make me interested for the "XWiki Jabber, Google
Talk, Skype Integration" idea. Hope I have the ability to contribute a
little to open source XWiKi project.
--
--------------------------------------------------------------
Regards,
Shamal Roy
For once, let's self-congratulate ourselves. I want to thank everyone
who has participated to the development of the XWiki Enterprise 1.8
release. I know all committers have been extremely busy, working night
and days, and the work they have all achieved is tremendous. Well done
guys!
Thanks
-Vincent
PS: Now let's finish completely this new rendering/wysiwyg for 1.9
final :)
fmancinelli (SVN) wrote:
> Author: fmancinelli
> Date: 2009-03-23 22:15:24 +0100 (Mon, 23 Mar 2009)
> New Revision: 17953
>
> Modified:
> platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiUtils.java
> platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java
> Log:
> XWIKI-3449: Authenticated XWiki user name might be incorrect in XMLRPC login
> XWIKI-3450: Allow guest access to be disabled in XMLRPC
> + /* Check if we must grant access when no token is provided */
> + boolean allowGuest = context.getWiki().ParamAsLong("xwiki.authentication.always", 0) != 1;
> +
Fabio, you are using this parameter wrong. This doesn't mean that only
authenticated users are allowed, but it controls the optimization done
by Thomas, which is to only check the authentication only if there is no
Principal in the session. This parameter forces to check the cookies at
each request instead of using the session object.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hello,
I am planning to submit an application for the upcoming Google Summer of
Code 2009
to develop a collaborative drawing/mapping application for xwiki using
GWT but with
some variation.
I intend to achieve this by developing a web front end to the Compendium
Mapping tool.
Compendium is very flexible concept mapping tool that was recently fully
open-sourced.
It is extensible through the use of 'stencils' which allow for modelling
in other modelling
languages such as UML.
I would like to know what you think about this. Your input will be very
much appreciated.
Kind Regards,
Kojo Gambrah-Sampaney.
Hi all,
When the XWiki class is instantiated, it is done in a way that made it
almost singleton, except for one special case that seems to be for
test purposed, but I feel it is now useless. I am asking because if
XWiki is a singleton, some very often used synchronisation could be
optimized to avoid useless locking.
Here is the excerpt from getMainXWiki() that shows this special case:
String xwikiname = "xwiki";
XWiki xwiki = null;
XWikiEngineContext econtext = context.getEngineContext();
try {
if (context.getRequest().getRequestURL().indexOf("/
testbin/") != -1) {
xwikiname = "xwikitest";
context.setDatabase("xwikitest");
context.setOriginalDatabase("xwikitest");
}
} catch (Exception e) {
}
context.setMainXWiki(xwikiname);
Anyone knows for what it was ? is it still in use ? could it be
removed ?
Denis
On Mar 24, 2009, at 8:36 AM, asiri (SVN) wrote:
> Author: asiri
> Date: 2009-03-24 08:36:32 +0100 (Tue, 24 Mar 2009)
> New Revision: 17954
>
> Modified:
> platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentModelBridge.java
> platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentName.java
> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/
> XWikiDocument.java
> Log:
> XWIKI-3427: Introduce DocumentModelBridge.setParent() method
>
> * Changed tha parameter type of setParent() method from
> DocumentModelBridge to DocumentName.
>
> Modified: platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/
> bridge/DocumentModelBridge.java
> ===================================================================
> --- platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentModelBridge.java 2009-03-23 21:15:24 UTC (rev 17953)
> +++ platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentModelBridge.java 2009-03-24 07:36:32 UTC (rev 17954)
> @@ -30,11 +30,11 @@
> public interface DocumentModelBridge
> {
> /**
> - * Sets the parent document attribute of this document to the
> given value.
> + * Sets the parent document name attribute for this document.
> *
> - * @param parent the {@link DocumentModelBridge} representing
> the parent document.
> + * @param parentName name of the parent document.
> */
> - void setParent(DocumentModelBridge parent);
> + void setParent(DocumentName parentName);
>
> /**
> * Retrieve the full name of the document, in the
> <code>Space.Name</code> format, for example <tt>Main.WebHome</tt>.
>
> Modified: platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/
> bridge/DocumentName.java
> ===================================================================
> --- platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentName.java 2009-03-23 21:15:24 UTC (rev 17953)
> +++ platform/core/trunk/xwiki-bridge/src/main/java/org/xwiki/bridge/
> DocumentName.java 2009-03-24 07:36:32 UTC (rev 17954)
> @@ -77,4 +77,14 @@
> {
> return this.page;
> }
> +
> + /**
> + * Converts this {@link DocumentName} into a string
> representation.
> + *
> + * @return a string representing this {@link DocumentName} of
> the form wiki:space.page.
> + */
> + public String toString()
> + {
> + return getWiki() + ":" + getSpace() + "." + getPage();
This will fail if the wiki, space or page are null.
Note that the serializer should resolve not specified values when
calling getXXX() using current wiki/space. You can do this by
injecting the Execution component and accessing the XWikiContext. Then
you can call getDoc().getSpace() to get the current space. Use
"WebHome" when the page isn't specified and use getDatabase() when the
wiki isn't specified.
Also you should create a DocumentNameSerializer() interface and a
DefaultDocumentNameSerializer implementation:
String serialize(DocumentName();
Then refactor XWikiDocument to use DocumentNameSerializer in
setFullName()
Thanks
-Vincent
> + }
> }
>
> Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> doc/XWikiDocument.java
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/
> XWikiDocument.java 2009-03-23 21:15:24 UTC (rev 17953)
> +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/
> XWikiDocument.java 2009-03-24 07:36:32 UTC (rev 17954)
> @@ -71,6 +71,7 @@
> import org.suigeneris.jrcs.rcs.Version;
> import org.suigeneris.jrcs.util.ToString;
> import org.xwiki.bridge.DocumentModelBridge;
> +import org.xwiki.bridge.DocumentName;
> import org.xwiki.rendering.block.Block;
> import org.xwiki.rendering.block.HeaderBlock;
> import org.xwiki.rendering.block.LinkBlock;
> @@ -570,9 +571,9 @@
> /**
> * {@inheritDoc}
> */
> - public void setParent(DocumentModelBridge parent)
> - {
> - this.parent = parent.getFullName();
> + public void setParent(DocumentName parentName)
> + {
> + this.parent = parentName.toString();
> }
>
> public String getFullName()