December 2013 - Pharo-users

Re: [Pharo-users] Glorp PostgreSQL Drivers in Ubuntu 12.04

by Esteban A. Maringolo

Hi all, it is a 32bit Ubuntu 12.04 hosted in Digital Ocean. The image starts, but once I access something that needs to open a GlorpSession I get that exception. I added a symlink from libpq.so to libpq.so.5.4, the other symlink was already there. $ ls -l /usr/lib/libpq* lrwxrwxrwx 1 root root 12 Dec 12 12:17 /usr/lib/libpq.so -> libpq.so.5.4 lrwxrwxrwx 1 root root 12 Mar 6 2012 /usr/lib/libpq.so.5 -> libpq.so.5.4 -rw-r--r-- 1 root root 163308 Mar 6 2012 /usr/lib/libpq.so.5.4 There is also a lot of libraries in /usr/lib/postgresql/9.1/ What is the expeced filename Pharo will look for? I'm not using the DBX driver, as far as I can tell, but the Native Postgres driver instead. Which is non-sense given the fact it requires de Glorp driver. I know. :-/ Esteban A. Maringolo 2013/12/12 Guillermo Polito <guillermopolito(a)gmail.com>: > Esteban, are you using dbxtalk? > > Either you use it or not, the VM will only find the external libraries if > they are in a well known path (that is, for example /usr/lib/). If your > libraries are in a different place, such as /usr/lib/i386blabla/ the VM > library searching mechanism will not find it. > > Now, to fix that, you have many ways. I'd suggest not to change the PATH nor > the LD_LIBRARY_PATH, cause you either change the library resolution for all > the applications, or you change completely the resolution path for all the > libraries the VM wants to load. The safest solution here, IMHO, is to add a > symbolic link to the required library in the VM directory. > > And well, others already talked about the 32-64 bit thingy. > > cheers, > Guille > > > On Thu, Dec 12, 2013 at 9:34 AM, jtuchel(a)objektfabrik.de > <jtuchel(a)objektfabrik.de> wrote: >> >> Esteban, >> >> sounds like you need to modify your PATH environment variable either >> globally or in a startup bash script for your Pharo image. The directory >> containing Postgres libs has to be in that PATH. >> And, the other Esteban also asks about 32 or 64 bits, because it is very >> likely you need to install a 32-bit driver if you are on a 64 Linux machine >> (and even some additional libraries, apt-get install ia32-libs, iirc), >> because Pharo doesn't support 64 bit libraries afaik. >> >> HTH >> >> Joachim >> >> Am 12.12.13 03:53, schrieb Esteban A. Maringolo: >> >>> Hi there, >>> >>> I'm moving my development server (Windows) into production (Ubuntu >>> 12.04) and I'm facing some issues with, among other things, the >>> PostgreSQL driver. >>> >>> I'm getting an: >>> "Error: External module not found" >>> >>> My database login is as follows: >>> >>> sampleLogin >>> ^Login new >>> database: (PostgreSQLPlatform new characterEncoding: 'utf8'); >>> username: 'user'; >>> password: 'secret'; >>> connectString: 'localhost_db'; >>> encodingStrategy: (DBXStaticEncoding newForEncoding: #utf8). >>> >>> And then just a regular accessor for the previous login: >>> >>> DatabaseAccessor forLogin: self sampleLogin. >>> >>> >>> How should I install the dependencies? >>> >>> I have a libpq.dll in my windows environment, and I already installed >>> libpq5 drivers in the server (apt-get install libpq5) >>> >>> What else should I do? >>> >>> Regards, >>> >>> Esteban A. Maringolo >>> >>> >> >> >> -- >> ----------------------------------------------------------------------- >> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de >> Fliederweg 1 http://www.objektfabrik.de >> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >> >> >

Dec. 12, 2013

[Pharo Trick: #0009] 'Enable halt/inspect once' button

by btc＠openinworld.com

When I have a 'self haltOnce' breakpoint that I am activating often, going "World > System > Enable halt/inspect once" each time is annoying. So using the Duplicate Halo on the menu item, I drag it onto the background so that it acts like a button. cheers -ben

Dec. 12, 2013

Re: [Pharo-users] [Pharo-dev] [Pharo Trick: #0008] - If appropriate use the memory file system

by Marcus Denker

Related to that: For Pharo4 I want to experiment to have the following: 1) one Memory FileSystem per RPackage (just an ivar there). 2) File Browser support to show all these so one can put files in the package filesystem 3) in Monticello, save all the files as part of the .zip (directory âresourcesâ) 4) When loading with MC, load all files from the resources dir into the package filesystem (at first the file support will be very simple, e.g. no support for diffs). ==> then store e.g. all the icons there instead of a MIME-Encode string. Marcus On 12 Dec 2013, at 12:39, Torsten Bergmann <astares(a)gmx.de> wrote: > ----------------------------------------------------------------------------------- > [Pharo Trick: #0008] - If appropriate use the memory file system > ----------------------------------------------------------------------------------- > Works in: Pharo 2.0, 3.0, ... > ----------------------------------------------------------------------------------- > > It may be possible that your application has to export some > data into an external file in a specific format. Pharo allows writing into > a file using Streams as any other Smalltalk. > > But sometimes you want to check the result right from the Pharo image > without having to look into the external file using external tools. > > So the trick here is to use the memory file system instead > of the real disk file system during development since also no > cleanup on the hard disk is required afterwards: > > |fs| > fs := FileSystem memory. > (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Exported data' ]. > (fs / 'hello.txt') readStream contents. > > The memory filesystem is also nice if you need to work with files > within a unit test. So when the test runs nothing remains left on the > hard disk. > > If you need a real copy of the file on the hard disk you can also copy > from the memory file system to the disk file system using #copyTo: > > |fs| > fs := FileSystem memory. > (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Memory first and then disk' ]. > (fs / 'hello.txt') copyTo: (FileSystem disk / 'exactCopy.txt') > >

Dec. 12, 2013

[Pharo Trick: #0008] - If appropriate use the memory file system

by Torsten Bergmann

----------------------------------------------------------------------------------- [Pharo Trick: #0008] - If appropriate use the memory file system ----------------------------------------------------------------------------------- Works in: Pharo 2.0, 3.0, ... ----------------------------------------------------------------------------------- It may be possible that your application has to export some data into an external file in a specific format. Pharo allows writing into a file using Streams as any other Smalltalk. But sometimes you want to check the result right from the Pharo image without having to look into the external file using external tools. So the trick here is to use the memory file system instead of the real disk file system during development since also no cleanup on the hard disk is required afterwards: |fs| fs := FileSystem memory. (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Exported data' ]. (fs / 'hello.txt') readStream contents. The memory filesystem is also nice if you need to work with files within a unit test. So when the test runs nothing remains left on the hard disk. If you need a real copy of the file on the hard disk you can also copy from the memory file system to the disk file system using #copyTo: |fs| fs := FileSystem memory. (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Memory first and then disk' ]. (fs / 'hello.txt') copyTo: (FileSystem disk / 'exactCopy.txt')

Dec. 12, 2013

Re: [Pharo-users] [Pharo-dev] [Pharo Trick: #0001] - Simple TODO list

by Serge Stinckwich

Nice idea Torsten, this kind of tricks ;-) Maybe we can save them online somewhere ? gists.github.com ? On Wed, Dec 11, 2013 at 12:16 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > the mailinglist, stackoverflow and other Pharo related medias are typically used > in the "here is a question to problem" followed by an "answer from community" style. > > But lets also think the other way around: if we already have a solution for a > problem that others may have too or may have in the future we should share the > answer/solution as well. > > I'm sure many of you have some tricks that make developing with Pharo much easier > and others can profit from these tricks if we share them here on the list. > > Be it > - a simple and useful script > - a simple key combination other may not yet know of > - a package one can use or how you use it > - a link to a nice description on the web related on how to use Pharo > - a custom tool that makes development easier > - an algorithm or something that you think was solved very elegant > - a way you solved a common problem easily in your app > - ... > > Then just describe it in a few lines and post it. Also write in which Pharo > version you tried it - this makes it easier for others to see in which > version the trick/solution is known to work. > > The idea goes like this: if you have a trick to share then send a mail with > subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND Pharo user > list (see http://lists.pharo.org) Make sure to increase the trick counter xxxx. > > Using this special subject one can later easily get the tricks from the > mailinglist archive. Also others can refer to the trick if it solves a common > problem other may ask for on the list. > > Lets see if we are able to reach the goals of 100, 1000 or more Pharo tricks ;) > > Bye > T. > > > I will start with something easy but useful: > > ----------------------------------------------------------------------------------- > [Pharo Trick: #0001] - Simple TODO > ----------------------------------------------------------------------------------- > Works in: Pharo3.0 Latest update: #30635 but should work in other versions too > ----------------------------------------------------------------------------------- > > If you develop an app with Pharo you may not yet fully implement all features. > Some kind of marker for future "ToDo's" is often needed. Using a pragma on a method is > the easiest solution here: > > foo > <todo: 'Add world later'> > "That method is not yet fully implemented" > > Transcript show: 'Hello' > > > Using a simple expression in the workspace you can browse all the TODOs for your > project afterwards in a window: > > SystemNavigation default browseAllSendersOf: #todo: > > You can even query the system for the todo descriptions if you need the full > list of things to work on: > > (PragmaCollector filter: [:prg | prg keyword = 'todo:']) > reset; > collect: [:each| each arguments first ] > > As the pragma keyword #todo: is very common and may be used by others too > it may be wise to use a custom one like "myappplicationTodo:" or similar. > ----------------------------------------------------------------------------------- > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Dec. 12, 2013

Re: [Pharo-users] Glorp PostgreSQL Drivers in Ubuntu 12.04

by Guillermo Polito

Esteban, are you using dbxtalk? Either you use it or not, the VM will only find the external libraries if they are in a well known path (that is, for example /usr/lib/). If your libraries are in a different place, such as /usr/lib/i386blabla/ the VM library searching mechanism will not find it. Now, to fix that, you have many ways. I'd suggest not to change the PATH nor the LD_LIBRARY_PATH, cause you either change the library resolution for all the applications, or you change completely the resolution path for all the libraries the VM wants to load. The safest solution here, IMHO, is to add a symbolic link to the required library in the VM directory. And well, others already talked about the 32-64 bit thingy. cheers, Guille On Thu, Dec 12, 2013 at 9:34 AM, jtuchel(a)objektfabrik.de < jtuchel(a)objektfabrik.de> wrote: > Esteban, > > sounds like you need to modify your PATH environment variable either > globally or in a startup bash script for your Pharo image. The directory > containing Postgres libs has to be in that PATH. > And, the other Esteban also asks about 32 or 64 bits, because it is very > likely you need to install a 32-bit driver if you are on a 64 Linux machine > (and even some additional libraries, apt-get install ia32-libs, iirc), > because Pharo doesn't support 64 bit libraries afaik. > > HTH > > Joachim > > Am 12.12.13 03:53, schrieb Esteban A. Maringolo: > > Hi there, >> >> I'm moving my development server (Windows) into production (Ubuntu >> 12.04) and I'm facing some issues with, among other things, the >> PostgreSQL driver. >> >> I'm getting an: >> "Error: External module not found" >> >> My database login is as follows: >> >> sampleLogin >> ^Login new >> database: (PostgreSQLPlatform new characterEncoding: 'utf8'); >> username: 'user'; >> password: 'secret'; >> connectString: 'localhost_db'; >> encodingStrategy: (DBXStaticEncoding newForEncoding: #utf8). >> >> And then just a regular accessor for the previous login: >> >> DatabaseAccessor forLogin: self sampleLogin. >> >> >> How should I install the dependencies? >> >> I have a libpq.dll in my windows environment, and I already installed >> libpq5 drivers in the server (apt-get install libpq5) >> >> What else should I do? >> >> Regards, >> >> Esteban A. Maringolo >> >> >> > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > >

Dec. 12, 2013

[Pharo-dev] [Pharo Trick: #0007] - Write UI prototype in a workspace

by Benjamin

----------------------------------------------------------------------------------- [Pharo Trick: #0007] - Write UI prototype in a workspace ----------------------------------------------------------------------------------- Works in: Pharo 2.0, 3.0, ... ----------------------------------------------------------------------------------- In Morphic, there is no way to quickly prototype a UI. But in Spec there is a Dynamic class supporting this, so one can try different things directly from a Workspace An example: m := DynamicComposableModel new. m instantiateModels: #( button ButtonModel list ListModel). m list items: #(1 2 3 4 5). m button label: 'Plip'; action: [ self halt ]. m openWithSpecLayout: (SpecLayout composed newColumn: [: c | c add: #list ; add: #button height: 26 ]; yourself). Ben

Dec. 12, 2013

[Pharo Trick: #0005] - Pick up morphs that do not want to be picked up"

by Torsten Bergmann

Post this trick to user list also as it was only on dev-list. Please send to both lists in the future: Gesendet:Â Donnerstag, 12. Dezember 2013 um 10:08 Uhr Von:Â "phil(a)highoctane.be" <phil(a)highoctane.be> An:Â "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> Betreff:Â [Pharo-dev] [Pharo Trick: #0005] - Pick up morphs that do not want to be picked up" Usually one can deal with morphs by doing the alt-shift-click on them, so that we get the halos and do whatever. Â Now, some morphs do not want to let you do this (like the Pharo image on the desktop background) - or you just don't see them as they are leftovers from experiments. Â A shift click (on Windows) brings a "find window" popup where you can select what you want, no matter what. Try to pick the ImageMorph in there for the Pharo Logo. Â Phil Â Â Â

Dec. 12, 2013

[Pharo Trick: #0006] - Run code from a button window

by Torsten Bergmann

----------------------------------------------------------------------------------- [Pharo Trick: #0006] - Run code from a standalone button window ----------------------------------------------------------------------------------- Works in: Pharo 2.0, 3.0, ... ----------------------------------------------------------------------------------- In Pharo there is a class called ButtonModel - it is a model used for buttons when building UI's with the Spec framework. But it can be used also standalone to open a button window with an action block: |b| b := ButtonModel new. b openWithSpec; label: 'Run my code'; action: [ Transcript open ] So you just have to click to run some code.

Dec. 12, 2013

[Pharo Trick: #0004] - Run code using a key command to speedup development

by Torsten Bergmann

----------------------------------------------------------------------------------- [Pharo Trick: #0004] - Run code using a key command to speedup development ----------------------------------------------------------------------------------- Works in: Pharo3.0 Latest update: #30637 but should work in other 2.0/3.0 versions ----------------------------------------------------------------------------------- If you have to run some code very often you typically have to evaluate it from a workspace over and over again. But to speed up you can assign a global keymapping which allows to run it with a simple keyboard shortcut: World on: $a shift command do: [ Object browse ]. Evaluate this once in a workspace. After that anytime you press SHIFT, the command button (on Windows this is ALT) and A together the block gets evaluated and your code runs easily. Background: =========== In Pharo there is a global morph called "World" representing the desktop. One can assign a key combination to any morph including this world. If you are interested on the Keymappings then read http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… for more

Dec. 12, 2013