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

[Pharo-project] Issue 3606 in pharo: [1.1.2] [Failing Test] Undeclared in package shout

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.1.2 New issue 3606 by marcus.d...(a)gmail.com: [1.1.2] [Failing Test] Undeclared in package shout http://code.google.com/p/pharo/issues/detail?id=3606 unstyledAcceptText styler hmm... these where not there before. Are we sure that 1.1 does *not* load the latest packages?

Jan. 28, 2011

Re: [Pharo-project] Issue 3576 in pharo: [Failing Tests] Hudson Full 1.1 Tests.Release.ReleaseTest.testUndeclared

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3576 by marcus.d...(a)gmail.com: [Failing Tests] Hudson Full 1.1 Tests.Release.ReleaseTest.testUndeclared http://code.google.com/p/pharo/issues/detail?id=3576 these are now gone

Jan. 28, 2011

Re: [Pharo-project] Issue 3469 in pharo: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy

by pharo＠googlecode.com

Updates: Labels: Milestone-1.1.2 Comment #2 on issue 3469 by marcus.d...(a)gmail.com: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy http://code.google.com/p/pharo/issues/detail?id=3469 (No comment was entered for this change.)

Jan. 28, 2011

[Pharo-project] Issue 3605 in pharo: [ENH]: Added #saveTo: method to MIMEDocument

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3605 by sean.p.d...(a)gmail.com: [ENH]: Added #saveTo: method to MIMEDocument http://code.google.com/p/pharo/issues/detail?id=3605 When downloading via Url classes, this makes it more straight-forward to save (an image for example), now: aUrl retrieveContents saveAs: savePath. instead of: FileStream forceNewFileNamed: anAbsolutePathString do: [ :str | str binary. str nextPutAll: (aUrl retrieveContents contents) ]. Attachments: MIMEDocument-saveAs.st 324 bytes

Jan. 28, 2011

Re: [Pharo-project] Issue 3595 in pharo: problem starting up with a script on windows

by pharo＠googlecode.com

Updates: Labels: Importance-High Comment #1 on issue 3595 by tudor.gi...(a)gmail.com: problem starting up with a script on windows http://code.google.com/p/pharo/issues/detail?id=3595 Is there nobody that has a Windows to test this issue?

Jan. 28, 2011

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

by Norbert Hartl

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] About FileSystem (probably not for 1.3)

by StÃ©phane Ducasse

On Jan 28, 2011, at 12:00 AM, Lukas Renggli wrote: >> I started to merge some of your changes to FS. > > I already merged most of the changes of Max into the main code. > >> Now I was wondering about this one: >> ***for my work on GitFS I needed a resumable exception (alternatively an ifPresent block would have done the trick but that would have ment more meddling with Filesystem) to delete existing files when copying. The following changes are a result of introducing this exception to the copy methods. >> *added class FSFileExistsResumbale and its superclass FSFilesystemException to support the changes to the copy methods >> *#copy:to: signals FSFileExistsResumbale instead of FSFileExists >> *FSCopyVisitor>>copyDirectory uses #ensureDirectory instead of #createDirectory >> *needed to change FSFilesystemTest>>testCopyDestExists to expect FSFileExistsResumable >> *FSReference>>basicCopyTo: signals FSFileExistsResumable instead of FSFileExists >> >> Could you explain us a bit more? > > This is not something that should go into the main code. If I remember > correctly this was a quick hack to avoid some problems in GitFS. Thanks lukas this is what I thought too. I picked some of the other elements. And I'm continuing to add comments. I will take your blog as starting material for a chapter. Stef > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Jan. 28, 2011

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

by StÃ©phane Ducasse

