Squeak-dev May 2020

squeak-dev@lists.squeakfoundation.org

43 participants
265 discussions

FFI: FFI-Tools-mt.4.mcz
by commits＠source.squeak.org 05 Jun '20

05 Jun '20

Marcel Taeumel uploaded a new version of FFI-Tools to project FFI: http://source.squeak.org/FFI/FFI-Tools-mt.4.mcz ==================== Summary ==================== Name: FFI-Tools-mt.4 Author: mt Time: 20 May 2020, 1:26:29.934581 pm UUID: 225e7ffe-5219-124d-8815-53e78501c1f9 Ancestors: FFI-Tools-mt.3 Makes icon for ExternalStructure more legible. Adds specializations for external data, type, union, and packaged structure. Tries to make visual style for external types a little bit different bc. those are not modeled as external object. =============== Diff against FFI-Tools-mt.3 =============== Item was added: + ----- Method: ExternalData class>>toolIcon (in category '*FFI-Tools') ----- + toolIcon + + ^ #externalData! Item was added: + ----- Method: ExternalPackedStructure class>>toolIcon (in category '*FFI-Tools') ----- + toolIcon + + ^ #externalPackedStructure! Item was added: + ----- Method: ExternalType class>>toolIcon (in category '*FFI-Tools') ----- + toolIcon + + ^ #externalType! Item was added: + ----- Method: ExternalUnion class>>toolIcon (in category '*FFI-Tools') ----- + toolIcon + + ^ #externalUnion! Item was added: + ----- Method: ToolIcons class>>externalData (in category '*FFI-Tools') ----- + externalData + + ^ Form + extent: 12@12 + depth: 32 + fromArray: #( 0 4294967295 4294967295 4294967295 0 4294967295 4294967295 4294967295 0 4294967295 0 0 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4278227710 4278227710 4278227710 4278227710 4294967295 4278190080 4294967295 0 0 4294967295 0 4278227710 4294967295 4294967295 4294967295 4278227710 4278227710 4294967295 0 0 0 0 0 4278227710 4294967295 4278227710 4278227710 4294967295 4278227710 0 0 0 0 0 0 4278227710 4294967295 4278227710 4278227710 4294967295 4278227710 0 0 0 0 0 0 4278227710 4294967295 4278227710 4278227710 4294 967295 4278227710 0 0 0 0 0 0 4278227710 4294967295 4294967295 4294967295 4278227710 4278227710 0 0 0 0 0 0 0 4278227710 4278227710 4278227710 4278227710 0 0 0 0) + offset: 0@0! Item was changed: ----- Method: ToolIcons class>>externalObject (in category '*FFI-Tools') ----- externalObject + ^ Form - ^ (Form extent: 12@12 depth: 32 fromArray: #( 0 4294967295 4294967295 4294967295 0 4294967295 4294967295 4294967295 0 4294967295 0 0 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 0 4294967295 0 0 0 4294967295 0 0 0 4294967295 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0) + offset: 0@0! - offset: 0@0)! Item was added: + ----- Method: ToolIcons class>>externalPackedStructure (in category '*FFI-Tools') ----- + externalPackedStructure + + ^ (Form + extent: 12@12 + depth: 32 + fromArray: #( 0 4294967295 4294967295 4294967295 0 4294967295 4294967295 4294967295 0 4294967295 0 0 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 4278235136 4278235136 4278235136 4278235136 4278235136 4294967295 4278190080 4294967295 0 0 0 4278235136 4278235136 4278235136 4294967295 4294967295 4294967295 4278235136 4294967295 0 0 0 0 4278235136 4278235136 4278235136 4294967295 4278235136 4278235136 4278235136 0 0 0 0 0 4278235136 4294967295 4294967295 4278235136 4294967295 4278235136 4278235136 0 0 0 0 0 4278235136 4294967295 4 294967295 4278235136 4278235136 4294967295 4278235136 0 0 0 0 0 4278235136 4294967295 4278235136 4294967295 4294967295 4294967295 4278235136 0 0 0 0 0 0 4278235136 4278235136 4278235136 4278235136 4278235136 0 0 0 0) + offset: 0@0)! Item was changed: ----- Method: ToolIcons class>>externalStructure (in category '*FFI-Tools') ----- externalStructure ^ (Form extent: 12@12 depth: 32 + fromArray: #( 0 4294967295 4294967295 4294967295 0 4294967295 4294967295 4294967295 0 4294967295 0 0 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4278235136 4278235136 4278235136 4278235136 4294967295 4278190080 4294967295 0 0 4294967295 0 4278235136 4278235136 4294967295 4294967295 4294967295 4278235136 4294967295 0 0 0 0 0 4278235136 4294967295 4278235136 4278235136 4278235136 4278235136 0 0 0 0 0 0 4278235136 4278235136 4294967295 4294967295 4278235136 4278235136 0 0 0 0 0 0 4278235136 4278235136 4278235136 4278235136 4294 967295 4278235136 0 0 0 0 0 0 4278235136 4294967295 4294967295 4294967295 4278235136 4278235136 0 0 0 0 0 0 0 4278235136 4278235136 4278235136 4278235136 0 0 0 0) - fromArray: #( 0 4294967295 4294967295 4294967295 0 4294967295 4294967295 4294967295 0 4294967295 0 0 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 0 4294967295 0 0 4278235136 4278235136 4278235136 0 0 4294967295 0 0 0 0 0 4278235136 4278235136 4294967295 4294967295 4278235136 0 0 0 0 0 0 0 4278235136 4294967295 4294967295 4278235136 4278235136 0 0 0 0 0 0 0 4278235136 4278235136 4294967295 4294967295 4278235136 0 0 0 0 0 0 0 4278235136 4294967295 4294967295 4278235136 4278235136 0 0 0 0 0 0 0 0 4278235136 4278235136 4278235136 0 0 0 0 0) offset: 0@0)! Item was added: + ----- Method: ToolIcons class>>externalType (in category '*FFI-Tools') ----- + externalType + + ^ (Form + extent: 12@12 + depth: 32 + fromArray: #( 0 4294967295 4294967295 4294967295 0 4294967295 4294967295 4294967295 0 4294967295 0 0 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 4287861651 4287861651 4287861651 4287861651 4287861651 4294967295 4278190080 4294967295 0 0 4294967295 4287861651 4294967295 4294967295 4294967295 4294967295 4294967295 4287861651 4294967295 0 0 0 0 4287861651 4294967295 4287861651 4287861651 4287861651 4294967295 4287861651 0 0 0 0 0 4287861651 4294967295 4294967295 4287861651 4294967295 4294967295 4287861651 0 0 0 0 0 4287861651 429 4967295 4294967295 4287861651 4294967295 4294967295 4287861651 0 0 0 0 0 4287861651 4294967295 4294967295 4294967295 4294967295 4294967295 4287861651 0 0 0 0 0 0 4287861651 4287861651 4287861651 4287861651 4287861651 0 0 0 0) + offset: 0@0)! Item was added: + ----- Method: ToolIcons class>>externalUnion (in category '*FFI-Tools') ----- + externalUnion + + ^ (Form + extent: 12@12 + depth: 32 + fromArray: #( 0 4294967295 4294967295 4294967295 0 4294967295 4294967295 4294967295 0 4294967295 0 0 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4278190080 4278190080 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4278190080 4294967295 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294967295 4278190080 4294967295 0 4294922834 4294922834 4294922834 4294922834 4294967295 4278190080 4294967295 0 0 4294967295 0 4294922834 4294967295 4294922834 4294922834 4294967295 4294922834 4294967295 0 0 0 0 0 4294922834 4294967295 4294922834 4294922834 4294967295 4294922834 0 0 0 0 0 0 4294922834 4294967295 4294922834 4294922834 4294967295 4294922834 0 0 0 0 0 0 4294922834 4294967295 4294922834 4294922834 4294 967295 4294922834 0 0 0 0 0 0 4294922834 4294922834 4294967295 4294967295 4294922834 4294922834 0 0 0 0 0 0 0 4294922834 4294922834 4294922834 4294922834 0 0 0 0) + offset: 0@0)!

