Hobo 2.0.0.pre2 released

[Bryan Larsen]

blog post here: http://hobocentral.net/blog/2012/09/25/2-0-0-pre2/

Note that Hobo/will_paginate is now required in your gemfile:

gem "will_paginate", :git => "git://github.com/Hobo/will_paginate.git"

Also note the new, very-cool, bottom-load-javascript option.

cheers,
Bryan

[Arnaud Doyen]

Hi Bryan,

Great release of Hobo 2.0. It seems to be already very stable and I like to use this new version (although it's still in pre-release).

One thing to say : could you update also hobo_bootstrap dependencies so that we can install it with pre2 ?

Thanks,

Arnaud.

2012/9/25 Bryan Larsen <br...@larsen.st>

--
You received this message because you are subscribed to the Google Groups "Hobo Users" group.
To post to this group, send email to hobo...@googlegroups.com.
To unsubscribe from this group, send email to hobousers+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.

[Bryan Larsen]

https://github.com/suyccom/hobo_bootstrap is the primary source for
hobo_bootstrap. My fork is just for feeding changes to Ignacio, so
you're going to have to wait for Ignacio to update the gem. Ignacio,
perhaps relaxing the version requirements for hobo_bootstrap to ~>
2.0.0 is a good idea so we don't have to synchronize so closely?

Bryan

[Bryan Larsen]

In the blog post I missed one major improvement:

The generator no longer adds rails-dev-tweaks to your Gemfile, instead
it adds quiet_assets. It also adds
config.watchable_dirs[File.join(config.root, 'app/view')] =
['dryml'] to your config/environments/development.rb

I recommend making those changes to any Rails 3.2 app, whether it's
running 2.0.0.pre2 or not.

cherr,
Bryan

[Ignacio Huerta]

Hi,

I tried pushing it to rubygems but s.add_runtime_dependency('hobo',
"~> 2.0.0") doesn't work with Hobo "pre" versions. This is what
happens while creating an app:

Bundler could not find compatible versions for gem "hobo":
In Gemfile:
hobo_bootstrap (= 2.0.0.pre2) ruby depends on
hobo (~> 2.0.0) ruby

hobo (2.0.0.pre2)

I investigated a bit and I need to use "~> 2.0.0.pre1" instead. I was
about to push a new "2.0.0.pre3" hobo_bootstrap version, but I'm not
sure if this is the right name.

What do you recommend, Bryan?

Regards,
Ignacio

El 26/09/12 00:55, Bryan Larsen escribi�:

--
Ignacio Huerta Arteche
http://www.ihuerta.net
Tel�fono: 0034 645 70 77 35
Email realizado con software libre

[Bryan Larsen]

If ~> 2.0.0.pre2 means that it will work with ~> 2.0.0.pre3 and 2.0.0
but not 2.0.1, that's OK for now. If it doesn't work with 2.0.0,
we'll have to think of something better.

It's OK if the hobo_bootstrap version number desynchronizes from hobo,
although in that case it should probably be significantly different
rather than similar...

Bryan

On Wed, Sep 26, 2012 at 1:59 PM, Ignacio Huerta <ign...@ihuerta.net> wrote:
> Hi,
>
> I tried pushing it to rubygems but s.add_runtime_dependency('hobo',
> "~> 2.0.0") doesn't work with Hobo "pre" versions. This is what
> happens while creating an app:
>
> Bundler could not find compatible versions for gem "hobo":
> In Gemfile:
> hobo_bootstrap (= 2.0.0.pre2) ruby depends on
> hobo (~> 2.0.0) ruby
>
> hobo (2.0.0.pre2)
>
> I investigated a bit and I need to use "~> 2.0.0.pre1" instead. I was
> about to push a new "2.0.0.pre3" hobo_bootstrap version, but I'm not
> sure if this is the right name.
>
> What do you recommend, Bryan?
>
> Regards,
> Ignacio
>

> El 26/09/12 00:55, Bryan Larsen escribió:

> Teléfono: 0034 645 70 77 35

[Ignacio Huerta]

Ok, I just pushed hobo_bootstrap-2.0.0.pre3 to rubygems, but I'm
afraid we need to update Hobo to make it work "out of the box",
because the "2.0.0.pre2" is being written into the new app's Gemfile :S.

I think for the moment it would be nice to keep it in sync with Hobo,
let's see how it works out.

Regards,
Ignacio



El 26/09/12 20:02, Bryan Larsen escribi�:

> If ~> 2.0.0.pre2 means that it will work with ~> 2.0.0.pre3 and
> 2.0.0 but not 2.0.1, that's OK for now. If it doesn't work with
> 2.0.0, we'll have to think of something better.
>
> It's OK if the hobo_bootstrap version number desynchronizes from
> hobo, although in that case it should probably be significantly
> different rather than similar...
>
> Bryan
>
> On Wed, Sep 26, 2012 at 1:59 PM, Ignacio Huerta
> <ign...@ihuerta.net> wrote:
>> Hi,
>>
>> I tried pushing it to rubygems but
>> s.add_runtime_dependency('hobo', "~> 2.0.0") doesn't work with
>> Hobo "pre" versions. This is what happens while creating an app:
>>
>> Bundler could not find compatible versions for gem "hobo": In
>> Gemfile: hobo_bootstrap (= 2.0.0.pre2) ruby depends on hobo (~>
>> 2.0.0) ruby
>>
>> hobo (2.0.0.pre2)
>>
>> I investigated a bit and I need to use "~> 2.0.0.pre1" instead. I
>> was about to push a new "2.0.0.pre3" hobo_bootstrap version, but
>> I'm not sure if this is the right name.
>>
>> What do you recommend, Bryan?
>>
>> Regards, Ignacio
>>

>> El 26/09/12 00:55, Bryan Larsen escribi�:

>> -- Ignacio Huerta Arteche http://www.ihuerta.net Tel�fono: 0034

>> 645 70 77 35 Email realizado con software libre

--
Ignacio Huerta Arteche
http://www.ihuerta.net

Tel�fono: 0034 645 70 77 35

[Arnaud Doyen]

I tried to use hobo_bootstrap pre3 but it needs hobo 2.0.0pre3 which doesn't exist yet.

Then, impossible to update bootstrap with hobo.

It says this :

Bundler could not find compatible versions for gem "hobo_jquery_ui":

  In Gemfile:

    hobo_bootstrap (= 2.0.0.pre3) ruby depends on

      hobo_jquery_ui (= 2.0.0.pre3) ruby

    hobo_jquery_ui (2.0.0.pre2)

2012/9/26 Ignacio Huerta <ign...@ihuerta.net>

Ok, I just pushed hobo_bootstrap-2.0.0.pre3 to rubygems, but I'm
afraid we need to update Hobo to make it work "out of the box",
because the "2.0.0.pre2" is being written into the new app's Gemfile :S.

I think for the moment it would be nice to keep it in sync with Hobo,
let's see how it works out.

Regards,
Ignacio

El 26/09/12 20:02, Bryan Larsen escribió:

> If ~> 2.0.0.pre2 means that it will work with ~> 2.0.0.pre3 and
> 2.0.0 but not 2.0.1, that's OK for now.  If it doesn't work with
> 2.0.0, we'll have to think of something better.
>
> It's OK if the hobo_bootstrap version number desynchronizes from
> hobo, although in that case it should probably be significantly
> different rather than similar...
>
> Bryan
>
> On Wed, Sep 26, 2012 at 1:59 PM, Ignacio Huerta
> <ign...@ihuerta.net> wrote:
>> Hi,
>>
>> I tried pushing it to rubygems but
>> s.add_runtime_dependency('hobo', "~> 2.0.0") doesn't work with
>> Hobo "pre" versions. This is what happens while creating an app:
>>
>> Bundler could not find compatible versions for gem "hobo": In
>> Gemfile: hobo_bootstrap (= 2.0.0.pre2) ruby depends on hobo (~>
>> 2.0.0) ruby
>>
>> hobo (2.0.0.pre2)
>>
>> I investigated a bit and I need to use "~> 2.0.0.pre1" instead. I
>> was about to push a new "2.0.0.pre3" hobo_bootstrap version, but
>> I'm not sure if this is the right name.
>>
>> What do you recommend, Bryan?
>>
>> Regards, Ignacio
>>

>> El 26/09/12 00:55, Bryan Larsen escribió:

>> -- Ignacio Huerta Arteche http://www.ihuerta.net Teléfono: 0034

>> 645 70 77 35 Email realizado con software libre

--
Ignacio Huerta Arteche
http://www.ihuerta.net

Teléfono: 0034 645 70 77 35

Email realizado con software libre

--

[Bryan Larsen]

I'm trying to fix your ajax file bug. That will give me an excuse to
release 2.0.0.pre3. :)

