Andrew Tween | 1 May 01:18
Picon

Re: [ANN] FreeType Plus release

Hi Brad,
----- Original Message ----- 
From: "Brad Fuller" <brad <at> bradfuller.com>
To: "The general-purpose Squeak developers list"
<squeak-dev <at> lists.squeakfoundation.org>
Sent: Monday, April 30, 2007 11:46 PM
Subject: Re: [ANN] FreeType Plus release

> Andrew Tween wrote:
> >>> All the menus really need re-working to provide nice scrolling lists.
> >>>
> >> Hmm, I'd say "to not need to scroll nor page in the first place" :)
> >>
> > :)
> > Do you have any ideas on how that could be done?
> > If, for instance, you had 999 fonts?
> >
> > A fisheye, everything tiny, until you hover over it view?
> > Or typing the font name to bring up matches?
> >
> > I'm curious
> >
> Could use cascading menus. based on mfr, or type/kind, or even alphabetical

Those are all good ideas.

But, wouldn't scrolling still be needed, at some point?
If you had 999 fonts beginning with 'A'.
Or, 999 Sans Serif fonts.
Or maybe, not that many fonts, but a small screen resolution (640x480).
(Continue reading)

Brad Fuller | 1 May 02:13

Re: [ANN] FreeType Plus release

Andrew Tween wrote:
> Hi Brad,
> ----- Original Message ----- 
> From: "Brad Fuller" <brad <at> bradfuller.com>
> To: "The general-purpose Squeak developers list"
> <squeak-dev <at> lists.squeakfoundation.org>
> Sent: Monday, April 30, 2007 11:46 PM
> Subject: Re: [ANN] FreeType Plus release
>
>
>   
>> Andrew Tween wrote:
>>     
>>>>> All the menus really need re-working to provide nice scrolling lists.
>>>>>
>>>>>           
>>>> Hmm, I'd say "to not need to scroll nor page in the first place" :)
>>>>
>>>>         
>>> :)
>>> Do you have any ideas on how that could be done?
>>> If, for instance, you had 999 fonts?
>>>
>>> A fisheye, everything tiny, until you hover over it view?
>>> Or typing the font name to bring up matches?
>>>
>>> I'm curious
>>>
>>>       
>> Could use cascading menus. based on mfr, or type/kind, or even alphabetical
(Continue reading)

Brad Fuller | 1 May 02:20

Re: [ANN] FreeType Plus release

Brad Fuller wrote:
> Andrew Tween wrote:
>   
>> Hi Brad,
>> ----- Original Message ----- 
>> From: "Brad Fuller" <brad <at> bradfuller.com>
>> To: "The general-purpose Squeak developers list"
>> <squeak-dev <at> lists.squeakfoundation.org>
>> Sent: Monday, April 30, 2007 11:46 PM
>> Subject: Re: [ANN] FreeType Plus release
>>
>>
>>   
>>     
>>> Andrew Tween wrote:
>>>     
>>>       
>>>>>> All the menus really need re-working to provide nice scrolling lists.
>>>>>>
>>>>>>           
>>>>>>             
>>>>> Hmm, I'd say "to not need to scroll nor page in the first place" :)
>>>>>
>>>>>         
>>>>>           
>>>> :)
>>>> Do you have any ideas on how that could be done?
>>>> If, for instance, you had 999 fonts?
>>>>
>>>> A fisheye, everything tiny, until you hover over it view?
(Continue reading)

Andrew Tween | 1 May 02:44
Picon

Re: [ANN] FreeType Plus release

Hi Brad,
> Oh.. forgot to add the obvious: change page dn/up to arrows above and
> below the menu. Hover over either and it automatically scrolls in that
> direction. That would at least make it easier for people to browse.

good idea.

> The
> problem, I think, is it takes a while to render the next "set" of font
> names. Right? Seems so on my system (which is slow with a lot of fonts.)
> So, you could have the rendered list before the request.

Yes. It is slow.
Sophie caches a bitmap of each font  and renders that instead of loading the
font through Freetype.and rendering the text.
Something similar is needed to speed things up.

Cheers,
Andy

Andrew Tween | 1 May 02:51
Picon

Re: [ANN] FreeType Plus release