4 8

[ANN] Git Browser and Squot
by Jakob Reschke 05 Jun '20

05 Jun '20

Hello together, Over the past two years you may have seen occasional mentions of “Squot” and more likely of the “Git Browser,” which can be installed from the menus of a plain Squeak image since 5.2. In case you ever wondered: Squot and the Git Browser belong together. Let me finally introduce you to them today, since this is the outcome of my master thesis from back in 2017. ==What is Squot?== Squot is a version control system (VCS) for objects. Not only packages, but arbitrary objects (such as Morphs, so you do not have to put Smalltalk instructions how to recreate it in the VCS, but you can rather track the object itself). It uses an external VCS as its backend to store versions. As of now, only one implementation for Git exists (except for some test stub repositories for the unit tests). It should be possible to add further backend VCSs without changing the core of Squot. Squot is an abbreviation of “Squeak object tracker,” loosely based on Git’s description in its manual page: “git - the stupid content tracker”. ==What is the Git Browser?== The Git Browser is a graphical user interface to operate on Squot working copies with a Git repository as a backend. It allows you to manage working copies, track packages (multiple per working copy, which are all versioned together), browse branches, create new commits, search for commits, synchronize with remote repositories, and perform checkouts and merges. It can be used without a Git outside of Squeak (it does not call external processes or shared libraries). The tool is primarily meant to maintain Squeak projects, which are published on GitHub or similar platforms, but can be used with any Git repository. ==Is it ready for use?== To work on Smalltalk projects: definitely yes. It has been used for at least three years in student courses at HPI (Potsdam). I am also using the Git Browser to work on Squot itself. To really track other objects than packages: possibly. It has some bugs left, so I would not recommend to rely on the tracking of objects other than packages for production use. For this reason, there is also no GUI yet to add other objects to a working copy in the Git Browser. There are occasional quirks when pushing to GitHub (“Connection closed”), so you might need to resort to the Git CLI sometimes. Currently you must also merge non-Smalltalk files outside of Squeak. To view the commit history as a graph, you can use external tools, such as gitk, SourceTree, or whatever your preferred Git GUI is. ==How can I use it?== 1) Install the Git Browser by choosing Tools > Git Browser in your Squeak image (since 5.2). This will also load several of dependencies via Metacello. 2) Once you have the Git Browser open, it will prompt you whether you want to create your first project now. If you would like to start a fresh and empty working copy on an empty Git repository, select “yes” and provide a path for the Git repository. If you would rather like to clone an existing Git repository, select “no.” 3) The Git browser itself has five panes: * On the top left, there is a list of projects. These are your working copies. Each working copy links something in your Squeak image to a Git repository outside of that image. Via the context menu of this list, you can add, change, or delete working copies and repositories. If this list is empty, you will want to start with the context menu here. * Below that, there is a list of branches in the currently selected project (if any). Via the context menu, you can add, rename, and remove branches, push to remote repositories, and switch branches. One branch is highlighted with a green dot; this is the branch that is currently checked-out. If you create new commits, they will go on this branch. * On the top right, there is the list of commits on the current branch (if any). You can compare commits with each other or a commit with the working copy, search for commits using the search bar below the list (or via list filtering to only search the headlines), create a new branch at a commit, reset the current branch to an older commit, or check out or merge specific objects from a commit. * In the bottom-left pane, the full log message of the selected commit will be displayed. In addition to that, it will also show the commit metadata, such as the author, committer, and the abbreviated SHA-1 hash of the commit and its parents. * Finally on the bottom right, there is a list of objects in the selected commit. These are usually the packages known in a particular commit. Via the context menu you can checkout or merge an object with the working copy (read checkout like “Load” in Monticello and merge like “Merge”), browse either the object as it was at the time of the commit, or what is currently loaded. You can also access the current scripts (preamble, postscript etc.) of packages here. 4) Between the panes, there is a strip of buttons. They operate on the current branch or the selected commit. At the far right, you can configure how things go to Git: that is your name and e-mail address for the commit metadata, the Smalltalk file format you want to produce (FileTree/Cypress or Tonel), and whether Squot should suppress writing its own configuration files (if you want to submit a pull request to a repository that is not developed with Squot, for example). Via the Feedback button, you can create an issue for Squot on GitHub directly from the image. You can also file these here: https://github.com/hpi-swa/Squot/issues 5) To add another package to a project, or remove a package from the set of tracked packages, open the menu of a project and choose “Change tracked packages”. Below that menu item, you can also change between writing FileTree/Cypress or Tonel files (“Set package storage format…”). 6) When you switch branches via the context menu of the branch list, note that it will stow away all your unsaved changes and the other branch is checked out clean. Your unsaved changes will be restored when you switch back to the original branch. This behavior is different from the Git CLI, and was conceived in an alternative Git frontend called “Gitless” (which addresses some of Git’s awkwardness). 7) When you want to commit, you will find that there is no Git staging area as far as the Git Browser and accompanying tools are concerned. Instead, you can choose which packages, classes, and methods you want to include or exclude in the commit dialog, like in Monticello in recent years. 8) When you checkout or merge something, you always first get a list of changes, from which you can choose what to load and what to skip. 9) To update the Git Browser when a new version was published, open the window dropdown menu (third button from the right in the title bar) and choose “self-update…”. It pulls the latest version from the master branch on GitHub. Ongoing development happens on the “develop” branch, not on master. You can also pull that version by choosing “set self-update branch…” in the same menu, and then invoke the update. ==How does it work internally? Why is it not a Monticello extension?== Squot knows of three presentations of an object: 1) the “live” object that is “the real thing,” which you can normally handle in Squeak, 2) one or more “shadows” of the object, which is a captured representation of one version of the “live” object (a snapshot); it is used to reason about different versions of the same object without loading them, 3) a “stored” object, for example serialized into a file. Objects are tracked in graphs of objects. You add an object graph by adding a “root object” to the working copy, from which all the other relevant objects can be reached. For example, you could add a complex Morph, which would include all of its submorphs. The tracked objects can to a certain degree control how they are captured; for example, the “root Morph” will direct Squot to ignore its #owner instance variable (because otherwise you would always track the whole World). To be able to identify an object in different versions of a graph, each object gets a unique name assigned when it is first captured. Objects may opt out of getting a name if they are true value objects for which identity does not matter when a shadow object is rematerialized to a live object during a load/checkout. Identity does not matter when it makes no difference whether two objects refer to the same instance of the value, or a different, equal instance (like Number, Point), or if there is only one instance by definition (like UndefinedObject, Boolean, Symbol). Packages, which are the only kind of object you can currently track in Monticello (besides configurations of packages), are just a special case of all of this. Read the rest of this paragraph as an example of what I wrote in the previous paragraph. The live package is represented by its PackageInfo. It subsumes the loaded behaviors and methods that are attributed to the package. A shadow package basically wraps an MCSnapshot of the package (Squot reuses MCSnapshots and MCDefinitions under the hood to represent shadows of packages, behaviors, methods). A stored package is a tree of files in FileTree/Cypress or Tonel format, for example. In theory, it could also be any other file representation, such as a plain file-out, or a SmartRefStream that contains the MCSnapshot. A PackageInfo is the “root object” of a package object graph in the working copy. PackageInfo will tell Squot that it does not want a unique name assigned, because a PackageInfo is already identified by its #packageName. To create the shadow package, PackageInfo also overrides the capturing process for Squot to find the classes, and methods (which are not directly referenced) and turn them into an MCSnapshot with Monticello. When a package is loaded in Squot, it will also use Monticello to actually install the changes. As a general way to capture any kind of object, Squot has shadow classes to capture objects as collections of slots that refer to other objects. Instance variables and indexed variables are two basic kinds of slots in this model. Specializations in this model are also possible: for example, Sets and Dictionaries use special kinds of slots for their elements or associations, so Squot does not capture their internals (the hashtable array and tally) instead. It takes into account that associations can be shared among multiple Dictionaries (like Bindings). Squot does not reuse the existing repository and versioning infrastructure of Monticello. I did this to be free of the constraints of the contemporary Monticello, and to not break it while developing Squot and its companion packages. Some concepts are also different: in Monticello you have packages and versions of packages, in Squot you have versions, each of which can contain one or more packages (or something else). That is, a Squot version could be viewed as a version of a configuration map. This maps better to the concepts of popular file-based version control systems like Git, Mercurial etc. Moreover, a Squot repository is not just a store for versions; it also knows branches (the managers of history). The Git Browser belongs to a package called Squit. Squit connects Squot and Git, like its name does. It provides Squot repositories and versions, that are in fact adapters for Git repositories and Git commits. To maintain the actual Git objects, Squit uses a package called FileSystem-Git, which allows developers to browse files in Git commits like regular file trees using the FileSystem API. (This was the first effort to support a Git implementation in Pharo, until Pharo abandoned it in favor of the libgit2 binding. If I remember the author timestamps correctly, FileSystem-Git was primarily developed by Max Leske, Camillo Bruni, Damien Cassou. The core Git classes are in turn based on the ones written by Tony Garnock-Jones, which can still be found on squeaksource. I converted FileSystem-Git back from Pharo to Squeak and made it work for its purpose (it is not a feature-complete Git, but you can read and write local and remote repositories correctly). Much of the work has already been done by the others, but some things needed to be fixed or added to make it usable. To that end, I revived the Squeak implementation of FileSystem and extended it where necessary. As of now it is not fully compatible with the API in Pharo (class names and some method names are different), but that is still not impossible to change.) More details can be found in our technical report [2]. ==Closing words== I hope you will have fun using Git with Squeak. Thanks to all those who have contributed to this project (and its dependencies/ingredients) so far! https://github.com/hpi-swa/Squot/graphs/contributors Kind regards, Jakob [1] https://www.hpi.uni-potsdam.de/swa/publications/ [2] https://www.hpi.uni-potsdam.de/swa/publications/media/ReschkeTaeumelPapeNie…

