June 2014 - Pharo-dev - lists.pharo.org

DBXTalk > OpenDBX > MySQL and OSX Lion : working on 2.0
by phil＠highoctane.be July 11, 2014

July 11, 2014

I've been struggling to get the whole thing to work in Pharo 2.0 So, here are some pointers: I am using Xcode 4.6.3 with command line tools installed. I used the MySQL 32-bit client: mysql-connector-c-6.1.0-osx10.7-x86.dmg I used opendbx stable-1.4 To compile OpenDBX itself in 32 bits mode and all, here is the script I used. [PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspaceOpenDbx philippeback$] cat compileopendbxosx.sh PATH=/Applications/Xcode.app/Contents/Developer/usr/bin:${PATH} echo `which ld` CPPFLAGS="-m32 -I/usr/local/mysql-connector-c-6.1.0-osx10.7-x86/include" \ CXXFLAGS="-m32 -I/usr/local/mysql-connector-c-6.1.0-osx10.7-x86/include" \ CFLAGS="-m32 -I/usr/local/mysql-connector-c-6.1.0-osx10.7-x86/include" \ LDFLAGS="-m32 -L/usr/local/lib -L/usr/local/mysql-connector-c-6.1.0-osx10.7-x86/lib -lmysqlclient" \ ./configure --with-backends="mysql" --disable-utils LDFLAGS="-m32 -L/usr/local/mysql-connector-c-6.1.0-osx10.7-x86/lib" make make install Now, I had to copy the libraries of the mysql client into /usr/local/lib/ The client libraries were in /usr/local/mysql-connector-c-6.1.0-osx10.7-x86/lib (you can ln -s them if you do not want to copy). To test that things were okay, I created the sodbxtest user, database, and all in MySQL. Then let's make sure we can use that one: mysql -usodbxtest -psodbxtest sodbxtest And then went to stable-1.4/test and issued: ./odbxtest -b mysql -h localhost -p 3306 -d sodbxtest -u sodbxtest -w sodbxtest Which should work. You can open the MySQL Workbench Admin tab > server status tab and see the commands issued. I had to do a symlink in: : /usr/local/pharo/bin/pharo-vm/Pharo.app/Contents/MacOS/Plugins/ (where I have my pharo vm installed) so that: libopendbx.dylib was pointing to /usr/local/lib/libopendbx.dylib Then, start the image where you have loaded the OpenDBXDriver configuration and run the tests. You can get the configuration from the World menu > Configurations OpenDBXDriver (GuillermoPolito.20) I installed the configuration and then did: (ConfigurationOfOpenDBXDriver project version: #stable) load. All tests for the MySQL backend turned up green. Maybe someone can put the above things in the right sections on the DBXTalk site, I didn't got enough info for the OSX version. Next step is to try to get GLORP running, not sure I'll go that route. Phil

6 8

Metacello-github + filetree-git async
by Yuriy Tymchuk July 11, 2014

July 11, 2014

Hi guys. My workflow is like this: I load a configuration on CI with github:// magic in metacello conf. Then on local machine I add a local gitfiletree repo to the project packages. The thing is that the last version if loaded, but gitfiletree repo is showing that second last is loaded. And yes, diffs with last one (not loaded by gitfiletree opinion) show no changes and diffs with second last (current one by gitfiletree opinion) show changes that were mede in last version. Any clue what can be the problem? Uko

6 15

Pharo logo on files.pharo.org
by Torsten Bergmann July 11, 2014

July 11, 2014

On the http://files.pharo.org page the picture is missing (it references http://www.pharo-project.org/images/pharo.png) and I think this is gone due to the website redesign. Maybe it can be added again so the page looks complete. Thx T.

2 2

Sharing/Versioning Data
by Sean P. DeNigris July 8, 2014

July 8, 2014

How do we do this now with MC? Are there options other than "encode in string returned by method" like I've seen done for image data? My use case is that I have a very static domain, and so doesn't require user changes. I think the easiest way to distribute it would be to edit the data on a dev image, and then somehow save the data in a way that can be committed with MC so that loading via MetaC config loads the latest version of the data. What would be the best way to do that? Thanks. p.s. on a related note, I'm also interested in distributing static files with the code e.g. maybe a PDF readme ----- Cheers, Sean -- View this message in context: http://forum.world.st/Sharing-Versioning-Data-tp4765528.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

6 8

NewList without Icons
by Nicolai Hess July 4, 2014

July 4, 2014

Hi, anyone knows how to use NewList without icons. Background: I have a collection with 5000 entries, every entry is a list of 20 strings. Inspecting this collection works, but scrolling the left pane of the inspector window is awfully slow. This is unexpected, as the only changing visual parts are the collection indices. For exampel, inspect the following collection: (1 to:5000) collect:[:x | (1 to:20) collect:[:t| t asString] ]. Dragging the scrollbar (or only dragging the window) is slow. Ok, there are many entries, but now, change this method (return nil instead of accessing the cache) NewList>>#iconForItem:at: ^nil "^ iconCache at: anItem ifAbsentPut: [ (self model iconForItem: anItem at: anIndex) asMorph ]" scrolling is smooth. The problem is, accessing the iconCache calls #hash on anItem, which is an IndexedEyeElement and this calls hash on its index AND on the value (the string array). The funny thing is, eyeinspector does not provide any icons at all. Therefore, is there a way to create the NewList and tell it to NEVER ask for icons? regards Nicolai

2 2

Athens and StrikeFont ( again )
by Nicolai Hess July 2, 2014

July 2, 2014

If I take a fresh pharo image I always have to reenable FT fonts before doing any athens rendering with text (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight). Ok, I know I have to open settings disable then enable FreeType and choose a FreeType font. But what exactly is the problem with Athens rendering and non FT fonts? Nicolai

8 16

[ANN]: Little NeoJSON Helper
by Sean P. DeNigris July 2, 2014

July 2, 2014

"Assuming Neo-JSON-Core is loaded" Gofer it smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; package: 'Neo-JSON-Utilities'; load. To aid in writing mappings, send "reader mapHelperFor: MyDomainClass", where MyDomainClass need not even exist. This will halt inside the mapping, and bring up an inspector on a NeoJSONMapHelper object. >From here, you can #generateInstVars to map the json keys to inst vars, translating underscores to camel case. Then you can inspect #mappingSnippet, which will give you the code to replace "reader mapHelperFor: MyDomainClass" with the new mappings to inst vars. For example: mapper for: DoDropletSize do: [ :m | m mapInstVars: #(name cpu slug memory id disk); mapInstVar: #costPerHour to: #cost_per_hour; mapInstVar: #costPerMonth to: #cost_per_month ]. It could be enhanced, especially with a UI to further customize the mappings (e.g. maybe you want to map the boolean "required" key to a more Smalltalkish "isRequired" inst var, but it makes the common cases a bit easier. HTH :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Little-NeoJSON-Helper-tp4756763.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 9

Re: [Pharo-dev] Versioner
by Stephan Eggermont July 2, 2014

July 2, 2014

Kilon wrote: >I disagreed with this Stephan > >"That being said, I am getting a bit nervous about how versioner is released. It should aim to improve the way people can work, and not to create a single workflow for all people working on pharo projects. I hope my >fears are unfounded." > >this what I was replying to. Ok. The concrete problem we ran into with the current version of Versioner is that it wants to resolve dependencies to exact versions. For configurations depending on Seaside, Magritte or Grease, this is normally unwanted. They should depend on the symbolic release versions. With the high number of changes in Pharo, exact versions have a short lifetime. Dale wrote: >In a programming language where the development environment allows script-based tools (as opposed to GUI-based tools) > it is much easier to construct custom "tools" to support variations in workflow >... individual developers routinely copy/share scripts that routinely need to be customized for their environment ... In order to work together effectively in open source projects it is important that contributors know what workflow is used in a project. That is easier when the number of different workflows is limited. Because projects depend on other projects the number of combinations of workflow is very large. Scriptable tools can easily support these resulting combinations. Building a GUI tool that is both very flexible and very easy to use seems to be less easy. Stephan

3 2

functions keys
by Pablo R. Digonzelli July 1, 2014

July 1, 2014

After exploring the image I believe functions keys (F1,F2, etc ) are not handling by KeyboardEvent class. I think it is very common use that function keys in business applications. Someone know if i am true about this topic? . Or maybe someone handling functions keys in an application? TIA Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 Email: pdigonzelli(a)softsargentina.com pdigonzelli(a)gmail.com Cel: 5493815982714

4 10

Versioner
by Diego Lont July 1, 2014

July 1, 2014

I am afraid this mail is going to be too long, but I feel it needs to be written. I will start with the conclusion, so you can skip the mail if you feel it does not interest you. Please keep the discussion on the Moose list, as there the discussion was started. I am very happy that versioner is being built. We need more and better software configuration tools, and versioner will make our life easier. That being said, I am getting a bit nervous about how versioner is released. It should aim to improve the way people can work, and not to create a single workflow for all people working on pharo projects. I hope my fears are unfounded. Software configuration management (SCM) is in my opinion an undervalued topic within the software world. One cannot find very many good books on them, and I am afraid this lack of knowledge shows in the way people go around with their SCM. So I would like to write down some observations of the SCM processes in Pharo that I believe we should keep in mind. The main target of SCM is to keep the impact of changes as minimal as possible. Good SCM allows all people working on a certain project, to make their changes, without causing trouble for other project members and people using this project. Open source projects are (in SCM terms) rather complex, as they involve a lot of people, including some people we do not know. 1. One of the best things of Metacello is that it does not require you to follow a certain workflow. It is very flexible and supports a large range of possible workflows. Within the Pharo community we have at least 3 different workflows: A. For Pharo core, we have a pharo inbox, where suggested fixes for reported bugs are put. These fixes are reviewed and, if accepted, integrated into Pharo. This ensures that the changes in Pharo hold (most of the time) to quite some quality standards. B. For the âcross-platformâ projects (Grease, Seaside, Magritte, etc.) all suggested fixes are put in the main repository on smalltalkhub. The fixes are, after review and tests, released by putting them in a âreleasedâ version of the configuration. Since not all fixes should be in all versions, and sometimes only concern a certain platform, the process for Pharo core would not work: releasing fixes are more complex because of the cross-platform issues. C. For the âmooseâ projects all suggested fixes are put in the main repository and are accepted by default. Since most projects evolve very fast, quality assurance is done afterwards, by submitting bug fixes. I can say a lot about why I believe these workflows are appropriate for their different projects, but the point I am trying to make here, is that these workflows have come to existence because of the different demands on them. And to stress my point about the flexibility (thank you Dale): When there was a problem with the workflow in the cross platform projects, I could find a solution (using releases) that Metacello supported. 2. Unfortunately Metacello does not have a good UI. And for large configurations like Seaside, it is a lot of work to keep them maintained. I dream of a tool that acts as a UI for Metacello: this tool is flexible as Metacello, while making the simple things real easy (hitting a button and done). Does versioner aim to do this? 3. I always get very nervous when someone says: They do it like this, and that works very well for them. So we should do that too. I do not believe that is always a good idea. The conclusion should be a question: Can we use that too? And now I cannot find the mail about the java SCM practice, but I do not think we can apply it to all our processes ... 4. Modularity is very important. Also for performing good SCM. And yes, we lack sufficient modularity in Moose. It should be better. I.e. because of the lack of modularity, it is sometimes hard to distinguish between where the change needs to be put in. So there is no clear group to point out who should accept the changes. So this is also an SCM problem. Cleaning up the configuration will help here very much. Thank you Steff for the good work here. And maybe you also have a point that the people working on Moose should have more focus on keeping things modular, because it makes the system better maintainable in a lot of ways. 5. Forking things will only make SCM worse, as it adds a complexity. So I very much hope we can come to an agreement how the process works, without resorting to drastic measures. Regards, Diego

4 6