Hi Brad,
> Some alternative ideas:
> * Category Based:
>  - Cascading Lists: (http://designinginterfaces.com/Cascading_Lists)
>  - Closable Panels (http://designinginterfaces.com/Closable_Panels)
> (which is similar to the tree-table)
>
> * Helpful navigation builtin to the selection:
>  - Jump (http://designinginterfaces.com/Jump_to_Item)
>
> *Alternative Selection:
>  - Create a "My Fonts" selection that contains either the fonts the user
> has selected recently, or ones that he selected manually to be in the My
> Fonts set.
>
> * Show All - I've seen menus where ALL the font names are shown. Takes
> up the whole freakin' screen. Scary, but you see them all.

These are all great ideas.
I look forward to seeing your implementations of them in Squeak ;)

(I'll do something with the font menus myself. Eventually. But if anyone doesn't
want to wait for 6-12 months to see some results, then dive in and have a go at
writing the interface that you would like to see).

Cheers,
Andy

David Griswold | 1 May 03:05

ESUG SummerTalk 2007 Strongtalk project

Hi everyone.

ESUG has graciously offered to fund a student to help with the Strongtalk
project as part of the SummerTalk 2007 program (thanks Stephane).
SummerTalk will pay the student 1500 euros for this work.   I will be acting
as mentor for this project.

While there are various possibilities for this project, I will be starting
to work on porting Squeak to the Strongtalk VM, and ideally I would like to
find someone who wants to work with me on that.    This will entail diving
deeply into the Squeak and Strongtalk VM interfaces, and figuring out how to
adapt the Squeak image so that it will boot off the Strongtalk VM.  This
ought to be a very interesting tour through the guts of two very interesting
systems.  If the port turns out to be too large a job, there are subtasks
that can be fairly easily defined, such as setting up the Strongtalk system
for re-bootstrapping, which is a necessary step.

Of course, there are other possibilities if that doesn't sound interesting
or if your talents lie in other areas.   For example, there is work in
progress on porting the Strongtalk VM to Linux and MacOS that is a high
priority for the Strongtalk project.

Please contact me if you are registered or if you know someone who might be
interested, at David.takeThisPartOut.Griswold.at.acm.org

- Dave

Milan Zimmermann | 1 May 06:00
Picon
Favicon

[OT] interaction devices {was: Re: Held an OLPC laptop today!]

Alejandro, Cees,

Thanks for suggestions. I have been long postponing to get a tablet, and the 
multitouch screen is very interesting. But I have to say I came to conclusion 
that any device that does not give 3 dimensional feedback, such as "grow a 
handle" (literally) when I want to grab it, or give a physical 3D touch feel 
(sort of vr gloves) is probably not the right direction.  I want to "grab" 
things, not "touch" them on a flat background. But I realize that may be a 
long wait, and good touch-type devices is a good solution. (I think even the 
first writing tools were 3 dimensional in a way - making grooves in clay as 
opposed to writing on flat papyrus)

Bret mentioned that next generation of the laptop may have a touch screen 
which will be great.

Milan
On 2007 April 30 08:22, Alejandro F. Reimondo wrote:
> Hi,
>
> >> One thing I realized trying to build a quick presentation, is that we
> >> really
> >> need a different interface then the mouse pad or mouse.
>
> One alternative is to make a device by yourself.
> We are working on self made devices to do multitouch interaction.
> There is some pages on my work
>  at http://www.aleReimondo.com.ar/MultiTouch
>  most of the explanations are in spanish in my workspace
>  but videos and photos on how to build a device yourself
>  can be understood...
(Continue reading)

Michael Perscheid | 1 May 09:07
Picon
Picon

RE: converting arrow to ':=' for assignment in squeak 3.9

Hi ---,

the simplest solution is
1. Open preference browser
2. Search for ':='
3. Switch the Button from syntaxHighligthingAsYouTypeLeftArrowAssignment to
syntaxHighligthingAsYouTypeAnsiAssignment

Regards,
Michael

> -----Ursprüngliche Nachricht-----
> Von: squeak-dev-bounces <at> lists.squeakfoundation.org [mailto:squeak-dev-
> bounces <at> lists.squeakfoundation.org] Im Auftrag von Philippe Marschall
> Gesendet: Montag, 30. April 2007 22:36
> An: The general-purpose Squeak developers list
> Betreff: Re: converting arrow to ':=' for assignment in squeak 3.9
> 
> 2007/4/30, Ralph Boland <rpboland <at> gmail.com>:
> > I am currently converting my squeak project from Squeak 3.8 to Squeak
> 3.9.
> > (Thanks by the way to the people who helped me installSqueak 3.9 in
> Linux.
> > Note that commands  'man squeak'  and  'man inisqueak'
> > still reports the existence of a  command 'inisqueak'
> > even though the command is not to be found.)
> >
> > My understanding was that as of 3.9  Squeak no longer supports use of
> the
> > arrow
(Continue reading)

Lukas Renggli | 1 May 09:15
Picon
Gravatar

Re: converting arrow to ':=' for assignment in squeak 3.9

What I did for Magritte, Pier, Seaside, Scriptaculous and many other
packages was:

      FixUnderscores fixPackage: 'Magritte'

This fixes all the assignments automatically and opens up an editor on
methods that couldn't be automatically fixed. It is a matter of
minutes to even clean up huge projects.

Cheers,
Lukas

--

-- 
Lukas Renggli
http://www.lukas-renggli.ch

Andrew P. Black | 1 May 09:33
Picon
Gravatar

Re: Another stupid Morphic Question

Thanks for your help Tom.  I am making progress, but I'm not there yet.

Brad: I'm not talking about the Halo operations, which work fine.  What I want to do is make the circles behave on redButtonPressed just as if I were using the "move" halo button.  This is the default behavior when the circle is in the World.

The key phrase was: "If handlesMouseDown: answers false, that means that your object
doesn't handle mouse down events, _so somebody else has to decide how
to handle them_".  So by setting handlesMouseDown to false, I was making the morph react to mouse down, which is a bit counter-intuitive.  The way to make it _not_ respond to mouse down is to have handlesMouseDown: answer true, but to have a mouseDown: evt method that does nothing.  Or maybe it should do 
evt wasHandled: true.

OK, so the converse is true.  if I want my circles to handle Mouse Down, then they need to answer true to handlesMouseDown: (that's easy), and then there needs to be a mouseDown: evt method that does the "right thing".  However, the right thing is very complicated!  I tried the following, based on Tom's code:


mouseDown: evt
evt redButtonPressed
ifTrue: ["pick it up"
evt wasHandled: true.
self removeHalo.
^ evt hand grabMorph: self from: owner]

but this glues the morph to the hand, and I have to click again (rather than releasing the red button) to drop it.  Once dropped, the circle is no longer embedded in its (former) owner.

I could probably find all of the bits of code that I need, to handle mouse move and so on, taking care of the offset between mouse click event and the origin of the Morph that I'm moving — most of the code must be in HaloMorph.  But this was the Default Behavior of the circle before I embedded it in the rectangle — surely there must be an easier way to get that default behavior back, other than duplicating the code from whereever it is hidden!

Andrew

Andrew P. Black
Department of Computer Science
Portland State University
+1 503 725 2411





Gmane