Re: [F-Script-talk] newbie questions

[Rainer K. <dri...@ma...>]

Hi Philippe,
>

> Yes. Actually the KFDecorator module adopts this kind of approach
> (see http://homepage.mac.com/kenferry/software.html#KFDecorator).
Yep, I had found KFDecorator (sorry for not mentioning) but was  
missing a way to add member variables.
But I hadn't seen JGType, thanks for the pointer!
>
> There are several limitations in the current implementation: no
> direct access to instances variables (you have to use KVC), no
> support for calling super etc.

understood. But is there a reason that the KVC for the variable names  
and references to super could not be easily done in the compiler?  
Each F-Script class could have a base class, either an objective-C  
class or a previously defined Smalltalk class and two additional  
dictionaries for added member variables and methods. If you then hook  
into the compiler, KVC for the variables could be done automatically  
and super would be available as well. The compiler would just have to  
distinguish if it is still at the Smalltalk layer for resolving  
symbols or already at the boundary to Objective-C.
Does that make sense?

>
> The saveSpace and loadSpace methods of the class System let you save
> or load an entire workspace. Not really the same as an image, though.
Yep, have found that as well (again sorry for not mentioning). But  
image and changes file would be shared between multiple open  
workspaces, changes would grow by both and in my mind the image would  
be part of the resources of the application (once modified probably  
stored in the users Library/Application Support folder and loaded  
automatically on app startup).
Does anybody have an idea in which classes to look to get an idea how  
iamge and changes file are maintained for example in Squeak?

>
> Best,
>
> Philippe

Thanks for the quick answer and pointers!

Rainer