Re: [Pharo-users] How to connect to DB2

[Thomas Sattler]

I have no problem using Garage to connect to Postgres.  Don't know if it
will work with DB2, but since it's ODBC, it should.

On Fri, Dec 22, 2017 at 6:36 PM, Andrei Stebakov 
wrote:

> Hi Stef
>
> I already checked Garage, it doesn't have support for DB2. It used to have
> support for odbc, but now it's deprecated.
>
> Andrei
>
> On Dec 22, 2017 15:11, "Stephane Ducasse"  wrote:
>
>> Hi andrei
>>
>> I do not know the status of OBDC but you should know that code on
>> squeaksource is in general quite old.
>> Have a look at Garage which is a kind of JBDC.
>>
>> https://github.com/pharo-rdbms/garage
>>
>> You should probably have a version available via the catalog
>>
>> Stef
>>
>> On Fri, Dec 22, 2017 at 2:43 PM, Andrei Stebakov 
>> wrote:
>> > Hi Stef
>> >
>> > Gofer new
>> >   squeaksource: 'ODBC';
>> >   package: 'ConfigurationOfODBC'; load.
>> >   (Smalltalk at: #ConfigurationOfODBC) load.
>> >
>> > When I execute the code above I got an exception doesNotUnderstand:
>> > #selector in RBParser>>externalFunctionDeclaration. Looks like
>> currentScope
>> > variable is not defined.
>> > Also if I install ODBC from the catalog it also fails.
>> >
>> > Andrei
>> >
>> >
>> > On Fri, Dec 22, 2017 at 2:19 AM, Stephane Ducasse <
>> stepharo.s...@gmail.com>
>> > wrote:
>> >>
>> >> Hi andrei
>> >>
>> >> First welcome to this list.
>> >> Second can you explain to us what is the experience that you did so
>> >> that you can state that ODBC is broken in Pharo 6.1?
>> >>
>> >> Stef
>> >>
>> >> On Thu, Dec 21, 2017 at 11:48 PM, Andrei Stebakov > >
>> >> wrote:
>> >> > Looks like ODBC is broken in Pharo 6.1.
>> >> > What's the best way to get access to DB2 in Pharo?
>> >> >
>> >> >
>> >>
>> >
>>
>>

Re: [Pharo-users] pharo 6.1 64bit segmentation fault on linux

[Cyril Ferlicot D.]

On 12/22/2017 10:33 PM, Johan Brichau wrote:
> Hi,
> 
> I’m also hitting this
> issue: 
> https://pharo.fogbugz.com/f/cases/20737/Segmentation-fault-trying-to-load-code-into-a-64-bits-Pharo-6-1-Linux
> Also reported
> here: 
> http://forum.world.st/Pharo-6-1-64-bits-segmentation-fault-loading-code-on-Linux-td5034346.html
> 
> This stops us from using Travis-CI because the OSX builds are just way
> too slow there.
> 
> Since more recent vms are working (see thread), any chance the vm for
> linux is updated on the pharo site so we can use Smalltalk-CI?
> 

Hi Johan,

I think there was some work to re-establish the vm distribution done
these days. See the result here:

https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/176

I hope this will help with the publication of a new stable VM. It is
also important for us at Synectique. To be able to have a 64bits linux
applications reliable would help us a lot in the simplifications of our
processes. :)

I guess that it will still have to wait some time since it's the end of
the year and there must be a lot of people taking holidays.

> thx for an update
> Johan


-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France



signature.asc
Description: OpenPGP digital signature

Re: [Pharo-users] How to connect to DB2

[Andrei Stebakov]

Hi Stef

I already checked Garage, it doesn't have support for DB2. It used to have
support for odbc, but now it's deprecated.

Andrei

On Dec 22, 2017 15:11, "Stephane Ducasse"  wrote:

