Hi devs,
As XE 1.4 Milestone 2 is now "physically" released I would like to
start XEM 1.2 Milestone 2 release on next Monday.
Adding to XE 1.4 M2 bugfixes an new features it also contains some
WikiManager user interface improvements.
See http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM12M2
Thanks
--
Thomas Mortagne
Hi all,
I think it would be great if all mentors introduce themselves to students,
the way we introduced ourselves.
I hope this introduction will help all XWiki GSoC participants.
--Sai Krishna.
http://filtrbox.com looks interesting, although the filtrbox :
dashboard<https://www.filtrbox.com/dashboard/>application is in flash,
which means you don't get the excellent emergent
effect of having google be able to search the filter pages, or being able to
have a search-hit bring you back to a "deep state" in the collaborative feed
reader...
For those planning on upgrading xwikiwatch in future releases, it is well
worth looking at filtrbox to get an idea of functional UI for doing this
class of application, even if it may be more difficult to achieve this style
of UI using standard web browser technologies.
--------------------------------------------------------------------------------------------
http://alwayson.goingon.com/permalink/post/26573
<http://alwayson.goingon.com/user/bradfeld>I have a very patterned daily
information consumption routine. The left-most tab in my browser is called
"Daily" and contains a set of web sites that I open up each morning and look
at as part of my routine. Recently, Filtrbox <http://www.filtrbox.com/> -
one of the TechStars <http://www.techstars.org/> companies - graduated to be
part of this tab.
I try virtually every news alerting system that I come across. I have a set
of about 100 keywords that I track daily - all of the companies we've
invested in, a number of people that I follow, and a handful of random
things I care about. My current staples are Google Alerts, Yahoo Alerts,
and Technorati. I can only seem to get Google and Yahoo via email, so they
show up in my inbox and get moved to my "Daily" email folder (which I read -
er - daily.) Technorati comes via RSS so I read it each morning in
FeedDemon.
The vision for Filtrbox <http://www.filtrbox.com/> when they started at
TechStars last summer was to create an integrated single dashboard of all
this keyword alert information. The tagline "more knowledge, less noise"
says it all. My partner Seth Levine and I totally resonated with this -
Seth has a great post about Filtrbox up titled *Know what you don't
know<http://www.sethlevine.com/blog/archives/2008/04/know-what-you-d.php>
*which addresses how he thinks about the problem and how Filtrbox solves it
for him.
For a while I found the Filtrbox data interesting, but not really that
additive. In addition, the UI was "ok" but there where lots of little things
that slowed me down. About three months ago I noticed I was finding new
information from it that wasn't appearing in my other keyword searches and
that it was streamlining this information in ways that I hadn't expected,
such as eliminating duplicates (e.g. the same alert coming from Google,
Yahoo, and Technorati - which happens many times each day - only appeared
one in Filtrbox) and allowing me to filter based on thresholds for each
keyword. In addition, as the UI evolved, I found I was spending less time
scanning the alerts and more time clicking through onto the interesting
ones.
I hit a tipping point about a month ago where Filtrbox became more useful to
me than Google+Yahoo+Technorati. I haven't turned off the other alerts yet,
but I find that I'm not getting much additional info from them anymore now
that I use Filtrbox as my top level sort.
Filtrbox is still in private beta, but if you are interested in playing
around with it you can get a golden ticket by clicking on the special magic
Brad Feld Filtrbox link <https://www.filtrbox.com/signup.php?code=foundry>.
I'm really proud of Ari Newman, Tom Chikoore, and team. They have reached
the point where their service is very valuable to me and gets noticeably
better every single week.
---------------------------------------------------------------------------------------------
Hi Niels,
Welcome to Filtrbox! You are joining thousands of professionals and
businesses who use Filtrbox to stay in-the-know and ahead of the game. The
Filtrbox service is in private beta, which means we are still adding
features and improving the service. Your feedback is greatly appreciated so
let us know how we can make Filtrbox even better. We will send out a survey
in the coming month to ask more specific questions.
The purpose of the Filtrbox private beta is for us to get real-world
feedback from our customers and to ensure the service is ready for
prime-time usage. We hope you find real value in Filtrbox, and that you will
provide us with feedback, good or bad, on your experience and what you'd
like to see in the product going forward.
With this registration code you are given a "Filtrbox Free" account which
provides 10 Filtrs and 15 days of article history. You can also invite
friends and colleagues to try Fiiltrbox via our "Shared Filtrs" feature.
Once you create a FiltrGroup, you can click on the Share button on the
Filtrs tab and add email addresses.
If you find you need more Filtrs or article history, you can upgrade to
"Filtrbox Pro", our subscription-based service which provides 25 Filtrs and
45 days of article history. You can upgrade right from the Account tab.
In exchange for your free account, we ask that you give us feedback and ask
questions! There is a new community-driven web support site we are trying
out. Right now it requires you to register with them, but shortly we'll have
in integrated with our service. Check it out for FAQ items and answers to
common questions. http://getsatisfaction.com/filtrbox
If you don't find what you are looking for, please email us directly at
support(a)filtrbox.com and we'll get right back with you.
We highly recommend watching the screen-cast tutorials for a quick primer on
some key features: http://www.filtrbox.com/video.php
+++++++Account Info+++++++
Login: NielsMayer(a)gmail.com
Account Type: Free
Access your Filtrbox Account at:
https://www.filtrbox.com/dashboard/
++++++++++++++++++++++++
There are three ways to get help if needed:
FAQs: http://filtrbox.com/help.php
Support/Community: http://getsatisfaction.com/filtrbox
Email: support(a)filtrbox.com
Stay in touch:
subscribe to our blog: http://filtrbox.com/blog
follow us on Twitter: http://twitter.com/filtrbox
Thanks for your business!
The Filtrbox Team
-----------------------------------------------------------
-- Niels
http://nielsmayer.com
This message is for all of you (especially the Orthodox, who are celebrating
Easter this night)
Hope your Easter is filled with all the brightness and warmth you spread all
around you, and I wish you peace, happiness, health and all the joy you can
spend with your families.
Jesus Christ be with you all.
Happy Easter
PaÅŸte Fericit
Joyeuse Pâques
Buona Pasqua
Boa Páscoa
śubh īsţar
Fuhkwuhtjit Faailohk
(sorry - couldn't found how is translated in Tamil) :P
Hello Devs,
Is it possible to create groups in XWiki for each space. Meaning, can each
space have its own set of different groups?
If I create a new class like the XWiki.XWikiGroups fro each space and use it
like the original (XWiki.XWikiGroups) class for including objects, will it
work?
Will these groups be captured in the Administration window to configure
Rights?
Thanks for all help
Hello Devs,
In our project we need to eb able to assign different rights to different
users but, we do not want to give access to the Administration Page to
everybody.
So, I create a page where I would fill in a drop down box wit user names and
group name and then write a script to add the selected user tothe selected
group.
For this, I did the following but, this added objects of
XWiki.XWikiGroup(one for each of the users) to this page and now this page
shows up in my Admin space with the other groups. Is there a method to just
get a list of all user names in the XWiki, that I can use instead of using
this complex query. or Is there a better way to do this.
Also, once I select a user and a group, how do I add the user to the group.
Is there a method/script for that? I see a "adduorg.vm" in the templates.
What is the purpose of this script? where is it called? What is "uorg"?
Use this Form to Assign New Roles or modify Existing Roles for the members
of ROCK!
<html>
<form>
Select User:
<select name="currentusers">
#set ($sql = ", BaseObject as obj where obj.name=doc.fullName and
obj.className='XWiki.XWikiUsers'")
#foreach ($item in $xwiki.searchDocuments($sql))
#set($userdoc=$xwiki.getDocument($item))
#set($userobj=$userdoc.getObject("XWiki.XWikiUsers"))
#set($username=$userobj.getName())
<option value="$username">$username</option>
#end
</select>
Select Role:
<select name="rockroles">
#set ($sql = ", BaseObject as obj where obj.name=doc.fullName and
obj.className='XWiki.XWikiGroups' and obj.name<>'XWiki.XWikiGroupTemplate'")
#foreach ($item in $xwiki.searchDocuments($sql))
<option value="$item">$item</option>
#end
</select>
</form>
</html>
Please help!
Thanks
Hi Sergiu,
Why 1 mn and not 30 sec as proposed by Ludovic? He convinced me that
it doesn't cost anything to run it every 30 sec and that'll spread the
indexing work (like the GC does) and let users search faster when new
changes are made to docs.
Thanks
-Vincent
On Apr 25, 2008, at 2:50 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-04-25 02:50:17 +0200 (Fri, 25 Apr 2008)
> New Revision: 9365
>
> Modified:
> xwiki-platform/xwiki-plugins/trunk/lucene/src/main/java/com/xpn/
> xwiki/plugin/lucene/IndexUpdater.java
> Log:
> XPLUCENE-10: Reduce the default indexing period to 1 minute
>
>
> Modified: xwiki-platform/xwiki-plugins/trunk/lucene/src/main/java/
> com/xpn/xwiki/plugin/lucene/IndexUpdater.java
> ===================================================================
> --- xwiki-platform/xwiki-plugins/trunk/lucene/src/main/java/com/xpn/
> xwiki/plugin/lucene/IndexUpdater.java 2008-04-25 00:30:08 UTC (rev
> 9364)
> +++ xwiki-platform/xwiki-plugins/trunk/lucene/src/main/java/com/xpn/
> xwiki/plugin/lucene/IndexUpdater.java 2008-04-25 00:50:17 UTC (rev
> 9365)
> @@ -55,7 +55,7 @@
> /**
> * Milliseconds of sleep between checks for changed documents
> */
> - private int indexingInterval = 3000;
> + private int indexingInterval = 60000;
>
> private boolean exit = false;
>
> @@ -405,7 +405,7 @@
>
> this.indexingInterval =
> 1000 * Integer.parseInt(config
> - .getProperty(LucenePlugin.PROP_INDEXING_INTERVAL,
> "300"));
> + .getProperty(LucenePlugin.PROP_INDEXING_INTERVAL,
> "60"));
>
> // Note: There's no need to open the Searcher here (with a
> call to
> // openSearcher()) as each
>
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications
thanks for the cleanup, see below
On Apr 25, 2008, at 5:22 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-04-25 05:22:47 +0200 (Fri, 25 Apr 2008)
> New Revision: 9369
>
> Modified:
> xwiki-platform/core/trunk/xwiki-core/pom.xml
> Log:
> XWIKI-2337: Move common dependencies versions to the parent pom
> dependencyManagement section
> XWIKI-2338: Upgrade some commons packages
> Upgrade the core pom
[snip]
> <!-- VMA: I'm not sure if we have the right to distribute this
> jar. It's not on the central repository because
> of licensing issues. -->
> + <!-- Sergiu: No, we cannot redistribute it. And we definitely
> shouldn't put it in our repo.
> + We can redistribute version 1.1, but we should make users
> approve their License Agreement.
> + Can we drop this completely? Why is it needed? -->
it's needed for sending mail. Sun was supposed to provide new
redistributable licenses with new releases of their jars. We need to
check if it's been done.
>
> + <!-- TODO: Version 1.1 is available, should we upgrade? -->
that means upgrading mail. Yes we should especially if the license is
good now.
>
> <dependency>
> <groupId>javax.transaction</groupId>
> <artifactId>jta</artifactId>
> @@ -136,6 +141,7 @@
> <!-- There's only a 2.2.9.1 version of jgroups on the central
> repository
> (http://repo1.maven.org/maven2/jgroups/jgroups-all/).
> Upload a newer version
> (http://sourceforge.net/project/showfiles.php?group_id=6081&package_id=94868
> ). -->
> + <!-- TODO: 2.4.1 is there now, although 2.6.2 is released on
> Sourceforge; should we upgrade? -->
This is used by oscache for clustering I think. I'd not upgrade unless
you have verified that clustering works fine before, then upgrade then
test again.
[snip]
> +
> + <!-- Things that should probably be removed -->
> + <dependency>
> + <groupId>org.apache.velocity</groupId>
> + <artifactId>velocity-tools</artifactId>
> + <version>1.3</version>
> + </dependency>
why do you say that? We're using it.
> + <dependency>
> + <groupId>joda-time</groupId>
> + <artifactId>joda-time</artifactId>
> + <version>1.4</version>
> + </dependency>
> + <dependency>
> + <groupId>backport-util-concurrent</groupId>
> + <artifactId>backport-util-concurrent</artifactId>
> + <version>3.0</version>
> + </dependency>
> </dependencies>
> <build>
> <plugins>
Thanks
-Vincent
Hi Sergiu,
Cool you fixed this. See below.
On Apr 25, 2008, at 1:41 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-04-25 01:41:36 +0200 (Fri, 25 Apr 2008)
> New Revision: 9363
>
> Modified:
> xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> doc/XWikiAttachment.java
> Log:
> XWIKI-2336: Broken attachments can break working with a document
> XWIKI-1937: importing a document with attachments over an existing
> document fails
> Done.
>
>
> Modified: xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/
> xwiki/doc/XWikiAttachment.java
> ===================================================================
> --- xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> doc/XWikiAttachment.java 2008-04-24 21:10:23 UTC (rev 9362)
> +++ xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> doc/XWikiAttachment.java 2008-04-24 23:41:36 UTC (rev 9363)
> @@ -48,7 +48,7 @@
> public class XWikiAttachment
> {
> private static final Log LOG =
> LogFactory.getLog(XWikiAttachment.class);
> -
> +
> private XWikiDocument doc;
>
> private int filesize;
> @@ -489,15 +489,25 @@
>
> public void loadContent(XWikiContext context) throws
> XWikiException
> {
> - if (attachment_content == null)
> -
> context.getWiki().getAttachmentStore().loadAttachmentContent(this,
> context, true);
> + if (attachment_content == null) {
> + try {
> +
> context.getWiki().getAttachmentStore().loadAttachmentContent(this,
> context, true);
> + } catch (Exception ex) {
> + LOG.error("Failed to load content for attachment ["
> + getFilename() + "]", ex);
I think we should always explain what is going to happen and what
state the system is in when we log an error and we carry on without
stopping the action. Can we add some comment in the log that explains
what it means? The user will see a big stack trace and he'll wonder
what he has to do to fix it. What can we tell him?
OTOH if there's nothing he should do then we shouldn't show a stack
trace, only a warning with no trace.
>
> + }
> + }
> }
>
> public XWikiAttachmentArchive loadArchive(XWikiContext context)
> throws XWikiException
> {
> if (attachment_archive == null) {
> - attachment_archive =
> context.getWiki().getAttachmentVersioningStore()
> - .loadArchive(this, context, true);
> + try {
> + attachment_archive =
> +
> context.getWiki().getAttachmentVersioningStore().loadArchive(this,
> context,
> + true);
> + } catch (Exception ex) {
> + LOG.error("Failed to load archive for attachment ["
> + getFilename() + "]", ex);
> + }
Same here.
Thanks
-Vincent