Maintaining Your Gemstone Installation
Norbert Hartl has some useful maintenance tips for Gemstone/S developers and admins. Hat tip Dale
Technorati Tags: gemstone
. .
The author of this blog, James Robertson, passed away in April 2014. This blog is being maintained by David Buck (david@simberon.com).
Norbert Hartl has some useful maintenance tips for Gemstone/S developers and admins. Hat tip Dale
Technorati Tags: gemstone
Good news for Scratch fans - there's a port in progress from the (fairly old) rev of Squeak that Scratch uses to Pharo. You can check the progress and participate via the Google Code Page
Bob explains how easy it is to push up a nice, simple graph using Seaside
Technorati Tags: seaside
If you want to test Squeak Source 3, it's live - but it's for testing right now, note the warning:
The contents of this repository will NOT survive beyond the lifetime of the public Alpha. DO NOT store anything you are not willing to lose in this repository.
Technorati Tags: squeak, squeak source
Travis has been working on an interface to Uniscribe:
I've been working on a Uniscribe interface to VisualWorks Smalltalk off and on for the last two weeks or so. One of the frustrating things for me so far, is the lack of a good post-doc resource to go to for help with this stuff. There's the MSDN docs, which are OK, but when you have questions beyond that, I have as of yet, not found any of the resources I'm used to using for this kind of thing, such as mailing lists, etc. And the amount of "tutorial" style pages out there is pretty small. So I thought I'd at least leave a trail of breadcrumbs here.
Technorati Tags: visualworks
Sean DeNegris talks about simpler data storage:
In an enlightening blog post, Ramon Leon explains that most applications are designed for small businesses with small amounts of data. Therefore most applications will never have to scale (i.e. become the next Twitter), so a relational database is overkill. However, persisting by simply saving the image is slow and error-prone.
Based on these ideas, he suggests a simple (one class) framework which saves only your model. The idea is to use it as long as you can get away with, which may be forever.
I packaged the code from the post, added a few tests, and put it on SqueakSource as SimplePersistence.
You have no idea how many security headaches I've avoided by using binary serialization to store the posts on this blog instead of a SQL Database. As with Sean's example, my storage needs are lightweight, and a relational database would be overkill. Not to mention being an attack vector....
Technorati Tags: storage
Looks like JTalk is still making good progress:
As announced in an earlier blog-post, i implemented a RemoteRunner for the jtalk-server (based on the jtalk-project). It's very simple: if you implement a Method runRemote in your class, e.g. RemoteTest, then by executing:
RemoteRunner new runClass: RemoteTestwill execute the Smalltalk-Code implemented in the runRemote-Method on the server. The example prints out the date and time of the server.
BOSS is one of the more useful pieces of VisualWorks, so I'm interested to see that the Pharo project is acquiring a modern equivalent. Via Torsten:
Fuel - a new project to implement binary object serialization for Pharo is part of the ESUG SummerTalk. It's work in progress but already usable, there is a ConfigurationOfFuel metacello config to easily load it.
The existence of a Metacello configuration is key - it makes it very, very easy to load (and thus much easier to contribute to the project). Good stuff!
Technorati Tags: serialization, fuel, pharo
This afternoon I had to export part of a tree of objects from one UI to a smaller one (to allow for end user editing of those objects). This all backs to a database, so I didn't want the AspectAdaptors (this is VisualWorks) I was hooking up to make changes to the actual domain objects; I wanted copies. Using #copy and #postCopy is pretty straightforward, but I wanted to check to make sure that I was doing it correctly
As part of our development toolset, we have some mods that add a little "inspect it" button to every window. That's highly useful, and got me most of where I wanted to go. The last step was simply using base functionality of VW that a lot of people probably aren't aware of - you can drag objects from an inspector and drop them on a workspace, creating a workspace variable that points to that object. Doing that from each piece of the UI, I was then able to run a simple #== check on the objects, and verify that my copy operation was working correctly. Kind of a cool thing to be able to do, that drag/drop between tools.
Igor Stasenko has implemented Ephemerons for Cog. Why should you care? Eliot explains that.
Hat tip Torsten
Technorati Tags: ephemerons, cog
Previous | Next | (1107 total) |