> Hi andrei
>
> I do not know the status of OBDC but you should know that code on
> squeaksource is in general quite old.
> Have a look at Garage which is a kind of JBDC.
>
> https://github.com/pharo-rdbms/garage
>
> You should probably have a version available via the catalog
>
> Stef
>
> On Fri, Dec 22, 2017 at 2:43 PM, Andrei Stebakov 
> wrote:
> > Hi Stef
> >
> > Gofer new
> >   squeaksource: 'ODBC';
> >   package: 'ConfigurationOfODBC'; load.
> >   (Smalltalk at: #ConfigurationOfODBC) load.
> >
> > When I execute the code above I got an exception doesNotUnderstand:
> > #selector in RBParser>>externalFunctionDeclaration. Looks like
> currentScope
> > variable is not defined.
> > Also if I install ODBC from the catalog it also fails.
> >
> > Andrei
> >
> >
> > On Fri, Dec 22, 2017 at 2:19 AM, Stephane Ducasse <
> stepharo.s...@gmail.com>
> > wrote:
> >>
> >> Hi andrei
> >>
> >> First welcome to this list.
> >> Second can you explain to us what is the experience that you did so
> >> that you can state that ODBC is broken in Pharo 6.1?
> >>
> >> Stef
> >>
> >> On Thu, Dec 21, 2017 at 11:48 PM, Andrei Stebakov 
> >> wrote:
> >> > Looks like ODBC is broken in Pharo 6.1.
> >> > What's the best way to get access to DB2 in Pharo?
> >> >
> >> >
> >>
> >
>
>

[Pharo-users] pharo 6.1 64bit segmentation fault on linux

[Johan Brichau]

Hi,

I’m also hitting this issue: 
https://pharo.fogbugz.com/f/cases/20737/Segmentation-fault-trying-to-load-code-into-a-64-bits-Pharo-6-1-Linux
 

Also reported here: 
http://forum.world.st/Pharo-6-1-64-bits-segmentation-fault-loading-code-on-Linux-td5034346.html
 


This stops us from using Travis-CI because the OSX builds are just way too slow 
there.

Since more recent vms are working (see thread), any chance the vm for linux is 
updated on the pharo site so we can use Smalltalk-CI?

thx for an update
Johan

Re: [Pharo-users] Learning Morphic

[Hilaire]

In the Pharo by Example book there is one chapter about Morphic. It is a 
good starter.


Regarding the use of Athens canvas there is no such doc. You can take a 
look at the internal of Roassal or DrGeo or any package using Athens for 
graphics rendering.


Morphic will be replaced by blocs


--
Dr. Geo
http://drgeo.eu

[Pharo-users] Learning Morphic

[T.D. Telford]

I am primarily interested in graphical shapes and bit maps (for fractals).  I 
want to put graphical shapes or bitmaps in a window or bordered area. I have 
not been very successful in finding documentation about how to do this in 
Morphic.  In contrast, I find the documentation for Roassal easy to find and to 
the point.  Perhaps someone could point me to Morphic documentation (or supply 
examples) on my area of interest that includes a lot of examples. Thanks.

Re: [Pharo-users] Fuel transfer from Pharo 1.4 to Pharo 6.1

[Stephane Ducasse]

I would use STON because this is a solid solution.

Stef

On Tue, Nov 28, 2017 at 1:20 PM, Andreas Brodbeck  wrote:
> Am 28.11.17 um 11:13 schrieb H. Hirzel:
>> Hello Andreas
>>
>> Unfortunately Fuel is not meant for this kind of use case of migrating
>> an object model.
>
> That's sad to hear. From 1.4 to 6.1 is a big step, I agree, but I really
> thought that Fuel can be considered as a good "transport vehicle" at
> least for small steps like from Pharo 5 to 6.
>
>>
>> So other options have to be considered.
>
> That probably would be a custom mechanism storing objects in a database
> or fileformat and re-import, I think. Lots of work and very error prone.
> But maybe the only way unfortunately ...
>
> SIXX would be an option you think?
>
>>
>> Does your object model have cycles?
>
> Yes.
>
>
> Regards,
> Andreas
>
> --
> Andreas Brodbeck
> www.mindclue.ch
>
>

Re: [Pharo-users] Iceberg, Git and Package version

[Stephane Ducasse]

>From a baseline you can refer to a none github configuration

here is an example from the pillar newpipeline dev branch it shows you
both: dependencies on github projects and smalltalkhub


baseline: spec

spec
for: #common
do: [ spec blessing: #baseline.
spec repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main/'.
spec
baseline: 'OSSubprocess'
with: [ spec
repository: 'github://marianopeck/OSSubprocess:v0.2.5/repository' ];

   baseline: 'Mustache'
   with: [ spec repository: 'github://noha/mustache:v1.0/repository' ];

project: 'Cocoon'
with: [ spec
className: #ConfigurationOfCocoon;
versionString: #stable;
repository: 'http://smalltalkhub.com/mc/PharoExtras/Cocoon/main' ];

   project: 'JSON'
   with: [ spec
  className: #ConfigurationOfJSON;
  versionString: #stable;
  repository:
'http://smalltalkhub.com/mc/PharoExtras/JSON/main/' ];


project: 'LightPhaser'
with: [ spec
className: #ConfigurationOfLightPhaser;
versionString: '1.0.2';
repository: 'http://smalltalkhub.com/mc/Pier/LightPhaser/main/' ];
project: 'PetitParser'
with: [ spec
className: #ConfigurationOfPetitParser;
versionString: #stable;
loads: #('Tests');
repository: 'http://www.smalltalkhub.com/mc/Moose/PetitParser/main' ];
project: 'PetitParserTest'
with: [ spec
className: #ConfigurationOfPetitParser;
versionString: #stable;
loads: #('Tests');
repository: 'http://www.smalltalkhub.com/mc/Moose/PetitParser/main' ].
spec
package: 'Pillar-Cli' with: [ spec requires: #('Pillar-ExporterCore') ];
package: 'Pillar-Cli-PillarVersion' with: [ spec requires: #('Pillar-Cli') ];
package: #'Pillar-ExporterAsciiDoc'



On Thu, Dec 21, 2017 at 3:48 PM, Vitor Medina Cruz  wrote:
>> This is mostly true, but ATM you may want to wrap your BaselineOf in a
>> ConfigurationOf (i.e. refer to A with a SHA from B) for tool integration
>> e.g. only Configs show up in the catalog. IIUC, one additional constraint
>> to
>> be aware of (not sure how important it is in practice) is that in the past
>> with mcz repos, one could refer to a specific version of each package, but
>> now you would only be able to specify a version for the whole git repo.
>
>
> I was about to ask that after reading through Metacello docs — While I find
> usefull to define groups and dependencies at package level (I need only
> package A from ThatProject on version 2.6, cool!), I didn't understand why
> define version at package level If many dependencies exists to different
> versions of different packages belonged to the same project, doesn't that
> means (or is an indicative) that those packages should be separeted in
> different projects? I don't think this constraint will be a problem.
>
>
> On Thu, Dec 21, 2017 at 12:37 PM, Sean P. DeNigris 
> wrote:
>>
>> CyrilFerlicot wrote
>> >> Now I got lost
>>
>> A ConfigurationOfXyz was doing two things:
>> 1) Declaring the project structure of packages and their dependencies in a
>> #baselineXyz: method
>> 2) Tagging specific sets of package versions with meaning symbolic to the
>> project e.g. 1.2 or stable or whatever
>>
>>
>> CyrilFerlicot wrote
>> > So, you just need Metacello to manage the dependencies... This is what
>> > BaselineOf do. You just manage the dependencies part and
>> > not the versionning part that is already managed by git.
>>
>> A BaselineOfXyz is very similar to what configurations did for #1, with a
>> few simplifications (e.g. you don't need to declare the method a
>> "baseline"
>> or specify a repo because you obviously already know the repo because
>> that's
>> where you just got the baseline itself)
>>
>>
>> CyrilFerlicot wrote
>> > The equivalent of a ConfigurationOf version in now the SHA of a commit
>> > or
>> > a tag/release
>> > of git).
>>
>> This is mostly true, but ATM you may want to wrap your BaselineOf in a
>> ConfigurationOf (i.e. refer to A with a SHA from B) for tool integration
>> e.g. only Configs show up in the catalog. IIUC, one additional constraint
>> to
>> be aware of (not sure how important it is in practice) is that in the past
>> with mcz repos, one could refer to a specific version of each package, but
>> now you would only be able to specify a version for the whole git repo.
>>
>> HTH
>>
>>
>>
>> -
>> Cheers,
>> Sean
>> --
>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>
>

Re: [Pharo-users] How to connect to DB2

[Stephane Ducasse]

Hi andrei

I do not know the status of OBDC but you should know that code on
squeaksource is in general quite old.
Have a look at Garage which is a kind of JBDC.

https://github.com/pharo-rdbms/garage

You should probably have a version available via the catalog

Stef

On Fri, Dec 22, 2017 at 2:43 PM, Andrei Stebakov  wrote:
> Hi Stef
>
> Gofer new
>   squeaksource: 'ODBC';
>   package: 'ConfigurationOfODBC'; load.
>   (Smalltalk at: #ConfigurationOfODBC) load.
>
> When I execute the code above I got an exception doesNotUnderstand:
> #selector in RBParser>>externalFunctionDeclaration. Looks like currentScope
> variable is not defined.
> Also if I install ODBC from the catalog it also fails.
>
> Andrei
>
>
> On Fri, Dec 22, 2017 at 2:19 AM, Stephane Ducasse 
> wrote:
>>
>> Hi andrei
>>
>> First welcome to this list.
>> Second can you explain to us what is the experience that you did so
>> that you can state that ODBC is broken in Pharo 6.1?
>>
>> Stef
>>
>> On Thu, Dec 21, 2017 at 11:48 PM, Andrei Stebakov 
>> wrote:
>> > Looks like ODBC is broken in Pharo 6.1.
>> > What's the best way to get access to DB2 in Pharo?
>> >
>> >
>>
>

Re: [Pharo-users] NeoCSVWriter: how to output an empty quoted field

[Sven Van Caekenberghe]

Hi Joachim,

nil fields normally write as 'empty quoted fields':

String streamContents: [ :out | (NeoCSVWriter on: out) nextPut: #(nil nil nil) 
].

 => '"","",""'

Is this not what you want/need ?

Sven

> On 22 Dec 2017, at 15:05, jtuc...@objektfabrik.de wrote:
> 
> Hi,
> 
> I need to write a number of empty quoted fields in a CSV export. The 
> receiving application will complain about missing quotes for empty text 
> fields... (don't ask, I've done all the eye rolling for you already)
> 
> My frst attempt was:
> 
> writer addConstantField: '""'.
> 
> 
> But this doesn't write the quotes - I really don't see why, but it's the case.
> 
> Also, adding
> 
> writer addObjectField: [:a| '""'].
> 
> 
> doesn't really work, because it will literally add the double quotes between 
> single quotes... (???)
> 
> 
> 
> Do I really have to implement some method that returns an empty String on my 
> business objects and use:
> 
> writer addQuotedField: #justAnEmptyString. ?
> 
> Am I missing some switch to enable quotes for empty quoted fields?
> 
> My version of NeoCSVWriter on VA Smalltalk is not actually a current one...
> 
> 
> 
> Joachim
> 
> And, btw: Happy Holidays to all of you and a Happy new Year!
> 
> 
> 
> 
> -- 
> ---
> Objektfabrik Joachim Tuchel  mailto:jtuc...@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
> 
> 

[Pharo-users] NeoCSVWriter: how to output an empty quoted field

[jtuc...@objektfabrik.de]

Hi,

I need to write a number of empty quoted fields in a CSV export. The 
receiving application will complain about missing quotes for empty text 
fields... (don't ask, I've done all the eye rolling for you already)


My frst attempt was:

writer addConstantField: '""'.


But this doesn't write the quotes - I really don't see why, but it's the 
case.


Also, adding

writer addObjectField: [:a| '""'].


doesn't really work, because it will literally add the double quotes 
between single quotes... (???)




Do I really have to implement some method that returns an empty String 
on my business objects and use:


writer addQuotedField: #justAnEmptyString. ?

Am I missing some switch to enable quotes for empty quoted fields?

My version of NeoCSVWriter on VA Smalltalk is not actually a current one...



Joachim

And, btw: Happy Holidays to all of you and a Happy new Year!




--
---
Objektfabrik Joachim Tuchel  mailto:jtuc...@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

Re: [Pharo-users] How to connect to DB2

[Andrei Stebakov]

Hi Stef

Gofer new
  squeaksource: 'ODBC';
  package: 'ConfigurationOfODBC'; load.
  (Smalltalk at: #ConfigurationOfODBC) load.

When I execute the code above I got an exception doesNotUnderstand:
#selector in RBParser>>externalFunctionDeclaration. Looks like currentScope
variable is not defined.
Also if I install ODBC from the catalog it also fails.

Andrei


On Fri, Dec 22, 2017 at 2:19 AM, Stephane Ducasse 
wrote:

> Hi andrei
>
> First welcome to this list.
> Second can you explain to us what is the experience that you did so
> that you can state that ODBC is broken in Pharo 6.1?
>
> Stef
>
> On Thu, Dec 21, 2017 at 11:48 PM, Andrei Stebakov 
> wrote:
> > Looks like ODBC is broken in Pharo 6.1.
> > What's the best way to get access to DB2 in Pharo?
> >
> >
>
>

Re: [Pharo-users] Fuel serialize of 70MB takes forever on Linux vs. Mac

[Mariano Martinez Peck]

On Fri, Dec 22, 2017 at 9:40 AM, Andreas Brodbeck  wrote:

> Am 19.12.17 um 11:40 schrieb Andreas Brodbeck:
> > Am 18.12.17 um 20:45 schrieb Henrik-Nergaard:
> >
> > So: It's not the storage! It's something inside Fuel. I keep
> > investigating and will update here.
>
> ... so here are my latest findings:
>
> I took both images onto the same machine, a Mac. And these are the
> differences of the same Fuel serialization:
>
> *
> Fuel 2.1.10 Pharo 6.1 (#60520) 64bit: 90 seconds
> Fuel 2.1.10 Pharo 6.1 (#60527) 32bit: 245 seconds
> *
>
> For the record, here the versions of the two (equal) VMs:
>
> VM 32bit: 5.0 5.0.201707201942 Mac OS X built on Jul 20 2017 21:45:23
> UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)
> [Production Spur VM]
>
> VM 64bit: 5.0 5.0.201707201942 Mac OS X built on Jul 20 2017 21:08:05
> UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)
> [Production Spur 64-bit VM]
>
>
>
> I didn't expect the 64bit version to be a faster VM generally. What
> could be the reason here?
>
>
We have a special cluster for numbers that when they fit there, the
serialization is faster (see #clusterClassForSmallInteger:). If bigger than
the allowed range then it follows the slower kind of variable/indexed
object.
Another possibility could be Floats.
Can you check in your debug if you have a cluster (FLSmallIntegerCluster
subclass ) with MANY numbers?
Else, check with many floats..

I think it should be somehow related to that...

Cheers,




>
> Cheers, Andreas
>
> --
> Andreas Brodbeck
> www.mindclue.ch
>
>
>


-- 
Mariano
http://marianopeck.wordpress.com

Re: [Pharo-users] Fuel serialize of 70MB takes forever on Linux vs. Mac

[Andreas Brodbeck]

Am 19.12.17 um 11:40 schrieb Andreas Brodbeck:
> Am 18.12.17 um 20:45 schrieb Henrik-Nergaard:
> 
> So: It's not the storage! It's something inside Fuel. I keep
> investigating and will update here.

... so here are my latest findings:

I took both images onto the same machine, a Mac. And these are the
differences of the same Fuel serialization:

*
Fuel 2.1.10 Pharo 6.1 (#60520) 64bit: 90 seconds
Fuel 2.1.10 Pharo 6.1 (#60527) 32bit: 245 seconds
*

For the record, here the versions of the two (equal) VMs:

VM 32bit: 5.0 5.0.201707201942 Mac OS X built on Jul 20 2017 21:45:23
UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)
[Production Spur VM]

VM 64bit: 5.0 5.0.201707201942 Mac OS X built on Jul 20 2017 21:08:05
UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)
[Production Spur 64-bit VM]



I didn't expect the 64bit version to be a faster VM generally. What
could be the reason here?


Cheers, Andreas

-- 
Andreas Brodbeck
www.mindclue.ch

Re: [Pharo-users] [Pharo-dev] [ANN] Gemtalk Systems upgraded to Gold Membership

[Esteban Lorenzano]

thanks!

> On 22 Dec 2017, at 08:32, Marcus Denker  wrote:
> 
> The Pharo Consortium is very happy to announce that Gemtalk Systems
> has upgraded to Gold Member status.
> 
> About
> - Gemtalk Systems: https://gemtalksystems.com
> - Pharo Consortium: http://consortium.pharo.org
> 
> The goal of the Pharo Consortium is to allow companies and institutions to
> support the ongoing development and future of Pharo.
> 
> Individuals can support Pharo via the Pharo Association:
> 
> http://association.pharo.org
> 

Re: [Pharo-users] And Mac too Re: [ANN] OpenSSL-Pharo works on Windows

[Esteban Lorenzano]

> On 22 Dec 2017, at 07:57, Stephane Ducasse  wrote:
> 
> We appreciate it!

+1

> 
> 
> On Fri, Dec 22, 2017 at 3:38 AM, Pierce Ng  wrote:
>> On Wed, Dec 20, 2017 at 08:57:59PM +0100, Stephane Ducasse wrote:
>>> great news.
>>> And this is super great that you plan to work on different platforms!
>>> THANKS
>> 
>> This is my little way of giving back to Pharo and the community.
>> 
>> And now I have added #macModuleName to the library and tested it successfully
>> with 64-bit Pharo on my Mac that runs Sierra.
>> 
>> Pierce
>> 
>> 
> 

Re: [Pharo-users] [ANN] OpenSSL-Pharo works on Windows

[Norbert Hartl]

That is really great. SSL is really somthing important.

Well done!

Norbert

> Am 20.12.2017 um 08:55 schrieb Pierce Ng :
> 
> Hi all,
> 
> OpenSSL-Pharo now works on Windows. Tested on Windows 10 with a fresh 32-bit
> Pharo 6.1 zip package downloaded from pharo.org. On Windows this library uses
> libeay.dll which is bundled with the Pharo VM.
> 
>  Metacello new
>baseline: 'OpenSSL';
>smalltalkhubUser: 'PierceNg' project: 'OpenSSL-Pharo';
>load.
> 
> Pierce