Congratulation to the XWiki team for the first release! and thanks for your replies.
I didn't realize I'v tried it before your release notice! :-) (as I thought it was released some time in the last week) Anyway, I've been actively waiting for it.
The key decision is just whether I should use XE and copy the XWS functions, or hack the code and request for features to allow XWS be used for public service. It seems obviously that the latter option is much better. As mentioned before, it's for a JUG. The use cases are straightforward:
- a global blog+wiki+photo that is readable by anonymous users and editable by a few committee members, (maybe comment by registered users) - Some spaces for collaboration works that any registered member are editable, and - every user could create his own space.
The functions are pretty much there already. The key missing thing is just making the global space publicly accessible. I'll fire some Jira issues later. Thanks.
If you are ready to look under the hood, we can definitely help you realizing that. Actually having your organization's space visible by unregistered users is not very hard. Once its created, you can do as follow (logged as Admin): - Click the "Administration" link in the XWiki toolbar - Click the "Space rights" tab in the administration page - Select your organization top-level space in the drop-down list (the one without any suffix: Space_MyOrganization, not Space_MyOrganization_Wiki or Space_MyOrganization_Blog) - Once its loaded, click twice the checkbox for unregistered users under "view" to have it green-checked (it should appear with a red circle at first). - ... and your done! The _Wiki, _Blog, etc. spaces will inherit their rights from that top-level one, so you shouldn't have anything to do for them. If you want to have registered users able to comment, you can check the "comment" box for XWikiAllGroup as well. Hope this helps, Jerome.
Regards, mingfai
On Mon, Mar 17, 2008 at 4:28 PM, Vincent Massol <[email protected]> wrote:
On Mar 17, 2008, at 6:37 AM, Mingfai wrote:
hi,
I wonder if I'm the first few outside people to try XWS milestone 1. :-)
Well, I'm evaluating the XWiki series of products for my Java User Group in Hong Kong. XWS "looks" better than XE to me and it seems XWS allows every user to create his/her own space of blog, wiki, photo and files, that perfectly fit my needs. I wonder:
- could XWS provide public registration, and anonymous (/non-logged-in) user access mode? - could XE actually do all XWS can do and I should use XE for public service? In fact, I feel XE has steeper learning curve than XWS. It seems XE does not provide individual blog, photo and file spaces
XE can do everything. It's a second generation wiki. All XWiki products are based on XE (and the underlying platform). For example even if in XE you have one blog by default, nothing prevents you to create as many as you want in the way you want them to be (you can imagine any kind of use case).
XWS is definitely meant to be a wrapper around XE to make it simpler and to provide a solution which is oriented towards personal work spaces that you can share with others. XE is generic, XWS implements a specific solution based on work groups.
Thus if XWS matches your needs you should definitely use it over XE.
Thanks -Vincent
- any pointer if I want to limit one user to create only one space? - could anyone point me to where I may be able to customize the space name and url? basically, the use of "Space_" as prefix look quite odd to me and i would like to remove it. And if it is possible i would want to make the url shorter. Currently, it's something like: " http://mydomain.com/xwiki/bin/view/Space_username/", i am able to remove the context "xwiki", and i suppose it shouldn't be difficult to turn Space_username to username. It's most desirable to turn bin/view to nothing or make it a single "folder", e.g. remove "/bin" (i suppose the action cannot be removed.)
regarding URL, i wonder if the developers like to go to the REST-ful direction. Some people think in REST-ful URL only resource but not action should be put as the path. (certainly, i understand in using Struts, some options may not be available)
Thank you very much.
Regards, mingfai
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users