Bryan

[Arnaud Doyen]

Yes indeed :-)

You are totally excused ;-)

2012/9/26 Bryan Larsen <br...@larsen.st>

[Bob Sleys]

I'm trying to create a new blank hobo 2.0.0-pre3 app and when I get to running the wizard I keep getting the following error

         run    bundle install from "."

Fetching gem metadata from https://rubygems.org/........

Fetching gem metadata from https://rubygems.org/..

NoMemoryError: failed to allocate memory

An error occured while installing rake (0.9.2.2), and Bundler cannot continue.

Make sure that `gem install rake -v '0.9.2.2'` succeeds before bundling.

Doing a gem list shows I indeed do have rake 0.9.2.2 installed.  I also tried creating a new blank gemset in RVM with just the following gems in it

*** LOCAL GEMS ***

bundler (1.1.5)

rake (0.9.2.2)

rubygems-bundler (1.0.3)

rvm (1.11.3.5)

and then a bundle install from the app dir (after creating the app via hobo new and not running the wizard) and get basically the same error.  If you look close at the error it looks to me like there is perhaps an extra quote mark but that might just be a display thing.

Bob

[Bryan Larsen]

We'll start with the obvious: is your hard disk or temp partition full?

Bryan

> --
> You received this message because you are subscribed to the Google Groups
> "Hobo Users" group.

