Squeak-dev September 2012

squeak-dev@lists.squeakfoundation.org

36 participants
151 discussions

Re: Transform sends to ANSI standard?
by Hernán Morales Durand 27 Sep '12

27 Sep '12

On 25/09/2012 19:35, Benoit St-Jean wrote: > On 25/09/2012 2:31 PM, Hernán Morales Durand wrote: >> >> Hi folks, >> I am rewriting packages to be compatible or more portable between >> Smalltalks. Code Critics gives the following information on my packages: >> >> - #cr, #crlf, #lf, #space, #tab, #findTokens:, ... are not part of the >> ANSI string protocol. >> >> - #cr and #lf are not part of the ANSI stream protocol. >> >> - The ANSI standard does not support #asInteger and #asString on Object. >> >> - Some collection methods are not ANSI compatible: #pairsDo:, >> #collect:thenDo:, #reject:thenDo:, #detectSum:, #valuesDo:, >> #keysSortedSafely, #new:withAll:, etc. >> >> Does anyone have an idea on how to transform those sends to be ANSI >> compatible? > > Hi Hernan, > > I don't think being ANSI-compatible should be a goal in any case. You > won't find any Smalltalk flavor (commercial or Open Source) that is > fully ANSI-compatible. All vendors have their > extensions/exceptions/versions. Just have a look at Glorp to convince > yourself of differences between Smalltalk implementations! > > But if your goal is portability, I'd say you should start by having your > code compatible with VAST, VW, Dolphin & Squeak. You'll probably cover > most of other Smalltalks variants by doing so. The ANSI standard was > never, to my knowledge, 100% fully respected by any Smalltalk vendor. > Most of them tried to but none of them implemented it with 100% > compliance. In other words, just do your best at satisfying > compatibility with the most vendors. Hi Benoit, Just for the record :) I've worked with a custom implementation of Smalltalk which was 100% tested ANSI-compatible. It was in 2004 and unfortunately the project never saw the light except for our customer. However I wasn't in the team responsible for the ANSI compliance, but for the testing. It was called "Chachara Smalltalk" and it has some interesting features at that time: No object table, compacting generational GC with variable # of generations, C++ VM with reified ST meta-model, etc. You may see a screenshot here: http://www.screencast.com/t/PGm5VPr0 that proves nothing, but sometimes it's nice to see screenshots. > > This one uses Xtreams, the other one Nautilus browser or Zinc, the other > one starts Array indices at 1, this other one does this, the other one > does that, one uses Smalltalk while the other uses SmalltalkImage, etc. > Yes, but the goal of the standard is to provide an ideal protocol of behaviors. Globals are only defined if they conform a protocol. UI, Database and Graphics were unspecified until Smalltalk implementations converge... which could be never. > Unfortunately, we're not in the Java world. You'll eventually need a > Bundle/Application/Project/Package named "Portability" just like > everyone else... > I'm afraid so... I wonder what's the status of Grease. Any Seasider reading? Cheers, Hernán

1 0

Transform sends to ANSI standard?
by Hernán Morales Durand 26 Sep '12

26 Sep '12

Hi folks, I am rewriting packages to be compatible or more portable between Smalltalks. Code Critics gives the following information on my packages: - #cr, #crlf, #lf, #space, #tab, #findTokens:, ... are not part of the ANSI string protocol. - #cr and #lf are not part of the ANSI stream protocol. - The ANSI standard does not support #asInteger and #asString on Object. - Some collection methods are not ANSI compatible: #pairsDo:, #collect:thenDo:, #reject:thenDo:, #detectSum:, #valuesDo:, #keysSortedSafely, #new:withAll:, etc. Does anyone have an idea on how to transform those sends to be ANSI compatible? Best regards, Hernán

4 4

XML status in 4.3
by Hernán Morales Durand 25 Sep '12

25 Sep '12

You may be interested if you work with XML in Squeak. The instructions in http://www.squeaksource.com/XMLSupport.html for Squeak 4.3 only produces endless debuggers. It seems there are unsynchronized YAXO XML versions: In the Squeak trunk repo and XML-Parser in SqS (http://www.squeaksource.com/XMLSupport). The last common ancestor is: Name: XML-Parser-Alexandre_Bergel.19 UUID: a8fe6c4d-fa69-4921-8ef5-f939749ee78b Ancestors: XML-Parser-Alexandre_Bergel.18 Minor change in XMLElement>>contentString. I've managed to merge the contents from XMLSupport, but have to manually file in two missing dependencies: -OrderPreservingDictionary -BitmapCharacterSet which I've attached here. If you have comments or better approaches I'd be glad to see it. Cheers, Hernán

