December 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Popularity or not of smalltalk?

by James Ladd

While pleading for Smalltalk support with a developer from a popular and great IDE company, I got the following response (below) Is there anything I can do/show to prove or disprove the popularity of Smalltalk? Rgs, James. >>Hello James.>>About Smalltalk plugin. Weel, Iâm not sure Smalltalk has a big audience now. Iâve never heard about commercial products based on Smalltalk. >>Here, some statistics http://langpop.com/

Dec. 6, 2010

Re: [Pharo-project] ProcessWrapper

by Facundo Vozzi

Hi Levente, I'll try with ProcessWrapperPlugin in order to use it with Pharo 1.1.1. I would love that squeak and pharo join back together. Thanks you very much, Facu On Sat, Dec 4, 2010 at 10:24 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Sat, 4 Dec 2010, Facundo Vozzi wrote: > > Hi all, >> anybody is using ProcessWrapper in Pharo 1.1.1 ? I'm using windows and It >> works fine on Squeak 4.1.1 but it doesn't on >> my Pharo 1.1.1 which is my development environment. >> > > I uploaded a new version to the repository (ProcessWrapper-Core.ul-30) > which fixes two issues in Pharo 1.2 (both related to the lack of proper > deprecation policy in Pharo). > > Pharo 1.1 (and 1.1.1) is a bit harder to fix, because there's a bug in > MIMEDocument class >> #guessTypeFromName:. This method tries to send > #forURIReturnSingleMimeTypeOrDefault: to MIMEType, but that class doesn't > implement this method. Actually no class implements this is Pharo 1.1. > > But you can avoid this problem by downloading the prebuilt plugin dll from > > http://people.inf.elte.hu/uzonyile/ProcessWrapper/2/ProcessWrapperPlugin.dl… copy it to your image or VM folder before loading the package to your > image. > > > Levente > > >> Thanks in advance, >> Facu >> >> >

Dec. 6, 2010

Re: [Pharo-project] ProcessWrapper

by Facundo Vozzi

I use it to export html to pdf with wkhtmltopdf. Facu On Sat, Dec 4, 2010 at 5:16 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > What does ProcessWrapper do? > > Lukas > > On 4 December 2010 16:24, Facundo Vozzi <facundov79(a)gmail.com> wrote: > > Hi all, > > anybody is using ProcessWrapper in Pharo 1.1.1 ? I'm using windows and > It > > works fine on Squeak 4.1.1 but it doesn't on > > my Pharo 1.1.1 which is my development environment. > > Thanks in advance, > > Facu > > > > -- > Lukas Renggli > www.lukas-renggli.ch > >

Dec. 6, 2010

Re: [Pharo-project] Global shortcut keys in Pharo

by Tony Fleig

Sean, what is the URL of your SqS projects page? TF On Sun, Dec 5, 2010 at 6:59 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > Mariano Martinez Peck wrote: >> >> I remember... Sean working on KeyMapping, KeyBindings or >> something like that. >> > > Yes, I ported KeyMapping to Pharo because it seemed like the model people > liked best. Â IIRC KeyBindings probably wouldn't be too hard to port. Â Both > are on SqueakSource, but if I didn't have write access, check my SqS > projects page for updated versions. > > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Global-shortcut-keys-in-Pharo-tp3072091p3073313.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Dec. 6, 2010

Re: [Pharo-project] Comments or no integration: a simple choice for you

by Tony Fleig

As a new reader of Pharo code I have frequently been dismayed at the lack of even the most cursory comments for many of the classes. Yes, good code (short methods, good names, etc.) doesn't require commenting, but a brief overview of a class's purpose and essential processing can help quite a lot. Examples of common usage patterns are essential if you want people to use the class properly. Good decision. TF On Sun, Dec 5, 2010 at 12:52 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I decided that I will not integrate any code that is not documented in Pharo. > > I strongly suggest to remove from Pharo-dev packages whose classes are not commented. > I'm not sure that I will look at code or answer question to code that is not commented. > We should change our mindset and it seems that we do not care, so we should take radical decisions: > Â Â Â Â less changes, less progress, more comments. > > And for once I will not bash the past. Smalltalk was always with methods fully documented. > We are just plain lazy and this is a shame. > > Stef >

Dec. 5, 2010

Re: [Pharo-project] Comments or no integration: a simple choice for you

by Mariano Martinez Peck

