Squeak-dev October 2016

squeak-dev@lists.squeakfoundation.org

40 participants
114 discussions

The Trunk: UpdateStream-pre.8.mcz
by commits＠source.squeak.org 07 Oct '16

07 Oct '16

Patrick Rein uploaded a new version of UpdateStream to project The Trunk: http://source.squeak.org/trunk/UpdateStream-pre.8.mcz ==================== Summary ==================== Name: UpdateStream-pre.8 Author: pre Time: 7 October 2016, 9:08:28.891404 am UUID: 068ac226-4fee-8d4c-82a8-602d55d4f067 Ancestors: UpdateStream-mt.7 Remove post method which was used in the MonticelloConfigurations tool =============== Diff against UpdateStream-mt.7 =============== Item was removed: - ----- Method: MCConfigurationBrowser>>post (in category '*UpdateStream') ----- - post - "Take the current configuration and post an update" - | name update managers names choice | - (self checkRepositories and: [self checkDependencies]) ifFalse: [^self]. - name := UIManager default - request: 'Update name (.cs) will be appended):' - initialAnswer: self configuration suggestedNameOfNextVersion. - name isEmpty ifTrue:[^self]. - self configuration name: name. - update := MCPseudoFileStream on: (String new: 100). - update localName: name, '.cs'. - update nextPutAll: '"Change Set: ', name. - update cr; nextPutAll: 'Date: ', Date today printString. - update cr; nextPutAll: 'Author: Posted by Monticello'. - update cr; cr; nextPutAll: 'This is a configuration map created by Monticello."'. - - update cr; cr; nextPutAll: '(MCConfiguration fromArray: #'. - self configuration fileOutOn: update. - update nextPutAll: ') upgrade.'. - update position: 0. - - managers := Smalltalk at: #UpdateManager ifPresent:[:mgr| mgr allRegisteredManagers]. - managers ifNil:[managers := #()]. - managers size > 0 ifTrue:[ - | servers index | - servers := ServerDirectory groupNames asSortedArray. - names := (managers collect:[:each| each packageVersion]), servers. - index := UIManager default chooseFrom: names lines: {managers size}. - index = 0 ifTrue:[^self]. - index <= managers size ifTrue:[ - | mgr | - mgr := managers at: index. - ^mgr publishUpdate: update. - ]. - choice := names at: index. - ] ifFalse:[ - names := ServerDirectory groupNames asSortedArray. - choice := UIManager default chooseFrom: names values: names. - choice == nil ifTrue: [^ self]. - ]. - (ServerDirectory serverInGroupNamed: choice) putUpdate: update.!

1 0

Re: [squeak-dev] The Trunk: Help-Squeak-CorePackages-pre.1.mcz
by David T. Lewis 07 Oct '16

07 Oct '16

On Thu, Oct 06, 2016 at 04:19:46PM +0000, commits(a)source.squeak.org wrote: > Patrick Rein uploaded a new version of Help-Squeak-CorePackages to project The Trunk: > http://source.squeak.org/trunk/Help-Squeak-CorePackages-pre.1.mcz > > ==================== Summary ==================== > > Name: Help-Squeak-CorePackages-pre.1 > Author: pre > Time: 6 October 2016, 6:15:21.412487 pm > UUID: fd531696-fd5a-344d-b269-0a45c3609f20 > Ancestors: > > Introduces a new help topic which adds short descriptions for every core package as an overview and first point of information for someone not familiar with the image. > Very nice! I like this. Dave

1 0

Daily Commit Log
by commits＠source.squeak.org 06 Oct '16

06 Oct '16

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2016-October/068992.ht… Name: Help-Squeak-CorePackages-pre.1 Ancestors: Introduces a new help topic which adds short descriptions for every core package as an overview and first point of information for someone not familiar with the image. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2016-October/068993.ht… Name: MonticelloConfigurations-pre.146 Ancestors: MonticelloConfigurations-mt.145 Removes the Post button which is based on an API which does not exist anymore and re-names the Store button to Save to be consistent with Monticello vocabulary. =============================================

1 0

The Trunk: MonticelloConfigurations-pre.146.mcz
by commits＠source.squeak.org 06 Oct '16

06 Oct '16