2 3

Daily Commit Log
by commits＠source.squeak.org 25 Sep '12

25 Sep '12

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2012-September/005526.… Name: Network-dtl.137 Ancestors: Network-ul.136 Add a preference for "Enable IPv6 and new network support" in preference category "general". If enabled, IPv6 and the new network support will be enabled if the required primitives are present in the VM, otherwise the new network support is disabled regardless of whether the VM provides IPv6 primitives. =============================================

1 0

[ANN] Updated FunSqueakCog4.2-10549-alpha.8.zip
by Edgar J. De Cleene 24 Sep '12

24 Sep '12

You could found it in http://ftp.squeak.org/Experiments/FunSqueakCog4.2-10549-alpha.8.zip List of packages as doing PackageOrganizer default packageNames saveOnFile for fresh Squeak4.2-10548-alpha, importing the .obj into Fun and doing the difference with PackageOrganizer default packageNames on it ('AST-Core' 'AST-Semantic' 'Aida' 'Alien-VMMaker-Plugins' 'Balloon3D-Constants' 'Balloon3D-Plugins' 'BroomMorphs-Base' 'BroomMorphs-Connectors' 'CGPrereqs' 'Comet-Core' 'Comet-Examples' 'Comet-Pharo-Core' 'Comet-Tests-Core' 'ConfigurationOfAida' 'ConfigurationOfGofer' 'ConfigurationOfGrease' 'ConfigurationOfKomHttpServer' 'ConfigurationOfMagritte2' 'ConfigurationOfMetacello' 'ConfigurationOfOmniBrowser' 'ConfigurationOfPier2' 'ConfigurationOfPierAddOns2' 'ConfigurationOfSPort2' 'ConfigurationOfSeaside30' 'ConfigurationOfSwazoo2' 'ConfigurationOfXMLSupport' 'Connectors' 'ConnectorsBasicDistro' 'ConnectorsDemo' 'ConnectorsGraphLayout' 'ConnectorsShapes' 'ConnectorsText' 'ConnectorsTools' 'ConsCell' 'Continuation' 'DynamicBindings' 'ECompletion' 'Environments' 'FFI-Kernel' 'FFI-Pools' 'FSM' 'FreeType' 'Freetype-Plugin' 'FunctionalTalk' 'Functions' 'Gofer-Core' 'Grease-Core' 'Grease-Pharo-Core' 'Grease-Tests-Core' 'Grease-Tests-Pharo-Core' 'HTML' 'InstanceEncoder' 'JQuery-Core' 'JQuery-Tests-Core' 'JQuery-Tests-UI' 'JQuery-UI' 'Javascript-Core' 'Javascript-Pharo-Core' 'Javascript-Tests-Core' 'Javascript-Tests-Pharo-Core' 'KomHttpServer' 'KomServices' 'Magritte-Model' 'Magritte-Morph' 'Magritte-Pharo-Model' 'Magritte-Pharo-Seaside' 'Magritte-Seaside' 'MemoryAccess' 'Metacello-Core' 'Metacello-MC' 'Metacello-Platform' 'MorphicGames' 'MorphicPuzzle' 'MorphicWrappers' 'MuO' 'MuO39' 'Network-IRC' 'OB-Morphic' 'OB-Refactory' 'OB-Regex' 'OB-SUnitIntegration' 'OB-Shout' 'OMeta2-Postload' 'OMeta2-Preload' 'OSC' 'OSProcess' 'Ocompletion' 'OmniBrowser' 'People' 'Pier-Blog' 'Pier-Book' 'Pier-Documents' 'Pier-EditorEnh' 'Pier-Google' 'Pier-LinkChecker' 'Pier-Model' 'Pier-Pharo-Model' 'Pier-Pharo-Persistency' 'Pier-Pharo-Seaside' 'Pier-Seaside' 'Pier-Security' 'Pier-Setup' 'PluggableMemory' 'ProcessProperties' 'Prolog' 'Prototype-Core' 'Prototype-Tests-Core' 'REPLMorph' 'RSS-Core' 'RSS-Examples' 'RSS-Tests-Core' 'Refactoring-Core' 'Refactoring-Spelling' 'Regex' 'RoelTyper' 'Scriptaculous-Components' 'Scriptaculous-Core' 'Scriptaculous-Tests-Components' 'Scriptaculous-Tests-Core' 'Seaside-Adaptors-Comanche' 'Seaside-Adaptors-Swazoo' 'Seaside-Canvas' 'Seaside-Component' 'Seaside-Core' 'Seaside-Development' 'Seaside-Email' 'Seaside-Environment' 'Seaside-Examples' 'Seaside-FileSystem' 'Seaside-Flow' 'Seaside-HTML5' 'Seaside-InternetExplorer' 'Seaside-Pharo-Canvas' 'Seaside-Pharo-Continuation' 'Seaside-Pharo-Core' 'Seaside-Pharo-Development' 'Seaside-Pharo-Email' 'Seaside-Pharo-Environment' 'Seaside-Pharo-Flow' 'Seaside-Pharo-Tools-OmniBrowser' 'Seaside-Pharo-Tools-Web' 'Seaside-RenderLoop' 'Seaside-Session' 'Seaside-Swazoo' 'Seaside-Tests-Adaptors-Comanche' 'Seaside-Tests-Canvas' 'Seaside-Tests-Component' 'Seaside-Tests-Core' 'Seaside-Tests-Development' 'Seaside-Tests-Email' 'Seaside-Tests-Environment' 'Seaside-Tests-Examples' 'Seaside-Tests-FileSystem' 'Seaside-Tests-Flow' 'Seaside-Tests-Functional' 'Seaside-Tests-HTML5' 'Seaside-Tests-InternetExplorer' 'Seaside-Tests-Pharo-Continuation' 'Seaside-Tests-Pharo-Core' 'Seaside-Tests-Pharo-Development' 'Seaside-Tests-Pharo-Functional' 'Seaside-Tests-RenderLoop' 'Seaside-Tests-Session' 'Seaside-Tests-Tools-Web' 'Seaside-Tests-UTF8' 'Seaside-Tools-Core' 'Seaside-Tools-OmniBrowser' 'Seaside-Tools-Web' 'Seaside-Welcome' 'Seaside-Widgets' 'Services' 'SharedPool-Speech' 'Shout' 'ShoutWorkspace' 'SlangBrowser' 'SplitJoin' 'Sport' 'Star functions' 'StringFormat' 'Swazoo' 'TestBrowser' 'VB-Regex' 'VMConstruction-Plugins-AioPlugin' 'VMConstruction-Plugins-OSProcessPlugin' 'VMConstruction-Plugins-XDisplayControlPlugin' 'VMMaker'). I start a page on trying to write all I made http://wiki.squeak.org/squeak/6159 Remember, the image is created and saved with John Cog Vm, I have working on Mac and Vista until now, no luck with Ubuntu, but sure my fault. I must to do some quick dirty fixes for having the tall house of cards, put in the page for brave and deeper Squeakers take, refine and put in trunk Must keep older builds into Experiments, or delete ? Edgar

