November 2013 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Nov. 14, 2013

Nov. 14, 2013

Branch: refs/tags/30572 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 7e8aec: 30572
by GitHub Nov. 14, 2013

Nov. 14, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 7e8aecb3db7443eac0fed55f1837fd13794d6e55 https://github.com/pharo-project/pharo-core/commit/7e8aecb3db7443eac0fed55f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-14 (Thu, 14 Nov 2013) Changed paths: A Deprecated30.package/MIMEType.class/README.md A Deprecated30.package/MIMEType.class/class/accessing/defaultSuffixes.st A Deprecated30.package/MIMEType.class/class/accessing/huntForDashAndRemove_.st A Deprecated30.package/MIMEType.class/class/accessing/mimeMappings.st A Deprecated30.package/MIMEType.class/class/accessing/simpleSuffixForMimeType_.st A Deprecated30.package/MIMEType.class/class/accessing/suffixForMimeType_.st A Deprecated30.package/MIMEType.class/class/class initialization/initialize.st A Deprecated30.package/MIMEType.class/class/class initialization/initializeDefaultSuffixes.st A Deprecated30.package/MIMEType.class/class/class initialization/initializeStandardMIMETypes.st A Deprecated30.package/MIMEType.class/class/class initialization/standardMIMETypes.st A Deprecated30.package/MIMEType.class/class/class initialization/standardMIMETypes2.st A Deprecated30.package/MIMEType.class/class/instance creation/contentTypeURLEncoded.st A Deprecated30.package/MIMEType.class/class/instance creation/defaultHTML.st A Deprecated30.package/MIMEType.class/class/instance creation/defaultStream.st A Deprecated30.package/MIMEType.class/class/instance creation/defaultText.st A Deprecated30.package/MIMEType.class/class/instance creation/forExtensionReturnMimeTypesOrNil_.st A Deprecated30.package/MIMEType.class/class/instance creation/forFileNameReturnMimeTypesOrDefault_.st A Deprecated30.package/MIMEType.class/class/instance creation/forFileNameReturnMimeTypesOrNil_.st A Deprecated30.package/MIMEType.class/class/instance creation/forFileNameReturnSingleMimeTypeOrDefault_.st A Deprecated30.package/MIMEType.class/class/instance creation/forFileNameReturnSingleMimeTypeOrNil_.st A Deprecated30.package/MIMEType.class/class/instance creation/fromMIMEString_.st A Deprecated30.package/MIMEType.class/class/instance creation/main_sub_.st A Deprecated30.package/MIMEType.class/class/instance creation/main_sub_parameters_.st A Deprecated30.package/MIMEType.class/class/instance creation/new.st A Deprecated30.package/MIMEType.class/definition.st A Deprecated30.package/MIMEType.class/instance/accessing/main.st A Deprecated30.package/MIMEType.class/instance/accessing/main_.st A Deprecated30.package/MIMEType.class/instance/accessing/parameters_.st A Deprecated30.package/MIMEType.class/instance/accessing/sub.st A Deprecated30.package/MIMEType.class/instance/accessing/sub_.st A Deprecated30.package/MIMEType.class/instance/comparing/=.st A Deprecated30.package/MIMEType.class/instance/comparing/beginsWith_.st A Deprecated30.package/MIMEType.class/instance/comparing/hash.st A Deprecated30.package/MIMEType.class/instance/converting/asMIMEType.st A Deprecated30.package/MIMEType.class/instance/printing/printOn_.st R FileSystem-Core.package/MIMEType.class/README.md R FileSystem-Core.package/MIMEType.class/class/accessing/defaultSuffixes.st R FileSystem-Core.package/MIMEType.class/class/accessing/huntForDashAndRemove_.st R FileSystem-Core.package/MIMEType.class/class/accessing/mimeMappings.st R FileSystem-Core.package/MIMEType.class/class/accessing/simpleSuffixForMimeType_.st R FileSystem-Core.package/MIMEType.class/class/accessing/suffixForMimeType_.st R FileSystem-Core.package/MIMEType.class/class/class initialization/initialize.st R FileSystem-Core.package/MIMEType.class/class/class initialization/initializeDefaultSuffixes.st R FileSystem-Core.package/MIMEType.class/class/class initialization/initializeStandardMIMETypes.st R FileSystem-Core.package/MIMEType.class/class/class initialization/standardMIMETypes.st R FileSystem-Core.package/MIMEType.class/class/class initialization/standardMIMETypes2.st R FileSystem-Core.package/MIMEType.class/class/instance creation/contentTypeURLEncoded.st R FileSystem-Core.package/MIMEType.class/class/instance creation/defaultHTML.st R FileSystem-Core.package/MIMEType.class/class/instance creation/defaultStream.st R FileSystem-Core.package/MIMEType.class/class/instance creation/defaultText.st R FileSystem-Core.package/MIMEType.class/class/instance creation/forExtensionReturnMimeTypesOrNil_.st R FileSystem-Core.package/MIMEType.class/class/instance creation/forFileNameReturnMimeTypesOrDefault_.st R FileSystem-Core.package/MIMEType.class/class/instance creation/forFileNameReturnMimeTypesOrNil_.st R FileSystem-Core.package/MIMEType.class/class/instance creation/forFileNameReturnSingleMimeTypeOrDefault_.st R FileSystem-Core.package/MIMEType.class/class/instance creation/forFileNameReturnSingleMimeTypeOrNil_.st R FileSystem-Core.package/MIMEType.class/class/instance creation/fromMIMEString_.st R FileSystem-Core.package/MIMEType.class/class/instance creation/main_sub_.st R FileSystem-Core.package/MIMEType.class/class/instance creation/main_sub_parameters_.st R FileSystem-Core.package/MIMEType.class/class/instance creation/new.st R FileSystem-Core.package/MIMEType.class/definition.st R FileSystem-Core.package/MIMEType.class/instance/accessing/main.st R FileSystem-Core.package/MIMEType.class/instance/accessing/main_.st R FileSystem-Core.package/MIMEType.class/instance/accessing/parameters_.st R FileSystem-Core.package/MIMEType.class/instance/accessing/sub.st R FileSystem-Core.package/MIMEType.class/instance/accessing/sub_.st R FileSystem-Core.package/MIMEType.class/instance/comparing/=.st R FileSystem-Core.package/MIMEType.class/instance/comparing/beginsWith_.st R FileSystem-Core.package/MIMEType.class/instance/comparing/hash.st R FileSystem-Core.package/MIMEType.class/instance/converting/asMIMEType.st R FileSystem-Core.package/MIMEType.class/instance/printing/printOn_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script228.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30572.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/MetacelloConfigurationBrowserToolbar.class/instance/initialization/setInstallModel.st M Tools.package/MetacelloConfigurationBrowserToolbar.class/instance/initialization/setLoadModel.st A Zinc-Resource-Meta-Core.package/ZnUrl.class/instance/converting/asUrl.st Log Message: ----------- 30572 11999 Move MimeType to Deprecated30 https://pharo.fogbugz.com/f/cases/11999 12131 Metacello Browser: more revealing button labels https://pharo.fogbugz.com/f/cases/12131 12159 ZnUrl should respond to asUrl https://pharo.fogbugz.com/f/cases/12159 http://files.pharo.org/image/30/30572.zip

