- Pharo-dev - lists.pharo.org

[Pharo-project] Logos/Icons available

by StÃ©phane Ducasse

Hi all I released the logos and icons samuel sent me. https://gforge.inria.fr/frs/?group_id=1299 Stef

May 19, 2009

Re: [Pharo-project] MNU Error in Class Browser (Package Browser)

by Alexandr Batalshikov

Creating method OBTextSelection>>isClassNode ^false solve problem with Class Browser but I don't know how create appropriate patch in right way. / Alexander.

May 19, 2009

Re: [Pharo-project] Inspect it wrong shortcut

by Alexandr Batalshikov

On Windows XP with pharo0.1-10309dev09.05.3.image:Alt+i -- run Inspect Alt+Shift+i -- run Explore Ctrl+i -- also run Explore and changing any setting in section "keyboard" in Preference Browser no any effects for me. / Alexander 2009/5/18 Mariano Martinez Peck <marianopeck(a)gmail.com> > I am sorry. I was confuse, It is under Windows that happened to me, not > Linux. In Linux works ok. > > Anyone with Windows can confirm this ? > > thanks! > > Mariano > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

[Pharo-project] Win32Setup - custom VM and app tutorial

by Torsten Bergmann

Hi, there is now a ready made setup for installing pharo on windows. http://gforge.inria.fr/frs/download.php/22307/setup_pharo_0.0.0.1.exe It is available in the Win32 Setup section on http://gforge.inria.fr/frs/?group_id=1299 Far from perfect, but working. Use at your own risk! Additionally you will find a short tutorial below on how to build a custom Pharo VM and distribution for Win32 Systems. It can also help if you want to create a (commercial) application based on pharo. Have fun Torsten ----------------------------------------------------------------------------------------------- SECTION A - Building a Pharo windows VM ======================================= Since Pharo has its roots in Squeak Smalltalk the Squeak virtual machine is used. These steps allow you build a more "pharoized" virtual machine: - setup the tools environment for compiling the VM as described on [1] - grab the lates Squeak VM sources from [2], here we use the squeak 3.11.2 VM so we download "SqueakVM-Win32-3.11.2-src.zip" - extract it into a directory of your choice - make a parallel copy of directory winbuild and name it "pharobuild" - in the "pharobuild" directory -- delete the three *.ico files from squeak (squeak.ico, squeak2.ico and squeak3.ico) -- copy the pharo.ico file from [3] into the directory -- copy the splash.bmp file from [4] into the directory -- edit "Makefile" with a text editor and set the name of the new VM to "Pharo" in line 12 ("VM = Pharo"), note the uppercase -- rename the file "Squeak.def.in" into "Pharo.def.in" (note the uppercase) -- rename the file "Squeak.rc" into "Pharo.rc" (note the uppercase) -- edit "Pharo.rc" with a text editor and modify all 3 icon definitions to use "pharo.ico" now -- run "make" to build the VM -- you will now find a "Pharo.exe" (with the custom icon) and two external plugins ("FT2Plugin.dll" and "SqueakFFIPrims.dll") in the pharobuild\obj\vm directory SECTION B - Building a pharo distribution ========================================= - create a new directory "pharodist" - copy the "Pharo.exe", "FT2Plugin.dll" and "SqueakFFIPrims.dll" built in section A into this directory - also copy splash.bmp into this directory - download SqueakV39.sources.zip from [5] - extract the file "SqueakV39.sources" from this ZIP right into your "pharodist" directory (make sure you extract it exactly into this folder so you have a "pharodist/SqueakV39.sources" file - Download the latest pharo dev image (here we use pharo0.1-10309dev09.05.3.zip from [6]) and extract it into your "pharodist" directory - from this ZIP you should now extract the *.image file and the *.changes file into your "pharodist" directory (you should now have a "pharodist/pharo0.1-10309dev09.05.3.changes" and "pharodist/pharo0.1-10309dev09.05.3.image") - you can start pharo by dragging the "pharo0.1-10309dev09.05.3.image" onto the "Pharo.exe" file - note that automatically a new file "Pharo.ini" is created in your "pharodist" directory - save the image as "pharo.image" (you should now have a pharo.image and pharo.changes file - delete the old "pharo0.1-10309dev09.05.3.changes" and "pharo0.1-10309dev09.05.3.image" file - if you wish to further customize the application you can set some parameters in the Pharo.ini file (a list of all available parameters can be found at [7]) SECTION C - Building a setup ============================ - copy "Pharo.ico" into the "pharodist" directory - create a file "license.rtf" in the "pharodist" directory and clip the license from pharo-project.org into this file - download and install the free NSIS installer package, here we use version 2.42 from [8] - also download the file "ZIPDLL.zip" plugin from [9] - Extract ZipDLL.dll to directory "Plugins" in your NSIS installation - Extract ZipDLL.nsh to directory "Include" in your NSIS installation - copy the file "setup.nsi" file (attached to this mail) to your "pharodist" directory and compile it using NSIS (right click on the file and select "Compile NSIS script" from the context menu - you should now have a "setup_pharo_0.0.0.1.exe" ready for distribution - easy, istnt it? Things to improve: ================== - better looking icons for pharo exe (with transparency) - setup script with custom header on the installer wizard (MUI_HEADERIMAGE_BITMAP, etc) - setup script with installer and uninstaller icons (MUI_ICON, MUI_UNICON) - better version schema - automated build on a build machine (if someone has a windows box accessible from the web tell us) - ... [1] http://www.squeakvm.org/win32/compiling.html [2] http://www.squeakvm.org/win32/release [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-May/008513.html [4] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-May/008559.html [5] http://gforge.inria.fr/frs/download.php/4621/SqueakV39.sources.zip [6] http://gforge.inria.fr/frs/download.php/22298/pharo0.1-10309dev09.05.3.zip [7] http://www.squeakvm.org/win32/settings.html [8] http://nsis.sourceforge.net [9] http://nsis.sourceforge.net/ZipDLL -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