7 21

Connectors on 4.3?
by Lawson English 24 Sep '12

24 Sep '12

I was hoping to use the Connectors package with Squeak 4.3 so I obtained it from gemstone, where Chriss Muller had left a version with the underscores (and a few other incompatibilities I assume) removed. Unfortunately, it asks for QHsmMorphicEventHandler QHsmMorph as part of the install process via Monticello. Are these in another package that I missed or do I need to reinvent the wheel and try to make them work with 4.3 as well? Thanks. L -- Squeak from the very start (introduction to Squeak and Pharo Smalltalk for the (almost) complete and compleate beginner). https://www.youtube.com/playlist?list=PL6601A198DF14788D&feature=view_all

2 1

Why would you choose Squeak today?
by Hernán Morales Durand 24 Sep '12

24 Sep '12

No flame war intended. Maybe this topic has been discussed on this list, but I've never found a satisfactory conclusion. With "today" I mean why to start a software project *from scratch* with Squeak? My usage today is to load and try packages which only works under Squeak. Yours may be different, so it would be nice to know what squeak developers think about. What thing does have Squeak that others doesn't? Why would you choose Squeak over Pharo or Cincom Smalltalk? Cheers, Hernán

7 7

Re: Why would you choose Squeak today?
by Joseph J Alotta 24 Sep '12

24 Sep '12