Patrick Rein uploaded a new version of MonticelloConfigurations to project The Trunk: http://source.squeak.org/trunk/MonticelloConfigurations-pre.146.mcz ==================== Summary ==================== Name: MonticelloConfigurations-pre.146 Author: pre Time: 6 October 2016, 6:34:12.000487 pm UUID: fb8e5e56-8586-1943-b186-e48db629e1da Ancestors: MonticelloConfigurations-mt.145 Removes the Post button which is based on an API which does not exist anymore and re-names the Store button to Save to be consistent with Monticello vocabulary. =============== Diff against MonticelloConfigurations-mt.145 =============== Item was changed: ----- Method: MCConfigurationBrowser>>buttonSpecs (in category 'morphic ui') ----- buttonSpecs ^ #(('Add' addDependency 'Add a dependency') ('Update' updateMenu 'Update dependencies') ('Install' installMenu 'Load/Merge/Upgrade into image') ('Up' up 'Move item up in list' canMoveUp) ('Down' down 'Move item down in list' canMoveDown) ('Remove' remove 'Remove item' canRemove) + ('Save' store 'Store the configuration to a repository') - ('Store' store 'store configuration') - ('Post' post 'Post this configuration to an update stream') )!

1 0

The Trunk: Help-Squeak-CorePackages-pre.1.mcz
by commits＠source.squeak.org 06 Oct '16

06 Oct '16