3 3

Error in Promises/A+ reject implementation?
by Jakob Reschke 05 Jun '20

05 Jun '20

Hello all, I think our Promise behaves wrong, but I would like a second opinion. We have this test case: testifRejectedRunsBlockIfPromiseFails | p q error | error := nil. p := Promise new. q := p ifRejected: [:e | error := e]. p rejectWith: KeyNotFound new. self assert: q isRejected. self assert: KeyNotFound equals: error class. But the JavaScript behavior is actually different: x = {}; p = Promise.reject("Rejected"); q = p.then(null, error => error); q.then(value => { x.value = value; }, error => { x.error = error }); x // <- { value: "Rejected" } The difference: the chained promise q is resolved instead of rejected. Otherwise x would look like this: { error: "Rejected" }. I think the behavior in our Promise is also in violation with the Promises/A+ specification it claims to implement (https://promisesaplus.com/): [...] 2.2.7 then must return a promise. promise2 = promise1.then(onFulfilled, onRejected); 2.2.7.1 If either onFulfilled or onRejected returns a value x, run the Promise Resolution Procedure [[Resolve]](promise2, x). 2.2.7.2 If either onFulfilled or onRejected throws an exception e, promise2 must be rejected with e as the reason. [...] So if I understand this correctly, since in the test case Promise p gets rejected and the ifRejected: block evaluates to e without being curtailed by an exception, Promise q should be resolved, not rejected, with e, according to §2.2.7.1. Do you agree and should we fix this? On an only slightly related note, I am unhappy that I cannot debug errors in promise handler blocks (then: [...] ifRejected: [...]). It catches all those errors and just rejects the promise. In a server environment that would probably be ok, but at development time at least I want to have the chance to investigate the problem in a debugger. Especially those programmer's errors resulting in MessageNotUnderstood, which I could fix on the fly and let the program proceed. In JavaScript you cannot resume exceptions, but in Smalltalk you can. It might be nice to turn the on: Error do: [:e | p rejectWith: e] code in Promise into an ifCurtailed: [p rejectWith: e] to allow exceptions/errors to be resumed before rejecting the promise. The promise would still be rejected if you press Abandon in the debugger. Problem: further errors in the rejected handlers would result in "Unwind error during termination". This could in turn be avoided by rejecting the promise in the "future", that is the next cycle of the world. Opinions? Kind regards, Jakob

