- Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo Glorp 1.7 <-> VisualWorks

by stepharo

> Many of them are here, AFAIR they were Lorenzano, Polito, Peck. Paid by ESUG because we already wre convinced that databse support is important. > > Even with its outdated condition, ORM hasn't changed much in the past > years, so current GLORP fits most of the needs, it's proven, it's > tested and it's reliable. > > >> Where is the best place to ask about Glorp by the way? > I wonder the same. > > The official discussion group is > https://groups.google.com/forum/#!forum/glorp-group > But it is not very active. > > So IMHO, for Pharo use this is the best place, and for VisualWorks its > own mailing list. > > > Regards! > > > > Esteban. > >

Oct. 3, 2014

Re: [Pharo-users] invoking python from pharo

by kilon alios

Everything you done is correct. all this information you see in your terminal is debugging of error reporting. Python errors are send back to Pharo and trigger pharo debugger. So yes everything you see is to be expected. I use it to check that everything goes as planned with python execution. if you want to disable it just do the following Ephestos sendMessage: 'alogging = False'. It will stop typing / logging all this info and instead print what you want to print. Your can turn it back to true of course pyAtlas runs the python side as standalone so there is no need to use Blender , pyAtlas works both with py 2.7 and python 3 thanks for the information on how to download the py on the go. I will definetly integrate it. On Fri, Oct 3, 2014 at 10:40 PM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > I would use only the Python bridge but not the Blender features (Cube, > etc). Will be the Python bridge and parser contained in its own package? > > I have started from MinGW and evaluated > > Ephestos sendMessage: 'print("hello world")'. > Ephestos sendMessage: 'x = 3'. > Ephestos getValue: 'x'. > > $ python pyAtlas.py > creating thread > calling create_socket_connection > hello world > ('pherror : ', ['', 'no error\n']) > I have sent err : --->no error > <---- and removed it from the list of errors > ('pherror : ', ['', 'no error\n']) > I have sent err : --->no error > <---- and removed it from the list of errors > ('eval with pherror: ', ['', 'RetValue:3']) > ('pherror : ', ['', 'RetValue:3']) > I have sent err : --->RetValue:3 <---- and removed it from the list of > errors > > Is this expected? > > I don't know if there are other reasons but you could download the raw .py > file from > https://raw.githubusercontent.com/kilon/pyAtlas/master/pyatlas.py using > Metacello Configuration and start the script using OSProcess or > ProcessWrapper. This is how I do it for BioSmalltalk: > > >>... > spec for: #'common' do: [ > spec blessing: #'baseline'. > spec preLoadDoIt: #preLoad. > > >>preLoad > | urlIndex | > urlIndex := 1. > [ self downloadFiles: urlIndex ] > on: ZdcPluginMissing > do: [ : ex | > urlIndex := urlIndex + 1. > ex retry ]. > > >>downloadFiles: urlIndex > | url response | > url := (self platformFilesUrl at: urlIndex) asZnUrl. > fileRef := FileSystem disk workingDirectory / url pathSegments > last. > (response := ZnEasy get: url) isSuccess > ifTrue: [ fileRef writeStreamDo: [ : stream | stream nextPutAll: > response contents ] ] > ifFalse: [ self error: 'Cannot download files' ] > > >>platformFilesUrl > " Answer a <Collection> of download URLs for the current platform " > > ^ Smalltalk os isWin32 > ifTrue: [ #('http://...zip' > 'http://...zip') ] > ifFalse: [ #('http://....tar.gz' > 'http://....tar.gz') ]. > > Cheers, > > HernÃ¡n > > > > 2014-09-25 14:11 GMT-03:00 kilon alios <kilon.alios(a)gmail.com>: > > Hi there, I promised to do this a long time ago, but since you asked it I >> done it now. >> >> So as Ben said I am the author of Ephestos, a communication bridge >> between Blender and Pharo . >> >> To go directly to the how to . Ephestos is basically a socket bridge that >> send via sockets strings from pharo to python that then python executes as >> python commands. >> >> Ephestos is made so it works inside blender but I promised Atals a spin >> off project that allows the same socket bridge to be used as a standalone. >> To use do the following. >> >> 1) Get Ephestos , you can find it and install it with the configuration >> browser in your image in Pharo 3 and Pharo 4. Make sure you have a recent >> release though because I added it recently. >> >> 2) Get pyAtlas , this is the python side , you can get it from here --> >> https://github.com/kilon/pyAtlas >> >> 3) in your command line cd to the pyAtlas directory and execute : >> python3 pyAtlas.py >> >> 4) in Pharo you can now try any python code you want >> >> for example >> >> Ephestos sendMessage: 'print("hello world")'. >> Ephestos sendMessage: 'x = 3'. >> x := Ephestos getValue: 'x'. >> x inspect. >> >> Ephestos sendMessage: string, basically sends the python command to be >> executes while getValue: sends the command and returns a value as a string. >> >> you can use string 'exit' to close the socket bridge but this part is >> buggy as it seems to keep the binding of the sokcet active and I have to >> wait to clean it up in macos to reopen the bridge. >> >> You can also use pharo syntax and python errors will trigger the pharo >> debugger with a title the python error itself. >> >> You can find more information about Ephestos in my gitbook that can be >> read here >> >> https://www.gitbook.io/book/kilon/ephestos >> >> Also I forgot to add that sendMessage can send multiline strings , so its >> possible to send python class definitions and other stuff, you type the >> string exactly as you would type python code respecting whitespaces. If you >> want to execute loads of lines of python code then it would be better to >> put your code in a python module and do >> >> Ephestos sendMessage: 'import mymodule' >> >> assuming your module is called 'mymodule' , python import basically are >> executions of code. >> >> If you have any questions just ask. >> >> Bare in mind this is a socket bridge so its not ideal for sending >> thousands of messages per second and you may run into the occasional bug or >> two which I will fix if you report it. Nonetheless it should allow you to >> execute any kind of code and not just call python functions or python >> methods. >> >> >> >> On Thu, Sep 25, 2014 at 7:40 PM, Ben Coman <btc(a)openinworld.com> wrote: >> >>> Pablo R. Digonzelli wrote: >>> >>> Hi all , I need to invoke python rutines from Pharo. I need some >>> orientation about the best way to do it. >>> 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 >>> >>> >>> Search the [pharo-dev] list for Ephestos by kilon. >>> cheers -ben >>> >> >> >