1 0

Re: [Pharo-dev] help needed with fixing the SpecDebugger
by Stephan Eggermont Nov. 14, 2013

Nov. 14, 2013

Doru wrote: >I need a bit of help with the issue of the SpecDebugger relying on the default inspector being implemented in Spec. Hmm, one gets used to having a decent inspector. Going back to the Pharo 3 default is not funnyâ¦ The GTInspector might be a bit of an ugly duckling, but there really is a big bad-ass powerful swan in there. I strongly support the help request. And phd organization of course. Stephan

1 0

Spec new release :)
by Benjamin Nov. 14, 2013

Nov. 14, 2013

Hello everyone, I am glad to announce a step has been made in Spec with the introduction of five new models: TreeNodeModel, TreeColumnModel, MenuModel, MenuGroupModel and MenuItemModel. I. Trees The two first models (TreeNodeModel, TreeColumnModel) are used to build and specify trees (in addition with TreeModel). a) TreeNodeModel TreeNode represent a node of the tree, and hold some basic information like what the children of the node are, or which icon to use. Previously, one could use directly subclasses of MorphTreeNodeModel directly. This has been removed to loose the bonds between Spec and Morphic. If you used direct Morphic nodes in your tree, you will need to replace them by TreeNodeModel instances. You could also have used TreeModel methods used to generically describe your nodes. In this case, the only change you will need is how you access the content of a node. The MorphTreeNodeModel method used for this is #item while in TreeNodeModel it is #content. TreeNodeModel also support filtering out of the box with an extensible mechanism. b) TreeColumnModel TreeColumnModel is used to specify the columns used to render the tree nodes. Where one used to use TreeColumnMorph, now TreeColumnModel have to be use. The mainly behave the same, only the API differs to provide a less morphic oriented set of methods. TreeColumnModel also resolve some some updating issue encountered in TreeColumnMorph. II. Menus The three remaining models are used to build menus for the spec models. The way to build menus has been rethink to provide a more natural way to think menus. a) MenuModel A MenuModel is a quite a simple object with only an optional name, an optional icon and a list of menu groups. A MenuModel can also be turned into an auto-refreshing menu. The main method of MenuModel is #addGroup: which takes a block as argument and build a group before adding it to the menu model groups list. Example: aMenu addGroup: [ :aGroup | aGroup addItem: [ :anItem | anItem name: 'Browse Full'; action: [ self browseSelectedObject ]; shortcut: $b command mac | $b alt win | $b alt unix ]. aGroup addItem: [ :anItem | anItem name: 'Browse Class'; action: [ self browseSelectedObjectClass ] ] ]. b) MenuGroupModel A MenuGroupModel represent a set of menu items which belong to a same logical set by providing related actions. A menu group only hold a list of menu items. The main method of MenuGroupModel is #addItem: , as you have seen in the previous example. Example: aGroup addItem: [ :anItem | anItem name: 'Browse Hierarchy'; action: [ self browseSelectedObjectClassHierarchy ]; shortcut: $h command mac | $h alt win | $h alt unix ] c) MenuItemModel A menu item is the core of a menu. It is the object that can actually perform an action. A MenuItemModel holds multiple information related to this action like the name of the menu entry, the optional icon you want to use, if the action is doable in the current context, and the optional shortcut triggering the action. An interesting feature is that by applying a menu to a spec model, the shortcuts of its items will be used to automatically bind the corresponding key combination to the menu item action (taking in account the context to prevent to fire action when it does not make sense). So far, this feature has been introduced only in NewListModel to fix the possible issues before a global deployment. Thanks for reading this long email, thanks for your support and your feedback, and see you soon :) Ben

