# |
Jul 17th 2009, 10:25 |
ProLoser|Work |
since acl would be more versatile |
# |
Jul 17th 2009, 10:25 |
ProLoser|Work |
or at least auth + acl |
# |
Jul 17th 2009, 10:24 |
ProLoser|Work |
is it definately a bad idea to bundle auth into a plugin? |
# |
Jul 17th 2009, 10:05 |
ProLoser|Work |
what do u need it for? |
# |
Jul 17th 2009, 10:03 |
gravyface |
where's the bakery 1.0 source? svn? |
# |
Jul 17th 2009, 09:40 |
ProLoser|Work |
no real os/specs/browser limitation |
# |
Jul 17th 2009, 09:40 |
ProLoser|Work |
but etherpad is a very nice fall back |
# |
Jul 17th 2009, 09:40 |
ProLoser|Work |
i definately agree |
# |
Jul 17th 2009, 09:40 |
techno-geek |
seems a lot more useful |
# |
Jul 17th 2009, 09:40 |
techno-geek |
I still would rather get cola working in eclipse |
# |
Jul 17th 2009, 09:39 |
ProLoser|Work |
only reason i ask is cuz i thought it would be helpful if you guys knew about this: etherpad.com |
# |
Jul 17th 2009, 09:38 |
ProLoser|Work |
or anyone know? |
# |
Jul 17th 2009, 09:38 |
ProLoser|Work |
gwoo or markstory? |
# |
Jul 17th 2009, 09:38 |
ProLoser|Work |
if anyone knows? |
# |
Jul 17th 2009, 09:37 |
ProLoser|Work |
who gave the speech on 2 person programming btw? |
# |
Jul 17th 2009, 09:37 |
ProLoser|Work |
i still say we get more people to work on this though |
# |
Jul 17th 2009, 09:36 |
ProLoser|Work |
but it does decrease plugin encapsulated modularity |
# |
Jul 17th 2009, 09:36 |
ProLoser|Work |
i understand, only reason why i'd consider making it 1 whole plugin package is you can call the pieces and use them individually out of the package, without even using the package |
# |
Jul 17th 2009, 09:35 |
techno-geek |
let people pick exactly what functionality they want |
# |
Jul 17th 2009, 09:35 |
techno-geek |
Id rather bundle everything separately |
# |
Jul 17th 2009, 09:35 |
ProLoser|Work |
which works for me too :) |
# |
Jul 17th 2009, 09:34 |
ProLoser|Work |
unless all this is going together in 1 plugin, along with the session component and helper |
# |
Jul 17th 2009, 09:34 |
ProLoser|Work |
i like that appraoch, and those can be bundled into another plugin |
# |
Jul 17th 2009, 09:34 |
ProLoser|Work |
lemme know when you got that ready, if it's 1 method and all of it simply interacts with authorize i may just take the time personally to move it into datasources + behavior |
# |
Jul 17th 2009, 09:33 |
techno-geek |
anyway back to work |
# |
Jul 17th 2009, 09:33 |
ProLoser|Work |
okay |
# |
Jul 17th 2009, 09:32 |
techno-geek |
it just has a processPayment($data = array()) method |
# |
Jul 17th 2009, 09:32 |
techno-geek |
yes |
# |
Jul 17th 2009, 09:32 |
techno-geek |
just got to make sure its worth the time |
# |
Jul 17th 2009, 09:32 |
ProLoser|Work |
but it's still a component right? |
# |
Jul 17th 2009, 09:32 |
techno-geek |
we can evolve it anyway we see fit |
# |
Jul 17th 2009, 09:31 |
ProLoser|Work |
like the datasources+behavior approach |
# |
Jul 17th 2009, 09:30 |
ProLoser|Work |
so we don't want to create a common pass-through for all the payment gateways? |
# |
Jul 17th 2009, 09:30 |
ProLoser|Work |
this one: http://bakery.cakephp.org/articles/view/authorize-net-aim-integration-component ? |
# |
Jul 17th 2009, 09:30 |
techno-geek |
well I also standardized the input so that it works in the way that would be expected from the cart component |
# |
Jul 17th 2009, 09:29 |
ProLoser|Work |
that's all? |
# |
Jul 17th 2009, 09:29 |
techno-geek |
I can probably get it to you later too |
# |
Jul 17th 2009, 09:29 |
techno-geek |
I am using the Authorize.net component from the bakery, except I modified it to remove some errors and add a little bit extra logic to it for test mode, etc. |
# |
Jul 17th 2009, 09:28 |
ProLoser|Work |
when can i see the payment gateway code? |
# |
Jul 17th 2009, 09:28 |
techno-geek |
its coming along well. I ran it by a co-worker and he was happy with our ideas as well |
# |
Jul 17th 2009, 09:28 |
techno-geek |
yeah. just the re-work with the new array structure |