Re: [Pharo-users] Any perspective of Woden in Pharo 6.1/7 ?????

2018-01-12 Thread casimiro barreto 
Will try. Currently on 2 projects involving pharo. The most pressing one is
a system for the calculation of uncertainties in measures. This system is
part of a homologation system for smart card readers and smart card chips.
The other is a simulation system that´s under non disclosure clause. Woden
would be used in a third incoming project (simulations in crowd management
in airports).

Best regards,

Casimiro

2018-01-10 19:43 GMT-02:00 Alexandre Bergel :

> Hi Casimiro!
>
> Sorry for the late reply.
> We do have a working version of Woden for Pharo 7.
> It would be great if you could try.
> https://github.com/ronsaldo/woden2
>
> On OSX, I did:
> -=-=-=-=-=-=-=-=-=
> git clone https://github.com/ronsaldo/woden2.git
> cd woden2
> ./loadWoden2.sh
> -=-=-=-=-=-=-=-=-=
>
> It takes time to install & compile (~ 10 minutes?), but it works well
>
> Alexandre
>
>
> > On Jan 2, 2018, at 5:21 AM, Casimiro - GMAIL 
> wrote:
> >
> > Is there any perspective of Woden working in Pharo 6.1 or later versions
> (7)
> >
> > Best regards,
> >
> >
> > Casimiro
> > --
> > The information contained in this message is confidential and intended
> to the recipients specified in the headers. If you received this message by
> error, notify the sender immediately. The unauthorized use, disclosure,
> copy or alteration of this message are strictly forbidden and subjected to
> civil and criminal sanctions.
> >
> > ==
> >
> > This email may be signed using PGP key ID: 0x4134A417
>
>


-- 
The information contained in this message is confidential and
intended to the recipients specified in the headers. If you received
this message by error, notify the sender immediately. The
unauthorized use, disclosure, copy or alteration of this message
are strictly forbidden and subjected to civil and criminal sanctions.

[Pharo-users] Internationalization

2017-10-15 Thread casimiro barreto 
Hello,

I´m using seaside & have some trouble regarding dates (displayed in
English). What´s the easy way to display dates in other languages?
Particularly dateInput shows dates in English format (month, day, year) and
months in English.

Best regards,

Casimiro

-- 
The information contained in this message is confidential and
intended to the recipients specified in the headers. If you received
this message by error, notify the sender immediately. The
unauthorized use, disclosure, copy or alteration of this message
are strictly forbidden and subjected to civil and criminal sanctions.

Re: [Pharo-users] Help with Garage and sanitized strings

2017-09-19 Thread casimiro barreto 
Problem solved. Question marks shouldn´t be inside apostrophes

'SELECT * FROM chaves_de_encriptacao WHERE numero_funcional = ?'

and not:

'SELECT * FROM chaves_de_encriptacao WHERE numero_funcional = ''?'''


2017-09-18 20:11 GMT-03:00 Casimiro de Almeida Barreto <
casimiro.barr...@gmail.com>:

> By the way, the following script fails with the same Exception
> (mysql_stmt_send_long_data):
>
> | db str sttmt |
>
> db := GADriver
> connectToConnectionString:
> 'mysql://localhost:3306/leaincertezas?user=learoot&password=welcomeLEA'.
>
> str := 'INSERT INTO chaves_de_encriptacao (numero_funcional,
> chave_privada, chave_publica) VALUES (''?'', ''?'', ''?'')'.
>
> sttmt := db prepare: str.
> sttmt at: 1 bind: '10'.
> sttmt at: 2 bind: '0BC0DE0FG32A128AB2EF01'.
> sttmt at: 3 bind: 'BEC0D01279F92123FAB2E0'.
>
> sttmt execute.
>
> db close.
>
> But the script:
>
> | db str sttmt |
>
> db := GADriver
> connectToConnectionString:
> 'mysql://localhost:3306/leaincertezas?user=learoot&password=welcomeLEA'.
>
> str := 'INSERT INTO chaves_de_encriptacao (numero_funcional,
> chave_privada, chave_publica) VALUES (''10'', ''0BC0DE0FG32A128AB2EF01'',
> ''0BC0DE0FG32A128AB2EF01'')'.
>
> db execute: str.
>
> db close.
>
> Results:
>
> MariaDB [leaincertezas]> SELECT * FROM chaves_de_encriptacao;
> +--+++
> | numero_funcional | chave_privada  | chave_publica  |
> +--+++
> |   10 | 0BC0DE0FG32A128AB2EF01 | 0BC0DE0FG32A128AB2EF01 |
> +--+++
> 1 row in set (0.00 sec)
>
>


