Actually, CINCOM’s framework will likely see adoption in the enterprise (in recent years, financials) and Ruby on Rails remain the small ISV temptation that it already is … and no, Smalltalk is not dead: just look at the CINCOM client list.

Nor is PROLOG dead. One of the vendors simply chooses to mention their software and their clients, not their language. Competitive advantage, I suppose. What Seaside has done for Smalltalk we may yet see Logtalk do for PROLOG.

As for Curl, there should be an announcement soon …

Falcon is a multi-paradigm language – not yet as multiply gifted as Oz, but on its way.

The plans for Falcon from here to 1.0 are very ambitious: like Io, it is a language to keep an eye on. Are you coming with?

‘Aule’ means hall or entryway (it is ‘Eule’ that mean owl … ) and because of the ‘lobby’ concept in the Io language, I had once suggested it as a name for Io. “Simple” was taken, so ‘Aule’ it is!

Here is what the documentation says:

resync-file (accessor) Class: ComponentMetaData Package: CURL.LANGUAGE.COMPONENT

getter public sealed resync-file:#String
setter public sealed resync-file:#String

Set component resynchronization time from specified file.

When specified in the meta-data for an applet or script this attribute defines the URL of a file whose when-last-modified time will be used to set the value of process-resync-as-of.

When setting this value through this setter, the value must contain an absolute URL or an exception will be thrown. When setting via the applet or script declaration a relative path may be used or the empty string may be used as shorthand for the main applet or script load file.

What I could have added were the tags of some of my bookmarks in my Curl Documentation Viewer, such as

never-returns
unreachable
EmptySource
OpenPackage

But I think that Curl templates are a very handy way to implement alternative technical ebooks: what is needed is for a technical ebook publisher such as Springer to adopt Curl as an alternative offering.

Regardless, I must get over to Lulu about that Curl ebook …

Regardless, the Curl framework is using an abstract DataObject class with two subclasses: StandardDataObject and DynamicDataObject. It was interesting to see that one DataObject factory method uses
from-traits
    traits:DataObjectTraits
as traits are not much discussed in relation to Curl.

The supported types are bool, null, String, int, double, DateTime, DataObject, Array, ExtendedArray, ByteArray, AMFXmlDocument with the latter being just a wrapper for a String of XML. An ExtendedArray used to obtain a DataObject from a ByteInputStream or to put to a ByteOutputStream with its AMFSerializer and AMFDeserializer children.

Here is the default constructor for the DataObjectTraits:

{StandardDataObjectTraits.default
    name:String,
    members:StringArray,
    dynamic?:bool = true,
    externalizable?:bool = false
}

so this look very approachable. But it has nothing to do with Traits as in Squeak or Scala. Traits were introduced to help structure the refactoring of code in a way in which categorizing methods could not. Traits are classes which are not intended to have instances but which can implement methods. That is a very natural thing in Curl, but without a refactoring browser, their usefulness as an explicit cosntruct is dificult to demonstrate (an Eclipse plugin might be in the offing.) The Curl 7.0 introduction of a library access modifier should make naming classes with Trait more meaningful.

Now to get BlazeDS running on my Apache localhost.

I have come to rely on Mozilla Prism for the sites at which I make daily changes: but I know that Curl offers a an enterprise SSB alternative to GreaseMonkey. And I can see a Curl GTD browser that makes TiddlyWiki seem lame in comparison. Let 42 useful browsers bloom!

The two projects with available downloads are for Curl 6.0 at this moment and do not yet have detailed English documentation. I had no problem deploying the LIB project as as to be able to install 6.0 documentation for the Curl Documentation Viewer. The ORB project has pre-compiler pre-processed pcurl code files containing standard Curl docs.

The ORB project includes both Curl and Java directories along with a curl-orb-client.jar which has classes such as CurlSerializableStreamWriter and a set of server-side JAR files including curl-serializer.jar and curl-orb-server.jar From what I can see, the object request project includes code for generating mappings between object instances in Java and object instances in Curl.

This attention to the j2ee server-side should help move Curl towards the goal of Curl as a secure enterprise platform and not just a mature web-content language for the client-side.