Oct. 3, 2014

Re: [Pharo-users] Pharo Glorp 1.7 <-> VisualWorks

by stepharo

>> Unfortunately, we don't have the manpower to maintain such >> a beast, are there many people using glorp in production? With PostgresV2? > I am making a living out of two projects using GLORP+PostgresV2 since > almost a year. So me, and my company, depends on it. > > I'd join an community driven "ORM Task Force" for Pharo. IMHO merging > VW's and Pharo's version won't be an easy quest. > While debugging GLORP I learnt a few things about its internals, and I > think other users share the same learning process. > So I am willing to spend some time on this. :) At annecy 2013 I asked nail ross to organize a glorp tutorial and I gathered some text. what would be good is to have some chapters on Glorp (to complement the reddit.st chapter of sven. Getting a nice doc is a way to get more people and more interest. I can look for the files I have around. I cannot work on something I never used.

Oct. 3, 2014

Re: [Pharo-users] Glorp + NBSQLite3

by stepharo

On 24/9/14 18:17, Pierce Ng wrote: > Hello, > > I am pleased to report that I have gotten Glorp working with NBSQLite3 > enough to run Sven's Reddit.st. Cool what is NBSQLite3 (a nativeboost version)? Nice. Would be nice once you API stabilize that we get a chapter or on NBSQLite3 :) > > As mentioned in my blog post, there is more work to be done to get > Glorp fully integrated with NBSQLite3, but preliminary results are > encouraging. > > http://www.samadhiweb.com/blog/2014.09.24.glorp.nbsqlite3.html > > Pierce > > >