-- 
The information contained in this message is confidential and
intended to the recipients specified in the headers. If you received
this message by error, notify the sender immediately. The
unauthorized use, disclosure, copy or alteration of this message
are strictly forbidden and subjected to civil and criminal sanctions.

Re: [Pharo-users] Pharo crashing under new Fedora 24 (64bits plus 32bits libraries)

2016-06-24 Thread casimiro barreto 
It is a Samsung with NVIDIA but Optimus ... And primusrun won't work
because of dynamically linked libraries
Em 23/06/2016 23:27, "Renaud de Villemeur" 
escreveu:

> Hi.
>
> Pharo5 can run properly on Fedora 24, with Seaside3.2, OpenGL, or default
> image.
> What kind of graphic card do you have ? Is it a NVidia ? The default
> driver in Fedora, "Nouveau", is 64 bit only. I had to install the
> proprietary NVidia driver lib in 32 bit to be able to run pharo, They are
> still from fedora 23, as rpm-fusion didn't update its repo yet
> (xorg-x11-drv-nvidia-cuda-358.16-2.fc23.i686 and
> xorg-x11-drv-nvidia-libs-358.16-2.fc23.i686).
>
> Here is a list of all 32 bits library I have. My system is not a fresh
> install, but Pharo is the only 32 bit apps, so I guess this list is quite
> accurate. Can you check if you have a similar list on your system ?
> $ rpm -qa | grep i686 | grep -v devel | sort -u
> alsa-lib-1.1.1-1.fc24.i686
> bzip2-libs-1.0.6-20.fc24.i686
> cairo-1.14.6-1.fc24.i686
> clang-libs-3.8.0-1.fc24.i686
> elfutils-libelf-0.166-2.fc24.i686
> expat-2.1.1-2.fc24.i686
> fontconfig-2.11.94-6.fc24.i686
> freetype-2.6.3-2.fc24.i686
> gamin-0.1.10-22.fc24.i686
> glib2-2.48.1-1.fc24.i686
> glibc-2.23.1-8.fc24.i686
> keyutils-libs-1.5.9-8.fc24.i686
> krb5-libs-1.14.1-6.fc24.i686
> libcom_err-1.42.13-4.fc24.i686
> libdrm-2.4.68-1.fc24.i686
> libedit-3.1-14.20150325cvs.fc24.i686
> libffi-3.1-9.fc24.i686
> libgcc-6.1.1-2.fc24.i686
> libICE-1.0.9-5.fc24.i686
> libpciaccess-0.13.4-3.fc24.i686
> libpng-1.6.23-1.fc24.i686
> libselinux-2.5-3.fc24.i686
> libsepol-2.5-3.fc24.i686
> libSM-1.2.2-4.fc24.i686
> libssh2-1.7.0-5.fc24.i686
> libstdc++-6.1.1-2.fc24.i686
> libuuid-2.28-3.fc24.i686
> libvdpau-1.1.1-3.fc24.i686
> libverto-0.2.6-6.fc24.i686
> libwayland-client-1.10.0-1.fc24.i686
> libwayland-server-1.10.0-1.fc24.i686
> libX11-1.6.3-3.fc24.i686
> libXau-1.0.8-6.fc24.i686
> libxcb-1.11.1-2.fc24.i686
> libXdamage-1.1.4-8.fc24.i686
> libXext-1.3.3-4.fc24.i686
> libXfixes-5.0.2-2.fc24.i686
> libXrender-0.9.9-3.fc24.i686
> libxshmfence-1.2-3.fc24.i686
> libXxf86vm-1.1.4-3.fc24.i686
> llvm-libs-3.8.0-1.fc24.i686
> mesa-libEGL-11.2.2-2.20160614.fc24.i686
> mesa-libgbm-11.2.2-2.20160614.fc24.i686
> mesa-libGL-11.2.2-2.20160614.fc24.i686
> mesa-libglapi-11.2.2-2.20160614.fc24.i686
> mesa-libOpenCL-11.2.2-2.20160614.fc24.i686
> ncurses-libs-6.0-5.20160116.fc24.i686
> nss-softokn-freebl-3.24.0-1.0.fc24.i686
> ocl-icd-2.2.8-3.git20151217.0122332.fc24.i686
> opencl-utils-1-2.svn16.fc24.i686
> openssl-libs-1.0.2h-1.fc24.i686
> pcre-8.39-2.fc24.i686
> pixman-0.34.0-2.fc24.i686
> pkgconfig-0.29-2.fc24.i686
> pyzy-0.1.0-12.fc24.i686
> readline-6.3-8.fc24.i686
> SDL2-2.0.4-4.fc24.i686
> sqlite-libs-3.11.0-3.fc24.i686
> xorg-x11-drv-nvidia-cuda-358.16-2.fc23.i686
> xorg-x11-drv-nvidia-libs-358.16-2.fc23.i686
> xz-libs-5.2.2-2.fc24.i686
> zlib-1.2.8-10.fc24.i686
>
> and for display:
>
> $ ldd vm-display-X11
> linux-gate.so.1 (0xf778f000)
> libpthread.so.0 => /lib/libpthread.so.0 (0xf7729000)
> libGL.so.1 => /usr/lib/nvidia/libGL.so.1 (0xf7622000)
> libX11.so.6 => /lib/libX11.so.6 (0xf74e1000)
> libc.so.6 => /lib/libc.so.6 (0xf7313000)
> /lib/ld-linux.so.2 (0x565d)
> libnvidia-tls.so.358.16 => /usr/lib/nvidia/tls/libnvidia-tls.so.358.16
> (0xf730d000)
> libnvidia-glcore.so.358.16 => /usr/lib/nvidia/libnvidia-glcore.so.358.16
> (0xf50b8000)
> libXext.so.6 => /lib/libXext.so.6 (0xf50a4000)
> libdl.so.2 => /lib/libdl.so.2 (0xf509f000)
> libxcb.so.1 => /lib/libxcb.so.1 (0xf5079000)
> libm.so.6 => /lib/libm.so.6 (0xf5022000)
> libXau.so.6 => /lib/libXau.so.6 (0xf501e000)
>
> Beware that under Fedora, SSL in Pharo is not available. I think that's a
> known issue, due to library mismatch: Pharo is compiled with openssl
> v1.0.0, while Fedora use v1.0.2h.
> $ ldd libSqueakSSL.so
> linux-gate.so.1 (0xf7754000)
> libssl.so.1.0.0 => not found
> libc.so.6 => /lib/libc.so.6 (0xf7551000)
> /lib/ld-linux.so.2 (0x5659f000)
>
> $ rpm -qa | grep ssl | grep i686 | grep -v devel
> openssl-libs-1.0.2h-1.fc24.i686
>
> $ rpm -ql openssl-libs.i686 | grep libssl | grep -v hmac
> /usr/lib/libssl.so.1.0.2h
> /usr/lib/libssl.so.10
>
> Regards
> Renaud
>
>
>
> 2016-06-23 16:31 GMT-04:00 Esteban Lorenzano :
>
>> I’m sorry, but this is not enough information… normally crash should let
>> a crash.dmp file… also a way to reproduce the problem would be cool… a
>> description of what you are doing, etc.
>>
>> cheers,
>> Esteban
>>
>>
>> On 23 Jun 2016, at 22:10, Casimiro - GMAIL 
>> wrote:
>>
>> Pharo 5 crashes. VM does a SIGSEGV 0x at start
>>
>> Running GDB I got:
>>
>> (gdb) run
>> Starting program: /home/CdAB63/Downloads/pharo5.0/bin/pharo
>> Missing separate debuginfos, use: dnf debuginfo-install
>> glibc-2.23.1-8.fc24.i686
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib64/libthread_db.so.1".
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x in ?? ()
>> (gdb) backtrace full
>> #0  0x00