- Pharo-dev - lists.pharo.org

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

by Miguel CobÃ¡

There isn't a full solution that I know of, but maybe you can use lucene to store index info outside smalltalk and use the references to search for the real smalltal objects. There are also bindings for several nosql databases for lucene and solr like mongo db and cassandra and there are bindings in smalltalk for mondodb and cassandra. Cheers El jue, 27-01-2011 a las 20:48 +0100, laurent laffont escribiÃ³: > 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 ? > > Laurent Laffont - @lolgzs > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Jan. 27, 2011

[Pharo-project] Databases with full text search support

by laurent laffont

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 ? Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Jan. 27, 2011

Re: [Pharo-project] Issue 3603 in pharo: O/ECompletion failure in Trait methods

by Levente Uzonyi

On Thu, 27 Jan 2011, Henrik Sperre Johansen wrote: > On 27.01.2011 19:53, Levente Uzonyi wrote: >> On Thu, 27 Jan 2011, pharo(a)googlecode.com wrote: >> >>> Status: Accepted >>> Owner: ryd...(a)gmail.com >>> CC: romain.r...(a)gmail.com >>> Labels: Milestone-1.2-DevImage Milestone-1.3-DevImage OCompletion >>> >>> New issue 3603 by ryd...(a)gmail.com: O/ECompletion failure in Trait methods >>> http://code.google.com/p/pharo/issues/detail?id=3603 >>> >>> A debugger pops up when typing in after super in a trait method, since >>> traits do not implement superclass. >> >> The bug is not related to OCompletion. Traits implement (via TPureBehavior) >> #allSuperclasses, #withAllSuperclasses, etc., but lack >> #superclass. > So which implementation of #superclass would you recommend for Trait, which > would keep O/ECompletion working without modification? > I can't think of any which makes sense really. nil is a possiblity or remove the super- and subclass related methods, see below. > > IMO, if code in the component eventually needs to be changed to not raise a > debugger, it's related. We could ignore the errors, but hiding bugs is a bad idea IMHO. We can add a check too, but what can you say about the following anomalies in the trait implementation? | justATrait | justATrait := TPureBehavior. justATrait isTrait. "true ok" justATrait isBehavior. "false strange" justATrait allSuperclasses. "an OrderedCollection() ok if there should be none" justATrait withAllSuperclasses. "an OrderedCollection(TPureBehavior) ok, but the comment says it should contain Object too" justATrait subclasses. " #() acceptable" justATrait superclass. "Error WTF?" Btw, what happened to the clipboard in Pharo 1.2 on windows? If I copy text, the line endings are CRs, not CRLFs, so the text is a single line. Levente >

Jan. 27, 2011

Re: [Pharo-project] Issue 3603 in pharo: O/ECompletion failure in Trait methods

by Henrik Sperre Johansen

On 27.01.2011 19:53, Levente Uzonyi wrote: > On Thu, 27 Jan 2011, pharo(a)googlecode.com wrote: > >> Status: Accepted >> Owner: ryd...(a)gmail.com >> CC: romain.r...(a)gmail.com >> Labels: Milestone-1.2-DevImage Milestone-1.3-DevImage OCompletion >> >> New issue 3603 by ryd...(a)gmail.com: O/ECompletion failure in Trait >> methods >> http://code.google.com/p/pharo/issues/detail?id=3603 >> >> A debugger pops up when typing in after super in a trait method, >> since traits do not implement superclass. > > The bug is not related to OCompletion. Traits implement (via > TPureBehavior) #allSuperclasses, #withAllSuperclasses, etc., but lack > #superclass. So which implementation of #superclass would you recommend for Trait, which would keep O/ECompletion working without modification? I can't think of any which makes sense really. IMO, if code in the component eventually needs to be changed to not raise a debugger, it's related. Cheers, Henry

Jan. 27, 2011

Re: [Pharo-project] Issue 3603 in pharo: O/ECompletion failure in Trait methods

by Levente Uzonyi

On Thu, 27 Jan 2011, pharo(a)googlecode.com wrote: > Status: Accepted > Owner: ryd...(a)gmail.com > CC: romain.r...(a)gmail.com > Labels: Milestone-1.2-DevImage Milestone-1.3-DevImage OCompletion > > New issue 3603 by ryd...(a)gmail.com: O/ECompletion failure in Trait methods > http://code.google.com/p/pharo/issues/detail?id=3603 > > A debugger pops up when typing in after super in a trait method, since traits > do not implement superclass. The bug is not related to OCompletion. Traits implement (via TPureBehavior) #allSuperclasses, #withAllSuperclasses, etc., but lack #superclass. Also note that these methods are not in sync with their comments. Btw it's a bit strange (but acceptable) that Traits are not Behaviors. Levente > Reproduction steps at: > http://screencast.com/t/yyjLLm0S > > Mailing list thread: > http://forum.world.st/First-commit-to-Pharoinbox-Need-advice-tp3237535p3241… > >

