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

Re: [Pharo-project] Issue 3579 in pharo: "declare temp" adds the variable twice

by pharo＠googlecode.com

Comment #6 on issue 3579 by marianopeck: "declare temp" adds the variable twice http://code.google.com/p/pharo/issues/detail?id=3579 grrrrr yes, you are right :(

Jan. 28, 2011

Re: [Pharo-project] [ANN 1.2RC2] and TODO 1.2

by Tudor Girba

Hi Marcus, I integrated it in the Moose build and everything is Ok: http://hudson.moosetechnology.org/job/moose-latest-dev/139/ Cheers, Doru On 28 Jan 2011, at 13:56, Marcus Denker wrote: > Hi, > > 1.2 > ==== > We now have a RC2 of the Core image. > -> all tests are green: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/ > -> no known show stopping issues > This can be downloaded here: > https://gforge.inria.fr/frs/download.php/28189/PharoCore-1.2rc2-12324.zip > > But of course what people want to actually use is the Full Image (with Refactoring Tools...) > > For 1.2Full, we have some issues left before we can do a release. > > Hudson: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/t… > Bugs: http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.2-DevImage > > The nice thing is that with the Hudson server, up-to-date 1.2RC2 can be downloaded: > image: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… > One-Click: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… > > We should use it and test... > > 1.1 > === > > While fixing those, we should take care to not break the 1.1Full Build. *And* we should take th > opportunity to make it green, too. > I already (in parallel to 1.2), fixed (or added workarounds) to all failing tests in Core. > > What is left is 1.1.2 Full: > > http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.1.2-DevIma… > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.1/lastCompletedBuild/t… > > 1.3a > === > > As simple changes where piling up *and* we need to move on, we started 1.3 this week. > This has seen already 21 updates (and 51 closed bug tracker entries). > > The first goal will be to get all tests green, I will make sure that only issues are tagged 1.3 > that are either to be integrated, failing tests or show-stoppers. This way we wil have a TODO > list of issues to be fixed first. > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

Jan. 28, 2011

Re: [Pharo-project] Issue 3334 in pharo: [Kernel Dependencies] Model>>#patchworkUIThemeColor

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #2 on issue 3334 by stephane...(a)gmail.com: [Kernel Dependencies] Model>>#patchworkUIThemeColor http://code.google.com/p/pharo/issues/detail?id=3334 Instead of that we moved Model into Kernel-UI and at the end it should be in UI-Basic

Jan. 28, 2011

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

by Mariano Martinez Peck

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] Issue 3607 in pharo: MNU #stylerStyled: in Finder for basic usage

by pharo＠googlecode.com

Updates: Cc: Benjamin.VanRyseghem.Pharo Comment #1 on issue 3607 by marianopeck: MNU #stylerStyled: in Finder for basic usage http://code.google.com/p/pharo/issues/detail?id=3607 (No comment was entered for this change.)

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

Comment #8 on issue 2586 by ryd...(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 This is a regression introduced recently, I think it belongs in 1.2 even though it's kinda late in release cycle. A working clipboard is nice to have :)

Jan. 28, 2011

Re: [Pharo-project] Issue 3376 in pharo: DisplayObject remove dependence to FileStream

by pharo＠googlecode.com

Comment #2 on issue 3376 by stephane...(a)gmail.com: DisplayObject remove dependence to FileStream http://code.google.com/p/pharo/issues/detail?id=3376 in 13024

Jan. 28, 2011

Re: [Pharo-project] Issue 3376 in pharo: DisplayObject remove dependence to FileStream

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #1 on issue 3376 by stephane...(a)gmail.com: DisplayObject remove dependence to FileStream http://code.google.com/p/pharo/issues/detail?id=3376 in 13024

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: Status: Fixed Comment #7 on issue 2586 by ryd...(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 This change broke the clipboard on Windows, which does transformation of canonical CR's to CRLF's. A new fix, which preserves the functionality on other platforms than Unix is in Inbox, SLICE-Issue2586-UnbreakWindowsClipboard

Jan. 28, 2011

Re: [Pharo-project] [Seaside] state of the art in seaside/magritte/glorp on Squeak/OSX/FreeBSD

by Mariano Martinez Peck

On Thu, Jan 27, 2011 at 1:20 PM, Randal L. Schwartz <merlyn(a)stonehenge.com>wrote: > > So I've had my head buried in Perl for the past six months, and lost > track of where Seaside has gone. > > I know Seaside 3.0 is out. And Magritte/Pier have been updated (although > the docs still look amazingly sparse :). And there's something called > SqueakDBX for talking to Postgresql. > > My client has restarted the project we began a year ago but had to set > aside for economic reasons. I need to build a Seaside app that talks to > Postgresql, and runs on FreeBSD. I'd prefer to use something like > Glorp, but I'm not sure that's been updated in a while in the Squeak > world, unless SqueakDBX did it. > No. The Glorp version for Squeak/Pharo is still several years old. However, it has been updated at least to work in the latest Pharo (I guess squeak too but I am not sure). You can use Glorp directly and use the PostgreSQL native driver (where you don't need the postgres client libraries), or you can use GlorpDBX with SqueakDBX driver, where you need to install OpenDBX and the PostgreSQl libraries. > > So, what's the current state of the art for Seaside, Magritte, Glorp, > and Postgresql bindings for Squeak? And has anyone managed to get a > modern VM running on FreeBSD... I can't seem to get the latest sources > to build (too many Linuxisms). I'll be developing on OSX, so that's > reasonably secure. > > -- > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 > <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> > Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. > See http://methodsandmessages.posterous.com/ for Smalltalk discussion > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

Jan. 28, 2011