Hi everyone,
XWiki is a platform for building wikis. Our default Wiki is a demo
wiki showing what can be done with XWiki. We need to improve it so
that it can stand the competition with the nicest wikis available out
there (and beat them! :)).
I've started a page to gather feedback from users and developers on
what should be improved to make our default wiki better.
It would be nice if you could all help by providing your own feedback
and experience of using XWiki. Feel free to edit and comment on the
following page:
http://www.xwiki.org/xwiki/bin/view/Idea/DefaultWikiImprovements
You can also answer and discuss on this thread if you want but
eventually we'll need to have everything on that page so that all
ideas are gathered together.
Then once we get all this feedback we could start prioritarizing the
different improvements that you suggest.
Thanks everyone for your help
-The XWiki Dev team
Hi,
I'd like to propose the following general principles for the V2
Architecture (http://www.xwiki.org/xwiki/bin/view/Idea/ArchitectureV2):
* XWiki Core API is made only of interfaces. These are all the
interfaces that are implemented by components
* XWiki Components are simple java classes (POJO) implementing the
XWiki interfaces.
* XWiki Core Distributions consist in XWiki Core + some chosen
components. Our current XWiki will be a Core Distribution.
* XWiki Containers are special modules that integrate XWiki in a
given container. For example: integration in Servlet Containers (this
means a web.xml file, servlet context listeners, packaging in a WAR,
etc), in Portlet Container, in J2ME environments, etc. XWiki
Containers depend on XWiki Core Distributions.
Are we ok with this?
If so, I'll move that to http://www.xwiki.org/xwiki/bin/view/Idea/
ArchitectureV2
Thanks
-Vincent
PS: I'll keep sending some Architecture ideas so that we start
shaping up our Architecture document and so that everyone has a clear
idea of what's happening and can participate.
How can I turn off the "shortcut" URLs where /bin/Space/Page is
interpreted as /bin/view/Space/Page?
(Specifically, I'm using mod_redirect to clean up the URL
architecture and need to assume that anything prefixed /bin that
isn't /bin/view needs to be passed through as an action.)
- - -
Hans Gerwitz
http://phobia.com/
Hi All,
I have had a search through the archives and couldn't find much on this
topic, though if there is a thread I have missed please point me in the
right direction and accept my apologies.
My primary question is has the project considered supporting the Apache
2.0 license (or similar)? We generally find this makes integration with
other OSS projects a lot easier as its much less restrictive then
GPL/LGPL which in turn attracts more folks, especially from corporate land.
I understand that LGPL may have been chosen to ensure that the community
is forced to release modifications back to the project, however we have
personally found that this works equally as well with the Apache 2.0
license and removes the extra confusion (we are programmers after all
not lawyers :) ).
A change to Apache 2.0 or a dual license if it was felt needed would
certainly get a big vote from myself.
regards,
Bradley
--
Bradley Beddoes
Lead Software Architect
http://intient.com
Intient - "Open Source, Open Standards"
Hello,
I was wondering if there is a way to tag the whole blog entry and be able to display it later under the Tags page?
Thank you for your time and help in advance.
Regarding http://jira.xwiki.org/jira/browse/XWIKI-929
XWikiRightsServiceImpl list several categories of access rights: view, edit,
comment, delete, register, admin, programming. Each action is mapped to one
of these categories. For example, /viewrev/ is a 'view' action, /propupdate/
is an 'edit' action.
Currently, the most permissive right is "view", but some actions need an
even more permissive right. For example, if the wiki requires authentication
for viewing, then the skin will not be displayed.
We should add a new access right class, "unrestricted", which cannot be used
in the Access Rights Editor, but is used internally to allow some actions to
always be executed, regardless of the access rights of the user.
This raises some security issues, like what if the skin really shouldn't be
accessible? What if a plugin registers an unrestricted action, but nothing
should be unrestricted? For this, we can do the following:
- add an option in xwiki.cfg, 'security.allow_unrestricted', which can
disable unrestricted access; in this case 'unrestricted' behaves as 'view'.
- add an option in XWikiPreferences, which actions are allowed to behave as
unrestricted. Although some plugins by default register an action as
'unres', we can force this action to require 'view' rights.
We need to add this, a lot of users are complaining that the skin isn't
displayed, we just have to decide how do we secure this right.
Sergiu
--
http://purl.org/net/sergiu
Hi-
There exists:
http://jxdbcon.sourceforge.net/
Which apparently supports the setCatalog method that the native driver
lacks... Has anyone tried this, to allow virtual wikis?
-Tom
--
May 4, 1970: Alison Krause, Jeffrey Miller, Sandra Scheuer, William Schroeder.
Hi,
I'd like us to change the skin names for 1.0 B6. We need to do this
before the 1.0 release and now is a good time (actually already a bit
late but that's ok).
Here's the proposal:
1) Rename xwiki10b1/ into albatros/
Question: Should we name it with 2 's'. I've done a google fight and
"albatros" won. Is that correct?
http://www.googlefight.com/index.php?
lang=en_GB&word1=Albatros&word2=Albatross
2) Rename default/ into dodo/
3) Remove new/ altogether
4) Rename xwiki10/ into finch/
5) set xwiki.defaultskin= albatros and xwiki.defaultbaseskin=albatros
WDYT?
Thanks
-Vincent
Hi everyone,
I've just started a page where users can learn how to configure XWiki:
http://www.xwiki.org/xwiki/bin/view/AdminGuide/Configuration
Feel free to add configuration topics in there. XWiki is
configuration rich and for the moment there are only a few
information on there. We need more!
Thanks
-Vincent
I've been using xwiki for a week or so, and now I want to change the
functionality a bit. After importing the recommended xar file, I see
the spaces navigation on the right under the search field. Right now it
shows all spaces (even those the user doesn't have permission to see)
and all pages within that space. I'd like to change the navigation so
that only viewable spaces and top level pages (those without a parent)
are shown. However, I can't figure out what file or files I need to
modify. I'm assuming that it's something in the /skins/xwiki10b1
folder.
Anyone have any suggestions for me?
Thanks,
Eric
Hi,
I'd like to propose disabling stats in the standalone distribution.
I've noticed that stats are bad for performances as they generate
half of all database queries! Thus I'd like to turn them off by
default so that users who install the default standalone distribution
do not suffer from them. I'd like to do this for 1.0 B6.
WDYT?
Thanks
-Vincent
Hi everyone,
Good news, XWiki has been accepted by Google as a participating
organization for GSoC 2007 (http://code.google.com/soc/) :-)
So far we have 17 projects we're proposing to students. They're
listed on http://www.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/.
Just to wet everyone's appetite here's the current list:
- Subversion Integration
- Google Web Toolkit Wykiwyg Editor
- OpenOffice Plugin
- WebDAV API
- Google Docs Integration
- Office Import
- WikiModel Integration
- IDE Editor Integration
- Social Networking Functionalities
- Collaborative tools on top of xwiki
- AJAX Interface Improvements
- Storage Improvements
- ApplicationWizard
- XWikiOffline
- GadgetsIntegration
- FunctionalTestSuite
- Skin wizard
It's also possible to propose new projects (on the same page, at the
bottom of the page there's a new project submission form).
Anyone who's a student can apply at http://groups.google.com/group/
google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-
student-applicants
Even if you're not a student yourself you can help by:
- proposing new ideas of projects
- spreading the word (on your blog, by talking to friends, sending
emails to students you know, etc) that XWiki is looking for bright
students to register for implementing a XWiki project.
Thanks everyone
-Vincent
Hi everybody...
The work with the new wysiwyg architecture has started and we got the
first little results. A very
basic html2xwiki converter was programmed. But I have droped the
handmade converter and used an other aproach: JParsec
I got it running, but I have a question about the copyrights and licences.
As I used a lot of code from
http://jparsec.codehaus.org/Html2Confluence I dont know how the file
header of the source files sould look like.
Thanks,
austriancoder
Hi,
On the user list we've had some brainstorming on how to call XWiki
skins. Everyone seemed to agree that using bird names is a good idea.
Here are some potential names suggested for skins:
- Dove
- Emu
- Kiwi
- Grasswren
- Condor
- Warbler
- Kestrel
- Redtail
- Dodo
- Pigeon
- Albatross
- Booby
- Sparrow
- Finch
- Wren
- Crow
- Turkey
- Thunderbird
- Piasa (a local phenomenon, from a primitive painting on the cliffs
on the eastern shore of the Mississippi, attributed to the Piasa
tribe, which looks rather like a griffin)
- Thunder Chicken
- etc
Here's my +1
Thanks
-Vincent
Hi all,
i'm very interested in xwiki and up to now i'm very satisfied with its features.
I just got one problem. I've got a wiki page with multiple subpages (children) and i want to generate a PDF which contains the wiki page with all its subpages. I couldn't find any option which enables me doing that.
So i want to know if there is any posibility doing that.
Thanks in advance
Christoph
--
"Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ...
Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out
When I set it up so that until I add users to a group manually, they are
only allowed to view and register, XWiki is still allowing them to edit
_their own profile_, no matter what.
This defeats the #1 reason I'm blocking them from editing- the misuse of
my Wiki for Google Ranking Spam.
What they do is, they register, they put a milling links for spam stuff
in their profile comments and such, then the add links from external
places to there, and so forth, to scam Google into thinking lots of
different sites link to them, then Google sees MY domain linking to the
spam sites, and maybe dings me, TOO!
If I set it up for no editing until I add a user to the "editors" group,
I mean NO editing- PERIOD- *especially* including their profile! Which
is *often* where Google Ranking Spammers put their scams!
-Tom
--
May 4, 1970: Alison Krause, Jeffrey Miller, Sandra Scheuer, William Schroeder.
Isn't that sufficiently annoying to either rollback the 1.0B5 or get a
1.0B6 out ASAP ?
Ludovic
Sergiu Dumitriu a écrit :
>
>
> On 3/13/07, *david.weilerthiessen(a)purina.nestle.com
> <mailto:david.weilerthiessen@purina.nestle.com>* <
> david.weilerthiessen(a)purina.nestle.com
> <mailto:david.weilerthiessen@purina.nestle.com>> wrote:
>
> Hi
>
> Just installed the newest and greatest XWiki - 1.0-beta-5.2310 and
> finding that I get a javascript error when I try to save documents.
>
> Message:
> Error: 'wikiEditor' is undefined
>
>
> Happens only when I save from the Wiki editor. When saving from
> the Wysiwyg editor I do not get the error.
>
> Running on Window 2000, Tomcat 5.5, MySQL, IE 6.0 SP1.
>
> My content does save - just have to wait for IE to tell my that it
> has an issue.
>
> Such an obvious error - makes me thing I have a config issue.
>
>
> ... and yet you don't. It was an error in a javascript file, which I
> was aware of, but didn't find any time for it.
>
> Now it's fixed in the trunk, and it will be solved in the next beta.
>
> http://jira.xwiki.org/jira/browse/XWIKI-975
>
>
> --
> http://purl.org/net/sergiu
> ------------------------------------------------------------------------
>
>
> --
> 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
>
--
Ludovic Dubost
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
AIM: nvludo Yahoo: ludovic
On Mar 13, 2007, at 10:02 AM, Pablo Oliveira wrote:
> On Mar 13, Sergiu Dumitriu (JIRA) wrote :
>> P.S.: It's so bad that there's no better way of getting
>> configuration parameters. There should be a separate component,
>> accessible from anywhere.
>
> I really do agree here. This would be a great step towards a more
> modular XWiki. Even if not related: It's really annoying to have
> to pass an XWiki instance to the storage module, just so it can
> retrieve some conf parameters...
We'll have to take a decision here in the future:
1) either we provide a configuration per component
2) or we provide a global configuration
I prefer 1) because:
- a component is encapsulated completely in a JAR
- a component shouldn't see by default configuration from other
components. It's these other components who should offer APIs to
return configuration data if required
-Vincent
Hi committers,
I propose we adopt the SVN configuration from the Maven project.
Right now everyone has his own config which is a pain for several
reasons:
- line encodings are different. For example in Jeremi's commit all
the lines of XWikiMessageTool were modified even though he only
touched a few lines.
- expansion of @version $Id: $
- correct mime types
Here's the file I propose to use: http://maven.apache.org/developers/
svn-eol-style.txt
This is from http://maven.apache.org/developers/committer-
environment.html
If everyone agrees, please install it in your .subversion/ directory
(on unix) and somewhere in your profile under Subversion/ on windows.
I'll also put it up on xwiki.org
Thanks
-Vincent
Hi,
I committed in SVN the automatic inclusion of our Functional Test
suite in the default wiki. Sergiu rightly pointed that we need to
discuss this before including it as it's not completely end user
focused.
Here are the reasons I thought it would be good to be included:
1) It's related to end users if we say that this is a feature to
verify that XWiki is correctly installed. They can delete it after if
they want. I strongly believe tests should extend to users in some
manner, especially for an open source project.
2) This would allow users to help us discover problems in a more
controlled manner. Indeed if users have this app installed, once they
encounter a problem they could record a test suite proving the
problem and give it to us. This would 1) increase our test suite and
2) allow us to reproduce the pb, fix it and verify the fix passes the
test. In some way this is about transforming a portion of our users
into contributors :)
Now Sergiu says that this is increasing the size of the default Wiki.
Yes this is true. It goes from 320KB to 542KB. Is it worth it?
To be honest, I don't know if this will work or not but I was curious
to try it out and see what we can come up with.
My idea here is really to try lowering the bar for writing functional
tests for everyone and for us to get better at controlling if XWiki
works or not.
We could have another wiki (say "wikidebug" or "wikitest") which is
the default wiki + the Selenium app and let people interested use it.
But it won't be as effective I think. I find it kind of cool to have
our installation verification tool inside the delivered default wiki.
Another idea: we could have a button in Selenium.WebHome to
completely remove the space if the user doesn't want it for example.
Anyway I'm curious to know what everyone thinks about this. I agree
with Sergiu that it's not 100% required. At the same I'm curious with
the experiment.
Thanks
-Vincent
PS: If we decide we don't want it I'll remove it from the build so
that it isn't included in the default wiki by default and I'll mark
XWIKI-959 as won't fix.
Hi all,
While working on encodings problems, I saw that some of the source
file do use non ascii chars (which is normal, especially in unit tests).
But, there is currently no decision on the encoding of the source
file, hence, compilers cannot correctly read the files that do use
non ascii chars. This leads to tests working on single instances but
not on others, only due to compilation settings.
There are 2 solutions:
1. force everybody to use UTF-8 encoding for their source files (it's
quite easy to st up most IDE once and for all for this...) and
specify the encoding in javac parameters in ant and maven.
2. force everybody to use unicode escapes (\uXXXX) to specify a non
ascii char in the sources (easily detectable on build, but harder for
developpers who have to use native2ascii)
Current files with non ascii chars:
/Users/serasset/dev/xwiki/trunks-users/xwiki/core/src/main/java/com/
xpn/xwiki/plugin/autotag/FrenchStemmer.java
/Users/serasset/dev/xwiki/trunks-users/xwiki/core/src/main/java/com/
xpn/xwiki/plugin/autotag/AutoTagPlugin.java
(Both are in ISO-8859-1)
/Users/serasset/dev/xwiki/trunks-users/xwiki/core/src/test/java/com/
xpn/xwiki/content/LinkTest.java
(this one seems to be encoded in VISCII (vietnamese encoding)
As in LinkTest.java, the test uses vietnamese characters, it's likely
that ISO-8859-1 encoding is not a viable option for the xwiki source
encoding. In the mean time, LinkTest.java should use \uXXXX uniocde
escapes in order to run correctly in all installs.
Can you please tell me which solution you prefer ?
Regards,
--
Gilles Sérasset
GETALP-LIG
BP 53 - F-38041 Grenoble Cedex 9
Phone: +33 4 76 51 43 80
Fax: +33 4 76 44 66 75