> To view this discussion on the web visit
> https://groups.google.com/d/msg/hobousers/-/vslAgb5rNegJ.

[Bob Sleys]

Nope

/ has 41.6 Gb avail

/home has 21.7 Gb avail

plenty of disk space

also plenty of mem  using 1.3Gb of 3.8Gb at the time I run bundle install.

Bob

[Ignacio Huerta]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is a weird error, that should be plenty of RAM to work with :P.

If you monitor "top" while you are running bundle, do you any process
eating too much memory? You can order them by memory use with they "M"
key :)

It's probably not related, but sometimes documentation stuff consumes
a lot of resources. I use a "/home/user/.gemrc" file with the
following line:

gem: --no-rdoc --no-ri

Regards,
Ignacio

El 05/10/12 20:25, Bob Sleys escribi�:

> <http://github.com/Hobo/will_paginate.git>"

>>>
>>> Also note the new, very-cool, bottom-load-javascript option.
>>>
>>> cheers, Bryan
>>
>> -- You received this message because you are subscribed to the
>> Google
> Groups
>> "Hobo Users" group. To view this discussion on the web visit
>> https://groups.google.com/d/msg/hobousers/-/vslAgb5rNegJ

> <https://groups.google.com/d/msg/hobousers/-/vslAgb5rNegJ>.

>>
>> To post to this group, send email to hobo...@googlegroups.com

> <javascript:>.

>> To unsubscribe from this group, send email to

>> hobousers+...@googlegroups.com <javascript:>. For more options,

>> visit this group at
>> http://groups.google.com/group/hobousers?hl=en

> <http://groups.google.com/group/hobousers?hl=en>.

>
> -- You received this message because you are subscribed to the
> Google Groups "Hobo Users" group. To view this discussion on the
> web visit

> https://groups.google.com/d/msg/hobousers/-/vCqVKJHk04QJ. To post

> to this group, send email to hobo...@googlegroups.com. To
> unsubscribe from this group, send email to
> hobousers+...@googlegroups.com. For more options, visit
> this group at http://groups.google.com/group/hobousers?hl=en.

- --

Ignacio Huerta Arteche
http://www.ihuerta.net

