December 2013 - Pharo-users

Glorp PostgreSQL Drivers in Ubuntu 12.04
by Esteban A. Maringolo Dec. 13, 2013

Dec. 13, 2013

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

7 15

MooseDay schedule
by Marcus Denker Dec. 13, 2013

Dec. 13, 2013

>> De : Anne Etien <anne.etien(a)univ-lille1.fr> >> >> Hi, >> >> Please find bellow the schedule of the MooseDay >> http://www.lifl.fr/~etien/MooseDay.html >> The idea is really to present works developed on top of (or around) Moose and to have fruitful discussions. So I planned 30 mn per topic, but the schedule is quite flexible. Lot of time is foreseen for discussions. >> >> 10h: welcome >> 10h30: APIEvolutionMiner - Andre Hora >> 11h: FamixDiff - Nicolas Anquetil >> 11h30: Orion - Jannik Laval and Anne Etien >> >> 12h: Lunch offered by ESUG. >> >> 14h: First works on Version - Yuriy Tymchuk >> 14h30: Roassal - Alexandre Bergel >> >> 15h-15h30 break >> >> 15h30: GraphET - Alexandre Bergel >> 16h: Use of GraphET - Serge Stinckwich >> 16h30: Around tests - Alain Plantec >> >> Reminder, the MooseDay will take place in Inria B building room B31. Directions to come can be found there (http://www.inria.fr/en/centre/lille/overview/locations) >> >> See you next week in Lille ;o) >> >> Anne >>

1 0

Is OpenDBX alive?
by Esteban A. Maringolo Dec. 13, 2013

Dec. 13, 2013

As a side question about my dependency issues... Is the OpenDBX project still active? Not its Smalltalk side, I mean... the core project. To me it seems like it was a great attempt to have something similar to ODBC but for all platforms. But I'm not seeing a wide usage of it in the wild. Seems like everybody else is happy with their JDBC, DBI and similar "DB layers" on the language side. Regards, Esteban A. Maringolo

4 4

Nginx Reverse Proxying
by Esteban A. Maringolo Dec. 12, 2013

Dec. 12, 2013

Hi there, I continue with my server setup... I'm trying to setup nginx as the HTTP front end. I have two servers, one for the Zinc SeasideAdaptor running on 8080 and another server running on 8081 (maybe there is a way to run both on the same server). ZnZincServerAdaptor startOn: 8080. ZnServer startDefaultOn: 8081. ZnServer default delegate: (ZnWebSocketDelegate map: 'ws' to: MyWsHandler new). In the Seaside side I have three "entry points": /app : which is a standard Seaside application /app-api/v1/ :which is a WARestfulHandler (REST API, with Basic HTTP Auth) /assets (File Directory for static files) I plan to put a nginx in front of those services, mainly for performance purpose of static file serving, and to avoid the exposure of my server directy to internet. Supposing the hostname is app01.mydomain.com ? My requirements are 1) I want that http://app01.mydomain.com/app be forwarded to http://localhost:8080/app, the same with app-api 2) Same for websockets, maybe to http://ws01.mydomain.com to http://localhost:8081/ws 3) http://app01.mydomain.com/assets be served statically. I know this is a request which isn't directly related with Pharo nor Seaside, but given the fact it's a common setup I hope somebody will help me with this. Sorry for the crosspost. Regards, Esteban A. Maringolo

1 0

[launcher] fixed layout of tollbar buttons
by btc＠openinworld.com Dec. 12, 2013

Dec. 12, 2013

Hi Damien, Benjamin.V.R. I see in "PharoLauncher-Spec-DamienCassou.17" that the layout of the toolbar buttons is fixed, which is really great. However in trying to learn from that for future reference, seeing it relies on an empty column being added "seems" like a hack to workaround some issue with Spec. Should that be logged as a bug? Or is there some greater architectural background for this that I am missing? PhLCommandTooldbar>>dynamicLayout "(newer)" "Create a spec layout with 1 row, and as many columns as there are command classes" ^ SpecLayout composed newRow: [ :r | r newColumn: [ :col | ]. "<--------FIX" self commandClasses do: [ :commandClass | r add: commandClass specId width: self class toolbarHeight ] ] I tried digging into Spec to look at this myself, and my naive intuition felt it was something to do with initialization of LayoutFrames, but that was my first exposure to LayoutFrame and I quickly got lost. However I was reminded of Igor commenting "i only know that if you using proportional layout, then if you want submorphs to be laid down properly, you must use addMorph:fullFrame: instead of just addMorph:" [1] I tried this with a few hacks, but tit was really shooting in the dark and unsuccessful. [1] https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg08838.html cheers -ben

2 4

Re: [Pharo-users] [Pharo-dev] [Pharo Trick: #0009] 'Enable halt/inspect once' button
by btc＠openinworld.com Dec. 12, 2013

Dec. 12, 2013

1 0

[Pharo Trick: #0008] - If appropriate use the memory file system
by Torsten Bergmann Dec. 12, 2013

Dec. 12, 2013

----------------------------------------------------------------------------------- [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')

3 2

[Pharo Trick: #0001] - Simple TODO list
by Torsten Bergmann Dec. 12, 2013

Dec. 12, 2013

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. -----------------------------------------------------------------------------------

8 8

[Pharo Trick: #0006] - Run code from a button window
by Torsten Bergmann Dec. 12, 2013

Dec. 12, 2013

----------------------------------------------------------------------------------- [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.

2 1

[Pharo Trick: #0005] - Pick up morphs that do not want to be picked up"
by Torsten Bergmann Dec. 12, 2013

Dec. 12, 2013

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 Â Â Â

1 0