smalltalk

To me it seems the main point of Seaside is that it is more like normal "desktop" programming. The control flow looks much more like "traditional" programming instead of "web" programming. Is that a correct impression? I know it's about Web programming but it's does not looks like it from the programmers side. It looks much more than driving "desktop" applications. Does this clarify the question a bit? Your impression is correct. Seaside is designed for what I call a tree-like control flow, as desktop GUI apps have. Comparing to the Aida/Web , another Smalltalk web framework, which is meant

I am using the Squeak 5 class SecureSMTPClient to send e-Mails over SSL/TLS. It works fine on my Windows machine (thanks to the answer to that question ). However, on Linux i get: Error: primitiveSSLCreate failed And it prints in a console (but only the first time the image attempts to send the mail): # ioLoadModule(/home/squeak5vm/SqueakSSL): /home/squeak5vm/SqueakSSL: undefined symbol: clock_gettime Squeak "primitives" are functions that talk to the platform and libraries. My guess is, that this Linux does not provide some version of some SSL/TLS library that Squeak expects. But what exactly

I commit several versions of Monticello packages to a local repository on my disk during the day. At a later time I want to sync the local repository with a Smalltalkhub.com repository. At the moment I copy the local commits manually one by one to the Smalltalkhub repository using the Monticello browser. How can i automate this task? You can use Gofer to automate your Monticello tasks. Gofer new package: 'MyProject-Core'; package: 'MyProject-Tests'; url: 'http://smalltalkhub.com/mc/USER/MyProject/main/' username: 'USER' password: '***'; push. In the Gofer chapter of the "deep into pharo" new

I am using Squeak 4.4 update 12327, and VM version 4.1.1. I tried to load VMMaker with ConfigurationOf scripts but always fails with exceptions mainly in the Freetype package. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfVMMaker'; load. ((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.4') load or Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfVMMaker'; load. (Smalltalk at:#ConfigurationOfVMMaker) project lastVersion load. or Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfVMMaker'; load.

I’d like to display a table of values and be able to select cells. How would I do this in Pharo Smalltalk? I’ve heard talk of Morphic widgets able to do this, but I’m still really new to Smalltalk. Clement Bera I would look into TreeModel class side examples. I used to do that: tree := TreeModel new. tree openWithSpec. tree columns: (Array with: (TreeColumnModel new displayBlock: [:node | node content first asString ]; headerLabel: 'Name'; yourself) with: (TreeColumnModel new displayBlock: [:node | node content second asString ]; headerLabel: 'Last Name'; yourself) with: (TreeColumnModel new

Can someone explain how the organisation of classes in Pharo works in different versions of Pharo? All Classes are part of the Smalltalk global (have always been, seem to stay like this?) Classes can have a Category, but thats only a kind of tag? (has always been, seems to stay like this? But the categories are somehow mapped to packages sometimes ?) There are different kinds of Packages in different Versions of Pharo MCPackages representing Monticello Packages PackageInfo RPackage (Pharo 1.4)? In addition there is SystemNavigation which somehow helps navigating classes and methods based on

The Smalltalk object thisContext look strange and marvelous. I can't understand what it is and how it works. And even how it enables continuations. For C's call-stack, I can easily imagine how is it implemented and working. But for this... I can't. Please help me to understand it. I think it is not an easy question. The stack is reified in the image with instances of MethodContext. A MethodContext can have a sender, which is another MethodContext. That one can have another one...generating a whole stack. MethodContext are instantiated by the VM while executing CompiledMethod (which are also