Push ruby19 support

[joneslee85]

I believe everyone here understands how different between ruby18 and
ruby19 and what advantages ruby19 offers over ruby18. Rails community
is working hard to push support for ruby19 and Rails 3.0 will still
use 1.8.7 but prefer ruby 1.9.2. Romul's been working on spree ruby19
support, however the progress is slow. I believe this is because of
lacking resources and contributions from our community. So IMHO should
Spree community organize a bug hunt day for ruby19 support would
benefits ruby19 developers out there and help Spree to stay on par
with Rails development.

[Sean Schofield]

What issues still need to be solved for Ruby 1.9? My understanding is
that there were only a couple of minor sticking points. Its also
annoying that active merchant is not updating anytime soon (it
appears) and they have a perfectly good Ruby 1.9 fix in their edge
code.

Has anyone looked in depth at the active merchant issue? I was really
hoping we could use a hack plugin to "patch" the latest official
active merchant plugin. How feasible is that? Or are the fixes
scattered throughout?

Sean Schofield

-------------------------------------------
Rails Dog LLC
2 Wisconsin Circle, Suite 700
Chevy Chase, MD 20815
voice: (301)560-2000
-------------------------------------------

[Roman Smirnov]

1) We are waiting for release ActiveMerchant 1.4.3 with support for
Ruby 1.9
2) RoR 2.3.4 still have many nonASCII problems with work on Ruby 1.9,
in the first place is:
* Incorrect work of the MySQL driver with nonASCII encodings
* ERB bugs with nonASCII enciodings
So for fully support Ruby 1.9 we should to wait for a new version of
RoR, and hope that it will fix the existing bugs

As for Spree-Core, there is not revealed any not patched bugs in the
work with Ruby 1.9

[Roman Smirnov]

> Has anyone looked in depth at the active merchant issue? How feasible is that? Or are the fixes scattered throughout?

They skipped magic-comments in several files. In principle, we can try
to put only those files in the spree/lib, perhaps it will help avoid
the using of ActiveMerchant as plugin. But I do not see much point at
this juncture.

On Nov 4, 5:44 pm, Sean Schofield <s...@railsdog.com> wrote:
> What issues still need to be solved for Ruby 1.9?  My understanding is
> that there were only a couple of minor sticking points.  Its also
> annoying that active merchant is not updating anytime soon (it
> appears) and they have a perfectly good Ruby 1.9 fix in their edge
> code.
>
> Has anyone looked in depth at the active merchant issue?  I was really
> hoping we could use a hack plugin to "patch" the latest official
> active merchant plugin.  How feasible is that?   Or are the fixes
> scattered throughout?
>
> Sean Schofield
>
> -------------------------------------------
> Rails Dog LLC
> 2 Wisconsin Circle, Suite 700
> Chevy Chase, MD 20815
> voice: (301)560-2000
> -------------------------------------------
>

[Marcos Luis Ortiz Valmaseda]

Why is needed this gem?
Which is its use on Spree?


"The hurry is enemy of the success: for that reason.......Be patient"

Ing. Marcos L. Ortiz Valmaseda
Línea Soporte y Despliegue
Centro de Tecnologías de Almacenamiento y Análisis de Datos (CENTALAD)

Linux User # 418229
PostgreSQL User
http://www.postgresql.org
http://www.planetpostgresql.org/
http://www.postgresql-es.org/


----- Mensaje original -----
De: "Roman Smirnov" <pom...@gmail.com>
Para: "Spree" <spree...@googlegroups.com>
Enviados: Jueves, 5 de Noviembre 2009 5:51:13 (GMT-0500) Auto-Detected
Asunto: [spree-user] Re: Push ruby19 support

[Sean Schofield]

>> Has anyone looked in depth at the active merchant issue? How feasible is that?   Or are the fixes scattered throughout?
>
> They skipped magic-comments in several files. In principle, we can try
> to put only those files in the spree/lib, perhaps it will help avoid
> the using of ActiveMerchant as plugin. But I do not see much point at
> this juncture.

Since there seem to be other issues with the current Rails version
(and mysql driver), its probably easier to just wait. Maybe we can
make an official ruby_19 branch in railsdog version of the repo? We
could include the activemerchant plugin for now (just for testing) and
drop once ready.

Does it make sense to move Roman's stuff into railsdog at this point
so its easier to find for those who are interested?

[Sean Schofield]

Active Merchant is needed for gateway support. See the blog post from
yesterday on spreecommerce.com (and the docs that go with it.)

Sean Schofield

-------------------------------------------
Rails Dog LLC
2 Wisconsin Circle, Suite 700
Chevy Chase, MD 20815
voice: (301)560-2000
-------------------------------------------

[Jones Lee]

Having a ruby19 branch on railsdog is great. I think it is okay to ship ActiveMerchant lib til 1.4.3 release then we could remove it.

[Roman Smirnov]

> Maybe we can
> make an official ruby_19 branch in railsdog version of the repo?

And in what sense? Them also needed synchronize...
I think it is better to add a little guide in Spree README.markdown
for those who want to play around with Ruby 1.9.x