Hi everyone,
Good news, we've now fixed the search page on http://www.xwiki.org
(BTW the fix will be in the final XE 1.2 release).
It's now using Lucene to search on all subwikis of xwiki.org
Thanks
-Vincent
I would suggest to have extjs implemented for ajax.
Reasons already mentioned below.
File size is not an issue as it needs to be loaded only once.
I have done some work on albatross skin to replace the default template
layout with extjs border layout for my local wiki.
One thing you need to take care is that there may be some other js files
whose execution might conflict with ext-base.js execution.
For my implementation I had to comment out all the other js that were
getting loaded.
Also another cool thing would be to integration extjs with jquery. This
combination can lead to some rich UI.
I have not yet tested the gwt web interface with xwiki, but not sure if
anyone has combined extjs with gwt, also from the version 2.0 of extjs I
don't see any adapter for gwt.
Thanks
Sachin
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 14 Jan 2008 21:31:38 +0100
> From: "Luis Arias" <kaaloo(a)gmail.com>
> Subject: Re: [xwiki-devs] upgrade to gwt 1.4
> To: "XWiki Developers" <devs(a)xwiki.org>
> Message-ID:
> <26d206520801141231y6a673686r27f168685efd2a3d(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi J?r?me,
>
> You might also consider MyGWT:
>
> http://mygwt.net/
>
> if you're worried about the ext.js lib. It's a native implementation.
>
> For Curriki, there may be some issues with gwt-html-editor which in
> its 1.4 branch just brings up Fck Editor. I had some issues using
> gwt-html-editor trunk in 1.4.61.
>
> Luis.
>
> On Jan 14, 2008 9:55 AM, Jerome Velociter <jerome(a)xwiki.com> wrote:
>
> > > Hi all,
> > >
> > > we want to upgrade XWiki Web gwt to gwt 1.4 for the 1.3 version so,
> since
> > > gwttk does not have a version for gwt 1.4 and we depend on it for
> creating
> > > modal dialogs, we need to replace tk with something else. A good
> option is
> > > gwt-ext, which also can replace gwt-widgets and provides some more
> nice ui
> > > objects and client functionality (like date parsing -- which we get
> from
> > > gwt-widgets for the moment).
> > > The trouble with gwt-ext is that it requires ext javascript library to
> > > run, which means that any gwt application needs to import, besides the
> > > gwt.js file, some ext javascript files. Since the modal dialogs are
> > > defined in the web-gwt module (so our gwt-ext dependency is there) and
> we
> > > cannot import the ext javascript files at that level, the only
> solution is
> > > to rely on the application using web-gwt to include right all required
> > > files. It doesn't seem to me as good practice but I cannot figure out
> how
> > > big of an issue it is (since that application already has some rules
> to
> > > obey, js files to include, etc to have gwt working).
> > >
> > IMO,
> >
> > Pros for migrating to ext, vs. sticking to gwttk:
> > - larger community, visibility on roadmap
> > - lots of widgets/functionnalities available (datepickers, form
> > validation, etc.)
> > - gwt 1.4 already compatible
> >
> > Cons:
> > - every app has to import ext JS scripts in addition to gwt.js
> > - increases total JS size
> >
> > It would be great to have opinions from the Curriki development team on
> > the topic.
> >
> > Regards,
> > Jerome.
> >
> >
> > > WDYT?
> > >
> > >
> > > _______________________________________________
> > > devs mailing list
> > > devs(a)xwiki.org
> > > http://lists.xwiki.org/mailman/listinfo/devs
> > >
> >
> >
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
>
>
>
> --
> Luis Arias
> +33 6 14 20 87 93
> skype : kaaloo
>
> ------------------------------
>
>
Good day.
Yet one question - I can't find way to pass parameters from one screen to
another. In JSP this is usually doing thought session-scope variables.
Are exists some analog in XWiki ?
I.e. let I have page A and receive in one request with parameters. Than I want
forward such request (with parameters) to page B.
I can't find the way to do this: if in A before redirect I write
$context.put("X","Y"), than in B $context.get("X") return nothing.
May be I need care about passing some sessionId ?
--
Ruslan Shevchenko
GradSoft. http://www.gradsoft.ua
Hi,
I've heard that there are some places in xwiki where we need unique
ids (anyone remembers where?).
In any case I've found this JDK 1.5 class which can help us with the
implementation:
http://java.sun.com/j2se/1.5.0/docs/api/java/util/UUID.html
I'm posting it here for the record.
Thanks
-Vincent
1. I see, that xwiki-product-enterprise-manager in svn is not build by
default. (and building one in own directory cause to fetch 1.2x snapshots of
xwiki parts). Curious, why ?
2. Can be application-manager be installed on top of fresh
xwiki-product-enterprise with default pages ? (It is not work for me)
--
Ruslan Shevchenko
GradSoft. http://www.gradsoft.ua
Hello!
We have been customizing our instance of XWiki Enterprise (1.2) very
successfully but have hit a bit of a roadblock. We would like to modify the
layout of the Comments area, specifically to add a couple of controls we will
use for adding a "Rating" mechanism and we can't seem to find where we can
access the stylesheet for the template. We have successfully done this to the
Search Results page (Xwiki.Results) but cannot seem to determine how to do
something similar to the Comments area attached to each article.
Any suggestions would be greatly appreciated
Thanks in Advance!
Rob Masson
On Jan 11, 2008, at 6:28 PM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-01-11 18:28:47 +0100 (Fri, 11 Jan 2008)
> New Revision: 6782
>
> Modified:
> xwiki-platform/core/trunk/xwiki-core/pom.xml
> xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> render/groovy/GroovyTemplateEngine.java
> xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> store/XWikiHibernateBaseStore.java
[snip]
> Modified: xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/
> xwiki/store/XWikiHibernateBaseStore.java
> ===================================================================
> --- xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> store/XWikiHibernateBaseStore.java 2008-01-11 14:01:44 UTC (rev 6781)
> +++ xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/
> store/XWikiHibernateBaseStore.java 2008-01-11 17:28:47 UTC (rev 6782)
> @@ -80,7 +80,7 @@
> try {
>
> setHibUrl(XWiki.class.getClassLoader().getResource(path));
> } catch (Exception ex2) {
> - log.error("Failed setting the Hibernate
> configuration file with any method, storage cannot be configured",
> ex2);
> + log.error("Failed setting the Hibernate
> configuration file with any method, storage cannot be configured");
Why are we removing the stack trace? This is an error and the stack
trace will help debug the error.
The fact that the test is wrongly written is a different matter IMO.
The test must be forgetting to initialize something.
But we do need the max amount of info when debugging an ERROR level
error.
-Vincent
Good day, xwiki community.
I want to discuss path, with allows to set in configuration name of main wiki
database schema and prefixes for databases schemes of virtual wiki-s.
This allows to use few wiki-based applications on one computer.
Proposed path itself is attached.
The work of this path is
1. add configuration variables:
xwiki.db -- database schema name of main wiki instance.
xwiki.virtual.db.prefix -- prefix for database scheme-s of virtual wiki-s.
So, questions:
a) where I must write documentation for this parameters ?
b) can I submit JIRA issue now or exists some other things which i forgott.
--
Ruslan Shevchenko
GradSoft. http://www.gradsoft.ua
The XWiki development team is pleased to announce the release of XWiki
Enterprise Manager 1.0 Milestone 3.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This is the last XEM 1.0 milestone. RC1 and RC2 will follow.
The main modifications since XEM 1.0M2 are all XE 1.2 branch new
features as XEM 1.0M3 is now based on XE 1.2 Release Candidate 3.
Changes from 1.0 Milestone 3:
* XAAM-28: Add authors field to applications descriptors.
* XAAM-29: Add license field to applications descriptors.
* XAWM-23: Separate wiki and wiki alias concepts.
* XAWM-26: Add pretty name field to wikis decriptors.
* XAWM-29: Add users or groups rights at wiki creation time.
* XEM-78: Add default "xwiki" wiki descriptor.
* XEM-65: Make Application Manager and Wiki Manager more easily accessible.
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM10M3
Thanks
-The XWiki dev team