On Sun, Dec 5, 2010 at 9:52 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi guys > > I decided that I will not integrate any code that is not documented in > Pharo. > > I strongly suggest to remove from Pharo-dev packages whose classes are not > commented. > I think this is not a good idea...look this approx: | pharoCorePackages packagesDev nonCommentedClasses totalClasses | pharoCorePackages := #('MultilingualTests' 'Morphic' 'ToolBuilder-Kernel' 'PackageInfo' 'Polymorph-ToolBuilder' 'Network-Kernel' 'Network-Protocols' 'Compiler' 'System-Finalization' 'Settings-Graphics' 'Collections' 'Network-RemoteDirectory' 'Traits' 'Network-URI' 'Settings-Display' 'Collections-Abstract' 'Settings-Compiler' 'MonticelloMocks' 'ScriptLoader11' 'System-Digital Signatures' 'System-Localization' 'MenuRegistration' 'Polymorph-TaskbarIcons' 'Monticello' 'ToolBuilder-Morphic' 'MCDirtyPackage' 'Collections-Weak' 'Settings-Polymorph' 'Tests' 'HelpSystem-Core-Utilities' 'SUnit' 'Collections-Text' 'Compression' 'Morphic-MorphTreeWidget' 'HelpSystem-Core' 'ToolsTest' 'Gofer-Core' 'Gofer-Tests' 'Collections-Stack' 'FreeType' 'MonticelloConfigurations' 'Polymorph-Geometry' 'Collections-Support' 'SUnitGUI' 'HelpSystem-Core-Model' 'Tests-VM' 'System-Change Notification' 'System' 'Tests-ObjectsAsMethods' 'HostMenus' 'Network-MIME' 'Network-RFC822' 'VB-Regex' 'TrueType' 'DeprecatedPreferences' 'System-Clipboard' 'System-Settings' 'MorphicTests' 'System-Serial Port' 'NetworkTests' 'Collections-Unordered' 'System-Changes' 'System-Object Storage' 'Collections-Traits' 'System-Platforms' 'Tests-PrimCallController' 'Morphic-TrueType' 'Multilingual' 'Graphics' 'Collections-Strings' 'KernelTests' 'System-FileRegistry' 'Tests-Bugs' 'ToolBuilder-SUnit' 'Tests-Release' 'Morphic-Balloon' 'Settings-Network' 'System-Applications' 'Polymorph-Tools-Diff' 'Settings-Tools' 'ScriptLoader' 'ST80' 'FreeTypeSubPixelAntiAliasing' 'Settings-Kernel' 'Settings-System' 'CompilerTests' 'System-Tools' 'System-Hashing' 'System-Download' 'Collections-Streams' 'Tests-SystemChangeNotification' 'GraphicsTests' 'Polymorph-Widgets' 'Kernel' 'Tools' 'Settings-FreeType' 'FreeTypeTests' 'Settings-Monticello' 'HelpSystem-Tests' 'Polymorph-EventEnhancements' 'System-Support' 'MonticelloGUI' 'System-FilePackage' 'System-Object Events' 'Announcements' 'System-Text' 'Exceptions' 'Network-UUID' 'System-Pools' 'FixUnderscores' 'HelpSystem-Core-UI' 'GraphicsResources' 'Files' 'Gofer' 'Network-MailSending' 'Collections-Arrayed' 'CollectionsTests' 'Balloon' 'Network-Url' 'Collections-Sequenceable' ). packagesDev := (PackageInfo allPackages collect: [:each | each packageName]) difference: pharoCorePackages. nonCommentedClasses := packagesDev inject: 0 into: [:sum :each | sum + (((PackageInfo named: each) classes select: [:aClass | aClass comment asString includesSubString: 'is xxxxxxxxx.']) size)]. Transcript show: 'nonCommentedClasses: ', nonCommentedClasses asString. totalClasses := packagesDev inject: 0 into: [:sum :each | sum + (PackageInfo named: each) classes size ]. Transcript show: 'totalClasses: ', totalClasses asString. Shows: nonCommentedClasses: 1116 totalClasses: 1369 > I'm not sure that I will look at code or answer question to code that is > not commented. > We should change our mindset and it seems that we do not care, so we should > take radical decisions: > less changes, less progress, more comments. > > And for once I will not bash the past. Smalltalk was always with methods > fully documented. > We are just plain lazy and this is a shame. > > Stef >

Dec. 5, 2010

Re: [Pharo-project] Parsing and navigating Html

by StÃ©phane Ducasse

