January 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3620 in pharo: Settings: OCompletion settings appear twice

by pharo＠googlecode.com

Status: Accepted Owner: laurent....(a)gmail.com New issue 3620 by laurent....(a)gmail.com: Settings: OCompletion settings appear twice http://code.google.com/p/pharo/issues/detail?id=3620 Pharo image: dev 1.2 Steps to reproduce: 1. open settings 2. in search field type 'compl' then enter 3. OCompletion settings appear twice

Jan. 28, 2011

Re: [Pharo-project] Issue 3610 in pharo: Should remove Morphic-Undo

by pharo＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 3610 by aplan...(a)gmail.com: Should remove Morphic-Undo http://code.google.com/p/pharo/issues/detail?id=3610 SLICE-Issue-3610-Should-remove-Morphic-Undo

Jan. 28, 2011

[Pharo-project] Issue 3619 in pharo: Hudson Pharo 1.2dev OBBrowser keybinding

by pharo＠googlecode.com

Status: Accepted Owner: jbaptist...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3619 by jbaptist...(a)gmail.com: Hudson Pharo 1.2dev OBBrowser keybinding http://code.google.com/p/pharo/issues/detail?id=3619 Test in OB about keybinding, The setup create a OBPluggableTextMorph, which event should be intercept by the Test class. 2 solution to solve that. a mock class, respect the spirit of the old test, i beginning to do that but we should be care about the argument of the message send (i think is cause of the mock class don't initialize) correctly. Or remove these test . I publish the beginning of the fix. Attachments: OB-Tests-Morphic-jb.31.mcz 10.2 KB

Jan. 28, 2011

Re: [Pharo-project] Issue 3610 in pharo: Should remove Morphic-Undo

by pharo＠googlecode.com

Comment #1 on issue 3610 by aplan...(a)gmail.com: Should remove Morphic-Undo http://code.google.com/p/pharo/issues/detail?id=3610 Yes. for this one I will do the slice :)

Jan. 28, 2011

Re: [Pharo-project] Issue 3612 in pharo: Full Image uses wrong Theme

by pharo＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 3612 by Torsten....(a)astares.de: Full Image uses wrong Theme http://code.google.com/p/pharo/issues/detail?id=3612 added in ConfigurationOfPharo-tbn.129

Jan. 28, 2011

[Pharo-project] [update 1.2] #12325

by Marcus Denker

12325 ----- Issue 2586: line breaks lost on Linux when copying from one pharo image to another -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 28, 2011

Re: [Pharo-project] Issue 2586 in pharo: line breaks lost on Linux when copying from one pharo image to another

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Comment #9 on issue 2586 by marcus.d...(a)gmail.com: line breaks lost on Linux when copying from one pharo image to another http://code.google.com/p/pharo/issues/detail?id=2586 in 12325 TODO: 1.3

Jan. 28, 2011

Re: [Pharo-project] Databases with full text search support

by S Krish

I would recommend using Lucene indexing for the documents for various reasons.. not limited to the fact that if one is interested in indexing documents and millions of them.. it obviates talking of Databases... Now with Lucene, I would recommend using the Groovy bridge with XMLRpc from Pharo to be able to do anything you may want to pass back n forth the path to the documents.. and the fileentry properties of the document found through the indexed search.. Coincidentally, I have been intending to complete the half done work on this.. for last one year.. for our internal div..! -Skrish On Fri, Jan 28, 2011 at 11:53 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Fri, Jan 28, 2011 at 9:54 AM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Indeed actually we use successfully MySQL full text search engine and also >> Lucene (but not with Pharo ;) >> >> I think I should try OpenDBX. >> >> > You can also try the native MySQL client for Squeak. Not sure about its > current state, but you don't need any library. > http://www.squeaksource.com/MySQL.html > > For SqueakDBX, check everything in www.squeakdbx.org > > >> Laurent >> >> >> >> On Fri, Jan 28, 2011 at 3:44 PM, Mariano Martinez Peck < >> marianopeck(a)gmail.com> wrote: >> >>> Laurent: several relational databases provvide full text serach >>> capabilities. >>> >>> You can send a SELECT statement with a MATCH() function to the server and >>> get >>> the result of search back (in case of MySQL). I think OpenDBX >>> library has to do nothing special here: it depends on which query you >>> write. >>> >>> >>> MySQL and PostgreSQL server has support for full text search (aka. >>> tsearch in PostgreSQL I think). >>> >>> >>> cheers >>> >>> mariano >>> >>> >>> On Fri, Jan 28, 2011 at 3:57 AM, Norbert Hartl <norbert(a)hartl.name>wrote: >>> >>>> >>>> On 27.01.2011, at 20:48, laurent laffont wrote: >>>> >>>> > Hi, >>>> > >>>> > I need to have full text indexing and searching over a 3-5 million >>>> documents. Actually the products I work on are written in PHP - MySQL. >>>> > >>>> > What would you use (open source - mandatory - our products are open >>>> source) in Smalltalk world to do this ? >>>> > >>>> That topic troubled me some time in the last years. The first approach I >>>> took was postgresql+tsearch2 because I used Glorp back then. AFAIK tsearch2 >>>> has been incorporated into postgresql in the meantime so this is no extra >>>> weight. Stemming libraries for postgresql are quite good and available for >>>> some languages. If you would use Glorp you can even extend the query >>>> language to support it out of the box. >>>> I changed the setup as I moved from postgresql to gemstone. With the new >>>> setup I would have used postgresql only for the fulltext retrieval which I >>>> didn't like. I used SOLR [1] instead. It is a search server build upon >>>> lucene which supports faceted search and a lot of nifty stuff. I used >>>> magritte to generate the xml that I've put into SOLR. I was satisfied with >>>> this solution. But all solutions that need to cross the smalltalk boundary >>>> start to become cumbersome at some stage. >>>> If I find time I would take another approach. I found a smalltalk >>>> stemming library while observing the moose mailing list. If you have good >>>> stemming support it may be a reasonable effort to produce forward and >>>> inverted indexes of your objects with search capabilities. If you use >>>> magritte (or pragmas) then you could add the fields to index there. The rest >>>> would be automatic: Taking all fields that should be searchable. Tokenize >>>> and canonicalize (using stemming) the words and build forward and inverted >>>> index. The only thing that would be needed is a change notification system >>>> that updates the index but I think this is more of an easy task. Well, that >>>> is the sketch what I would try to do myself but don't find time right now. I >>>> personally think that the power you gain by search smalltalk objects >>>> directly outweighs all the external servers by some extent. >>>> If you use a special external database anyway that supports it, well, >>>> then this would be the easiest start. >>>> >>>> hope this helps, >>>> >>>> Norbert >>>> >>>> >>>> >>>> >>> >> >

