Hi Liliana.
Liliana wrote:
Hi,
We have an Intel dual core 64 bit server where we installed Ubuntu 7.04
We are all new in Squeak/Smalltalk; but we managed to develop a small
Seaside app in Squeak (on Windows XP) using Squeak 3.9 and Seaside 2.7
(latest).
We would now like to install this
Liliana wrote:
Hi,
We have an Intel dual core 64 bit server where we installed Ubuntu 7.04
We are all new in Squeak/Smalltalk; but we managed to develop a small
Seaside app in Squeak (on Windows XP) using Squeak 3.9 and Seaside 2.7
(latest).
We would now like to install this image on the
Thanks, this worked and helped.
So to extend this, and help my understanding, how do I refer to a
morph in a workspace? If I named the morph polyB, and I do something
like hide PolyB in the workspace it asks about PolyB.
On 3 Jun 2007, at 14:26, Bert Freudenberg wrote:
On Jun 3, 2007,
From: Michael van der Gulik [EMAIL PROTECTED]
Subject: Re: [Newbies] squeak on ubuntu linux
Hi Michael.
Thank you for your reply so far...
I would recommend trying the 64-bit binaries:
http://www.squeakvm.org/squeak64/. I have used this version of Squeak on
an AMD-64 machine without any
Etoys is a layer on top of Smalltalk, so in most cases you can
(unfortunately) not use the regular Smalltalk coding tools directly.
OTOH, it's Smalltalk after all so of course you *can* access
everything ;)
Also, the way you phrased it, it seems you may have missed the
distinction
I've been playing around with Squeak and noticed that if I try to debug
an expression (highlighting it in a workspace and clicking debug it in
menu) i'll end up freezing the whole system. This happens when I keep
clicking on Into button in debugger so that the last message sent is:
This is getting clearer. So would a better approach be to add a
method for this class? Would I add a method for PasteUpMorph such as
showa: polyb. Looking at the following script, showa method would
show self, and hide the argument polyb? Then when writing the morph
code I can refer to
On Monday 04 June 2007 4:40 pm, Bert Freudenberg wrote:
Now that only works for morphs that actually *have* a player, that
is, the morphs that are scripted.
I noticed that the 'debug' button has new entries for player the moment I open
a player on that morph, even before I start creating
On Jun 4, 2007, at 16:47 , subbukk wrote:
On Monday 04 June 2007 4:40 pm, Bert Freudenberg wrote:
Now that only works for morphs that actually *have* a player, that
is, the morphs that are scripted.
I noticed that the 'debug' button has new entries for player the
moment I open
a player on
I'm not sure what exactly you want to achieve. adding a method to a
class is how you approach things in Smalltalk. Scripting an object
is what you do in Etoys. These two do not go well together, you have
to choose. Etoys tile scripting is *not* an introduction to Morphic
programming. It's
On Sunday 27 May 2007 9:44 pm, Bert Freudenberg wrote:
There is a difference between class variables (which are like
static variables in other systems, so they get their fare share of
use) and class instance variables (very rarely used indeed). You
see class instance variables only when you
On Mon, Jun 04, 2007 at 02:00:42PM +0200, Damian Dobroczy??ski wrote:
I've been playing around with Squeak and noticed that if I try to debug
an expression (highlighting it in a workspace and clicking debug it in
menu) i'll end up freezing the whole system. This happens when I keep
clicking
On Jun 4, 2007, at 19:40 , subbukk wrote:
On Sunday 27 May 2007 9:44 pm, Bert Freudenberg wrote:
There is a difference between class variables (which are like
static variables in other systems, so they get their fare share of
use) and class instance variables (very rarely used indeed). You
Hi, Subbu,
Try:
ClassListBrowser browseClassesSatisfying: [:cl | cl class
instVarNames size 0] title: 'classes defining class-side inst vars'
Cheers,
-- Scott
On Jun 4, 2007, at 10:40 AM, subbukk wrote:
BTW, I used the code below to inspect classes with explicit CIVs:
(Smalltalk
Hi list,
I experimented with Magma objects in a Workspace window. Unfortunately,
after destroying this window several objects still exists and they are
invoked at the startup (just after or while the image is loaded) with
#startUp: message. I'd be very happy to remove some of these objects
from
On Tuesday 05 June 2007 1:21 am, Bert Freudenberg wrote:
class (instance variable) - instance variable of the class
(treated as an
object and therefore visible only to its methods and methods in its
subclasses).
I don't think that is correct - what do you mean by treated as an
object?
16 matches
Mail list logo