Patrick Rein uploaded a new version of Help-Squeak-CorePackages to project The Trunk: http://source.squeak.org/trunk/Help-Squeak-CorePackages-pre.1.mcz ==================== Summary ==================== Name: Help-Squeak-CorePackages-pre.1 Author: pre Time: 6 October 2016, 6:15:21.412487 pm UUID: fd531696-fd5a-344d-b269-0a45c3609f20 Ancestors: Introduces a new help topic which adds short descriptions for every core package as an overview and first point of information for someone not familiar with the image. ==================== Snapshot ==================== SystemOrganization addCategory: #'Help-Squeak-CorePackages'! CustomHelp subclass: #SqueakCorePackagesHelp instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Help-Squeak-CorePackages'! ----- Method: SqueakCorePackagesHelp class>>bookName (in category 'as yet unclassified') ----- bookName ^ 'Core Packages'! ----- Method: SqueakCorePackagesHelp class>>chronology (in category 'pages') ----- chronology "This method was automatically generated. Edit it using:" "SqueakCorePackagesHelp edit: #chronology" ^(HelpTopic title: 'Chronology' contents: 'Everything related to time, time spans, durations, time stamps, etc. For the subtleties of the single classes read the class comments of: Duration, Timespan, and DateAndTime. !! ]style[(138 8 2 8 6 11 2),LDuration Comment;,,LTimespan Comment;,,LDateAndTime Comment;,!!' readStream nextChunkText) key: #chronology! ----- Method: SqueakCorePackagesHelp class>>collections (in category 'pages') ----- collections "This method was automatically generated. Edit it using:" "SqueakCorePackagesHelp edit: #collections" ^(HelpTopic title: 'Collections' contents: 'Everything related to working with multiple objects such as Array, String (Collection of characters), Stream, Set, and Dictionary.!! ]style[(60 5 2 6 29 6 2 3 6 10 1),dArray browse;;,,dString browse;;,,dStream browse;;,,dSet browse;;,,dDictionary browse;;,!!' readStream nextChunkText) key: #collections! ----- Method: SqueakCorePackagesHelp class>>compiler (in category 'pages') ----- compiler "This method was automatically generated. Edit it using:" "SqueakCorePackagesHelp edit: #compiler" ^(HelpTopic title: 'Compiler' contents: 'This package contains the Squeak Smalltalk compiler. It includes a Scanner, Parser, and Compiler. In order to restore source code from byte code., it also includes a Decompiler. !! ]style[(67 7 2 6 6 8 70 10 2),dScanner browse;;,,dParser browse;;,,dCompiler browse;;,,dDecompiler browse;;,!!' readStream nextChunkText) key: #compiler! ----- Method: SqueakCorePackagesHelp class>>files (in category 'pages') ----- files "This method was automatically generated. Edit it using:" "SqueakCorePackagesHelp edit: #files" ^(HelpTopic title: 'Files' contents: 'The Files package provides access to the local file system through streams. It contains the FileDirectory class for listing and navigating folders. Besides the usual synchronous API it also provides a AsyncFile class for asynchronous reading from files.!! ]style[(92 14 96 9 43),dFileDirectory browse;;,,LAsyncFile Comment;,!!' readStream nextChunkText) key: #files! ----- Method: SqueakCorePackagesHelp class>>graphics (in category 'as yet unclassified') ----- graphics "This method was automatically generated. Edit it using:" "SqueakCorePackagesHelp edit: #graphics" ^(HelpTopic title: 'Graphics' contents: 'This package includes core classes for Smalltalk graphic objects as well as facilities and applications for operating on graphic objects. Key classes include Form and BitBlt. It further includes classes for rendering fonts and reading png, gif, or jpeg files.!! ]style[(158 4 5 6 87),dForm browse;;,,dBitBlt browse;;,!!' readStream nextChunkText) key: #graphics! ----- Method: SqueakCorePackagesHelp class>>kernel (in category 'pages') ----- kernel "This method was automatically generated. Edit it using:" "SqueakCorePackagesHelp edit: #kernel" ^HelpTopic title: 'Kernel' contents: 'This package provides the most basic Smalltalk objects. It contains classes for: Code compilation, class (hierarchy) (re-)definition, basic exception handling, process scheduling and synchronization, user input events, and primitive types such as numbers and Boolean values.!!' readStream nextChunkText! ----- Method: SqueakCorePackagesHelp class>>network (in category 'pages') ----- network "This method was automatically generated. Edit it using:" "SqueakCorePackagesHelp edit: #network" ^(HelpTopic title: 'Network' contents: 'The network package provides means to fetch network resources. Includes support for UDP, TCP, HTTP, FTP, Telnet, SMTP, and POP3. Some of them are implemented as Sockets, others are implemented as Protocol clients. Additionally, it includes classes for handling URIs, Urls, email addresses, and UUIDs. If SqueakSSL is installed properly it can also provide HTTPS support.!! ]style[(161 6 94 3 30 5 73),LSocket Hierarchy;,,LURI Comment;,,dUUID browse;;,!!' readStream nextChunkText) key: #network! ----- Method: SqueakCorePackagesHelp class>>pages (in category 'as yet unclassified') ----- pages ^ self class selectors copyWithoutAll: #(bookName pages)! ----- Method: SqueakCorePackagesHelp class>>sound (in category 'pages') ----- sound "This method was automatically generated. Edit it using:" "SqueakCorePackagesHelp edit: #sound" ^(HelpTopic title: 'Sound' contents: 'The sound package manages audible output and reading various sound file formats. It includes support for FM, WAVE, and MIDI. It also includes classes for synthesizing sound. Try for example: (AbstractSound majorScaleOn: PluckedSound default) play!! ]style[(191 55),d(AbstractSound majorScaleOn: PluckedSound default) play;;!!' readStream nextChunkText) key: #sound! ----- Method: SqueakCorePackagesHelp class>>system (in category 'pages') ----- system "This method was automatically generated. Edit it using:" "SqueakCorePackagesHelp edit: #system" ^(HelpTopic title: 'System' contents: 'The System package includes classes dealing with code change notifications, object events, weak arrays and finalization, object serialization, and the concept of projects. It also provides general system infrastructure such as the AppRegistry or classes for localization. Additionally, it includes the SmalltalkImage class which can be accessed through Smalltalk.!! ]style[(232 11 61 14 37 9 1),LAppRegistry Comment;,,LSmalltalkImage Comment;,,dSmalltalk inspect;;,!!' readStream nextChunkText) key: #system! SqueakCorePackagesHelp subclass: #SqueakFurtherCorePackagesHelp instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Help-Squeak-CorePackages'! ----- Method: SqueakFurtherCorePackagesHelp class>>balloonPackage (in category 'as yet unclassified') ----- balloonPackage "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #balloonPackage" ^(HelpTopic title: 'Balloon' contents: 'The Balloon package provides an engine for complex 2-D graphic objects and fast 2-D graphics rendering including anti-aliasing. It was originally written to render Flash. The main interface is BalloonCanvas which is used to render Morphs using the BalloonEngine. It also provides the FillStyle classes which enable gradient or form fill styles for Morphs. It has nothing to do with the Balloon help concept which shows help texts on mouse over.!! ]style[(193 13 239),dBalloonCanvas browse;;,!!' readStream nextChunkText) key: #balloonPackage! ----- Method: SqueakFurtherCorePackagesHelp class>>bookName (in category 'as yet unclassified') ----- bookName ^ 'Further'! ----- Method: SqueakFurtherCorePackagesHelp class>>commandLine (in category 'as yet unclassified') ----- commandLine "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #commandLine" ^(HelpTopic title: 'CommandLine' contents: 'The CommandLine package provides classes for running Squeak in headless mode while dealing with events requiring user input. Essentially, it introduces a special ToolSet (CommandLineToolSet) which handles tool requests.!! ]style[(162 7 2 18 30),dToolSet browse;;,,dCommandLineToolSet browse;;,!!' readStream nextChunkText) key: #commandLine! ----- Method: SqueakFurtherCorePackagesHelp class>>etoys (in category 'pages') ----- etoys "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #etoys" ^HelpTopic title: 'Etoys' contents: 'The Etoys package includes all of the Etoys system with extended Morphs, a tile-based scripting language user interface and interpreter, and several applications based upon that. This package also includes the Kedama project which provides means to create simulations with large numbers of objects based on a columnar storage.!!' readStream nextChunkText! ----- Method: SqueakFurtherCorePackagesHelp class>>monticello (in category 'pages') ----- monticello "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #monticello" ^(HelpTopic title: 'Monticello' contents: 'The Monticello package implements the infastructure and tools for working with the Monticello version control system. The package is split up into several categories: Monticello version control abstractions, serialization logic, repository management, tools, and monticello configuration management. Monticello configurations denote a combination of version from different packages which form a consistent state together.!!' readStream nextChunkText) key: #monticello! ----- Method: SqueakFurtherCorePackagesHelp class>>morphicExtras (in category 'pages') ----- morphicExtras "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #morphicExtras" ^(HelpTopic title: 'MorphicExtras' contents: 'MorphicExtras contains a collection of additional Morphs which are either graphical tools or provide an extended API, such as the BookMorph class. Many of these can be found in the Objects tool. Additionally, it includes extensions to the Morphic UI such as Flaps. !! ]style[(130 9 42 12 72),dBookMorph browse;;,,dObjectsTool newStandAlone openInWorld;;,!!' readStream nextChunkText) key: #morphicExtras! ----- Method: SqueakFurtherCorePackagesHelp class>>multilingual (in category 'as yet unclassified') ----- multilingual "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #multilingual" ^(HelpTopic title: 'Multilingual' contents: 'The Multilingual package adds support for multiple languages to Squeak. This includes the capabilities to import text in different encodings (think copy-and-paste), and render all kinds of fonts. An interesting multilingual method of the String class is #encodedCharSetAt:. !!' readStream nextChunkText) key: #multilingual! ----- Method: SqueakFurtherCorePackagesHelp class>>nebraska (in category 'as yet unclassified') ----- nebraska "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #nebraska" ^(HelpTopic title: 'Nebraska' contents: 'Nebraska is a toolkit for building remote interactions with Morphic in Squeak. It is modelled somewhat after Kansas, although as yet it''s a much simpler system. There is a shared world on some server on a network, and other people can connect to that world from afar. Whenever the shared world tries to draw to its screen, it sends drawing commands across the network. Whenever a user tries to perform a mouse or keyboard interaction, those interactions are forwarded to the server where a RemoteControlledHand acts on their behalf. See also http://wiki.squeak.org/squeak/1356!! ]style[(543 34),Rhttp://wiki.squeak.org/squeak/1356;!!' readStream nextChunkText) key: #nebraska! ----- Method: SqueakFurtherCorePackagesHelp class>>packageInfoPage (in category 'pages') ----- packageInfoPage "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #packageInfoPage" ^(HelpTopic title: 'PackageInfo' contents: 'The PackageInfo package provides classes providing a view on the classes in the system with respect to packages. These objects are only cached and represent no stored information. For more information look into the PackageInfo class.!! ]style[(215 11 7),LPackageInfo Comment;,!!' readStream nextChunkText) key: #packageInfoPage! ----- Method: SqueakFurtherCorePackagesHelp class>>pages (in category 'as yet unclassified') ----- pages ^ self class selectors copyWithoutAll: #(bookName pages)! ----- Method: SqueakFurtherCorePackagesHelp class>>preferenceBrowser (in category 'pages') ----- preferenceBrowser "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #preferenceBrowser" ^HelpTopic title: 'PreferenceBrowser' contents: 'The PreferenceBrowser package contains the implementation of the preference browser tool which is currently only available in Morphic and thus does not reside with the ToolBuilder-based tools.!!' readStream nextChunkText! ----- Method: SqueakFurtherCorePackagesHelp class>>protocols (in category 'as yet unclassified') ----- protocols "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #protocols" ^(HelpTopic title: 'Protocols' contents: 'This package deals with vocabularies as they are used in Etoys. A vocabulary is the set of words understood by an object when viewed from Etoys. You can see examples of vocabularies in methods named ''additionsTo[some vocabulary category name]''. Most of the methods behind a vocabulary term are implemented in Player which then often forward them to an implementation in its costume (often a Morph). See also: http://wiki.squeak.org/squeak/3944!! ]style[(411 34),Rhttp://wiki.squeak.org/squeak/3944;!!' readStream nextChunkText) key: #protocols! ----- Method: SqueakFurtherCorePackagesHelp class>>releaseBuilder (in category 'pages') ----- releaseBuilder "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #releaseBuilder" ^HelpTopic title: 'ReleaseBuilder' contents: 'This package contains the script for preparing a new release from a trunk image.!!' readStream nextChunkText! ----- Method: SqueakFurtherCorePackagesHelp class>>servicesPage (in category 'pages') ----- servicesPage "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #servicesPage" ^(HelpTopic title: 'Services' contents: 'Services are a concept for extending menus. You can register a service for a menu/application. A good starting point is the ServiceProvider.!! ]style[(124 15 1),LServiceProvider Comment;,!!' readStream nextChunkText) key: #servicesPage! ----- Method: SqueakFurtherCorePackagesHelp class>>shout (in category 'as yet unclassified') ----- shout "This method was automatically generated. Edit it using:" "ShoutHelp edit: #introduction" ^HelpTopic title: 'Shout' contents: 'The Shout package provides parsing and syntax highlighting for Smalltalk code. It can be used to create alternative highlighting mechanisms. !! ]style[(141)f1!!' readStream nextChunkText! ----- Method: SqueakFurtherCorePackagesHelp class>>squeakSSL (in category 'pages') ----- squeakSSL "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #squeakSSL" ^HelpTopic title: 'SqueakSSL' contents: 'The SqueakSSL provides the SecureSocket class which enables SSL encrpyted connections. For this to work the SqueakSSL plugin has to be installed. !!' readStream nextChunkText! ----- Method: SqueakFurtherCorePackagesHelp class>>st80 (in category 'as yet unclassified') ----- st80 "This method was automatically generated. Edit it using:" "ST80Help edit: #introduction" ^HelpTopic title: 'ST80' contents: 'The ST80 package bundles the MVC tool implementations in Squeak. They can be used through opening a MVC project. This is useful for example for debugging Morphic projects.!! ]style[(171)f1!!' readStream nextChunkText! ----- Method: SqueakFurtherCorePackagesHelp class>>systemReporter (in category 'pages') ----- systemReporter "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #systemReporter" ^HelpTopic title: 'SystemReporter' contents: 'SystemReporter provides the tool with the same name which provides information on the system such as VM or image versions, hardware information, or access to the debug log.!! ]style[(28 4 140),dSystemReporter open;;,!!' readStream nextChunkText! ----- Method: SqueakFurtherCorePackagesHelp class>>tests (in category 'pages') ----- tests "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #tests" ^(HelpTopic title: 'Tests' contents: 'This package includes tests for many parts of the core system where core packages do not provide tests themselves.!!' readStream nextChunkText) key: #tests! ----- Method: SqueakFurtherCorePackagesHelp class>>trueType (in category 'pages') ----- trueType "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #trueType" ^(HelpTopic title: 'TrueType' contents: 'The TrueType package includes classes for handling TrueType fonts. It provides domain abstractions as well as classes for importing TrueType fonts from files. A starting point is the TTCFont class.!! ]style[(183 7 7),LTTCFont Comment;,!!' readStream nextChunkText) key: #trueType! ----- Method: SqueakFurtherCorePackagesHelp class>>updateStream (in category 'pages') ----- updateStream "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #updateStream" ^(HelpTopic title: 'UpdateStream' contents: 'This package provides scripts for updating all core packages within the image from a server. All these scripts are on the class side of UpdateStreamDownloader. !! ]style[(136 22 2),dUpdateStreamDownloader browse;;,!!' readStream nextChunkText) key: #updateStream! ----- Method: SqueakFurtherCorePackagesHelp class>>versionNumber (in category 'pages') ----- versionNumber "This method was automatically generated. Edit it using:" "SqueakFurtherCorePackagesHelp edit: #versionNumber" ^HelpTopic title: 'VersionNumber' contents: 'This package includes domain specific code for handling version numbers either as a single VersionNumber or as a VersionHistory. It is used in the SqueakMap package.!! ]style[(91 13 9 14 39),LVersionNumber Comment;,,LVersionHistory Comment;,!!' readStream nextChunkText! SqueakCorePackagesHelp subclass: #SqueakUsefulCorePackagesHelp instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Help-Squeak-CorePackages'! ----- Method: SqueakUsefulCorePackagesHelp class>>bookName (in category 'as yet unclassified') ----- bookName ^ 'Commonly Used'! ----- Method: SqueakUsefulCorePackagesHelp class>>compression (in category 'pages') ----- compression "This method was automatically generated. Edit it using:" "SqueakUsefulCorePackagesHelp edit: #compression" ^(HelpTopic title: 'Compression' contents: 'The Compression package provides classes for dealing with compressed files or compressed data in general. Compression-Archives contains most of the file-handling classes (for example Archive). Compression-Streams provides streams which can compress data written to them. !! ]style[(183 7 81),dArchive browse;;,!!' readStream nextChunkText) key: #compression! ----- Method: SqueakUsefulCorePackagesHelp class>>installer (in category 'pages') ----- installer "This method was automatically generated. Edit it using:" "SqueakUsefulCorePackagesHelp edit: #installer" ^(HelpTopic title: 'Installer' contents: 'This package provides the Installer tool which can be used to install packages from various sources including Monticello or SqueakMap. !!' readStream nextChunkText) key: #installer! ----- Method: SqueakUsefulCorePackagesHelp class>>morphic (in category 'pages') ----- morphic "This method was automatically generated. Edit it using:" "SqueakUsefulCorePackagesHelp edit: #morphic" ^HelpTopic title: 'Morphic' contents: 'Morphic contains the Morphic UI framework including event handling, basic drawing of Morphs, and the implementation of the Morphic UI. The main API is in the Morph class and the event loop of the framework can be found in WorldState. The package also includes several example Morphs such as the ClickExerciser. The main entrance point for working with Morphs is by composing or subclassing Morph subclasses.!! ]style[(222 10 65 14 82 5 12),dWorldState browse;;,,dClickExerciser new openInWorld;;,,dMorph browse;;,!!' readStream nextChunkText! ----- Method: SqueakUsefulCorePackagesHelp class>>pages (in category 'as yet unclassified') ----- pages ^ self class selectors copyWithoutAll: #(bookName pages)! ----- Method: SqueakUsefulCorePackagesHelp class>>regex (in category 'as yet unclassified') ----- regex "This method was automatically generated. Edit it using:" "SqueakUsefulCorePackagesHelp edit: #regex" ^(HelpTopic title: 'Regex' contents: 'Regex provides a regex matching engine. It is mainly used through the interface exposed on String objects. See the *Regex-Core category on String. For the syntax of Squeak regular expressions see: RxParser class>>#a:introduction: and the subsequent methods on RxParser class. For more involved usages of regular expressions see the Regex-Core class category.!! ]style[(139 6 53 32 129),dString browse;;,,LRxParser class>>#a:introduction:;,!!' readStream nextChunkText) key: #regex! ----- Method: SqueakUsefulCorePackagesHelp class>>squeakMap (in category 'as yet unclassified') ----- squeakMap "This method was automatically generated. Edit it using:" "SqueakUsefulCorePackagesHelp edit: #squeakMap" ^(HelpTopic title: 'SM' contents: 'This package contains the model and the UI of SqueakMap, which is a repository for packages and applications in Squeak. You can access the SqueakMap catalog from the Apps menu item. Information on how to use SqueakMap can be found here: http://wiki.squeak.org/squeak/2726 The server resides at: http://http://map.squeak.org/ You can get an account to publish packages at: http://map.squeak.org/newaccount!!' readStream nextChunkText) key: #squeakMap! ----- Method: SqueakUsefulCorePackagesHelp class>>sunit (in category 'as yet unclassified') ----- sunit "This method was automatically generated. Edit it using:" "SqueakUsefulCorePackagesHelp edit: #sunit" ^(HelpTopic title: 'SUnit and SUnitGUI' contents: 'The SUnit package provides testing abstractions for unit tests. These comply to the XUnit testing model. The common use case is to subclass TestCase. However, SUnit-Extensions also contains TestCases for special use cases. The rest of the API is explained in SUnit-Tests. SUnitGUI contains the definition of the SUnit TestRunner which you can find in the world menu or the docking bar under Tools.!! ]style[(141 8 250),Rcode://TestCase;,!!' readStream nextChunkText) key: #sunit! ----- Method: SqueakUsefulCorePackagesHelp class>>toolBuilder (in category 'as yet unclassified') ----- toolBuilder "This method was automatically generated. Edit it using:" "SqueakUsefulCorePackagesHelp edit: #toolBuilder" ^(HelpTopic title: 'ToolBuilder' contents: 'ToolBuilder provides means to describe graphical user interfaces independently from the actual graphics framework used (e.g. MVC or Morphic). Examples of tools built with it are the Debugger, the system browser, or the monticello repository browser. To read about how to build tools start reading the ToolBuilder class comment.!! ]style[(182 8 112 11 15)f1,dDebugger browse;;,f1,LToolBuilder Comment;,f1!!' readStream nextChunkText) key: #toolBuilder! ----- Method: SqueakUsefulCorePackagesHelp class>>traitsPage (in category 'as yet unclassified') ----- traitsPage "This method was automatically generated. Edit it using:" "SqueakUsefulCorePackagesHelp edit: #traitsPage" ^(HelpTopic title: 'Traits' contents: 'Traits are an additional composition and reuse concept in Squeak allowing sideways composition of behavior. Traits are similar to MixIns. You can read about them here: http://scg.unibe.ch/archive/papers/Scha03aTraits.pdf!! ]style[(168 52)f1,Rhttp://scg.unibe.ch/archive/papers/Scha03aTraits.pdf;!!' readStream nextChunkText) key: #traitsPage! ----- Method: SqueakUsefulCorePackagesHelp class>>xml (in category 'as yet unclassified') ----- xml "This method was automatically generated. Edit it using:" "SqueakUsefulCorePackagesHelp edit: #xml" ^(HelpTopic title: 'XML' contents: 'This package provides classes for parsing XML files. You can implement your own Parser by subclassing the XMLParser class.!! ]style[(106 9 7)f1,dXMLParser browse;;,f1!!' readStream nextChunkText) key: #xml!