How come nobody mentions gnu smalltalk as a possibility? On Sep 24, 2012, at 7:00 AM, squeak-dev-request(a)lists.squeakfoundation.org wrote: > Re: Why would you choose Squeak today? (C

4 3

The Trunk: Network-dtl.137.mcz
by commits＠source.squeak.org 24 Sep '12

24 Sep '12

David T. Lewis uploaded a new version of Network to project The Trunk: http://source.squeak.org/trunk/Network-dtl.137.mcz ==================== Summary ==================== Name: Network-dtl.137 Author: dtl Time: 23 September 2012, 1:32:32.394 pm UUID: b4bcd6e4-6a2d-4fc6-be4b-0d01accc3c72 Ancestors: Network-ul.136 Add a preference for "Enable IPv6 and new network support" in preference category "general". If enabled, IPv6 and the new network support will be enabled if the required primitives are present in the VM, otherwise the new network support is disabled regardless of whether the VM provides IPv6 primitives. =============== Diff against Network-ul.136 =============== Item was changed: Object subclass: #NetNameResolver instanceVariableNames: '' + classVariableNames: 'DefaultHostName EnableIPv6 HaveNetwork ResolverBusy ResolverError ResolverMutex ResolverReady ResolverSemaphore ResolverUninitialized UseOldNetwork' - classVariableNames: 'DefaultHostName HaveNetwork ResolverBusy ResolverError ResolverMutex ResolverReady ResolverSemaphore ResolverUninitialized UseOldNetwork' poolDictionaries: '' category: 'Network-Kernel'! !NetNameResolver commentStamp: '<historical>' prior: 0! This class implements TCP/IP style network name lookup and translation facilities. Attempt to keep track of whether there is a network available. HaveNetwork true if last attempt to contact the network was successful. LastContact Time of that contact (totalSeconds). haveNetwork returns true, false, or #expired. True means there was contact in the last 30 minutes. False means contact failed or was false last time we asked. Get out of false state by making contact with a server in some way (FileList or updates).! Item was added: + ----- Method: NetNameResolver class>>enableIPv6 (in category 'system startup') ----- + enableIPv6 + <preference: 'Enable IPv6 and new network support' + category: 'general' + description: 'If true allow IPv6 support. If false, NetNameResolver useOldNetwork is set.' + type: #Boolean> + ^EnableIPv6! Item was added: + ----- Method: NetNameResolver class>>enableIPv6: (in category 'system startup') ----- + enableIPv6: aBool + "Set a preference to control whether IPv6 primitives and new network support + should be used if available, and reinitialize the UseOldNetwork flag to recognize + the setting. If true, the new networking support will be used if the VM provides + the required primitives. If false, IPv6 and new network support will not be used. + The new network support may be unreliable on some platforms, so this preference + allows it to be explicitly disabled." + + EnableIPv6 := aBool. + self initializeOldNetworkFlag + ! Item was changed: ----- Method: NetNameResolver class>>initialize (in category 'class initialization') ----- initialize "NetNameResolver initialize" "Note: On the Mac, the name resolver is asynchronous (i.e., Squeak can do other things while it is working), but can only handle one request at a time. On other platforms, such as Unix, the resolver is synchronous; a call to, say, the name lookup primitive will block all Squeak processes until it returns." "Resolver Status Values" ResolverUninitialized := 0. "network is not initialized" ResolverReady := 1. "resolver idle, last request succeeded" ResolverBusy := 2. "lookup in progress" ResolverError := 3. "resolver idle, last request failed" DefaultHostName := ''. UseOldNetwork := self hasIpv6PrimSupport not. + self enableIPv6: true. "Initialize preference to permit use of new networking" Smalltalk addToStartUpList: self. ! Item was added: + ----- Method: NetNameResolver class>>initializeOldNetworkFlag (in category 'system startup') ----- + initializeOldNetworkFlag + + UseOldNetwork := self hasIpv6PrimSupport not or: [self enableIPv6 ~= true]! Item was changed: ----- Method: NetNameResolver class>>startUp: (in category 'system startup') ----- startUp: resuming + "Set the UseOldNetwork flag if ipv6 primitives are not present or if the EnableIPv6 preference is not set." - "Set the UseOldNetwork flag if ipv6 primitives are not present" + resuming ifTrue: [self initializeOldNetworkFlag]! - resuming ifTrue: [UseOldNetwork := self hasIpv6PrimSupport not]!

1 0

Why would you choose Squeak today?
by Chris Cunnington 24 Sep '12

24 Sep '12

> Ours community is the most intellectually free. If not exactly the most literate. Let me try again: Ours is the community that is the most intellectually free. There. Got it right that time. Chris

1 0

← Newer
1
2
3
4
5
6
7
...
16
Older →

Jump to page: