November 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Postdoc position: security in dynamic languages
by StÃ©phane Ducasse Nov. 26, 2011

Nov. 26, 2011

Postdoc Position â¢ Duration: 3 years â¢ Starting date: end 2011 â¢ Where: RMOD team at INRIA Lille Nord Europe http://rmod.lille.inria.fr â¢ Salary: 55 Keuros net (before taxes) Keywords: dynamic languages, security, information flow, Smalltalk, Javascript The position will take place in the context of the Systematic Resilience project. We will focus on the following main tasks: â¢ Identification and understanding of security problems in Javascript and other dynamic languages â¢ Study and analyze existing approaches towards securing Javascript (Caja, isolates...) â¢ Comparison of different approaches to secure dynamic applications (Zope model, ZTK), Ruby â¢ Study of Mirrors/Capabilities as a basis for security in Javascript â¢ Proposition of an safe architecture for Resilience Please contact Stephane Ducasse (Stephane.Ducasse(a)inria.fr) for more information. http://rmod.lille.inria.fr/ http://stephane.ducasse.free.fr

1 0

[Pharo-project] Font lookup using styleName?
by Bernhard Pieber Nov. 26, 2011

Nov. 26, 2011

Hi everyone, I am using Pharo 1.3 and I am quite a newbie when it comes to Pharo so please be kind... I saw in the font chooser that Pharo supports font families with multiple styles. On my Mac for instance the font family Helvetica has the styles Light, Light Oblique, Regular, Oblique, Bold, and Bold Oblique. In the code font families are subinstances of FontFamilyAbstract and styles are subinstances of FontFamilyMemberAbstract. However, for creating fonts programmatically there seems to be no message which takes the style into account. There is LogicalFont class>>#familyName:pointSize:. How do I know which of the styles this uses? Then there is LogicalFont class>>#familyName:fallbackFamilyNames:pointSize:stretchValue:weightValue:slantValue:. How should I know which parameters I have to pass in to get a certain style? I would have expected a method like #familyName:styleName:pointSize: but I did not find one. Any idea why? Is this an omission or a feature? Cheers, Bernhard

3 4

Re: [Pharo-project] deprecated: in Deprecated14
by Marcus Denker Nov. 25, 2011

Nov. 25, 2011

On Nov 25, 2011, at 11:53 AM, Pavel Krivanek wrote: > Hi, > > I would like to ask if the current solution where the method > Object>>#deprecated: is placed in the package Deprecated14, is good. I think the idea was to deprecate deprecated: so people use the one with more infos... (deprecated:on:in:) But for small external projects, deprecated: is just fine and there are users. So I suggest we just move it out of the deprecated package and have it as a simple to use version of deprecation tagging. > For images where this package is not present (e.g. Pharo-Kernel) we > got unimplemented call and possible DNU. The method > #deprecated:on:in: is in the kernel. > > Of course if you do not have deprecated code in the image then call of > it should raise error. However some external packages (and some > internal packages like Zinc) do not have deprecated code in separate > package and do use #deprecated: for deprecation warnings. > > Because #deprecated: is bound to Pharo version, I think it would be > better solution to have a message named pharoDeprecated: that will be > called from Pharo packages that will be placed in Deprecated14 package > and then have #deprecated: message placed in the kernel that will be > used by external packages. > > Cheers, > -- Pavel > -- Marcus Denker -- http://marcusdenker.de

4 3

[Pharo-project] [update 1.4] #14238
by Marcus Denker Nov. 25, 2011

Nov. 25, 2011

14238 ----- Issue 4998: ContextPart>>#runUntilErrorOrReturnFrom: (for testing) http://code.google.com/p/pharo/issues/detail?id=4998 Issue 4994: Two failing test in ProcessTest http://code.google.com/p/pharo/issues/detail?id=4994 Issue 5014: zn updates http://code.google.com/p/pharo/issues/detail?id=5014 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] VM Exit Value
by Sven Van Caekenberghe Nov. 25, 2011

Nov. 25, 2011

Hi, For scripting purposes, I would like to use/control the VM exit status/value (on Linux). There is SmalltalkImage>>#snapshot:andQuit: but there is nothing there that indicates that one can set the process exit status. Is there a way to do that ? Has anyone a good idea on how the CogVM could communicate back to its invoking script whether is ran OK or not ? Thx, Sven

4 10

[Pharo-project] [update 1.4] #14237
by Marcus Denker Nov. 25, 2011

Nov. 25, 2011

14237 ----- Issue 5010: Testing GUI widgets http://code.google.com/p/pharo/issues/detail?id=5010 Issue 5027: rename _log.txt to PharoDebug.log http://code.google.com/p/pharo/issues/detail?id=5027 Issue 5026: update Pharo-Kernel and Pharo-Core package sets http://code.google.com/p/pharo/issues/detail?id=5026 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Building 32-bit Cairo library on Macs
by Igor Stasenko Nov. 25, 2011

Nov. 25, 2011

Hello, i'd like to know, if there's anyone who can help with making 32-bit version of cairo library on macs? Because if i just do: port install cairo everything is ok, except that VM cannot use that library because it is 64bit.. And if i set build_arch to "i386" in /opt/local/etc/macports/macports.conf and run it, it also doesn't going well (see the end of mail), because of having too much dependecies from libraries which already installed and 64-bit :( Is there a way to tell port to just build stuff in a separate place.. or is there a way to build cairo library without port? sudo port install cairo Warning: port definitions are more than two weeks old, consider using selfupdate ---> Fetching pkgconfig ---> Attempting to fetch pkg-config-0.25.tar.gz from http://lil.fr.distfiles.macports.org/pkgconfig ---> Verifying checksum(s) for pkgconfig ---> Extracting pkgconfig ---> Applying patches to pkgconfig ---> Configuring pkgconfig ---> Building pkgconfig ---> Staging pkgconfig into destroot ---> Installing pkgconfig @0.25_1 ---> Deactivating pkgconfig @0.23_1 ---> Activating pkgconfig @0.25_1 ---> Cleaning pkgconfig ---> Fetching libpixman ---> Attempting to fetch pixman-0.20.0.tar.bz2 from http://lil.fr.distfiles.macports.org/libpixman ---> Verifying checksum(s) for libpixman ---> Extracting libpixman ---> Configuring libpixman ---> Building libpixman ---> Staging libpixman into destroot ---> Installing libpixman @0.20.0_0 ---> Deactivating libpixman @0.16.4_0 ---> Activating libpixman @0.20.0_0 ---> Cleaning libpixman ---> Fetching xorg-util-macros ---> Attempting to fetch util-macros-1.11.0.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-util-macros ---> Verifying checksum(s) for xorg-util-macros ---> Extracting xorg-util-macros ---> Configuring xorg-util-macros ---> Building xorg-util-macros ---> Staging xorg-util-macros into destroot ---> Installing xorg-util-macros @1.11.0_0 ---> Deactivating xorg-util-macros @1.5.0_0 ---> Activating xorg-util-macros @1.11.0_0 ---> Cleaning xorg-util-macros ---> Fetching xorg-xtrans ---> Attempting to fetch xtrans-1.2.6.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-xtrans ---> Verifying checksum(s) for xorg-xtrans ---> Extracting xorg-xtrans ---> Configuring xorg-xtrans ---> Building xorg-xtrans ---> Staging xorg-xtrans into destroot ---> Installing xorg-xtrans @1.2.6_0 ---> Deactivating xorg-xtrans @1.2.5_0 ---> Activating xorg-xtrans @1.2.6_0 ---> Cleaning xorg-xtrans ---> Fetching xorg-bigreqsproto ---> Attempting to fetch bigreqsproto-1.1.1.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-bigreqsproto ---> Verifying checksum(s) for xorg-bigreqsproto ---> Extracting xorg-bigreqsproto ---> Configuring xorg-bigreqsproto ---> Building xorg-bigreqsproto ---> Staging xorg-bigreqsproto into destroot ---> Installing xorg-bigreqsproto @1.1.1_0 ---> Deactivating xorg-bigreqsproto @1.1.0_0 ---> Activating xorg-bigreqsproto @1.1.1_0 ---> Cleaning xorg-bigreqsproto ---> Fetching xorg-xcmiscproto ---> Attempting to fetch xcmiscproto-1.2.1.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-xcmiscproto ---> Verifying checksum(s) for xorg-xcmiscproto ---> Extracting xorg-xcmiscproto ---> Configuring xorg-xcmiscproto ---> Building xorg-xcmiscproto ---> Staging xorg-xcmiscproto into destroot ---> Installing xorg-xcmiscproto @1.2.1_0 ---> Deactivating xorg-xcmiscproto @1.2.0_0 ---> Activating xorg-xcmiscproto @1.2.1_0 ---> Cleaning xorg-xcmiscproto ---> Fetching xorg-xextproto ---> Attempting to fetch xextproto-7.1.2.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-xextproto ---> Verifying checksum(s) for xorg-xextproto ---> Extracting xorg-xextproto ---> Configuring xorg-xextproto ---> Building xorg-xextproto ---> Staging xorg-xextproto into destroot ---> Installing xorg-xextproto @7.1.2_0 ---> Deactivating xorg-xextproto @7.1.1_0 ---> Activating xorg-xextproto @7.1.2_0 ---> Cleaning xorg-xextproto ---> Fetching xorg-inputproto ---> Attempting to fetch inputproto-2.0.1.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-inputproto ---> Verifying checksum(s) for xorg-inputproto ---> Extracting xorg-inputproto ---> Configuring xorg-inputproto ---> Building xorg-inputproto ---> Staging xorg-inputproto into destroot ---> Installing xorg-inputproto @2.0.1_0 ---> Deactivating xorg-inputproto @2.0_0 ---> Activating xorg-inputproto @2.0.1_0 ---> Cleaning xorg-inputproto ---> Fetching xorg-xproto ---> Attempting to fetch xproto-7.0.20.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-xproto ---> Verifying checksum(s) for xorg-xproto ---> Extracting xorg-xproto ---> Configuring xorg-xproto ---> Building xorg-xproto ---> Staging xorg-xproto into destroot ---> Installing xorg-xproto @7.0.20_0 ---> Deactivating xorg-xproto @7.0.16_0 ---> Activating xorg-xproto @7.0.20_0 ---> Cleaning xorg-xproto ---> Computing dependencies for xorg-libXdmcp ---> Fetching xorg-libXdmcp ---> Attempting to fetch libXdmcp-1.1.0.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-libXdmcp ---> Verifying checksum(s) for xorg-libXdmcp ---> Extracting xorg-libXdmcp ---> Configuring xorg-libXdmcp ---> Building xorg-libXdmcp ---> Staging xorg-libXdmcp into destroot ---> Computing dependencies for xorg-libXdmcp ---> Installing xorg-libXdmcp @1.1.0_0 ---> Deactivating xorg-libXdmcp @1.0.3_0 ---> Activating xorg-libXdmcp @1.1.0_0 ---> Cleaning xorg-libXdmcp ---> Computing dependencies for xorg-libXau ---> Fetching xorg-libXau ---> Attempting to fetch libXau-1.0.6.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-libXau ---> Verifying checksum(s) for xorg-libXau ---> Extracting xorg-libXau ---> Configuring xorg-libXau ---> Building xorg-libXau ---> Staging xorg-libXau into destroot ---> Computing dependencies for xorg-libXau ---> Installing xorg-libXau @1.0.6_0 ---> Deactivating xorg-libXau @1.0.5_0 ---> Activating xorg-libXau @1.0.6_0 ---> Cleaning xorg-libXau ---> Computing dependencies for libxml2 ---> Dependencies to be installed: libiconv zlib ---> Fetching libxml2 ---> Attempting to fetch libxml2-2.7.8.tar.gz from http://lil.fr.distfiles.macports.org/libxml2 ---> Verifying checksum(s) for libxml2 ---> Extracting libxml2 ---> Configuring libxml2 Error: You cannot install libxml2 for the architecture(s) i386 because Error: its dependency libiconv only contains the architecture(s) x86_64. Error: Error: Did you upgrade to a new version of Mac OS X? If so, please see Error: Error: http://trac.macports.org/wiki/Migration Error: Error: Target org.macports.configure returned: incompatible architectures in dependencies Log for libxml2 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libxml2/main.log Error: Unable to upgrade port: 1 Error: Unable to execute port: upgrade xrender failed To report a bug, see <http://guide.macports.org/#project.tickets> -- Best regards, Igor Stasenko.

