- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Rubric: playing with selection

by StÃ©phane Ducasse

fun :) and continue because a good text editor will change our life On Jun 2, 2013, at 11:38 PM, plantec <alain.plantec(a)yahoo.com> wrote: > Hi all, > I've tried to manage the selection as a Morph. > I was curious to see if it was enough efficient. > and yes it is :) > http://vimeo.com/67516363 > Cheers > Alain > >

June 3, 2013

Re: [Pharo-dev] SOAP in Pharo

by phil＠highoctane.be

Easy answer to SOAP problems: IBM Datapower SOA Appliance. http://www-03.ibm.com/software/products/us/en/datapower/ I played with this one: http://www-03.ibm.com/software/products/us/en/datapower-xi50 Current stuff is http://article.wn.com/view/2013/04/29/SOA_Software_Enables_REST_Services_on… Short version: you shell out EUR 250K + IBM consulting fees and this translates whatever SOAP you want into something readable and it does it fast. Note: this is one of the hottest selling products of IBM at the moment, they ship it by the boatload to banks and organisations requiring heavy security/regulations. Putting Pharo behind this makes for a pretty good solution. Phil On Mon, Jun 3, 2013 at 7:31 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 03 Jun 2013, at 18:08, Norbert Hartl <norbert(a)hartl.name> wrote: > > > In order to use SOAP properly you need a full namespace aware xml > parser, a xml schema parser, a WSDL parser plus code generator and the will > to abuse HTTP completely . > > Even if you build a perfect tool you'll maybe face the not so perfect > responses from the remote side. > > Even using the Java stack with all its tools and frameworks, SOAP is still > terrible. Especially if you have to interface with Microsofts' idea of SOAP > and web services. > > But Johan implied already that it would not be fun. > > On the other hand, I think that XML Support _is_ namespace aware. So it > would not be too hard to actually generate/parse SOAP messages for real. > You could get already pretty far with that, IMHO. > > Sven > > PS: In another life I did http://common-lisp.net/project/cl-soap/ - it > was never perfect but it kind of worked to talk to Google AdWords. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > >

June 3, 2013

Re: [Pharo-dev] SOAP in Pharo

by Sven Van Caekenberghe

On 03 Jun 2013, at 18:08, Norbert Hartl <norbert(a)hartl.name> wrote: > In order to use SOAP properly you need a full namespace aware xml parser, a xml schema parser, a WSDL parser plus code generator and the will to abuse HTTP completely . > Even if you build a perfect tool you'll maybe face the not so perfect responses from the remote side. Even using the Java stack with all its tools and frameworks, SOAP is still terrible. Especially if you have to interface with Microsofts' idea of SOAP and web services. But Johan implied already that it would not be fun. On the other hand, I think that XML Support _is_ namespace aware. So it would not be too hard to actually generate/parse SOAP messages for real. You could get already pretty far with that, IMHO. Sven PS: In another life I did http://common-lisp.net/project/cl-soap/ - it was never perfect but it kind of worked to talk to Google AdWords. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

June 3, 2013

Re: [Pharo-dev] Bug in SmalltalkHub "delete package"

by Mariano Martinez Peck

On Fri, May 31, 2013 at 1:44 PM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Fri, May 31, 2013 at 5:48 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: > > Hi guys. I tried to remove a package from the "remove package" button in > the > > website. The package is indeed removed from the website, but if you take > a > > fresh image, add the repository and add it to monticello, you still can > see > > and browse the removed package.... > > > > any idea how to solve it? I need to remove packages for real... > > > please report the bug to > http://code.google.com/p/smalltalk-hub/issues/list with *precise* > steps and details on how to reproduce. > https://code.google.com/p/smalltalk-hub/issues/detail?id=25 > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- Mariano http://marianopeck.wordpress.com

June 3, 2013

Re: [Pharo-dev] SOAP in Pharo

by phil＠highoctane.be