Jan. 27, 2011

Re: [Pharo-project] First commit to Pharoinbox. Need advice.

by Henrik Sperre Johansen

On 27.01.2011 17:38, Igor Stasenko wrote: > On 27 January 2011 07:28, HwaJong Oh<daliot.oh(a)gmail.com> wrote: >> Yes, you are right. I was wrong. There is nothing super send. I had error >> editing my trait codes around "super", so i thought trait can super send. >> http://screencast.com/t/yyjLLm0S >> >> MoveMethod: >> >> FriendOfPointArray>> >> at: index >> >> ^(pointArray superAt: index * 2 - 1) @ (pointArray superAt: index * 2) >> >> to >> >> PointArrayTrait>> >> at: index >> >> ^(super at: index * 2 - 1) @ (super at: index * 2) >> >> >> while editing "pointArray superAt:" to "super at:", the editor made error. >> > Hehe.. funny mistake :) Yeah, I created an issue for it: http://code.google.com/p/pharo/issues/detail?id=3603 > Btw, what is this FriendOfPointArray? The name sounds strange > It actually has a class comment :) "Removes duplication of PointArray & ShortPointArray. They do not share same superclass, therefore this class is to remove to duplicated codes by extracting class" Hence my suggestion of a trait to keep it in rather than creating a new helper instance for each at: or at:put: Cheers, Henry

Jan. 27, 2011

Re: [Pharo-project] First commit to Pharoinbox. Need advice.

by Igor Stasenko

On 27 January 2011 07:28, HwaJong Oh <daliot.oh(a)gmail.com> wrote: > > Yes, you are right. I was wrong. There is nothing super send. I had error > editing my trait codes around "super", so i thought trait can super send. > Â http://screencast.com/t/yyjLLm0S > > MoveMethod: > > FriendOfPointArray >> > at: index > > Â Â Â Â ^(pointArray superAt: index * 2 - 1) @ (pointArray superAt: index * 2) > > to > > PointArrayTrait >> > at: index > > Â Â Â Â ^(super at: index * 2 - 1) @ (super at: index * 2) > > > while editing "pointArray superAt:" to "super at:", the editor made error. > Hehe.. funny mistake :) Btw, what is this FriendOfPointArray? The name sounds strange > Copying the code to native Mac editor, edit them, then copy back to Pharo > editor suceeded. > > > -- > View this message in context: http://forum.world.st/First-commit-to-Pharoinbox-Need-advice-tp3237535p3241… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Best regards, Igor Stasenko AKA sig.

Jan. 27, 2011

Re: [Pharo-project] SystemTracer

by Benjamin

It works for PharoCore-1.1-11196-UNSTABLE.1 but it seems to be the only version where it works :S Does someone know why ? Thanks, Ben On Jan 27, 2011, at 3:36 PM, Benjamin wrote: > Hello guys, > > for one of my projects, I'm trying to use SystemTracer to create anew image, but it appears that it doesn't work on Pharo ... > I can create a new image, but I can't open it. I've tried with an older VM (Squeak 3.8.18beta1U), but it's the same ... > > > Did someone already have this problem ? Does someone have a solution ? > > > > Thanks in advance, > > Ben

Jan. 27, 2011

Re: [Pharo-project] About FileSystem (probably not for 1.3)

by Alexandre Bergel

> ****Code without documentation and comments does not exist*** And tests. "A legacy application is an application that has no test" Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 27, 2011

[Pharo-project] Issue 3603 in pharo: O/ECompletion failure in Trait methods

by pharo＠googlecode.com

Status: Accepted Owner: ryd...(a)gmail.com CC: romain.r...(a)gmail.com Labels: Milestone-1.2-DevImage Milestone-1.3-DevImage OCompletion New issue 3603 by ryd...(a)gmail.com: O/ECompletion failure in Trait methods http://code.google.com/p/pharo/issues/detail?id=3603 A debugger pops up when typing in after super in a trait method, since traits do not implement superclass. Reproduction steps at: http://screencast.com/t/yyjLLm0S Mailing list thread: http://forum.world.st/First-commit-to-Pharoinbox-Need-advice-tp3237535p3241…

Jan. 27, 2011