Jan. 28, 2011

Re: [Pharo-project] does anybody knows who is using StandardToolSet?

by Igor Stasenko

On 28 January 2011 19:20, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > yes, check the archives. I opened tickes for that. and I sent several mails. > Seems no-one has time to do it. > we discussed that today. probably i will take care about it for 1.3.. not sure how soon it will be but i will :) > http://code.google.com/p/pharo/issues/detail?id=1915 > > On Fri, Jan 28, 2011 at 10:44 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> Because it would be good that it uses a registration mechanism. >> Hardcoding the classes of the tools is not optimal for example for the new >> Finder. >> >> Stef > > -- Best regards, Igor Stasenko AKA sig.

Jan. 28, 2011

Re: [Pharo-project] Databases with full text search support

by Mariano Martinez Peck

On Fri, Jan 28, 2011 at 9:54 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Indeed actually we use successfully MySQL full text search engine and also > Lucene (but not with Pharo ;) > > I think I should try OpenDBX. > > You can also try the native MySQL client for Squeak. Not sure about its current state, but you don't need any library. http://www.squeaksource.com/MySQL.html For SqueakDBX, check everything in www.squeakdbx.org > Laurent > > > > On Fri, Jan 28, 2011 at 3:44 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Laurent: several relational databases provvide full text serach >> capabilities. >> >> You can send a SELECT statement with a MATCH() function to the server and >> get >> the result of search back (in case of MySQL). I think OpenDBX >> library has to do nothing special here: it depends on which query you >> write. >> >> >> MySQL and PostgreSQL server has support for full text search (aka. >> tsearch in PostgreSQL I think). >> >> >> cheers >> >> mariano >> >> >> On Fri, Jan 28, 2011 at 3:57 AM, Norbert Hartl <norbert(a)hartl.name>wrote: >> >>> >>> On 27.01.2011, at 20:48, laurent laffont wrote: >>> >>> > Hi, >>> > >>> > I need to have full text indexing and searching over a 3-5 million >>> documents. Actually the products I work on are written in PHP - MySQL. >>> > >>> > What would you use (open source - mandatory - our products are open >>> source) in Smalltalk world to do this ? >>> > >>> That topic troubled me some time in the last years. The first approach I >>> took was postgresql+tsearch2 because I used Glorp back then. AFAIK tsearch2 >>> has been incorporated into postgresql in the meantime so this is no extra >>> weight. Stemming libraries for postgresql are quite good and available for >>> some languages. If you would use Glorp you can even extend the query >>> language to support it out of the box. >>> I changed the setup as I moved from postgresql to gemstone. With the new >>> setup I would have used postgresql only for the fulltext retrieval which I >>> didn't like. I used SOLR [1] instead. It is a search server build upon >>> lucene which supports faceted search and a lot of nifty stuff. I used >>> magritte to generate the xml that I've put into SOLR. I was satisfied with >>> this solution. But all solutions that need to cross the smalltalk boundary >>> start to become cumbersome at some stage. >>> If I find time I would take another approach. I found a smalltalk >>> stemming library while observing the moose mailing list. If you have good >>> stemming support it may be a reasonable effort to produce forward and >>> inverted indexes of your objects with search capabilities. If you use >>> magritte (or pragmas) then you could add the fields to index there. The rest >>> would be automatic: Taking all fields that should be searchable. Tokenize >>> and canonicalize (using stemming) the words and build forward and inverted >>> index. The only thing that would be needed is a change notification system >>> that updates the index but I think this is more of an easy task. Well, that >>> is the sketch what I would try to do myself but don't find time right now. I >>> personally think that the power you gain by search smalltalk objects >>> directly outweighs all the external servers by some extent. >>> If you use a special external database anyway that supports it, well, >>> then this would be the easiest start. >>> >>> hope this helps, >>> >>> Norbert >>> >>> >>> >>> >> >

Jan. 28, 2011