I can perfectly understand the feeling :-) Phil On Mon, Jun 3, 2013 at 6:35 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 03.06.2013 um 18:14 schrieb "phil(a)highoctane.be" <phil(a)highoctane.be>: > > ah ah +1000! > > And WS-* with all kinds of crypto doesn't help! > > No, I'm done with it since that project I described > > > http://norbert.hartl.name/blog/2010/10/05/isnt-soap-supposed-to-make-it-cle… > > Norbert > > Le 3 juin 2013 18:09, "Norbert Hartl" <norbert(a)hartl.name> a Ã©crit : > >> >> Am 03.06.2013 um 15:46 schrieb Johan Brichau <johan(a)inceptive.be>: >> >> > Hi, >> > >> > I have the distinguished pleasure of needing to interface with a SOAP >> service from within Pharo Smalltalk. >> > >> > Currently taking a look at SoapOpera and iWSDL projects on Squeaksource. >> > These projects seem to be unchanged since 2010 and broken in Pharo 1.4 >> > >> > Probably I will be spending some time to bring these to life again in >> current Pharo, but if anyone has some better pointers to use, please let me >> know. >> > >> Welcome to the club! >> >> The short version is: I use SOAP templates ! (like a lot of people out >> there) >> >> In order to use SOAP properly you need a full namespace aware xml parser, >> a xml schema parser, a WSDL parser plus code generator and the will to >> abuse HTTP completely . >> Even if you build a perfect tool you'll maybe face the not so perfect >> responses from the remote side. So my strategy with SOAP since years is >> (advizable only if there isn't a huge API with a huge variance of >> parameters): >> >> - Create all needed SOAP calls with any tool and snapshot them >> - build a small templating tool to insert values >> - send the snippet with every misguided header/setup the remote side >> needs to operate >> - take the response and first thing is strip off SOAP envelope >> - parse the xml and use pastell or something like that to query values to >> build objects (using it this way even has a name to make it look more >> professional. It is called document oriented SOAP :) ) >> >> Sounds hackish? Sounds stupid? Yes, you are right, it is. But it is by >> far less stupid as SOAP is. >> >> Sorry but I had to write this :) >> >> Norbert >> >> >> >> >

June 3, 2013

Re: [Pharo-dev] SOAP in Pharo

by Norbert Hartl

Am 03.06.2013 um 18:14 schrieb "phil(a)highoctane.be" <phil(a)highoctane.be>: > ah ah +1000! > > And WS-* with all kinds of crypto doesn't help! > No, I'm done with it since that project I described http://norbert.hartl.name/blog/2010/10/05/isnt-soap-supposed-to-make-it-cle… Norbert > Le 3 juin 2013 18:09, "Norbert Hartl" <norbert(a)hartl.name> a Ã©crit : > > > Am 03.06.2013 um 15:46 schrieb Johan Brichau <johan(a)inceptive.be>: > > > Hi, > > > > I have the distinguished pleasure of needing to interface with a SOAP service from within Pharo Smalltalk. > > > > Currently taking a look at SoapOpera and iWSDL projects on Squeaksource. > > These projects seem to be unchanged since 2010 and broken in Pharo 1.4 > > > > Probably I will be spending some time to bring these to life again in current Pharo, but if anyone has some better pointers to use, please let me know. > > > Welcome to the club! > > The short version is: I use SOAP templates ! (like a lot of people out there) > > In order to use SOAP properly you need a full namespace aware xml parser, a xml schema parser, a WSDL parser plus code generator and the will to abuse HTTP completely . > Even if you build a perfect tool you'll maybe face the not so perfect responses from the remote side. So my strategy with SOAP since years is (advizable only if there isn't a huge API with a huge variance of parameters): > > - Create all needed SOAP calls with any tool and snapshot them > - build a small templating tool to insert values > - send the snippet with every misguided header/setup the remote side needs to operate > - take the response and first thing is strip off SOAP envelope > - parse the xml and use pastell or something like that to query values to build objects (using it this way even has a name to make it look more professional. It is called document oriented SOAP :) ) > > Sounds hackish? Sounds stupid? Yes, you are right, it is. But it is by far less stupid as SOAP is. > > Sorry but I had to write this :) > > Norbert > > >

June 3, 2013

Re: [Pharo-dev] SOAP in Pharo

