- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: How can the main window title in Squeak and Pharo be set?

by Torsten Bergmann

> I downloaded the NBCog.exe and was able to execute the 'NBWin32Window > getFocus setWindowText: 'Hello using Native Boost' example you showed > above. It looks me to like they are direct calls to the Windows API > which don't require any external DLLs other the built in Windows > ones.. Yes, as I wrote I just call SetWindowTextA() function from Windows API. see http://msdn.microsoft.com/en-us/library/windows/desktop/ms633546(v=vs.85).a… This one is in User32.dll which comes with Windows. Bye Torsten

Jan. 11, 2013

Re: [Pharo-project] SmalltalkHub upgrade

by Nicolas Petton

-- GÃ¶ran Krampe <goran(a)krampe.se> writes: > Hi Nicolas! > > On 01/11/2013 06:57 PM, Nicolas Petton wrote: >> Guys, >> >> SmalltalkHub just got upgraded to version 0.9. This version includes a > > Great! Just a few things: > > - The explore page, I presume it "only" shows some recents, right? I > mean, I though I could browse or see the full list of users/projects > etc, but AFAICT I can not yet? Exactly. If you read carefully, you'll see that this page is a preview only ;) > > - Is the idea to also offer "regular URLs" for some entry points? To > enable google indexing etc? Yes, the next upgrade will include static pages (with a redirection to the Amber pages if JavaScript is available). This way all projects will be indexed by search engines. Nico

Jan. 11, 2013

Re: [Pharo-project] SmalltalkHub upgrade

by Nicolas Petton

Indeed, this is missing in this version, but will be added back :) Nico Helene Bilbo <thereluctantprogrammer(a)fastmail.fm> writes: > Nice. > I remember in a previous version there had been the possibility to browse > the source code, not only the diff? Or do i just not find it any more? > Anyway this would be nice to have. > > > > -- > View this message in context: http://forum.world.st/SmalltalkHub-upgrade-tp4662977p4662999.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Nicolas Petton http://nicolas-petton.fr

Jan. 11, 2013

Re: [Pharo-project] SmalltalkHub upgrade

by Helene Bilbo

Nice. I remember in a previous version there had been the possibility to browse the source code, not only the diff? Or do i just not find it any more? Anyway this would be nice to have. -- View this message in context: http://forum.world.st/SmalltalkHub-upgrade-tp4662977p4662999.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 11, 2013

Re: [Pharo-project] [squeak-dev] Global variable lookup

by Bert Freudenberg

