- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Vm-dev] Re: The roadmap aka fight plan to make image control host window

by Fernando Olivero

thanks for the info igor. maybe we could plug customized UI handlers for different devices, with different "raw" events. It would make coding and managing each of them, a lot simpler than now. Fernando On Wed, Sep 26, 2012 at 2:14 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 26 September 2012 13:12, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: >> Igor, i agree 100% percent with you! >> >> VM shouldn't have all the responsibility of handling a "single UI window". >> >> I've tried in the past to look at VM code, which handles this >> responsibility and change it, (no UI handling in the VM) ..but it >> proved to be a difficult task! We need a simpler, >> cleaner VM, pluggable UI handling would be awesome!. >> >> Do we need the pointer or Null at all in the VM? Cant the io handling >> be done completely separate from the VM? A native app for each >> platform, or something built using NB. >> > > This is highly platform-specific. > The ioProcessEvents called by VM during interrupt , so, > platform-specific code can > use it to signal any pending external events. > Interrupts is also used by scheduler to switch to another process when > something happens (like socket has new data to read, semaphore > signaled etc). > So, if VM won't support interrupts it will be highly problematic to > support green threading execution model. > And, of course, an interrupt is naturally a well-defined safe point in > VM execution. > So it is logical to have an entry point there, where plugin(s) can > hook-in and add own custom event handling procedure, > without need for patching a single global ioProcessEvents() function > over and over again. > > If at some point you'll have two independent modules (plugins) in VM > which want to put own custom handling code there, > you can always do it like following pseudocode: > > (during plugin initialization) > oldHandler := ioProcessEvents. > ioProcessEvents := &myHandler. > > (during call ) > myHandler > self doMyHandling. > call oldHandler > > > Now, of course it is a question, how often you may need that: a module > which adds own custom handler for VM interrupt. > Maybe we don't need that much flexibility? But do others see other way > of freeing VM from assumptions and tight coupling with > different parts of system? > > -- > Best regards, > Igor Stasenko.

Sept. 27, 2012

Re: [Pharo-project] Learnable Programming

by Goubier Thierry

It's a bit out of subject, but does Athens works on a Linux 64bits system ? Thierry Le 27/09/2012 09:59, StÃ©phane Ducasse a Ã©crit : > Indeed the key point for our community is how can we create the infrastructure to > be able to provide nice output and interactive. > > This is why Athens needs clients. > Now if nobody cares about Athens then it will get out slower than we want. > > Beside the text everything else is working. > I'm trying to understand how I can help igor and one task is to convert the current morph drawOn: on athensDrawOn: method. > I will keep the examples we will produce once I will sit with igor. > > Stef > > > On Sep 27, 2012, at 9:22 AM, Goubier Thierry wrote: > >> Cool! >> >> There are some very nice program flow representations in them. I'll have a look if I can display Jejak traces that way, and maybe explore the use of Roassal for this. >> >> Thierry >> >> Le 26/09/2012 21:59, Sven Van Caekenberghe a Ã©crit : >>> This is _very_ interesting and _very_ welll presented: >>> >>> http://worrydream.com/LearnableProgramming/ >>> >>> Keep on reading, it keeps on getting better towards the end. >>> >>> Sven >>> >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill >>> >>> >>> >> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 27, 2012

Re: [Pharo-project] Learnable Programming

by StÃ©phane Ducasse

Indeed the key point for our community is how can we create the infrastructure to be able to provide nice output and interactive. This is why Athens needs clients. Now if nobody cares about Athens then it will get out slower than we want. Beside the text everything else is working. I'm trying to understand how I can help igor and one task is to convert the current morph drawOn: on athensDrawOn: method. I will keep the examples we will produce once I will sit with igor. Stef On Sep 27, 2012, at 9:22 AM, Goubier Thierry wrote: > Cool! > > There are some very nice program flow representations in them. I'll have a look if I can display Jejak traces that way, and maybe explore the use of Roassal for this. > > Thierry > > Le 26/09/2012 21:59, Sven Van Caekenberghe a Ã©crit : >> This is _very_ interesting and _very_ welll presented: >> >> http://worrydream.com/LearnableProgramming/ >> >> Keep on reading, it keeps on getting better towards the end. >> >> Sven >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >> > > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Sept. 27, 2012

[Pharo-project] Welcome to newcomers

by StÃ©phane Ducasse