May 19, 2009

Re: [Pharo-project] ThirtyTwoBitRegister methods removed

by Alexandre Bergel

> To me, this raises a more general question. > How can we trace a particular change in Pharo? > Why when and where this change did occur? I know all is in the > Monticello repository, but is there a quick and convenient way to > answer such a question? I mean avoiding a manual scan of each and > every Monticello version... This is an interestion question that I asked myself many times. Here is an idea: - Adding a button 'search' in a Monticello repository inspector (the one you get when opening a repository) - with a 'search' button, you can then enter a method location such as TextMorphEditor>>keystroke: - the list of versions that either added the method or removed it according to the ancestors. How does that sound? I can work on it. Cheers, Alexandre > > > 2009/5/19 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> Hi folks. I noticed that this two methods were removed from >> ThirtyTwoBitRegister: >> >> asByteArray >> ^ ByteArray with: (low bitAnd: 16rFF) with: (low bitShift: >> -8) with: >> (hi bitAnd: 16rFF) with: (hi bitShift: -8) >> >> >> >> reverseLoadFrom: aByteArray at: index >> "Load my 32-bit value from the four bytes of the given >> ByteArraystarting at the given index. Consider the first byte to >> contain the >> mostsignificant bits of the word (i.e., use big-endian byte >> ordering)." >> >> hi := ((aByteArray at: index + 3) bitShift: 8) + >> ( aByteArray at: >> index + 2). >> low := ((aByteArray at: index + 1) bitShift: 8) + >> ( aByteArray at: >> index). >> >> >> >> I need them for Glorp. I looked but I didn't found a similar >> message for >> them. I don't think adding them as an extension is a good solution >> here >> since this seems to be very "internal". is there a reason of the >> removing? >> If not, could them be added again? If there are reason, which >> should be the >> best approach to fix this in mi case? >> >> I have no problem in commit them if you want. >> >> Thanks! >> >> Mariano >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 19, 2009

