Little VAST hacks: Keep Track of (and re-find) needed Changes

Sometimes you just need some easy hacks to make your life much easier. One of them is to keep track of things you have to do later. Be it cleanups, some other thing to take care of once "this is done". We as Smalltalk developers live, drink and breathe source code and objects and are … Continue reading Little VAST hacks: Keep Track of (and re-find) needed Changes

Pharo is moving to GtK3 (finally)

Today seems to be my Smalltalk-news-blogging-day 😉 It started off with an announcement from Instantiations about plans for the next release. Just a few minutes ago Esteban Lorenzano announced on the Pharo Mailing List that Pharo 8 will be based on Spec 2.0, a new version of the still quite young GUI framework in Pharo. … Continue reading Pharo is moving to GtK3 (finally)

News from Instantiations: VAST 9.2, IoT, new JITter

Last night Instantiations sent out a newsletter informing users and fans of VA Smalltalk about the latest developments around VA Smalltalk. It's not too much of a surprise that Instantiations is working on a new release 9.2 of VA Smalltalk which is scheduled to arrive later this year (let's speculate a little and spread rumors … Continue reading News from Instantiations: VAST 9.2, IoT, new JITter

VASTGoodies just turned 10

As Adriaan just announced on his blog, VAStGoodies.com was launched the 27th of January, 10 years ago now. But not only that, just a few days before that milestone, another milestone was reached: the 1000th upload! The introduction of VASTGoodies was a much-needed and welcomed addition to the Smalltalk universe. Back in the 2000's the … Continue reading VASTGoodies just turned 10

What to do when VAST x64 (and Seaside) on Linux need a little help finding libcrypto.so

[update: I just updated the title of the post, because on other Linux machines,  like our test and production servers, there is a link named libcrypto.so in the 64 bits libraries path, so the change to the ini file is not necessary there... 20591215 0 lrwxrwxrwx 1 root root 16 Jun 20 13:29 /usr/lib/x86_64-linux-gnu/libcrypto.so -> … Continue reading What to do when VAST x64 (and Seaside) on Linux need a little help finding libcrypto.so

Seaside, File Libraries and UTF-8

In my seemingly endless hunt for potential problems with Umlauts travelling between our users' web browsers and our Seaside images, I find new areas of "interest" almost daily. As a little background information, it might be useful to mention that at least the Smalltalk diealect we are using (VA Smalltalk) is not speaking UTF-8 natively, … Continue reading Seaside, File Libraries and UTF-8

Glorp findings – using count:

Conntinuing on the Customer/Order example from my last post, we might want to only send some ads to customers who have ordered at least twice in the past. For this we'd first have to cunt all orders of our customers who haven't ordered for at least 100 days. So the first step is to create … Continue reading Glorp findings – using count:

Glorp Subqueries – notExists:

I decided to get back to blogging after a very long break. Since I am quite busy with our Kontolino! project, I also decided that I need to get back to blogging with small articles that require little time - but might still be useful. So here is the idea: I am struggling with Glorp … Continue reading Glorp Subqueries – notExists:

Seaside Learnings, pt. 123

Note to self: never, never ever try to use show:onAnswer: or answer: in an Ajax callback. In your delegating WATask or  WAComponent you will see the callback code run as if all was good, just the new components won't show up in th browser. This will take a long time to debug and you won't … Continue reading Seaside Learnings, pt. 123

Why many managers failed…

So one of my posts on the Pharo Mailing list just made it into the Pharo Weekly News Blog 😉

Weekly news about Pharo

to understand the power they could have in their hand. Here is a testimony on the Pharo mailing-list. This is why we should build powerful new solutions in Pharo 🙂

Stef

Petr,

I’ve been working as a Consultant for many big corporations (mainly in VA Smalltalk) since 1996. The situation you describe is very well known to me. But in my opinion there is no technical reason for this. It’s a managerial problem. Ever since IBM went out to their customers and told them to move to Java for the better ini the mid-90ies, managers wanted the Smalltalk projects to go away as fast as possible. Nobody asked why IBM was still happily using VisualAge Smalltalk internally at that time frame….

So the Smalltalk projects were declared legacy by Management. Replacement projects were started with big efforts and optimism. Some went well, some somewhat came to fly in a bit…

View original post 486 more words