Hi guys
I would like to add Smalltalk, Objects and Design to our free book
libraries and I do not have a pdf saver on mac for
google book
https://books.google.fr/books?id=W8_Une9cbbgC&printsec=frontcover&num=15&hl=fr#v=onepage&q&f=false
Could one of you give a try?
Thanks
Stef
really nice!
Le 9/1/15 23:37, Torsten Bergmann a écrit :
Hi,
I've rewritten, refactored, commented the Event Recorder. The most
visible feature is that the UI is now based on Spec to fit Pharo style.
Currently it can record and replay events. Saving and loading
of events as *.tape files is sti
The book is incomplete.
I will probably scan my version if I have one.
Le 10/1/15 09:52, stepharo a écrit :
Hi guys
I would like to add Smalltalk, Objects and Design to our free book
libraries and I do not have a pdf saver on mac for
google book
https://books.google.fr/books?id=W8_Une9cbbgC&
Apparently this book is still on sold :(
Le 10/1/15 09:52, stepharo a écrit :
Hi guys
I would like to add Smalltalk, Objects and Design to our free book
libraries and I do not have a pdf saver on mac for
google book
https://books.google.fr/books?id=W8_Une9cbbgC&printsec=frontcover&num=15&hl=
May be this is the time to improve this package :)
I'm sorry I have no DB experience.
As part of the consortium agenda for this year we have
- better ffi
- better db support
Stef
Le 10/1/15 02:06, David Carlos Manuelda a écrit :
I've installed and tested PostgresV2 under pharo with the
SQL support is very poor in Pharo and many improvements are necessary.
PostgresV2 is actually probably the best solution available because it is
written only in Pharo and works on many platforms. The framework does the
work but it's a limited solution.
Olivier ;-)
2015-01-10 10:09 GMT+01:00 steph
Stef wrote:
>May be this is the time to improve this package :)
>I'm sorry I have no DB experience.
>As part of the consortium agenda for this year we have
> - better ffi
> - better db support
Moving to Levente's PostgreSQLv3 and migrating that
might be a better idea. He has been usi
Le 10/1/15 10:59, Stephan Eggermont a écrit :
Stef wrote:
May be this is the time to improve this package :)
I'm sorry I have no DB experience.
As part of the consortium agenda for this year we have
- better ffi
- better db support
Moving to Levente's PostgreSQLv3 and migrating that
olivier I added
http://www.squeaksource.com/PostgresV3/
and the link sent by stefan to your table.
we should check if it is working in Pharo.
Stef
Le 10/1/15 10:46, olivier auverlot a écrit :
SQL support is very poor in Pharo and many improvements are necessary.
PostgresV2 is actu
Le 10/1/15 02:04, Atlas a écrit :
I used PluggableTextMorph instead and an override to vIsScrollbarNeeded.
However, it seems problem (4) is also present in the PluggableTextMorph
class. Also, there is no font change button for LabelItems in the morphic
menu.
Looking at the, sometimes rather obsc
p...@highoctane.be wrote:
> This was asked a while ago, here is what I could find:
>
> On 29/10/2013 9:32 PM, Yanni Chiu wrote:
>
>>
>> Looking at the postgres docs, I see PREPARE and EXECUTE. I'll try to
>> start up a postgres server, and see if I can get it to work.
>>
>
> Here's an example:
Thanks Stef, that's good to know.
It's certainly not an easy task, and I am glad that there is progress!
Thanks Alain!
--
View this message in context:
http://forum.world.st/TextMorph-broken-tp4798645p4798755.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Hi Carlos,
I have no (or very small) experience with Postgres, but I guess it
works the same as for Mssql Server and Oracle.
The way it works with Mssql MsSql (and Oracle) is:
Prepared statements are not shared between connections from the client
side, the gain is on the server side.
Use
I think I got the MorphTreeTransformMorph now working, need to clean up the
code
and maybe I 'll upload this to the athens repository.
nicolai
2015-01-08 12:27 GMT+01:00 Nicolai Hess :
> A new Version of the AthensWrapWorldMorph (useful for testing Athens based
> drawing for morphs). And some c
Hi,
Nice document, however, about ODBC support column,
looking at and old (Pharo 1.3) image I have on my pc, I can see:
ODBCLibray>>moduleName
"Return the name of the module for this library"
SmalltalkImage current platformName = 'Win32' ifTrue: [ ^ 'odbc32' ].
SmalltalkI
Some of you may already have noticed that it is already available but there
was not yet a formal announcement, so here it is:
There is a new way/project to work with the SQLite3 embeddable database.
While in the past there was already a SQLite wrapper project for Pharo based
on FFI this one is
Hi Stephan,
Very interesting !
It would be good to switch from the textual V2 protocol to the binary V3, not
only is it faster (or should it be faster), it has more features and it is more
modern (ie. the way forward).
Do you think is would make sense to separate the different layers (or maybe
Hi,
The challenge with Python parsing is dealing with whitespace properly.
Jan Kurs was working on such a parser. I do not know how advanced it is.
Jan?
Cheers,
Doru
On Fri, Jan 9, 2015 at 7:30 PM, kilon alios wrote:
> Hello guys I am learning PettitParser , I dowloaded the video tutorials
The V2 version of the protocol doesn't support prepared statements.
When we were writing the PostgresV3 package, we planned to implement
prepared statements (via the extended query protocol), but later we
decided to not do it.
Why?
The protocol is way more complex than the simple query proto
Le 10 janv. 2015 20:04, "Levente Uzonyi" a écrit :
>
> The V2 version of the protocol doesn't support prepared statements.
>
> When we were writing the PostgresV3 package, we planned to implement
prepared statements (via the extended query protocol), but later we decided
to not do it.
>
> Why?
>
>
there is also the python.ast model which gives the ability to parse the
python syntax ( I can use this model because of my communication bridge
with python) which I can use but if there is something already done with
petitparser I would love to take a look too.
The documentation of module is in t
Levente Uzonyi wrote:
> The V2 version of the protocol doesn't support prepared statements.
>
> When we were writing the PostgresV3 package, we planned to implement
> prepared statements (via the extended query protocol), but later we
> decided to not do it.
>
> Why?
>
> The protocol is way mor
You can achieve the same with functions. Here's an example for a method
representing a function in PostgresV3:
ExampleSchemaMirror >> add: a and: b
begin
return a + b;
end;
And here's how you call that function:
ExampleSchemaMirror default add: 3 and: 4. "==> 7"
Levente
On
There's no documentation yet, but the mail quoted by Stephan has detailed
description with examples:
http://forum.world.st/Status-of-PostgresV3-td4780110.html
Levente
On Sat, 10 Jan 2015, p...@highoctane.be wrote:
Le 10 janv. 2015 20:04, "Levente Uzonyi" a écrit :
>
> The V2 version of th
24 matches
Mail list logo