14 64

[pharo-project/pharo-core] 340f1e: 30571
by GitHub Nov. 14, 2013

Nov. 14, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 340f1ecf713d5e0ad9c662b77975cb72c6554fae https://github.com/pharo-project/pharo-core/commit/340f1ecf713d5e0ad9c662b7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-13 (Wed, 13 Nov 2013) Changed paths: M ConfigurationCommandLineHandler-Core.package/ConfigurationCommandLineHandler.class/instance/accessing/loadRepositoryUrl.st M ConfigurationCommandLineHandler-Core.package/ConfigurationCommandLineHandler.class/instance/testing/hasRepositoryUrl.st A Files.package/SourceFileArray.class/instance/file system/close.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script227.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30571.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Spec-Core.package/AbstractAdapter.class/instance/protocol/bindKeyCombination_toAction_.st M Spec-Core.package/ComposableModel.class/instance/protocol-shortcuts/bindKeyCombination_toAction_.st A Spec-Core.package/ComposableModel.class/instance/protocol-shortcuts/bindMenuKeyCombination_toAction_.st A Spec-Core.package/ComposableModel.class/instance/protocol-shortcuts/removeKeyCombination_.st A Spec-Core.package/ComposableModel.class/instance/protocol-shortcuts/removeMenuKeyCombination_.st M Spec-Core.package/ComposableModel.class/instance/protocol/applyMenuModel_.st A Spec-Core.package/ComposableModel.class/instance/protocol/neglectMenuModel_.st A Spec-Core.package/MenuModel.class/instance/protocol/neglect_.st A Spec-Core.package/NewListModel.class/class/examples/exampleWithMenu2.st M Spec-Core.package/NewListModel.class/instance/initialize/registerEvents.st A Spec-MorphicAdapters.package/AbstractMorphicAdapter.class/instance/protocol-shortcuts/bindKeyCombination_toAction_.st A Spec-MorphicAdapters.package/AbstractMorphicAdapter.class/instance/protocol-shortcuts/bindMenuKeyCombination_toAction_.st A Spec-MorphicAdapters.package/AbstractMorphicAdapter.class/instance/protocol-shortcuts/removeKeyCombination_.st A Spec-MorphicAdapters.package/AbstractMorphicAdapter.class/instance/protocol-shortcuts/removeMenuKeyCombination_.st M System-Support.package/SmalltalkImage.class/instance/snapshot and quit/shutDown.st M System-Support.package/SmalltalkImage.class/instance/sources%2C change log/closeSourceFiles.st Log Message: ----------- 30571 12156 Move code in SmalltalkImage>>closeSourceFiles to SourceFileArray https://pharo.fogbugz.com/f/cases/12156 10890 Converting FileUrl w. spaces to FileReference (was Load configs from local folders) https://pharo.fogbugz.com/f/cases/10890 12150 Better Menu support https://pharo.fogbugz.com/f/cases/12150 http://files.pharo.org/image/30/30571.zip