4 5

Is there a pull-right hierarchical menu in Squeak?
by Stephen Pope 05 Jun '20

05 Jun '20

Hi all, The title says it all; my app (Siren) uses hierarchical menus extensively (see the attached screen shot for an example), and I'd rather not have them be many-click menus as in Squeak. Is there an implementation of true hierarchical/pull-right menus in Squeak or any of its descendants (I'm using Cuis). stp <http://forum.world.st/file/t9553/h-menu.jpg> -- Sent from: http://forum.world.st/Squeak-Dev-f45488.html

4 4

Monticello postscript problem
by Martin Kuball 04 Jun '20

04 Jun '20

Hi all, I have a problem with a postscript in one of my Monticello packages. It fails to execute because a class used in the script did not had it's initialize method run, yet. I took a look under the hood and found, that the postscript and the initializer execs are all mixed together in one list. But the postscript was not at the end of this list. So is this a bug or is there for some reason no guarantee that the postscript is run when everything else is done? I fixed this for me by running twice over the list. First for the non-scripts and then for the scripts. Not very pretty but seems to do the job. Martin

3 6

FFI | Squeak's Integer to C 'long' or 'long long'
by Marcel Taeumel 02 Jun '20

02 Jun '20

Hi, there! Here is a question of consistency. :-) In the definition of external structures, we write 'long' or 'long long'. In the definition of external pools, we write #Integer. The latter is automatically converted into a "(long long)" cast for printf. What is the better approach? I think it would be better to also write 'long' or 'long long' when defining external pools: <ffiVariable: MY_CONSTANT type: 'long long'> instead of <ffiVariable: MY_CONSTANT type: #LargePositiveInteger> Would make it easier to define platform-specific differences. Best, Marcel

