November 2013 - Pharo-users

[launcher] Re: PharoLauncher howto (was: SimplePersistence ...)

by btc＠openinworld.com

Nov. 21, 2013

[launcher] Re: PharoLauncher howto (was: SimplePersistence ...)

by btc＠openinworld.com

Nov. 21, 2013

[launcher] Re: [Pharo-dev] PharoLauncher

by btc＠openinworld.com

Well spotted. It is explained by PharoLauncher>>setImageRepository: aTemplateRepository templateRepository: anImageRepository also being wrong and reversed. If you might like to contribute to PharoLauncher and want to get into the swing of things, pharo.fogbugz.com has a 'Launcher' project'where you can log Cases to which you can attach mcz files. btw, you might find the various #settingsOn: methods interesting. btw2, for a while I had been collaborating with Damien in private, but we recently decided to move this to [pharo-users] and adding a [launcher] tag. I've cross-posted there. cheers -ben Mark Bestley wrote: > On 21/11/2013 15:00, Sean P. DeNigris wrote: >> Just starting to play with it... looks cool. >> >> One thing is that I'd like to be able to choose the default image >> location. >> It feels wrong to install them under ~/Library/Preferences on the Mac... >> > > Agreed > > > However I am confused by the code > > createLauncher > ^ self basicNew > setImageRepository: PhLTemplateGroupRepository > forSelectedGroups > templateRepository: PhLDirectoryBasedImageRepository > inPharoPreferencesDirectory; > initialize; > yourself > > Aren't the parameters of setImage and template the wrong way round? ie > it seems to pass the template dir to the image and vice versa >

Nov. 21, 2013

Re: [Pharo-users] Help with SQLite3 package

by Michel

Thanks Joachim. I did it and it's better. Michel. > Michel, > > Maybe you should consider using a link instead of a copy of the file. > I would also suggest to only add a link within to the sqlite installation directory rather than the pharo directory. Because then pharo will find sqlite3.so as well and you have way fewer dependencies. > > Joachim > > Michel <michel.revesche(a)wanadoo.fr> schrieb: > >> Hi Joachim, >> >> I have a sqlite library in /usr/lib named 'libsqlite3.so.0.8.6'. This >> directory is of course in the path. >> >> I made a copy of this library in my pharo2.0/bin directory and changed >> its name to 'libsqlite3.so' and it fixed the problem ! >> >> So I got it thanks to your help and a little luck. Depending on the >> linux distro this library name would differ. Somebody knows where it is >> defined in the image ? >> >> Regards, >> Michel. >> >>> Hi Michel, >>> >>> I am neither a Pharo nor a sqlite expert, but I would guess the sqlite >>> library is not in your image directory or you are starting pharo >>> without setting the PATH to a location that contains the sqlite library. >>> >>> HTH, >>> >>> Joachim >>> >>> Am 20.11.13 18:13, schrieb Michel: >>>> Hi pharoers, >>>> >>>> I am a newbie with Pharo. >>>> >>>> I installed the SQLite3 package in the Pharo2 image with the >>>> MetacelloConfigurationBrowser and tried a test with this script : >>>> db := SQLiteConnection fileNamed: '/home/michel/base_CD/BaseCD.db'. >>>> resu := db executeQuery: 'SELECT * FROM T_album'. >>>> resu inspect. >>>> >>>> And I got this error : External module not found. >>>> >>>> I am on Fedora linux and I think that I should give somewhere (in >>>> SQLiteReference class ?) the address of the libsqlite3.so file. Am I >>>> right ? >>>> >>>> Kind Regards, >>>> Michel. >>>> >>>> >>> >> >>

Nov. 21, 2013

Re: [Pharo-users] PharoLauncher howto (was: SimplePersistence ...)

by Sean P. DeNigris

Torsten Bergmann wrote > Usually for "end user experience" the launcher opens in full world mode - > so you see no Pharo > background/world menu - only the launcher. I liked the "full world" effect once I got used to it, but Pharo's idea of "fullscreen" is jarring in the Mac world. Also, since there's no longer an item in the World Menu, one has to dig into the core to find out how to un-fullscreen oneself. IMHO, I would not open in fullscreen by default. ----- Cheers, Sean -- View this message in context: http://forum.world.st/PharoLauncher-howto-was-SimplePersistence-tp4724028p4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 21, 2013

Re: [Pharo-users] PharoLauncher howto (was: SimplePersistence ...)

by btc＠openinworld.com

Nov. 21, 2013

Re: [Pharo-users] Any problems known here?

by Friedrich Dominicus

Norbert Hartl <norbert(a)hartl.name> writes: > Am 21.11.2013 um 06:57 schrieb Friedrich Dominicus > <frido(a)q-software-solutions.de>: > >> Norbert Hartl <norbert(a)hartl.name> writes: >> >>> Am 20.11.2013 um 18:42 schrieb Friedrich Dominicus >>> <frido(a)q-software-solutions.de>: >>> >>> I wonder if anyone has problems running a Pharo on a 64-bit System >>> (Debian) with multiarch. Because strange enough it can suddenly >>> not find >>> vm-display-X11 any more >>> >>> You need to install the desktop variant: >> I guess this will do for Ubuntu and Debian. >> >> But my probem was much more profane >> and ldd o vm-display-X11 has informed me that two libraries where not >> there. I installed them manually and after that Pharo start working >> again. >> >> So yeah ldd is your friend. >> >> But thanks for taking the time helping me. >> > Can you tell which libraries were missing? Maybe the dependencies of > the package needs to be adjusted. Can you tell which debian version > and channel (stable,â¦) you are using and what files were missing? I > think you know that but if you have the file you can find the package > that needs to be installed by doing I've not installed from the repository. I'm using Debian. And the missing libraries were libICE.so.6 and libSM.so Regards Friedrich

Nov. 21, 2013

Re: [Pharo-users] PharoLauncher howto (was: SimplePersistence ...)

by Norbert Hartl

Am 21.11.2013 um 17:01 schrieb Torsten Bergmann <astares(a)gmx.de>: > Hope this helps a little bit Yeah, thanks for your effort. I saw what you were mentioning but I needed confirmation that I didnât miss the most important feature :) Ok, so it is just not a tool for me. I have a project folders containing not only smalltalk stuff but also documentation and other files. The project folders are grouped by companies I work for. So central storage of images is a no-go. I do it the other way round. I have one directory where I symlink all current projects folders into. And this directory I put in the MacOS bar to have quick access. Then I open an image once and save a new version regularly using âsave asâ. This is a must for me because I experience a lot of image instability and the changes is broken so too easy to loose code. And it wouldnât work the way you told me because I save images often so copying _before_ opening an image is not an option. My workflow just needs manual setup of the projects folder which I would like to be solved somewhat more clever. But as I can see it now I need to stick to my stuff. Sad. I think PharoLauncher is nice. Norbert

Nov. 21, 2013

PharoLauncher howto (was: SimplePersistence ...)

by Torsten Bergmann

Norbert wrote: >How do you use it? Iâve just downloaded but failed to see how I can work with it. Warning: ======= Note that PharoLauncher is a project still in progress - I think Damien can tell you more about all the nice stuff. I just contributed some code and use it daily now. But lets continue with a short HOWTO (from my personal experience): -------------------------------------------------------------------------------------------------- PharoLauncher HOWTO: ==================== Before ====== I'm typically on Windows - in the past I had several folders with images everywhere on my HD. Sometimes with the VM, sometimes without. Lots of image searching as you can imagine. How I installed it: =================== So I downloaded a VM from http://files.pharo.org/vm/pharo/ and the latest ZIP with image and changes from https://ci.inria.fr/pharo-contribution/job/PharoLauncher/ I also put the source file into the same directory which I copied from the regular Pharo distro. All lives in one directory. I also use Linux boxes, for Ubuntu follow: http://www.pharo-project.org/pharo-download/ubuntu to get the launcher. Note that this currently will install an old image, so you have to load newer packages afterwards in the image or exchange the image. Installation will surely be simplified in the future. How I use it ============ Just launch the Pharo launcher image using the platform specific VM. Usually for "end user experience" the launcher opens in full world mode - so you see no Pharo background/world menu - only the launcher. Initially on a new computer the left side with local images is empty. On the right side are the images that are available on the web. Note that there are refresh buttons at the top of the list. Click "Refresh" in the right list to fetch all available images from the web. Select the image you like and download it. For instance you can download "Pharo3.0" -> "30587" which is the latest image as of today. Note that also the images from contribution CI are available. So you can easily download "Artefact", "Moose", ... images if you like. It will download the image into a specific directory somewhere in your users home directory. Each image gets an own folder. Use the "Show in folder" menu item if you want to open this location (may not yet work on all platforms) After download you can either "Launch" the image from the context menu in the right list. This will open the new image and close the launcher image. So you are ready to start working. What I do typically do is to "Copy" the image BEFORE I do any work and name it differently like "30587-MyStuff". Then I Launch the new copy and work with it, later throw it away or try that loading after commits works within new fresh images, ... Now === My HD is now much cleaner - all images are in a central place and I need only one icon/starter on the desk to open. PharoLauncher is also a very handy tool to download specific image update versions if you want to reproduce or fix Pharo bugs. I also associated one of the unused laptop keys with PharoLauncher - so the world of Smalltalk is just one click away... Things to know: =============== At the bottom there is a button to open a settings browser with specific settings for PharoLauncher. There is an option that enables the IDE again - so you can inspect the code or fix a bug. If it does not launch on your box then set a break in PhLImage>>launch to debug. Also note that it does not fit with the "Save as" image style - since each launcher image has to be in a new directory so far. So either use the "Copy" image, then "Launch" and then only "Save" in the target image or copy the "Saved as" image in a new folder and refresh the Launcher view on the right side. When you develop for it ======================= Either use the latest image from CI and enable the IDE as written before. You can also download the latest also in a Pharo 3.0 image. Just use the ConfigurationOfPharoLauncher from http://smalltalkhub.com/#!/~Pharo/PharoLauncher Then evaluate "PharoLauncher open". Currently it was rewritten using Spec for the UI, also all the actions are rewritten using Command Pattern so you can extend the buttons, menues if you like. Hope this helps a little bit Bye T.

Nov. 21, 2013

Re: [Pharo-users] Help with SQLite3 package

by Joachim Tuchel

Michel, Maybe you should consider using a link instead of a copy of the file. I would also suggest to only add a link within to the sqlite installation directory rather than the pharo directory. Because then pharo will find sqlite3.so as well and you have way fewer dependencies. Joachim Michel <michel.revesche(a)wanadoo.fr> schrieb: >Hi Joachim, > >I have a sqlite library in /usr/lib named 'libsqlite3.so.0.8.6'. This >directory is of course in the path. > >I made a copy of this library in my pharo2.0/bin directory and changed >its name to 'libsqlite3.so' and it fixed the problem ! > >So I got it thanks to your help and a little luck. Depending on the >linux distro this library name would differ. Somebody knows where it is >defined in the image ? > >Regards, >Michel. > >> Hi Michel, >> >> I am neither a Pharo nor a sqlite expert, but I would guess the sqlite >> library is not in your image directory or you are starting pharo >> without setting the PATH to a location that contains the sqlite library. >> >> HTH, >> >> Joachim >> >> Am 20.11.13 18:13, schrieb Michel: >>> Hi pharoers, >>> >>> I am a newbie with Pharo. >>> >>> I installed the SQLite3 package in the Pharo2 image with the >>> MetacelloConfigurationBrowser and tried a test with this script : >>> db := SQLiteConnection fileNamed: '/home/michel/base_CD/BaseCD.db'. >>> resu := db executeQuery: 'SELECT * FROM T_album'. >>> resu inspect. >>> >>> And I got this error : External module not found. >>> >>> I am on Fedora linux and I think that I should give somewhere (in >>> SQLiteReference class ?) the address of the libsqlite3.so file. Am I >>> right ? >>> >>> Kind Regards, >>> Michel. >>> >>> >> >> > > >

Nov. 21, 2013