Ubiquo 0.9

22 views
Skip to first unread message

Bernat Foj Capell

unread,
Jan 4, 2012, 9:54:51 AM1/4/12
to ubiquo...@googlegroups.com
Hi,

While there is still work in progress for version 0.8, it's time to
start working in 0.9.

The main target is to migrate to the current Rails edge. This
currently means rails 3.2, ruby 1.9.3 and jquery. And converting the
ubiquo plugins to engine gems.

The focus should be on doing this migration as painless as possible.
The idea is to have it in a matter of weeks, not years :). So we
should just do the minimal required changes, at least at this stage.
It's easy to start rethinking everything, but that would lead to an
endless path.

An exception to this, is when doing a change would mean to get rid of
a considerable amount of code, since maintaining less code is always
good. Also if the cost of transitioning some component is too high we
should discuss it.

For the sake of the simplicity of this transition, I don't think we
should keep compatibility with 0.8, Rails 2.3 or old rubies.

I've created a beta ubiquo gem that installs an ubiquo under Rails
3.2. To use it, do the following

rvm 1.9.3
gem install ubiquo --pre
ubiquo --edge --devel --rvm myubiquo09

Note that ATM the created project may not even start the server. First
step is to have a working project, so I will probably begin by
disabling problematic extensions and modules (even maybe plugins)
until we can start working on something solid.

When applying the ubiquo template, rails will tell you that there are
conflicts on their existing files, just overwrite them (press 'a').

The --rvm option creates a new gemset for the new project and installs
there the required gems

All this work will be done in the edge (master) branch. We have
0.8-stable for the existing projects.

Comments and ideas welcome

Cheers,
Bernat

Jordi Beltran

unread,
Jan 4, 2012, 10:32:55 AM1/4/12
to ubiquo...@googlegroups.com
Hi,

I'm really glad of hearing this. We need to go forward and this approach can be the shortest and painless.

Lets do it!


Cheers,
Jordi

2012/1/4 Bernat Foj Capell <bf...@gnuine.com>

--
Heu rebut aquest missatge perquè esteu subscrit al grup "ubiquo" de Google Grups.
Per publicar a aquest grup, envieu un correu electrònic a ubiquo...@googlegroups.com.
Per anul·lar la subscripció a aquest grup, envieu un correu electrònic a ubiquo-gnuin...@googlegroups.com.
Per obtenir més opcions, visiteu aquest grup a http://groups.google.com/group/ubiquo-gnuine?hl=ca.


Bernat Foj Capell

unread,
Jan 5, 2012, 5:08:35 AM1/5/12
to ubiquo...@googlegroups.com
Hi,

As commented with Juan, if you prefer a more stable environment while
developing there's no problem in using 1.9.2 and 3.1. The changes of
the future versions are not that important, and you may avoid strange
bugs. But keep in mind that 0.9 should support the new versions (avoid
deprecations, etc)

Cheers,
Bernat

--
Bernat Foj Capell
bf...@gnuine.com

gnuine
www.gnuine.com
C/ Pamplona, 96
Local 17
22@ - 08018 Barcelona

Tel: +34.93.567.94.94
Fax: +34.93.567.94.95

Bernat Foj Capell

unread,
Jan 11, 2012, 5:28:41 AM1/11/12
to ubiquo...@googlegroups.com
Hi,

I just pushed a new gem version (0.9.0.b4) that will already use
ubiquo plugins as gems.

So, to work on the rails 3.2 update, I recommend you to do:

rvm 1.9.3
gem install ubiquo --pre

ubiquo --edge --devel --rvm --gem-path ~/development/ubiquo_gems
--clone-gems myubiquo09

The --gem-path indicates where you have the gems code (remember that
they are no longer plugins so they are not inside the project)

The --clone-gems option will clone the gems repos inside --gem-path
(is intended to initialize your gem development folder, so if they are
already there, don't use it)

The gem only downloads the plugins that are already gemified. I will
update it as I gemify more plugins.

Cheers,
Bernat

Reply all
Reply to author
Forward
0 new messages