Oct. 3, 2014

Re: [Pharo-users] [ANN] JSON datatype support in PostgresV2 package

by Esteban A. Maringolo

2014-10-03 17:22 GMT-03:00 stepharo <stepharo(a)free.fr>: > > On 30/9/14 21:02, Esteban A. Maringolo wrote: >> >> As a side note to this discussion: >> >> Postgres Outperforms MongoDB and Ushers in New Developer Reality >> >> http://blogs.enterprisedb.com/2014/09/24/postgres-outperforms-mongodb-and-u… >> >> Maybe there could be a VoyagePostgresql alternative for anyone insterested >> ;-) > I would love now Voyage looks more for noSQL. IMHO NoSQL hype has already peaked, now it is settling at a more reasonable usage: a) document oriented, b) schemaless data, c) easy horizontal scaling. With PgSQL JSON you can achieve a) and b) pretty easily, having a single server if you already have data in it :) > Did you check ROE for RDB? Avi used it as a way to compose queries. It is the first time I hear about it. It isn't listed in SmalltalkHub. Regards! Esteban A. Maringolo

Oct. 3, 2014

Re: [Pharo-users] Parsing SQL in a Pharo system

by stepharo

Thanks for the information. May be Olivier could help us there. On 3/10/14 12:59, Pierce Ng wrote: > On Thu, Oct 02, 2014 at 03:43:05PM -0300, Esteban A. Maringolo wrote: >> Is the V2/V3 spec a PostgreSQL protocol spec or something made up in >> the Squeak community? > V2/V3 are PostgreSQL wire protocol versions. V3 supports parameter binding > and bulk copying, whereas V2 does not. > > There is some additional info at this squeak-dev thread: > > http://forum.world.st/Status-of-PostgresV3-td4780110.html > > Looking at the updated packages, there seems to be support in PostgresV3 (here > meaning the Smalltalk software) for parameter binding at the protocol level, > but the API does not provide any facility to use it. > > Pierce > >

Oct. 3, 2014

Re: [Pharo-users] Parsing SQL in a Pharo system

by stepharo

>> Do you really mean that the board is a kind of jerks and idiots that are >> lazy bastards? > Please slow down, I never, ever, suggested even remotely that. I know but do not say that the board is not interested. We just issue today a roadmap to inria and database is one of the items. >> If people that have interest in ORM do not help us how can make progress. >> When did you send a fix to Pharo? Remember Pharo is Yours. > I use it daily for my business, which on some aspects of its > technology stack like DB feels more like a bet than a safe decision. ??? > > I submitted a few commits to GLORP and PostgresV2 packages, does that count? Yes it does. This is important. >> Esteban is working like a mad on making sure that Spur is coming to us. >> May be we can say to esteban to stop Spur and 64 bits after and some >> VM bug fix and support for integrating better and .... >> to focus on Glorp and DBTalk. > I know, and I understand the priorities given the limited manpower. > That's why I mentioned I was making no demands, I was simply giving my opinion. Ok > Sept 30, subject "Better ORM tools/alternatives" I will check. Too busy with something else. > >>> I'm making no demands here, just giving my opinion about a "business >>> feature" (DBs) that I'd like better supported. >> This is on our roadmap. > Not in https://github.com/pharo-project/pharo-workingRoadmaps. No these ones are just random notes about what we should not forget. Like cleaning the huge mess in Fonts that produced mess in Roassal and Moose. > >> May pythoners are cooler than Pharoers when it comes to helping write code >> and documentation? > I have no idea, I don't participate in any Python community. > > But please consider that accusing me (or anybody) of treating you as > jerks or suggesting that if I don't send fixes I shouldn't emit > opinions is totally discouraging. OK I was in attacking mode. > > I know you're passionate and you live&love Pharo, and hence you speak > that way, and I can understand that, but even if I understand who, how > and why you're saying something it somehow hurts the feeling of > belonging to the community (to which I feel part of). Ok I will be nicer in the future. But my point is that the best way to help you is to start on what is important for you and try to make it work better. We can offer jenkins servers, disc space and some help but we cannot do everything. Stef