1 0

[pharo-project/pharo-core]
by GitHub Nov. 14, 2013

Nov. 14, 2013

Branch: refs/tags/30571 Home: https://github.com/pharo-project/pharo-core

1 0

help needed with fixing the SpecDebugger
by Tudor Girba Nov. 14, 2013

Nov. 14, 2013

Hi, I need a bit of help with the issue of the SpecDebugger relying on the default inspector being implemented in Spec. I investigated a bit, but now I am stuck. Details here: https://pharo.fogbugz.com/f/cases/12055/ Can anyone look at it? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

4 6

Instrumenting field accesses with Opal?
by Alexandre Bergel Nov. 13, 2013

Nov. 13, 2013

Hi! Is there a way to get notified when fields are accessed? That would be awesome Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

6 8

Fwd: In-memory FileSystem write streams not being polymorphic
by Nicolas Cellier Nov. 13, 2013

Nov. 13, 2013

---------- Forwarded message ---------- From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> Date: 2013/11/13 Subject: Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic The long answer is simple: the more responsibility you put in Stream, the more complexity you get. The first complexity that I'm speaking of is non-uniformity and random implementation (or un-implementation) of a set of features. I mean some streams in the huge hierarchy implement only half of the contract, but hey, what was the contract exactly? Ah, yes, there were no contract, just hacks left here and there randomly and concurrently in a big hierarchy. I add a new subclass, but don't implement all the features, there are too many of them, and I don't know them all.. I add a new feature, but don't implement it in all the classes, there are too many of them, and I don't know them all. This procedure invariably ends up with a blob of un-maintanable code, were two stream would not even agree on upToEnd behavior - I think you remember it :) If the goal is to replicate all the accumulated responsibilities of Squeak Streams, but with a clarified contract, I think this is a dead end: too much cruft to support, too many features, too many undefined or not well defined behaviors to be clarified. Xtreams takes the opposite path: concentrate on constructing a common, simple and uniform API, concerning streams, just basic stream methods. Some specialized streams then implement some specialized behavior, and you can compose them (by wrapping) when you need the specific API. This way, you ain't got to implement/maintain feature A into a few dozen of classes. And your brand new SpecialFeatureBStream only has to implement a few well known behaviours and your Special Feature B. The short answer is even more simple : a stream does not have a name, like a collection does not have a name, because we ain't gonna need it. If we really need a name, then we'll create a XTNamedReadStream and a XTNamedWriteStream responding to #name, but I doubt we'll do. 2013/11/13 Chris Muller <ma.chris.m(a)gmail.com> > On Wed, Nov 13, 2013 at 9:58 AM, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> Yes, a Wrapper would provide the legacy API. >> >> And yes, the name of a stream should better not be part of the API. >> Most stream don't have a name, and adding such API adds all sort of >> un-needed complexity. >> It's an internal detail that can eventually help for reporting error if >> accessible, but nothing more. >> >> > I know nothing about Xtreams but, IMO, this obsession with sterility > borders on mental illness. > > "All sort of un-needed complexity?" That's overstating it a bit, don't > you think? > > So you must really feel stressed that ALL Object's, in fact, have a #name, > huh? I admit this seems to push the limits but... > > what's the point of having any kind of different streams at all then? > It's the _differences_ between them that makes composing them useful. > Compression, encryption, filtering, sockets, files, circular, etc. You > think you'll be able to do all that and get away with all of them having > exactly the same API? > > IMHO working around that, passing extra objects around, sounds more > stressful than letting a stream on a _file_ know its filename.. > > If it really need it, the application certainly can retrieve the name from >> a higher level object (a FIleReference, FileDirectory or whatever). >> > > How does that solution allow uniformity in stream-using code? > > > > > > >> >> >> 2013/11/13 Chris Muller <asqueaker(a)gmail.com> >> >>> On Tue, Nov 12, 2013 at 7:31 AM, Nicolas Cellier >>> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> > It's just a matter of selecting a strategy. I've proposed two: >>> > A) create a wrapper class for legacy Stream compatibility selectors >>> > B) create extensions for Legacy Stream compatibility selectors >>> > My preference goes to A) >>> >>> By wrappers you mean the Xtreams are the innards doing the work and >>> the wrappers providing the legacy API? >>> >>> This would be a great way to test Xtreams. >>> >>> > The legacy support MUST be minimal (next nextPut: nextPutAll: peek >>> upTo: >>> > ...), otherwise we will import all the cruft in Xtream and would go >>> back to >>> > our starting point... >>> > Once the minimal support written (a few hours should be enough), we >>> should >>> > gradually switch each every legacy Stream usage -> Xtream. >>> > >>> > An area which require more work is those Streams that have mixed >>> conventions >>> > (one portion is interpreted as text, another as binary). >>> > In theory that's easy, we just have two streams and they both wrap on >>> a low >>> > level binary stream, but that means we have to be very cautious with >>> buffers >>> > and caches. >>> > >>> > Another area of work is usage of ugly selectors like name (we try to >>> access >>> > the file name from the Stream API, arghh). Those usages are bad and >>> require >>> > a rewrite. >>> >>> Are you saying a FileStream knowing its #name or #filename is bad? >>> >>> >> >

2 2

PharoV20.source
by Alexandre Bergel Nov. 13, 2013

Nov. 13, 2013

Hi! Why not to include this file in the VM? It often happens to me that this place is wrongly placed. When this happens, Pharo just shows a white screen, without letting what is the error. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

7 10