On Jan 27, 2011, at 10:56 PM, Dale Henrichs wrote: > Sounds good ... I'll work through the changes that I've made and try to extract out the goodness and then provide suggested changes (in the form of an mcz file you can merge if the changes make sense to you)... > > BTW, I used the FileSystem port with a Monticello port (replacing all of the FileDirectory stuff with FileSystem calls) and the Monticello port was based on a fairly recent Pharo version of Monticello:) Excellent > > Dale > > On 01/27/2011 01:34 PM, StÃ©phane Ducasse wrote: >> I'm. :) >> I do not want differences for the shake for them. I want an excellent system. >> I'm working on PharoTaskForces so if you can merge step by step it would be great. >> >> Stef >> >> >> On Jan 27, 2011, at 10:31 PM, Dale Henrichs wrote: >> >>> Stef, >>> >>> I have ported FileSystem to GemStone, but I had to make a number of changes that were necessary to improve the portability (at least for GemStone) ... It would be a bit of work for me to extract the changes, but I'd be willing to do it if you were interested in incorporated some of them (if not all) ... >>> >>> Dale >>> >>> On 01/27/2011 12:58 PM, StÃ©phane Ducasse wrote: >>>> Hi max >>>> >>>> I started to merge some of your changes to FS. >>>> Now I was wondering about this one: >>>> >>>> ***for my work on GitFS I needed a resumable exception (alternatively an ifPresent block would have done the trick but that would have ment more meddling with Filesystem) to delete existing files when copying. The following changes are a result of introducing this exception to the copy methods. >>>> *added class FSFileExistsResumbale and its superclass FSFilesystemException to support the changes to the copy methods >>>> *#copy:to: signals FSFileExistsResumbale instead of FSFileExists >>>> *FSCopyVisitor>>copyDirectory uses #ensureDirectory instead of #createDirectory >>>> *needed to change FSFilesystemTest>>testCopyDestExists to expect FSFileExistsResumable >>>> *FSReference>>basicCopyTo: signals FSFileExistsResumable instead of FSFileExists >>>> >>>> Could you explain us a bit more? >>>> >>>> Stef >>>>> >>>> >>> >> >

Jan. 28, 2011

Re: [Pharo-project] CommandShell

by Sean P. DeNigris

After loading CommandShell-dtl.50 (and .45, which works in Squeak 4.1), when I evaluate: (PipeableOSProcess command: 'ls') output I get a NonBooleanReceiver error when AttachableFileStream>>upToEndOfFile calls #atEndOfFile, which returns nil. Sean p.s. I also tried loading the latest Pharo package from the CommandShell repo -- View this message in context: http://forum.world.st/CommandShell-tp2226990p3243890.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 28, 2011

[Pharo-project] Smalltalk at FOSDEM in Brussels in February

by Geert Claes

For those who have missed http://astares.blogspot.com/2011/01/seaside-at-fossdem.html Torsten's and http://www.jarober.com/blog/blogView?showComments=true&printTitle=Seaside_a… James' blog posts or the post below on the Seaside mailing list; Smalltalk/Seaside at FOSDEM in Brussels on Sunday Feb 6 at 15:00 in room AW1.120 Link to FOSDEM: http://fosdem.org/2011/schedule/event/cfgmgmtdev http://fosdem.org/2011/schedule/event/cfgmgmtdev Stephan Eggermont wrote: > > Sunday 2011-2-6 we'll show how we deployed our Seaside application. If > you're interested, please join us. > > Stephan > > Configuration & Systems Management devroom (room AW1.120) > â¢ 15:00 - 15:45: Configuration management for developers (Stephan > Eggermont, Willem van den Ende) > > We created a server environment so a small startup could deploy its web > application with all the services it needs. Well, environment is a big > word... bootstrapped startups don't have money to manage redundant > servers, so we set up just one production server. Still, when disaster > strikes, we want to be able to have another server up and running within > thirty minutes. For developers laziness is a virtue. Therefore we want to > apply DRY (don't repeat yourself) to systems administration. So for this > project we considered each time we log in to the production server a > 'systems administration smell'. Attend our case study to see how we used a > configuration managent system (puppet), application specific scripts and a > few practices to keep us sane. See how far we have gotten towards our goal > of DRYness and fast recovery, and learn from our mistakes. > -- View this message in context: http://forum.world.st/Smalltalk-at-FOSDEM-in-Brussels-in-February-tp3243873… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 28, 2011