Hi paul I started to write some comments and more tests as well as writing a small Documentation. May be to be turned into a Help later. Now a question, I tried to write a comment for and I was wondering why not returning '' instead of nil in string. It will avoid to have isNil everywhere. I did not touch that code for now. string ^ (children size = 1 and: [(children at: 1) isString]) ifTrue: [(children at: 1) contents] ifFalse: [nil] testString | soup | soup := Soup fromString: 'foo'. self assert: (soup b string = 'foo'). soup := Soup fromString: 'feo'. self assert: (soup b string) isNil Stef

Dec. 5, 2010

Re: [Pharo-project] Pharo 1.1.1 (CogVM) crashes when saving Monticello packages to any repository due to possible bug in primitive UUID generation

by Mariano Martinez Peck

marcus, maybe we can fix this for the one clicks? cheers mariano On Sun, Dec 5, 2010 at 10:12 PM, jaayer <jaayer(a)zoho.com> wrote: > > > > > ---- On Sun, 05 Dec 2010 12:55:17 -0800 Igor Stasenko wrote ---- > > >On 5 December 2010 20:53, jaayer wrote: > >> > >> > >> I have found that I cannot save any package to any repository (local or > Squeaksource) using Pharo 1.1.1 with the CogVM on 64-bit Ubuntu 10.10. After > being prompted to describe the changes to the package and then accepting, > the entire image just crashes with the stack dump below. I do have the > proper IA32-libs installed (to run 32-bit applications on a 64-bit Linux), > and everything else seems to work fine, including loading of Monticello > packages. > >> > >> This code: "UUID new primMakeUUID" can produce the crash. Changing > UUID>>primMakeUUID to use the non-primitive implementation: > >> UUIDGenerator default generateBytes: self forVersion: 4. > >> stops the crashing. > >> > > > >UUID bug is well known for a long time. > >It is plaguing us for 2 years i think. > > I see, my mistake. I assumed it was new because this is the first time I > have ever encountered it on Linux after two years of using Pharo, and there > were no recent posts here discussing it (though searching just now, I found > a thread concerning Cog and UUID crashes from last October) or related > issues in the tracker that I could find. But I feel compelled to stress that > the current Pharo 1.1.1 OneClick distribution is shipping with this bug in > it, and the previous 1.1 distribution did not. Perhaps this quarrelsome > plug-in should be disabled by default, if only on Linux. I would hate for a > budding Pharo user to encounter this while going through the exercises in > Pharo By Example. > > >-- > >Best regards, > >Igor Stasenko AKA sig. > > > > > > >

Dec. 5, 2010

Re: [Pharo-project] Comments or no integration: a simple choice for you

by laurent laffont

On Sun, Dec 5, 2010 at 10:10 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Stef, > > IMHO, before we take such a stance, we should have a package comment pane > and encourage its use. A complex package is probably best documented with a > good high-level description and some type of example(s), which can take the > form of do-its in a package comment. > > A package comment could be expected to provide or point to appropriate > examples/tests for the package. That solves the problem while allowing for > contributors' styles and the "shape" of the code. Something with just a few > classes is well-served by class comments; something with many classes > presents the would-be reader with a treasure hunt to find the correct class > comment. > > We might also create a #help mechanism so that something like > > CzAuthor help > > gathers class and package comments that might exist. > HelpSystem does this and is included in PharoCore. See http://www.pharocasts.com/2010/09/document-with-helpsystem.html Laurent > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [ > pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse > [stephane.ducasse(a)inria.fr] > Sent: Sunday, December 05, 2010 3:52 PM > To: Pharo-project(a)lists.gforge.inria.fr Development > Subject: [Pharo-project] Comments or no integration: a simple choice for > you > > Hi guys > > I decided that I will not integrate any code that is not documented in > Pharo. > > I strongly suggest to remove from Pharo-dev packages whose classes are not > commented. > I'm not sure that I will look at code or answer question to code that is > not commented. > We should change our mindset and it seems that we do not care, so we should > take radical decisions: > less changes, less progress, more comments. > > And for once I will not bash the past. Smalltalk was always with methods > fully documented. > We are just plain lazy and this is a shame. > > Stef > >

Dec. 5, 2010

[Pharo-project] Pharocasts: access SQLite databases through ODBC

by laurent laffont

See how to setup and access an SQLite database through ODBC on Windows. Recorded by Torsten Bergmann. Enjoy: http://www.pharocasts.com/2010/12/access-database-through-odbc.html Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Dec. 5, 2010