Oct. 3, 2014

Re: [Pharo-users] Parsing SQL in a Pharo system

by stepharo

On 3/10/14 14:32, Stephan Eggermont wrote: > PostgresV3-Core/Pool looks perfectly usable. > > There is > PG3Connection>>md5HashMessage: aString > > ^Smalltalk globals > at: #MD5 > ifPresent: [ :md5 | (md5 hashMessage: aString) hex asLowercase ] > ifAbsent: [ WebUtils md5Digest: aString ] > > Which works in Pharo 4, though WebUtils doesn't exist anymore. > Replacing it is trivial > > md5HashMessage: aString > > ^Smalltalk globals > at: #MD5 > ifPresent: [ :md5 | (md5 hashMessage: aString) hex asLowercase ] > ifAbsent: [ (Smalltalk globals at: #WebUtils) md5Digest: aString ] > What was webUtils? Because I would raise an error instead.

Oct. 3, 2014

Re: [Pharo-users] [ANN] JSON datatype support in PostgresV2 package

by stepharo

On 30/9/14 21:02, Esteban A. Maringolo wrote: > As a side note to this discussion: > > Postgres Outperforms MongoDB and Ushers in New Developer Reality > http://blogs.enterprisedb.com/2014/09/24/postgres-outperforms-mongodb-and-u… > > Maybe there could be a VoyagePostgresql alternative for anyone insterested ;-) I would love now Voyage looks more for noSQL. Did you check ROE for RDB? Avi used it as a way to compose queries. Stef > > > Regards! > > Esteban A. Maringolo > > > 2014-09-05 10:23 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: >> 2014-09-05 4:18 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>> On 04 Sep 2014, at 21:43, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> >>>> Even though I don't use PharoExtras/JSON for my daily JSON >>>> manipulation (I use Seaside-JSON and NeoJSON), I found it to be the >>>> most "modular"/"independent" JSON package out there. >>> I don't see how the JSON and NeoJSON package differ in that respect. NeoJSON has no dependencies. Could you explain this point ? >> My Bad, I didn't mean exactly that. >> When I wrote the above paragraph I thought NeoJSON required the >> specification of a schema and couldn't simply convert JSON strings to >> Dictionaries. >> >> The only thing I like about PharoExtras/JSON is the fact JsonObject >> allows its direct manipulation without having to use dictionary >> accessors, but still allowing for it (because JsonObject IS a >> Dictionary). >> >> We can perfectly replace it by NeoJSON. Mine was a proof of concept, >> which once I debugged through a lot types of PGPacket ended up being >> simpler than thought. Supporting parametrized statements with JSON is >> something I would like to check (I guess it is only text). Adding >> support to jsonb type is linear too on the client side, just replicate >> what I did for json. >> >> >> >> I did a quick benchmark comparing JSON parsers and NeoJSON gets >> slightly faster as the stream gets larger. I didn't profile them >> memorywise. >> >> 31bytes JSON: >> NeoJSON: 73,600 per second. >> JSON: 42,700 per second. >> WAJsonParser: 79,400 per second. >> >> 309bytes JSON: >> NeoJSON: 14,200 per second. >> JSON: 12,400 per second. >> WAJsonParser: 13,900 per second. >> >> 17215bytes JSON: >> NeoJSON: 277 per second. >> JSON: 194 per second. >> WAJsonParser: 255 per second. >> >> https://gist.github.com/eMaringolo/5e7c865188036faa7202#file-json-bench > >

Oct. 3, 2014

Re: [Pharo-users] Pharo days: date proposal

by stepharo

thanks so we will communicate and set up all the boring ticketing and web page I guess.... On 2/10/14 18:30, Stephan Eggermont wrote: > That combines well with FOSDEM, which is the next two days in Bruxelles. > Yesterday I got a mail that we'll be having a smalltalk room on Sunday. > > Stephan > >

Oct. 3, 2014