8 24

[Pharo-project] [update 1.4] #14237
by Marcus Denker Nov. 25, 2011

Nov. 25, 2011

14237 ----- Issue 5010: Testing GUI widgets http://code.google.com/p/pharo/issues/detail?id=5010 Issue 5027: rename _log.txt to PharoDebug.log http://code.google.com/p/pharo/issues/detail?id=5027 Issue 5026: update Pharo-Kernel and Pharo-Core package sets http://code.google.com/p/pharo/issues/detail?id=5026 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Issue 5028: failing MCPackageManager initialization
by Pavel Krivanek Nov. 25, 2011

Nov. 25, 2011

http://code.google.com/p/pharo/issues/detail?id=5028 MCPackageManager class >> #initialize contains unimplemented call of #unregisterForNotifications so Monticello cannot be loaded to a fresh image. This method is no more present in the image. Does anyone know why it was removed? It seems to be related to same changes done by Stef. -- Pavel

2 1

[Pharo-project] deprecated: in Deprecated14
by Pavel Krivanek Nov. 25, 2011

Nov. 25, 2011

Hi, I would like to ask if the current solution where the method Object>>#deprecated: is placed in the package Deprecated14, is good. For images where this package is not present (e.g. Pharo-Kernel) we got unimplemented call and possible DNU. The method #deprecated:on:in: is in the kernel. Of course if you do not have deprecated code in the image then call of it should raise error. However some external packages (and some internal packages like Zinc) do not have deprecated code in separate package and do use #deprecated: for deprecation warnings. Because #deprecated: is bound to Pharo version, I think it would be better solution to have a message named pharoDeprecated: that will be called from Pharo packages that will be placed in Deprecated14 package and then have #deprecated: message placed in the kernel that will be used by external packages. Cheers, -- Pavel

1 0