1 0

Squeak works on OpenBSD
by Gerardo Santana Gómez Garrido 06 Oct '16

06 Oct '16

I'm happy to let you know that Squeak/Spur can now run on OpenBSD 6.0/amd64. The relevant changes have been made available to https://github.com/OpenSmalltalk/opensmalltalk-vm I look forward to meet more Clog developers to share some ideas to improve the build toolchain and code portability. Regards. -- Gerardo Santana

4 7

Environment declarations vs bindings
by Nicolas Cellier 05 Oct '16

05 Oct '16

Since we are at reviewing Environment, here is a small detail that bothers me. I already asked some months ago, but silence was the only response, so ping. Implementation of Environment is sometimes not obvious: - Environment>>associationAt: uses declarations inst.var.. - Environment>>associationOrUndeclaredAt: uses bindings inst.var. How can it be so different, the selector does not speak, does it? OK, there is a flag: #review in one of them, but that does not make code clearer, it's just a smell of over-complexity or ill-naming. Whatever the reason (self explaining code?) Colin does not comment class/methods, that's a fact. Chris made the effort of commenting Environment but then came this declarations/bindings split, and the comment did rapidly rot. We have here an un-healthy statu quo crying for change. So if we want to at least comment the class with the meaning/role/responsibility of inst vars, here is my understanding: environment bind: #Foo to: 0. just add to the declarations. (You see how names are not obvious: bind does not bind the new binding to bindings). If the Environment importSelf, then the ClassBinding/Global also goes to bindings... (thru an observer pattern and the magic of naming policies) The bindings is what is used by the compiler, so what if an environment does not importSelf? It means that the variable it declares are not bound, so it is not reachable (kind of invisible class/Global). IOW, the bindings will contain all the imports, including self-imports. importSelf is generally what we want to do, unless weird cases of powerless environment for obfuscation or trustless sandboxing reason. Now, associationAt: does not speak for itself. It's too hard to decide if we're speaking of own declarations or bindings... Analyzing the usage is difficult. bindingAt: would be less ambiguous, so IMO we cannot fix without semantic shift. The semantic will be carried by the senders (the Tools), and the tools by usage we want to make of Environment. So we first have to define that: what feature do we want to support? With which tool? That probably require yet another thread...

