+1, JV. On Mon, May 3, 2010 at 1:20 PM, Thomas Mortagne <[email protected]> wrote:

Hi devs,

I have been working on an search related administration UI and i would like to commit a first version on svn and put it as XE 2.4-SNAPSHOT dependency to start review and improvements. Better do it as soon as possible instead of arguing just before the release of 2.4M1 since it's functionally complete and just need potential UI work (even if it's not worst than others admin section UIs ;)).

This new application contains: * search administration UI: administration section that permit to choose the default engine ("lucene" and "web" for now) to use in the search panel and some Lucene status and control tools * all search related pages (panel, web/lucene search pages, XWiki.Result) moved from XE. I did not touched anything except the panel to support engine option, it's just a move for now * the default search engine is lucene

TODO before commit: * put some new textual content in ApplicationResources.properties for the admin page

TODO after first commit: * refactor ApplicationResources.properties to reflect the fact that some textual content moved from XE app to Search app * i will work on making "element to index" queue status refresh automatically using ajax

WDYT ?

Here is my +1

Thanks, -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

On 05/03/2010 01:20 PM, Thomas Mortagne wrote:

Hi devs,

I have been working on an search related administration UI and i would like to commit a first version on svn and put it as XE 2.4-SNAPSHOT dependency to start review and improvements. Better do it as soon as possible instead of arguing just before the release of 2.4M1 since it's functionally complete and just need potential UI work (even if it's not worst than others admin section UIs ;)).

This new application contains: * search administration UI: administration section that permit to choose the default engine ("lucene" and "web" for now) to use in the search panel and some Lucene status and control tools

"web" is not a nice name... Maybe "database query"?

* all search related pages (panel, web/lucene search pages, XWiki.Result) moved from XE. I did not touched anything except the panel to support engine option, it's just a move for now

I think we should have a Search page which does this disambiguation and make the panel (as well as the search box in the header) use this page, whose address doesn't change.

* the default search engine is lucene

TODO before commit: * put some new textual content in ApplicationResources.properties for the admin page

TODO after first commit: * refactor ApplicationResources.properties to reflect the fact that some textual content moved from XE app to Search app * i will work on making "element to index" queue status refresh automatically using ajax

What's this supposed to be?

WDYT ?

Here is my +1

+1 -- Sergiu Dumitriu http://purl.org/net/sergiu/

+1 On Mon, May 3, 2010 at 13:20, Thomas Mortagne <[email protected]>wrote:

Hi devs,

I have been working on an search related administration UI and i would like to commit a first version on svn and put it as XE 2.4-SNAPSHOT dependency to start review and improvements. Better do it as soon as possible instead of arguing just before the release of 2.4M1 since it's functionally complete and just need potential UI work (even if it's not worst than others admin section UIs ;)).

This new application contains: * search administration UI: administration section that permit to choose the default engine ("lucene" and "web" for now) to use in the search panel and some Lucene status and control tools * all search related pages (panel, web/lucene search pages, XWiki.Result) moved from XE. I did not touched anything except the panel to support engine option, it's just a move for now * the default search engine is lucene

TODO before commit: * put some new textual content in ApplicationResources.properties for the admin page

TODO after first commit: * refactor ApplicationResources.properties to reflect the fact that some textual content moved from XE app to Search app * i will work on making "element to index" queue status refresh automatically using ajax

WDYT ?

Here is my +1

Thanks, -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

+1 Thanks, Marius Thomas Mortagne wrote:

Hi devs,

I have been working on an search related administration UI and i would like to commit a first version on svn and put it as XE 2.4-SNAPSHOT dependency to start review and improvements. Better do it as soon as possible instead of arguing just before the release of 2.4M1 since it's functionally complete and just need potential UI work (even if it's not worst than others admin section UIs ;)).

This new application contains: * search administration UI: administration section that permit to choose the default engine ("lucene" and "web" for now) to use in the search panel and some Lucene status and control tools * all search related pages (panel, web/lucene search pages, XWiki.Result) moved from XE. I did not touched anything except the panel to support engine option, it's just a move for now * the default search engine is lucene

TODO before commit: * put some new textual content in ApplicationResources.properties for the admin page

TODO after first commit: * refactor ApplicationResources.properties to reflect the fact that some textual content moved from XE app to Search app * i will work on making "element to index" queue status refresh automatically using ajax

WDYT ?

Here is my +1

Thanks,