Group items tagged

F-Script is a lightweight open-source scripting layer specifically designed for the Mac OS X object system (i.e. Cocoa). F-Script provides scripting and interactive access to Cocoa frameworks and custom Objective-C objects. It aims to be a useful and fun tool for both beginners and experts, allowing interactively exploring, testing and using Cocoa-based objects and frameworks. Based on Smalltalk, F-Script provides a pure object-oriented environment that leverage Mac OS X technologies and includes significant innovations

Exploring Cocoa with F-Script Learn F-Script in 20 Minutes and Have Fun Playing with Core Image Scripting Cocoa with F-Script Creating Cocoa Classes with F-Script System-wide Scripting with F-Script Embedding F-Script into Cocoa Applications

So you win in terms of the interactive nature of F-Script but you don't move past the fussy little details that come along with Cocoa.

screenshot of him editing the OpenMCL listener window in the cocoa Interface Builder.

Its interactive Smalltalk-like Object-browser offers an intense way to explore the objects you've created, traverse their instance variables and methods and really start to interact with them in a way not normally permitted by Xcode. You can visually review the object's current state. You can pick new messages to send.

F-Script Anywhere, which is included in the standard F-Script binary distribution.With FSA, you can inject F-Script into any running Cocoa application and inspect the object tree at runtime -- without having source! Or even requiring source changes! From a development perspective, this lets you script your applications much more simply than AppleScript -- you don't have to create a parallel and incomplete object model.

Before Cocoa was really big and before there were a lot of objective C programmers because of that, I think they saw Java as being the future and they ported it to Java and since then I think Objective C has really seen a resurgence because Cocoa has really won as the way of developing application was then and I think they probably wouldn't have done that if they knew what they know now.

Web objects was what really opened my eyes to the idea of having extreme amounts of session state and extreme amounts of session state in a form of a tree of state full objects that represented part of the web page and that by keeping that around between requests you could keep much more information there and you could have a much higher level of abstraction when you were building a web application than using the kind of more traditional approach, which is to have a small amount of session states other stored on the cookies or stored on the server but have the best majority of the states be passed in the URL be passed in the form parameters and that core idea certainly was taken from web objects.

web objects didn't use continuations and Seaside doesn't have to use continuations now either, in the more recent versions of Seaside you can optionally use them

The industry stewards have countered Apple's move with their own application stores, so there's a huge opportunity to write the "killer app" for one of several smartphone platforms.

40 MB to less than 4 MB of free RAM

one-app-at-a-time requirement complicates any implementation of a copy-and-paste mechanism.

I can't imagine building a user interface intensive application through this technique. It would be extremely cool if they could integrate Interface Builder,

third attempt at having an Objective-C bridge in Squeak.

once we resolve the classOop we just send messages to the instance like we would do with a normal Smalltalk object.

When not using Renaissance, Objective-C software developers face the endless task of maintaining the views of their applications for GNUstep with Gorm and for Mac OS X with Interface Builder.

sharing a common user interface on both GNUstep and Mac OS X can lead to human interface guidelines (HIG) violations on both platforms.