5 6

trunk: Painter morph and object catalog broken
by Chris Muller 04 Oct '16

04 Oct '16

I updated a stock 5.1 image just to be sure -- attempting to use Squeak's Painter morph or open its object catalog results in various MNU's. I assume this is part of the Etoys import, how's it going? Thanks, Chris

3 2

Re: [squeak-dev] Environment declarations vs bindings
by Jakob Reschke 04 Oct '16

04 Oct '16

Many questions should be answered with tooling here, but in the particular case I mentioned, IMHO it is not about tooling. Until now, code that does `Smalltalk at: something` wants to look up something dynamically or it can't be sure that this class is actually loaded. As there was only one place to do such lookups, no differentiation about visibility or the source of a binding was necessary. Instances of `Smalltalk at: something` should either be replaced by an environment aware equivalent that makes clear if a name should be looked up *only* in the receiving environment (in its declarations), or if a name should be resolved, looking also in imported environments (in the bindings). As it is inconvenient to find all these pieces of code and change them all, `Smalltalk (globals)` could be the "active" environment (currently via dynamic scoping with `on: CurrentEnvironment do: ...`), not the original global environment. But then Environment>>at: must behave sensibly. I would expect that I can always do `Smalltalk at: #Object` to retrieve `Object` in any environment (under the assumption that every environment would import the "Kernel" or original environment). This is currently not the case, because Environment>>at: looks only into an environment's (own) declarations, not the imported bindings. 2016-09-29 17:30 GMT+02:00 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > > > 2016-09-29 15:15 GMT+02:00 Jakob Reschke <jakob.reschke(a)student.hpi.de>: >> >> Hi, >> >> Environment>>associationAt: is part of the Smalltalk globals >> Dictionary compatibility interface, right? As a quick and dirty fix, I >> changed instances of Smalltalk at: xyz in Monticello code to >> CurrentEnvironment signal at: xyz, but #at: also only reads in the >> declarations, so myEnvironment at: #MCWriter or myEnvironment at: >> #Object returns nil by default. It would make more sense to perform a >> full lookup via #valueOf:ifAbsent: in #at: and its cousins, wouldn't >> it? >> >> Best, >> Jakob >> > > I imagine that the question is about tools. > For now Smalltalk importSelf, so bindings and declarations do agree. > If an Environment does not importSelf, then some variables will be > invisibles (unbounds). Do we still want to see them in some tool, or not? > What's going on if we play with Alias? Do we want to see the Alias in some > browser? If not, then we'd better stick with declarations. > There is no easy solution. A single facade for two dictionaries cannot fit > all, so we need several different messages. > But it's much about what we want to do with those environments. > > >> >> 2016-09-29 7:33 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: >> > On 9/28/16, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> Since we are at reviewing Environment, here is a small detail that >> >> bothers >> >> me. I already asked some months ago, but silence was the only response, >> >> so >> >> ping. >> >> >> >> Implementation of Environment is sometimes not obvious: >> >> - Environment>>associationAt: uses declarations inst.var.. >> >> - Environment>>associationOrUndeclaredAt: uses bindings inst.var. >> >> How can it be so different, the selector does not speak, does it? >> >> >> >> OK, there is a flag: #review in one of them, but that does not make >> >> code >> >> clearer, it's just a smell of over-complexity or ill-naming. >> >> >> >> Whatever the reason (self explaining code?) Colin does not comment >> >> class/methods, that's a fact. >> > >> > Alternatively a description of the general ideas and the mechanism would >> > help. >> > >> > After all Environments is just a clever combination of a few >> > dictionaries to look up class names? Isn't it? ;-) >> > >> > However the fact that people did not move on much finalising the >> > implementation of environments since 2012 shows that it is hard to >> > reverse-engineer the intentions from the (incomplete) code. >> > >> > >> > >> > >> > >> >> Chris made the effort of commenting Environment but then came this >> >> declarations/bindings split, and the comment did rapidly rot. >> >> We have here an un-healthy statu quo crying for change. >> >> >> >> So if we want to at least comment the class with the >> >> meaning/role/responsibility of inst vars, here is my understanding: >> >> >> >> environment bind: #Foo to: 0. just add to the declarations. >> >> (You see how names are not obvious: bind does not bind the new binding >> >> to >> >> bindings). >> > >> > Environments >> > >> > bind: aSymbol to: anObject >> > | binding newBinding | >> > newBinding := aSymbol => anObject. >> > >> > binding := declarations associationAt: aSymbol ifAbsent: [nil]. >> > binding ifNotNil: >> > [binding class == newBinding class >> > ifTrue: [binding value: anObject] >> > ifFalse: [binding becomeForward: newBinding]. >> > ^anObject]. >> > >> > binding := undeclared associationAt: aSymbol ifAbsent: [nil]. >> > binding >> > ifNil: [binding := newBinding] >> > ifNotNil: >> > [undeclared removeKey: aSymbol. >> > binding class == newBinding class >> > ifTrue: [binding value: anObject] >> > ifFalse: [binding becomeForward: >> > newBinding]]. >> > >> > declarations add: binding. >> > self binding: binding addedTo: self. >> > ^anObject >> > >> > >> > Could you elaborate a bit please? >> > >> > >> > >> > >> >> If the Environment importSelf, then the ClassBinding/Global also goes >> >> to >> >> bindings... (thru an observer pattern and the magic of naming policies) >> >> >> >> The bindings is what is used by the compiler, so what if an environment >> >> does not importSelf? It means that the variable it declares are not >> >> bound, >> >> so it is not reachable (kind of invisible class/Global). >> >> >> >> IOW, the bindings will contain all the imports, including self-imports. >> >> importSelf is generally what we want to do, unless weird cases of >> >> powerless >> >> environment for obfuscation or trustless sandboxing reason. >> >> >> >> Now, associationAt: does not speak for itself. It's too hard to decide >> >> if >> >> we're speaking of own declarations or bindings... Analyzing the usage >> >> is >> >> difficult. bindingAt: would be less ambiguous, so IMO we cannot fix >> >> without >> >> semantic shift. >> > >> > This would need as well elaboration as well a separate thread. >> > >> > >> >> The semantic will be carried by the senders (the Tools), and the tools >> >> by >> >> usage we want to make of Environment. So we first have to define that: >> >> what >> >> feature do we want to support? With which tool? That probably require >> >> yet >> >> another thread... >> > >> > Yes >> > >> > --Hannes >> > >> >

12 21

Re: [squeak-dev] How to create a 'Hello world' example for environments
by Jakob Reschke 03 Oct '16

03 Oct '16

2016-10-03 16:44 GMT+02:00 Chris Cunnington <brasspen(a)gmail.com>: > Your change to Compiler>>evaluteCue:ifFail: looks great. I'm looking forward > to trying that out. Thank you, but I doubt that my change is really correct. You might want to compile an expression in Environment A and evaluate it in Environment B (like the Monticello loading methods: they are compiled in the default Environment, but it would be nice if they installed the methods from the loaded package into the current dynamic Environment). Since #evalueCue:ifFail: is called not only by #evaluate:environment:, that dynamic Environment binding should probably go "outside". You could also place that [ ... ] on: CurrentEnvironment do: ... around the `Compiler evaluate: 'WebServer exampleBrowse' environment: env.` do-it to gain the same effect. This is not required for the fileIn because it happens underway in EnvironmentLoader>>evaluate:logged:.

1 0