Tel�fono: 0034 645 70 77 35

Email realizado con software libre

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBwDQMACgkQBPlUJ6RHaORjUQCgxzwr5YqxpN9Md4g5XhasV/kM
cU4AnA0GKP7s3KM9abVoCmuSQvAUUeuD
=7XG2
-----END PGP SIGNATURE-----

[Bob Sleys]

It must have something to do with bundle v 1.1.5.  If I do a gem install on each gem bundle dies on the next bundle install will find it and use it and then die on the next needed gem.  So I just manually install it and one by one I'm getting everything installed.

Very odd though and I have no idea why bundler is giving nomem errors since there is plenty of mem and no large amount of mem or being allocated.  It's like I doing a check for needed memory but checking for xGb instead of xMb.

Bob

On Tuesday, September 25, 2012 5:23:50 PM UTC-4, Bryan Larsen wrote:

[Bob Sleys]

Ok it's not bundler.  I updated it to v 1.2.1 and I'm still getting the error.  It must be something with my current install but I have no idea what.

[Bob Sleys]

Ok got through manually installing all the gems, running the wizard and manually installing all the additional gems.  I choose to use bootstrap as my theme.  I the coped the controllers and models over from the app I'm porting over to hobo v.2, No view changes yet just models and controllers.

I'm now seeing a few odd things.

First I getting spammed with the following in the terms I started the server from

[2012-10-06 11:19:11] WARN  Could not determine content-length of response body. Set content-length of the response or set Response#chunked = true

Second I have children :gyms in the user model.  Since it's a new database I have no gyms set but after logging in and going to http://localhost:3000/users/1-bob-sleys The header for the children collection is showing the following.

Bob Sleys&#x27; Gyms

No records to display

Not a big issue

On the plus side I love that more theme options are included in the wizard now.

Bob

On Tuesday, September 25, 2012 5:23:50 PM UTC-4, Bryan Larsen wrote:

[Bryan Larsen]

> First I getting spammed with the following in the terms I started the server
> from
> [2012-10-06 11:19:11] WARN Could not determine content-length of response
> body. Set content-length of the response or set Response#chunked = true

The easy fix is to switch to thin instead of webrick:

http://cookbook.hobocentral.net/manual/faq#how_do_i_get_rid_of_

Bryan

[Bob Sleys]

Sorry to be spamming but I can edit previous messages.

Just noticed that form field lists, though listed in the dryml, are coming out empty.  It's not a css error as the html source for where the fields should be lists is simply blank.

Ie the auto tag for the gym form is

<def tag="form" for="Gym">

  <form merge param="default">

    <error-messages param/>

    <field-list fields="name, email, phone, address, notes, machines, tickets, users" param/>

    <div param="actions">

      <submit label="#{ht 'gym.actions.save', :default=>['Save']}" param/><or-cancel param="cancel"/>

    </div>

  </form>

</def>

But I don't see the fields listed in the html.  The hidden fields are there but right after that is a blank row where the form fields should go and then the actions, ie the save button.

Bob

On Tuesday, September 25, 2012 5:23:50 PM UTC-4, Bryan Larsen wrote:

[Bryan Larsen]

Double check your permissions. That's the usual cause of that sort of error.

Bryan

> --
> You received this message because you are subscribed to the Google Groups
> "Hobo Users" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/hobousers/-/rzGn9MlJYNsJ.

[Bob Sleys]

Do you need attr_accessible set for each field we want editable now?  I added it to one of my models and its working now.  I also tried generating a test resource and sure enough it was added to the model by the generator for that new models fields.

It's probably a good thing to have just not mentioned in the v2 changes list, or I missed where it was now needed.

Bob

[Bryan Larsen]

http://cookbook.hobocentral.net/manual/changes20#attribute_whitelist

Bryan

> https://groups.google.com/d/msg/hobousers/-/KCiYdmIJjgEJ.

[Bob Sleys]

DOH my bad sorry.

[Bryan Larsen]

Hey, it's one of the last clauses in a very long document. You're excused.

Bryan

> https://groups.google.com/d/msg/hobousers/-/vWZ9IjsbSXUJ.