2 3

function keys in squeak
by Martin Kuball 02 Jun '20

02 Jun '20

Hi, it seems that squeak is ignoring function key events (F1 - F12). I tried Sensor kbdTest but nothing happens when I press a function key. Am I missing something? Martin

4 3

FFI | Byte alignment
by Marcel Taeumel 31 May '20

31 May '20

Hi, there. In ExternalType class >> #initializeAtomicTypes, there is an interesting claim and a piece of dead code: "On 32 bits Windows and MacOS, double and long have an alignment of 8. But on Linux, their alignment is 4" (Smalltalk wordSize = 4 and: [Smalltalk platformName = 'unix']) ifTrue: [ (#('double longlong ulonglong') includes: typeName) ifTrue: [ byteAlignment := 4 ] ]. As you can see, there are single quotes missing and so will the path "byteAlignment := 4" never be reached. I tried to figure out whether one should either fix the conditional or remove the entire passage. Maybe this got long fixed inside the FFI plugin? Best, Marcel

7 18

A nicer look & feel for chess
by Stéphane Rollandin 31 May '20

31 May '20

Hello, We have a cool chess implementation in Squeak, but its UI is rather outdated and, dare I say, ugly. I propose in the attached archive another skin with a nicer look & feel. The pieces images are from Wikimedia Commons, so I guess they are fine for inclusion: https://commons.wikimedia.org/wiki/Category:SVG_chess_pieces To try it, do ChessMorph2 new openInWorld or (ChessMorph2 new squareSize: 100) openInWorld (the board is scalable from its halo yellow handle) Stef

1 0

[ANN] Aida/Web v6.8 released
by Janko Mivšek 31 May '20

31 May '20

Dear Squeakers, Aida got recently a development push and together with improvements over several years it is now a time for a new release. Main effort was put on realtime and Single-Page Applications (SPA) to be prepared for a forthcoming decade of web development. A dependency mechanism was introduced for domain objects to announce its changes easily. Web apps can subscribe to changes and update elements of a web page accordingly. Multitab support is another improvement to mention, also many minor ones and patches, more in https://www.aidaweb.si/release-notes-6.8 To install on Squeak (tested on latest 5.3 64bit): i := Installer monticello http: 'http://squeaksource.com'. i project: 'SPort'; install: 'Sport-2.031'. i project: 'Swazoo'; install: 'Swazoo-2.4final.2'. i project: 'Aida'; install: 'Aida-6.8final.2'. .. then open http://localhost:8888 . Aida/Web is a Smalltalk web framework for building dynamic web applications the Smalltalk way. From classical to single-page web apps, on high-level so that building web apps becomes a joy, not a hassle! https://www.aidaweb.si Best regards Janko

6 9

← Newer
1
...
4
5
6
7
8
9
10
...
27
Older →

Jump to page: