[squeak-dev] Fullscreen UI

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

[squeak-dev] Fullscreen UI

Udo Schneider
Hi,

I want to create a fullscreen UI on my own for learning/testing some
concepts (and no - I have no plans to do a fully featured UI). I neither
want to rely on Morphic nor MVC.

My idea is to simply "get" a form representing the Display and a Sensor
providing all the kbd/mouse events.

Where do I have to hook in? Any pointers?

CU,

Udo


Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Fullscreen UI

Edgar J. De Cleene



El 8/22/08 7:36 AM, "Udo Schneider" <[hidden email]> escribió:

> Hi,
>
> I want to create a fullscreen UI on my own for learning/testing some
> concepts (and no - I have no plans to do a fully featured UI). I neither
> want to rely on Morphic nor MVC.
>
> My idea is to simply "get" a form representing the Display and a Sensor
> providing all the kbd/mouse events.
>
> Where do I have to hook in? Any pointers?
>
> CU,
>
> Udo

Look at Form , Display, Sensor.
But you don't have a way to avoid MVC, Morphic, Tweak, GTK or some other
implemented or in development GUI.
At less you plan is made your own.

Edgar



Reply | Threaded
Open this post in threaded view
|

[squeak-dev] Re: Fullscreen UI

Udo Schneider
Edgar J. De Cleene wrote:
> Look at Form , Display, Sensor.
> But you don't have a way to avoid MVC, Morphic, Tweak, GTK or some other
> implemented or in development GUI.
> At less you plan is made your own.
Thanks for the pointers. Is it possible to create Projects with a
non-MVC/Morphic UI.

I'm just thinking of using the regular Morphic based tools to develop
something and then switch into a "MyUI" Project testing things out. Does
 this make sense?

CU,

Udo


Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Re: Fullscreen UI

Edgar J. De Cleene



El 8/22/08 9:49 AM, "Udo Schneider" <[hidden email]> escribió:

> Edgar J. De Cleene wrote:
>> Look at Form , Display, Sensor.
>> But you don't have a way to avoid MVC, Morphic, Tweak, GTK or some other
>> implemented or in development GUI.
>> At less you plan is made your own.
> Thanks for the pointers. Is it possible to create Projects with a
> non-MVC/Morphic UI.
>
> I'm just thinking of using the regular Morphic based tools to develop
> something and then switch into a "MyUI" Project testing things out. Does
>  this make sense?
>
> CU,
>
> Udo
>
Juan Vuletich have Morphic 3.0 , a next generation of Squeak UI with a very
simplified and nice Morphic.
Maybe you should look his later works.
Or very soon you could find in a iPhone near to you...


Edgar



Reply | Threaded
Open this post in threaded view
|

[squeak-dev] Re: Fullscreen UI

Udo Schneider
Edgar J. De Cleene wrote:
> Juan Vuletich have Morphic 3.0 , a next generation of Squeak UI with a very
> simplified and nice Morphic.
> Maybe you should look his later works.
Simplified Morphic sounds good as a starting point. I'll take a look at it.

> Or very soon you could find in a iPhone near to you...
Wasn't there some kind of restriction not allowing any VM on the iPhone.
Or does this only apply to non-jailBrocken iPhones?

CU,

Udo


Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Re: Fullscreen UI

Edgar J. De Cleene



El 8/22/08 10:08 AM, "Udo Schneider" <[hidden email]>
escribió:

> Wasn't there some kind of restriction not allowing any VM on the iPhone.
> Or does this only apply to non-jailBrocken iPhones?
>
> CU,
>
> Udo
John McIntosh have a iPhone VM and a Squeak 3.4 or a derivative of it
running.

Don't say nobody I tell this :=)

Edgar



Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Re: Fullscreen UI

Yoshiki Ohshima-2
In reply to this post by Udo Schneider
At Fri, 22 Aug 2008 14:49:01 +0200,
Udo Schneider wrote:

>
> Edgar J. De Cleene wrote:
> > Look at Form , Display, Sensor.
> > But you don't have a way to avoid MVC, Morphic, Tweak, GTK or some other
> > implemented or in development GUI.
> > At less you plan is made your own.
> Thanks for the pointers. Is it possible to create Projects with a
> non-MVC/Morphic UI.
>
> I'm just thinking of using the regular Morphic based tools to develop
> something and then switch into a "MyUI" Project testing things out. Does
>  this make sense?

  Yes, it does.  You certainly don' thave to try to hook your UI up
with the Projects and Processes, etc. at first.  Just define a method
at your new class that would look like:

doCycles

   [true] whileTrue: [
           self processEvents.  "handle user events and route them to widgets."
           self updateDisplay.  "write stuff to Display, with a proper
                                 fiddling of #deferUpdates:."
   ]

and from a Morphic workspace, execute:

m := MyUI new.
m doCycles.

Especially because it will be in full-screen, it just looks like a
native-fullscreen UI.

-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

[squeak-dev] Re: Fullscreen UI

Udo Schneider
Yoshiki Ohshima wrote:

>   Yes, it does.  You certainly don' thave to try to hook your UI up
> with the Projects and Processes, etc. at first.  Just define a method
> at your new class that would look like:
>
> doCycles
>
>    [true] whileTrue: [
>   self processEvents.  "handle user events and route them to widgets."
>   self updateDisplay.  "write stuff to Display, with a proper
>                         fiddling of #deferUpdates:."
>    ]
>
> and from a Morphic workspace, execute:
>
> m := MyUI new.
> m doCycles.
>
> Especially because it will be in full-screen, it just looks like a
> native-fullscreen UI.
Thanks for those pointers. I think I can see at least some light now.

Thanks,

Udo


Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Re: Fullscreen UI

Randal L. Schwartz
>>>>> "Udo" == Udo Schneider <[hidden email]> writes:

>> [true] whileTrue: [
>> self processEvents.  "handle user events and route them to widgets."
>> self updateDisplay.  "write stuff to Display, with a proper
>> fiddling of #deferUpdates:."
>> ]

[true] whileTrue: aBlock

is better written as:

aBlock repeat.

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<[hidden email]> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Re: Fullscreen UI

Yoshiki Ohshima-2
At Fri, 22 Aug 2008 15:56:04 -0700,
Randal L. Schwartz wrote:

>
> >>>>> "Udo" == Udo Schneider <[hidden email]> writes:
>
> >> [true] whileTrue: [
> >> self processEvents.  "handle user events and route them to widgets."
> >> self updateDisplay.  "write stuff to Display, with a proper
> >> fiddling of #deferUpdates:."
> >> ]
>
> [true] whileTrue: aBlock
>
> is better written as:
>
> aBlock repeat.

  Heh.  The idea behind it was that once he takes this way, soon he
wants to replace "true" with an instance variable and create a sort of
quit button to escape back to the hosting environment.

-- Yoshiki