Re: [Pharo-project] AlienFFI new package

by Fernando olivero

IA32ABIPlugin ?? NewsqueakIA32ABIPLugi Michael, The entry for the plugin is there, could you change the name to AlienFFI plugin please. The version for MAC OS is 1.1.0. I dont know the versions of the other OS, perhaps Eliot can provide that info. Fernando On May 19, 2009, at 9:42 AM, Torsten Bergmann wrote: >> 1. place the external plugin IA32ABI in the proper folder > > Can you make the plugins for the various platforms available > and send a mail to Michael Rueger (or on the list) > so they get included on http://code.google.com/p/pharo/wiki/VMPluginOverview > > Thx > Torsten > -- > Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + > Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2009

Re: [Pharo-project] System > About is too big for the Pharo screen

by Adrian Lienhard

This is issue http://code.google.com/p/pharo/issues/detail?id=657 There is a fix but it has not been integrated yet. Adrian On May 19, 2009, at 10:21 , Oscar Nierstrasz wrote: > > If your real screen is not big enough, you can never get rid of this > information box. Can it be fixed so it is the right size for the > default Pharo image? > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2009

[Pharo-project] System > About is too big for the Pharo screen

by Oscar Nierstrasz

If your real screen is not big enough, you can never get rid of this information box. Can it be fixed so it is the right size for the default Pharo image? - on

May 19, 2009

Re: [Pharo-project] ThirtyTwoBitRegister methods removed

by Nicolas Cellier

To me, this raises a more general question. How can we trace a particular change in Pharo? Why when and where this change did occur? I know all is in the Monticello repository, but is there a quick and convenient way to answer such a question? I mean avoiding a manual scan of each and every Monticello version... Or is it logged in the ChangeSet? In this case, what hidden menu or code snippet will help tracking the change? Or should we use the issue tracker? Ideally, the reason for every change should be logged here. And every Monticello uploaded should refer to an issue. Even if this were strictly applied, not sure that is the way to retrieve information at such a detailed level. If none of these tools can provide an easy answer, then yes, requests on mailing lists, IRC, or internet search can provide a much efficient answer. But that's the signature a tool is lacking. I wish Mariano gets an answer, but an answer on the method would be more profitable to every one. Cheers Nicolas 2009/5/19 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi folks. I noticed that this two methods were removed from > ThirtyTwoBitRegister: > > asByteArray > Â Â Â Â Â Â ^ ByteArray with: (low bitAnd: 16rFF) with: (low bitShift: -8) with: > (hi bitAnd: 16rFF) with: (hi bitShift: -8) > > > > reverseLoadFrom: aByteArray at: index > Â Â Â Â Â Â Â Â "Load my 32-bit value from the four bytes of the given > ByteArraystarting at the given index. Consider the first byte to contain the > mostsignificant bits of the word (i.e., use big-endian byte ordering)." > > Â Â Â Â Â Â Â Â hi := ((aByteArray at: index + 3) bitShift: 8) + ( aByteArray at: > index + 2). > Â Â Â Â Â Â Â Â low := ((aByteArray at: index + 1) bitShift: 8) + ( aByteArray at: > index). > > > > I need them for Glorp. I looked but I didn't found a similar message for > them. I don't think adding them as an extension is a good solution here > since this seems to be very "internal". is there a reason of the removing? > If not, could them be added again? If there are reason, which should be the > best approach to fix this in mi case? > > I have no problem in commit them if you want. > > Thanks! > > Mariano > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

[Pharo-project] AlienFFI new package

by Torsten Bergmann

>1. place the external plugin IA32ABI in the proper folder Can you make the plugins for the various platforms available and send a mail to Michael Rueger (or on the list) so they get included on http://code.google.com/p/pharo/wiki/VMPluginOverview Thx Torsten -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

May 19, 2009