March 2014 - Pharo-dev - lists.pharo.org

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

[ANN] Merchant - a credit card processing library

by Sebastian Sastre

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] ComposableModel>>initialExtent

by Benjamin

Sounds good :P I will integrate it into Spec dev (I think itâs safer for now to not remove it into Pharo since itâs frozen) Ben On 12 Mar 2014, at 19:04, Laurent Laffont <laurent.laffont(a)gmail.com> wrote: > As far as I see, it seems safe to remove ComposableModel>>initialExtent .... Spec tests green, TWM tests green and I haven't seen any problem yet. What do you think ? > > Laurent > > > Le mercredi 12 mars 2014, 17:36:20 Benjamin a Ã©crit : >> The first answer is: >> ComposableModel was not a subclass of model at first :P >> >> >> Ben >> >> On 12 Mar 2014, at 13:09, Laurent Laffont <laurent.laffont(a)gmail.com> wrote: >> >>> Hi, >>> >>> I'm trying to have tests green for TWM. I found: >>> >>> ComposableModel>>initialExtent >>> ^ nil >>> >>> on superclass Model there's >>> >>> Model>>initialExtent >>> ^ RealEstateAgent standardWindowExtent >>> >>> that sounds good. So I don't understand why ComposableModel redefine #initialExtent to answer nil. Any explanation ? >>> >>> Laurent >>> >> >

March 12, 2014

Re: [Pharo-dev] Status of the VM?

by Eliot Miranda

On Wed, Mar 12, 2014 at 3:59 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > Hi Eliot, > > > Anyway, the interesting question to me is what are the advantages >>> of your approach? >>> >> >> One is interactivity. The tool supports drilling down to instruction >> level, which is good for critical code sequences such as method >> prolog. >> >> Another is comprehensibility. Because it can distinguish between >> generated machine code (specific methods and runtime routines), >> functions in the VM and other support code (including stuff like >> Linux on stack system call entry) one sees all activities in the VM >> presented meaningfully. >> > > That's of course important, I agree. But if one uses out-of-image tools, > this could be seen too, couldn't it? > If one uses tools like OProfile or cachegrind, all this data are > collected and available for analysis. There's no symbol table info in the executable for generated methods, so no. In those tools the data is just somewhere in memory, not ascribable to specific functions. Of course with my profiler I had to write that support. I don't know those other tools and so don't know if they allow import of labels to analyse jitted code. Brief googling seems to indicate that neither has support for labelling jitted code. Another is evolvability. Because it's written in smalltalk I can >> develop the tool quickly and do so while I'm using it. >> >> But this is because it's written in Smalltalk rather than because it > runs within the debugee/profilee, no? That's what I said, yes ;-) -- best, Eliot

March 12, 2014

Re: [Pharo-dev] ComposableModel>>initialExtent

by Laurent Laffont

As far as I see, it seems safe to remove ComposableModel>>initialExtent .... Spec tests green, TWM tests green and I haven't seen any problem yet. What do you think ? Laurent Le mercredi 12 mars 2014, 17:36:20 Benjamin a Ã©crit : > The first answer is: > ComposableModel was not a subclass of model at first :P > > > Ben > > On 12 Mar 2014, at 13:09, Laurent Laffont <laurent.laffont(a)gmail.com> wrote: > > > Hi, > > > > I'm trying to have tests green for TWM. I found: > > > > ComposableModel>>initialExtent > > ^ nil > > > > on superclass Model there's > > > > Model>>initialExtent > > ^ RealEstateAgent standardWindowExtent > > > > that sounds good. So I don't understand why ComposableModel redefine #initialExtent to answer nil. Any explanation ? > > > > Laurent > > >

March 12, 2014

Re: [Pharo-dev] [Pharo-users] Tiling Window Manager in 3.0: working but still issues with WorldMorph

by Laurent Laffont

Hi Phil, with latest ConfigurationOfTilingWindow manager World management (almost) works. Still a little display issue when creating a new world (need to change back and forth, seems to be some World repaint issue). I've also merged some experiments with GrowlMorph. Laurent Le mardi 11 mars 2014, 13:27:57 Laurent Laffont a Ã©crit : > Thanks a lot Phil. I will try to have a look. > > Laurent > > > Le samedi 8 mars 2014, 11:57:30 phil(a)highoctane.be a Ã©crit : > > TWM works in 3.0 after some work on icons and updating menus. > > > > Gofer new > > smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; > > configuration; > > load. > > > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: '3.0') > > load > > > > You can also use > > > > ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: > > #development) load > > > > but this will for sure change over time. > > > > There is the World management icon which is still there and it looks like > > it can create worlds but switching between them just breaks havoc. > > > > Maybe should we just remove that feature from TWM as 3.0 doesn't seem to be > > multiworld friendly. > > > > Nothing done on tests nor themeing (which appears to be not that working > > well in 3.0 either due to theming changes); > > > > At least the thing is back :-) [I missed it...] > > > > Phil > >

March 12, 2014