by phil＠highoctane.be

ah ah +1000! And WS-* with all kinds of crypto doesn't help! Phil Le 3 juin 2013 18:09, "Norbert Hartl" <norbert(a)hartl.name> a Ã©crit : > > Am 03.06.2013 um 15:46 schrieb Johan Brichau <johan(a)inceptive.be>: > > > Hi, > > > > I have the distinguished pleasure of needing to interface with a SOAP > service from within Pharo Smalltalk. > > > > Currently taking a look at SoapOpera and iWSDL projects on Squeaksource. > > These projects seem to be unchanged since 2010 and broken in Pharo 1.4 > > > > Probably I will be spending some time to bring these to life again in > current Pharo, but if anyone has some better pointers to use, please let me > know. > > > Welcome to the club! > > The short version is: I use SOAP templates ! (like a lot of people out > there) > > In order to use SOAP properly you need a full namespace aware xml parser, > a xml schema parser, a WSDL parser plus code generator and the will to > abuse HTTP completely . > Even if you build a perfect tool you'll maybe face the not so perfect > responses from the remote side. So my strategy with SOAP since years is > (advizable only if there isn't a huge API with a huge variance of > parameters): > > - Create all needed SOAP calls with any tool and snapshot them > - build a small templating tool to insert values > - send the snippet with every misguided header/setup the remote side needs > to operate > - take the response and first thing is strip off SOAP envelope > - parse the xml and use pastell or something like that to query values to > build objects (using it this way even has a name to make it look more > professional. It is called document oriented SOAP :) ) > > Sounds hackish? Sounds stupid? Yes, you are right, it is. But it is by far > less stupid as SOAP is. > > Sorry but I had to write this :) > > Norbert > > > >

June 3, 2013

Re: [Pharo-dev] SOAP in Pharo

by Norbert Hartl

Am 03.06.2013 um 15:46 schrieb Johan Brichau <johan(a)inceptive.be>: > Hi, > > I have the distinguished pleasure of needing to interface with a SOAP service from within Pharo Smalltalk. > > Currently taking a look at SoapOpera and iWSDL projects on Squeaksource. > These projects seem to be unchanged since 2010 and broken in Pharo 1.4 > > Probably I will be spending some time to bring these to life again in current Pharo, but if anyone has some better pointers to use, please let me know. > Welcome to the club! The short version is: I use SOAP templates ! (like a lot of people out there) In order to use SOAP properly you need a full namespace aware xml parser, a xml schema parser, a WSDL parser plus code generator and the will to abuse HTTP completely . Even if you build a perfect tool you'll maybe face the not so perfect responses from the remote side. So my strategy with SOAP since years is (advizable only if there isn't a huge API with a huge variance of parameters): - Create all needed SOAP calls with any tool and snapshot them - build a small templating tool to insert values - send the snippet with every misguided header/setup the remote side needs to operate - take the response and first thing is strip off SOAP envelope - parse the xml and use pastell or something like that to query values to build objects (using it this way even has a name to make it look more professional. It is called document oriented SOAP :) ) Sounds hackish? Sounds stupid? Yes, you are right, it is. But it is by far less stupid as SOAP is. Sorry but I had to write this :) Norbert

June 3, 2013

Re: [Pharo-dev] WhatsUp from: 2013-06-03 until: 2013-06-16

by Igor Stasenko

On 3 June 2013 07:00, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > Mainly spent time synchronizing with team, discussing next steps and planning. So, the only significant thing, is - Fixed a bug in VM (thanks to Guillermo). > > ### What's next, until 2013-06-16 (*): > - start work on TxText , including: - review and understand new code - implement Athens renderer for it - look how we can plug it into system -- Best regards, Igor Stasenko.

June 3, 2013

Re: [Pharo-dev] WhatsUp from: 2013-06-03 until: 2013-06-16

by btc＠openinworld.com

phil(a)highoctane.be wrote: > ### Here's what I've been up to since the last WhatsUp: > > - Learned how to use Seaside-REST and use it in Amber > What reference material did you find useful ? cheers -ben

June 3, 2013