On 11.01.2013, at 11:19, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > On Fri, Jan 11, 2013 at 11:05 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> FYI, this is a code from Pharo, which we are did _right_ (of course >> from Pharo perspective ;) >> > +1. local variable definitions override explicitly imported variable definitions inherited variable definitions override "global" variable definitions. Yep. Thanks Igor, that looks more reasonable. >> But does the system automatically recompile importers of shared pools when bindings are added or removed from shared pools? At least Squeak does not. And this is an issue in the context of loading Monticello packages. With the VMMaker I refactored a lot of globals into shared p[ools when I decomposed ObjectMemory from the Interpreter hierarchy and added the Cogit hierarchy. I would have to manually recompile to get the references right on e.g. moving a variable from being a class variable of ObjectMemory into some shared pool, or on moving the variable from one shared pool to another. Let's fix it. - Bert - >> >> >> Class>>bindingOf: varName >> "Answer the binding of some variable resolved in the scope of the >> receiver, or nil >> if variable with such name is not defined" >> >> "The lookup recurses up to superclasses looking inside their class >> and shared pools, >> but not the environment, since two classes, even if they have >> ancestry relationship, >> could use different environments. >> That's why we doing an environment lookup only as a last step of symbol lookup >> and taking only the environment of receiver only, not any of it's >> superclass(es) " >> >> | aSymbol binding | >> aSymbol := varName asSymbol. >> >> ^ (self innerBindingOf: aSymbol) ifNil: [ >> self environment bindingOf: aSymbol >> ] >> >> >> Class>>innerBindingOf: aSymbol >> "Answer the binding of some variable resolved in the scope of the >> receiver, or one of its superclass >> but do not look up binding in receiver's environment. >> Use #bindingOf: for looking up the variable binding in a full scope, >> including receiver's environment" >> >> | binding | >> >> "First look in classVar dictionary." >> binding := self classPool bindingOf: aSymbol. >> binding ifNotNil: [^binding]. >> >> "Next look in shared pools." >> self sharedPools do: [:pool | >> | aBinding | >> aBinding := pool bindingOf: aSymbol. >> aBinding ifNotNil: [^aBinding ]. >> ]. >> >> superclass ifNotNil: [ >> ^ superclass innerBindingOf: aSymbol. >> ]. >> ^ nil >> >> >> On 11 January 2013 19:28, Bert Freudenberg <bert(a)freudenbergs.de> wrote: >> > bindingOf:environment: >> > > > -- > Best regards, > Igor Stasenko. > > > > > -- > best, > Eliot >

Jan. 11, 2013

Re: [Pharo-project] Fwd: How can the main window title in Squeak and Pharo be set?

by Eliot Miranda

On Fri, Jan 11, 2013 at 10:57 AM, Frank Church <vfclists(a)gmail.com> wrote: > On 11 January 2013 13:34, Torsten Bergmann <astares(a)gmx.de> wrote: > > From the history of Squeak and Pharo you can: > > > > 1. Squeak.exe (VM for Windows) was always able to set this using > > the Setting "WindowTitle" in Pharo.ini - see > > http://squeakvm.org/win32/settings.html > > > > This was implemented by Andreas Raab (maintainer of SqueakVM) > > > > 2. Later there was the idea in Squeak for a project > > called "Areithfa Ffenestri" that should add more > > support code to Squeak to allow access to the > > native window or open new ones: > > > > http://wiki.squeak.org/squeak/3862 > > > > This is a VM plugin that is not in all VM's and even after > > years AFAIK not fully implemented on all platforms. > > > > If it is available then you can do what Bert Freudenberg > > suggested here: > > > > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2013-January/167766.… > > > > Dont know if the Pharo VM maintainers added this plugin > > too. You have to ask Igor or Esteban. > > > > 3. While Squeak tries to stay platform independent and > > encapsulate platform dependent logic mostly into VM plugins > > to unify the access there is some other idea in Pharo now: > > > > With the growing need to easily access platform logic > > of the underlying OS or access external libraries written in > > other languages there is a new FFI plugin which is > > (since Pharo 2.0) will be included in the standard distribution. > > > > This new Foreign Function Interface (FFI) is called > > NativeBoost and will move more logic into Smalltalk > > itself. So you dont have to write/compile a plugin. > > > > You just need a VM with NativeBoost support (NBCog.exe on Windows) > > > > Using native Boost (when in Pharo 2.0) you can (already!) > > write: > > > > NBWin32Window getFocus setWindowText: 'Hello using Native Boost' > > > > to change the window title. Internally I just call the > > Windows Win32-API function "SetWindowTextA" using the > > window handle. > > > > If someone from other platforms implements an NBUnixWindow, > > NBMacWindow, NBRiscOSWindow, ... we can also implement a > > common interface class (NBPharoWindow for example). > > > > Hope this helps a little bit > > > > Bye > > T. > > > > I downloaded the NBCog.exe and was able to execute the 'NBWin32Window > getFocus setWindowText: 'Hello using Native Boost' example you showed > above. It looks me to like they are direct calls to the Windows API > which don't require any external DLLs other the built in Windows > ones.. > > However on Linux would that mean it may be necessary to use different > code for Gnome or KDE/Qt for instance, or use some other native or > crossplatform widgetset like Wx? > IIRC no. This is at the XLib level. See XStoreName/XSetTextProperty. -- best, Eliot

Jan. 11, 2013

Re: [Pharo-project] [squeak-dev] Global variable lookup

by Eliot Miranda

On Fri, Jan 11, 2013 at 11:05 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > FYI, this is a code from Pharo, which we are did _right_ (of course > from Pharo perspective ;) > +1. local variable definitions override explicitly imported variable definitions inherited variable definitions override "global" variable definitions. But does the system automatically recompile importers of shared pools when bindings are added or removed from shared pools? At least Squeak does not. And this is an issue in the context of loading Monticello packages. With the VMMaker I refactored a lot of globals into shared p[ools when I decomposed ObjectMemory from the Interpreter hierarchy and added the Cogit hierarchy. I would have to manually recompile to get the references right on e.g. moving a variable from being a class variable of ObjectMemory into some shared pool, or on moving the variable from one shared pool to another. > > Class>>bindingOf: varName > "Answer the binding of some variable resolved in the scope of the > receiver, or nil > if variable with such name is not defined" > > "The lookup recurses up to superclasses looking inside their class > and shared pools, > but not the environment, since two classes, even if they have > ancestry relationship, > could use different environments. > That's why we doing an environment lookup only as a last step of > symbol lookup > and taking only the environment of receiver only, not any of it's > superclass(es) " > > | aSymbol binding | > aSymbol := varName asSymbol. > > ^ (self innerBindingOf: aSymbol) ifNil: [ > self environment bindingOf: aSymbol > ] > > > Class>>innerBindingOf: aSymbol > "Answer the binding of some variable resolved in the scope of the > receiver, or one of its superclass > but do not look up binding in receiver's environment. > Use #bindingOf: for looking up the variable binding in a full > scope, > including receiver's environment" > > | binding | > > "First look in classVar dictionary." > binding := self classPool bindingOf: aSymbol. > binding ifNotNil: [^binding]. > > "Next look in shared pools." > self sharedPools do: [:pool | > | aBinding | > aBinding := pool bindingOf: aSymbol. > aBinding ifNotNil: [^aBinding ]. > ]. > > superclass ifNotNil: [ > ^ superclass innerBindingOf: aSymbol. > ]. > ^ nil > > > On 11 January 2013 19:28, Bert Freudenberg <bert(a)freudenbergs.de> wrote: > > bindingOf:environment: > > > > -- > Best regards, > Igor Stasenko. > > -- best, Eliot

Jan. 11, 2013

Re: [Pharo-project] Fwd: How can the main window title in Squeak and Pharo be set?

by Frank Church

On 11 January 2013 13:34, Torsten Bergmann <astares(a)gmx.de> wrote: > From the history of Squeak and Pharo you can: > > 1. Squeak.exe (VM for Windows) was always able to set this using > the Setting "WindowTitle" in Pharo.ini - see > http://squeakvm.org/win32/settings.html > > This was implemented by Andreas Raab (maintainer of SqueakVM) > > 2. Later there was the idea in Squeak for a project > called "Areithfa Ffenestri" that should add more > support code to Squeak to allow access to the > native window or open new ones: > > http://wiki.squeak.org/squeak/3862 > > This is a VM plugin that is not in all VM's and even after > years AFAIK not fully implemented on all platforms. > > If it is available then you can do what Bert Freudenberg > suggested here: > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2013-January/167766.… > > Dont know if the Pharo VM maintainers added this plugin > too. You have to ask Igor or Esteban. > > 3. While Squeak tries to stay platform independent and > encapsulate platform dependent logic mostly into VM plugins > to unify the access there is some other idea in Pharo now: > > With the growing need to easily access platform logic > of the underlying OS or access external libraries written in > other languages there is a new FFI plugin which is > (since Pharo 2.0) will be included in the standard distribution. > > This new Foreign Function Interface (FFI) is called > NativeBoost and will move more logic into Smalltalk > itself. So you dont have to write/compile a plugin. > > You just need a VM with NativeBoost support (NBCog.exe on Windows) > > Using native Boost (when in Pharo 2.0) you can (already!) > write: > > NBWin32Window getFocus setWindowText: 'Hello using Native Boost' > > to change the window title. Internally I just call the > Windows Win32-API function "SetWindowTextA" using the > window handle. > > If someone from other platforms implements an NBUnixWindow, > NBMacWindow, NBRiscOSWindow, ... we can also implement a > common interface class (NBPharoWindow for example). > > Hope this helps a little bit > > Bye > T. > I downloaded the NBCog.exe and was able to execute the 'NBWin32Window getFocus setWindowText: 'Hello using Native Boost' example you showed above. It looks me to like they are direct calls to the Windows API which don't require any external DLLs other the built in Windows ones.. However on Linux would that mean it may be necessary to use different code for Gnome or KDE/Qt for instance, or use some other native or crossplatform widgetset like Wx? -- Frank Church ======================= http://devblog.brahmancreations.com

Jan. 11, 2013

Re: [Pharo-project] SmalltalkHub upgrade

by GÃ¶ran Krampe

Hi Nicolas! On 01/11/2013 06:57 PM, Nicolas Petton wrote: > Guys, > > SmalltalkHub just got upgraded to version 0.9. This version includes a Great! Just a few things: - The explore page, I presume it "only" shows some recents, right? I mean, I though I could browse or see the full list of users/projects etc, but AFAICT I can not yet? - Is the idea to also offer "regular URLs" for some entry points? To enable google indexing etc? regards, GÃ¶ran

Jan. 11, 2013

Re: [Pharo-project] Fwd: How can the main window title in Squeak and Pharo be set?

by Eliot Miranda

On Fri, Jan 11, 2013 at 5:34 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > From the history of Squeak and Pharo you can: > > 1. Squeak.exe (VM for Windows) was always able to set this using > the Setting "WindowTitle" in Pharo.ini - see > http://squeakvm.org/win32/settings.html > > This was implemented by Andreas Raab (maintainer of SqueakVM) > > 2. Later there was the idea in Squeak for a project > called "Areithfa Ffenestri" that should add more > support code to Squeak to allow access to the > native window or open new ones: > > http://wiki.squeak.org/squeak/3862 > > This is a VM plugin that is not in all VM's and even after > years AFAIK not fully implemented on all platforms. > > If it is available then you can do what Bert Freudenberg > suggested here: > > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2013-January/167766.… > > Dont know if the Pharo VM maintainers added this plugin > too. You have to ask Igor or Esteban. > > 3. While Squeak tries to stay platform independent and > encapsulate platform dependent logic mostly into VM plugins > to unify the access there is some other idea in Pharo now: > > With the growing need to easily access platform logic > of the underlying OS or access external libraries written in > other languages there is a new FFI plugin which is > (since Pharo 2.0) will be included in the standard distribution. > > This new Foreign Function Interface (FFI) is called > NativeBoost and will move more logic into Smalltalk > itself. So you dont have to write/compile a plugin. > > You just need a VM with NativeBoost support (NBCog.exe on Windows) > > Using native Boost (when in Pharo 2.0) you can (already!) > write: > > NBWin32Window getFocus setWindowText: 'Hello using Native Boost' > > to change the window title. Internally I just call the > Windows Win32-API function "SetWindowTextA" using the > window handle. > > If someone from other platforms implements an NBUnixWindow, > NBMacWindow, NBRiscOSWindow, ... we can also implement a > common interface class (NBPharoWindow for example). > and an additional piece of history is that a number of plugins, including the HostWindowPlugin, were enhanced at Qwaq/Teleplace (now 3d ICC), in a cross-platform manner since we supported Mac and Windows initially and later had a linux prototype. The code for some of these enhanced plugins, including the HostWindowPlugin, was released along with Cog, which has an MIT license. So if you mine the COg branch you'll find code that can be folded back into trunk you'll get the enhanced functionality. For the Qwaq/Teleplace HostWindowPlugin that included setting the window title, repositioning and resizing the main window, querying its size, etc. > Hope this helps a little bit > +1. -- best, Eliot

Jan. 11, 2013