- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] method Quest :)

by Max Leske

On 13.03.2014, at 08:52, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > Hi guys > > I need the following behavior and I started to implement it (but Iâm not sure that I implemented in a good way). > But may be this method already exist. > > testDiffs > "self run: #testDiffs" > > self assert: (#(a b c d e f) diff: #(a b z k)) equals: {#(c d e f) . #(z k)}. isnât that the same as you would get with #difference:? > > Stef

March 13, 2014

method Quest :)

by Pharo4Stef

Hi guys I need the following behavior and I started to implement it (but Iâm not sure that I implemented in a good way). But may be this method already exist. testDiffs "self run: #testDiffs" self assert: (#(a b c d e f) diff: #(a b z k)) equals: {#(c d e f) . #(z k)}. Stef

March 13, 2014

Re: [Pharo-dev] [ANN] Merchant - a credit card processing library

by Pharo4Stef

Thanks this is nice to see all these packages getting exposure On 12 Mar 2014, at 22:01, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hi there, > > actually this was announced a long ago, but we moved it to github: > https://github.com/sebastianconcept/Merchant > > Also available in Pharo's ConfigurationOf.. catalog Hourrayyyy. > > It might be useful for other people > > sebastian > > o/ >

March 13, 2014

Re: [Pharo-dev] [ANN] Merchant - a credit card processing library

by Max Leske

Thanks Sebastien Iâll let your know if we use it. And Svenâs right: beautiful! Max On 13.03.2014, at 03:12, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > > On Mar 12, 2014, at 7:15 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> To answer my own question (RTFMâ¦): >> >> "This is a credit card processing library. I needed this for airflowing an application from flowing.â >> >> Where âairflowingâ and âflowingâ link to http://airflowing.com/ and http://flowingconcept.com/ respectively. >> >> >> On 12.03.2014, at 23:12, Max Leske <maxleske(a)gmail.com> wrote: >> >>> Thanks Sebastian, very cool! >>> >>> Do you use it in production, or know of anyone who does? We might want to use it too. > > > Forgot to mention that before doing it, I did took a look at ActiveMerchant which seems to be what Shopify uses: > http://activemerchant.org/ > > But yeah, thatâs right. We use it in airflowing > > Also in flowingâs invoice system for the consulting services we also do :D > > All over https and never saving credit cards info (only the gatewayâs token of the authorised cards, the sensible data only touches RAM and gets a nice nil on the instVar after the gateway's result) > > We could authorise and capture on debit cards too but the gateway weâre using has debit only for brazilian cards and doesnât provide the international debit feature (which seems to be kind of a big deal for vendors and banks) > > Let me know if you want to extend its API to your gateway, just push the merge requests. > > Here... this is how our invoice system looks: > <flowingInvoice.png>

March 13, 2014

Re: [Pharo-dev] [ANN] Merchant - a credit card processing library

by Sven Van Caekenberghe

On 13 Mar 2014, at 03:12, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > > On Mar 12, 2014, at 7:15 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> To answer my own question (RTFMâ¦): >> >> "This is a credit card processing library. I needed this for airflowing an application from flowing.â >> >> Where âairflowingâ and âflowingâ link to http://airflowing.com/ and http://flowingconcept.com/ respectively. >> >> >> On 12.03.2014, at 23:12, Max Leske <maxleske(a)gmail.com> wrote: >> >>> Thanks Sebastian, very cool! >>> >>> Do you use it in production, or know of anyone who does? We might want to use it too. > > > Forgot to mention that before doing it, I did took a look at ActiveMerchant which seems to be what Shopify uses: > http://activemerchant.org/ > > But yeah, thatâs right. We use it in airflowing > > Also in flowingâs invoice system for the consulting services we also do :D > > All over https and never saving credit cards info (only the gatewayâs token of the authorised cards, the sensible data only touches RAM and gets a nice nil on the instVar after the gateway's result) > > We could authorise and capture on debit cards too but the gateway weâre using has debit only for brazilian cards and doesnât provide the international debit feature (which seems to be kind of a big deal for vendors and banks) > > Let me know if you want to extend its API to your gateway, just push the merge requests. > > Here... this is how our invoice system looks: > <flowingInvoice.png> That looks really beautiful !

March 13, 2014

Re: [Pharo-dev] [ANN] Merchant - a credit card processing library

by Sebastian Sastre

On Mar 12, 2014, at 7:15 PM, Max Leske <maxleske(a)gmail.com> wrote: > To answer my own question (RTFMâ¦): > > "This is a credit card processing library. I needed this for airflowing an application from flowing.â > > Where âairflowingâ and âflowingâ link to http://airflowing.com/ and http://flowingconcept.com/ respectively. > > > On 12.03.2014, at 23:12, Max Leske <maxleske(a)gmail.com> wrote: > >> Thanks Sebastian, very cool! >> >> Do you use it in production, or know of anyone who does? We might want to use it too. Forgot to mention that before doing it, I did took a look at ActiveMerchant which seems to be what Shopify uses: http://activemerchant.org/ But yeah, thatâs right. We use it in airflowing Also in flowingâs invoice system for the consulting services we also do :D All over https and never saving credit cards info (only the gatewayâs token of the authorised cards, the sensible data only touches RAM and gets a nice nil on the instVar after the gateway's result) We could authorise and capture on debit cards too but the gateway weâre using has debit only for brazilian cards and doesnât provide the international debit feature (which seems to be kind of a big deal for vendors and banks) Let me know if you want to extend its API to your gateway, just push the merge requests. Here... this is how our invoice system looks:

March 13, 2014

ZnClient error - stream next gives nil --> MNU on <

by phil＠highoctane.be

https://pharo.fogbugz.com/default.asp?13069

March 12, 2014

Re: [Pharo-dev] Sort by property

by Nicolas Cellier

It's ultra-easy to port, I gave it a try at MCHttpRepository location: 'http://smalltalkhub.com/mc/nice/NiceVMExperiments/main' user: '' password: '' See packages TAG-SortFunctions and TAG-SortFunctionsTests Travis didn't mention the license, so we'll have to ask him. 2014-03-12 13:52 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > Is this multisort feature available for Pharo somewhere? > > Regards! > > > Esteban A. Maringolo > > > 2014-03-12 7:45 GMT-03:00 Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com>: > > I presume you all know about Griggs work on the subject > > > > > http://stackoverflow.com/questions/8204826/smalltalk-sort-a-collection-by-t… > > http://objology.blogspot.com/2010/11/tag-sortfunctions.html > > > > > > 2014-03-12 11:23 GMT+01:00 carlo.t <snoobabk(a)yahoo.ie>: > > > >> Hi Otto > >> > >> I think the main reason is to support the second usage scenario: > >> SequenceableCollection withAllSubclasses sortedAs: [:class | class > >> methodDict size]. > >> We could try and unify the sort: method to take only blocks while > >> sortedAs: > >> a symbol but then at the same time we could just put everything into one > >> method and use cull: perhaps to handle all the scenarios. > >> > >> Personally I don't feel too comfortable with the code below, apart from > >> the > >> performance penalties it also feels like code that is too 'clever' for > >> itself which obviously makes it complicated to understand and modify. I > >> wrote it mainly for people to voice opinions and get ideas flowing. I'd > >> have > >> 2 separate sort methods so that users can choose if they want the > runtime > >> characteristics of either. > >> > >> Example which can handle all current scenarios i.e. symbol or block > taking > >> 1 > >> or 2 arguments: > >> SequenceableCollection>>sort: aSortBlock > >> self > >> mergeSortFrom: 1 > >> to: self size > >> by: (self createSortBlock: aSortBlock) > >> > >> > >> SequenceableCollection>>createSortBlock: aSortBlockOrSymbol > >> ^ aSortBlockOrSymbol numArgs < 2 > >> ifTrue: [[ :a :b | (#(true false ) > >> includes: (aSortBlockOrSymbol > >> value: a)) > >> ifTrue: [ aSortBlockOrSymbol value: a] > >> ifFalse: [(aSortBlockOrSymbol value: a) > < > >> (aSortBlockOrSymbol value: > >> b)]]] > >> ifFalse: [[:a :b | aSortBlockOrSymbol cull: a cull: b]] > >> > >> > >> BTW the previous versions had a bug where it fails when called on an > empty > >> collection as the true/false check is done eagerly. > >> > >> Cheers > >> Carlo > >> > >> > >> > >> -- > >> View this message in context: > >> http://forum.world.st/Sort-by-property-tp4748500p4748757.html > >> Sent from the Pharo Smalltalk Developers mailing list archive at > >> Nabble.com. > >> > > > >

March 12, 2014

Re: [Pharo-dev] [ANN] Merchant - a credit card processing library

by Max Leske

To answer my own question (RTFMâ¦): "This is a credit card processing library. I needed this for airflowing an application from flowing.â Where âairflowingâ and âflowingâ link to http://airflowing.com/ and http://flowingconcept.com/ respectively. On 12.03.2014, at 23:12, Max Leske <maxleske(a)gmail.com> wrote: > Thanks Sebastian, very cool! > > Do you use it in production, or know of anyone who does? We might want to use it too. > > Cheers, > Max > > > On 12.03.2014, at 22:01, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> Hi there, >> >> actually this was announced a long ago, but we moved it to github: >> https://github.com/sebastianconcept/Merchant >> >> Also available in Pharo's ConfigurationOf.. catalog >> >> It might be useful for other people >> >> sebastian >> >> o/ >> >

March 12, 2014

Re: [Pharo-dev] [ANN] Merchant - a credit card processing library

by Max Leske

Thanks Sebastian, very cool! Do you use it in production, or know of anyone who does? We might want to use it too. Cheers, Max On 12.03.2014, at 22:01, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hi there, > > actually this was announced a long ago, but we moved it to github: > https://github.com/sebastianconcept/Merchant > > Also available in Pharo's ConfigurationOf.. catalog > > It might be useful for other people > > sebastian > > o/ >

March 12, 2014