Hi guys Since there are regularly new comers, here is a little ad-hoc welcome message :). First: Welcome! welcome and welcome Second: our goal is to create an ecosystem around pharo: if you need material to teach, if you have idea or needs for business or anything else just let us know. Our goal is to be able to reinvent our system and at the same time make sure that we can all create wealth at all levels. Third: we are working hard to get our vision: a nice, little and powerful reflective system. If you want to understand what we are doing please read the document Pharo vision on http://www.pharo-project.org/community/consortium You will understand our current effort. Four: you can get an impact on Pharo :) There are a lot of different ways to contribute. - feedback - bugs idea for enhancements see http://code.google.com/p/pharo/issues/list - book participation (we are working on deep into pharo http://rmod.lille.inria.fr/pbe2/ - translation - adding comments - building great stuff - using packagesâ¦. So welcome. Stef PS: Pharo is not the end, Pharo is the mean to create a powerful clean, lean system with a great community.

Sept. 27, 2012

Re: [Pharo-project] Learnable Programming

by Goubier Thierry

Cool! There are some very nice program flow representations in them. I'll have a look if I can display Jejak traces that way, and maybe explore the use of Roassal for this. Thierry Le 26/09/2012 21:59, Sven Van Caekenberghe a Ã©crit : > This is _very_ interesting and _very_ welll presented: > > http://worrydream.com/LearnableProgramming/ > > Keep on reading, it keeps on getting better towards the end. > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 27, 2012

Re: [Pharo-project] vm download site

by Camillo Bruni

On 2012-09-26, at 22:44, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 26 September 2012 20:42, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> http://pharo.gforge.inria.fr/ci/vm/mac >> http://pharo.gforge.inria.fr/ci/vm/linux >> >> and once we fixed the win builds >> http://pharo.gforge.inria.fr/ci/vm/mac/win >> > this url doesn't looks right. Perhaps you meant > > http://pharo.gforge.inria.fr/ci/vm/win yes of course :) the mac/win platform is yet to be invented :P

Sept. 27, 2012

Re: [Pharo-project] Workspace>>#theme

by Camillo Bruni

The workspace has been taken out of the StringHolder hierarchy with a bit too little love ;) https://code.google.com/p/pharo/issues/detail?id=6717 On 2012-09-26, at 22:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Clicking the window menu of a Workspace in 20308 gives a MNU Workspace>>#theme in Workspace>>#addModelItemsToWindowMenu: > > Maybe Workspace subclassing from Object is the problem ? > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > >

Sept. 27, 2012

Re: [Pharo-project] [Vm-dev] Re: No GUI on MacOSX 10.5.8 using Cocoa VM

by Yanni Chiu

On 26/09/12 11:07 AM, Yanni Chiu wrote: > > I'll try a bit more to get it to work on 10.5.8, now that I can build a VM. Okay, got it to work! Three changes: 1. SqueakOSXAppDelegate.h - use NSObject instead ofNSApplicationDelegate 2. sqSqueakOSXScreenAndWindow.h - use NSObject instead of NSWindowDelegate 3. SqueakOSXAppDelegate.m - use CoreGraphics instead of OpenGL //#ifndef USE_CORE_GRAPHICS //# import "sqSqueakOSXOpenGLView.h" //# define ContentViewClass sqSqueakOSXOpenGLView //#else # import "sqSqueakOSXCGView.h" # define ContentViewClass sqSqueakOSXCGView //#endif ==== Along the way, I found: Issue 5650: OneClick 1.4 can't be launched on MacOSX Mac Air 10.5.8 http://code.google.com/p/pharo/issues/detail?id=5650 While I agree that support for old OS releases should have a reasonable limit, I don't buy 10.5 dropped when 10.8 is around the corner is the right limit. My machine is circa 2009, just three years or so. Apple may have good reason to want to move the user/developer base off of 10.5, because of hardware (pad/phone) and UI native widget changes. In the Squeak/Pharo case, we just need a single window to draw in - that should hardly obsolete a three year old computer. I'll add this thread to the issue report (5650).

Sept. 26, 2012

Re: [Pharo-project] Roassal Survey

by Francois Stephany

On 26/09/12 15:19, Alexandre Bergel wrote: >>> Our todo list includes: >>> - book chapter on Roassal >> >> Maybe don't bother with that. Write short blog posts showing the stuff you can currently do with Roassal. And keep writing as the project evolves. >> >> I feel like the time a book is out, it's already outdated by the implementation. > > :-) > Well... My students are asking for a piece of documentation. And in my opinion, book chapter are more read than blog :-) You're right, a book has probably more authority than a blog post. And its probably more perenial as well. But a blog post is more aligned with *my* way of consuming tech/programming/library/framework information :p

Sept. 26, 2012

Re: [Pharo-project] Roassal Survey

by Alexandre Bergel

>> Our todo list includes: >> - book chapter on Roassal > > Maybe don't bother with that. Write short blog posts showing the stuff you can currently do with Roassal. And keep writing as the project evolves. > > I feel like the time a book is out, it's already outdated by the implementation. :-) Well... My students are asking for a piece of documentation. And in my opinion, book chapter are more read than blog :-) Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 26, 2012