Hi Owen, I revisited the tutorial with the new edition of the book, I applied step by step everything the tutorial mentioned, but the graph is not being loaded. I tested with FFX 2.0 & 3.6, Chrome 5.0, Internet Exporer 8.
I noticed that under the recipe table, there is now a larger area. When I right click on it with all browsers, it tells me that "Movie is not loaded" and underneath "About Adobe Flash Player 10" . "Movie is not loaded" is greyed out. Has actually anybody got this tutorial working? I have the latest Flash player in all of the browsers. I am using Hobo 1.0 + Rails 2.3.5 + Ruby 1.8.7 + postgres 8.3 64 bit + Solaris 10 zone. I would appreciate any feedback. Thanks... On Mon, Mar 22, 2010 at 11:20 AM, Owen Dall <[email protected]> wrote: > Let me know if you have suggestions on how to make Marcelo's tutorial on > Fusion Charts easier... > > Thanks, > > Owen > > On Mon, Mar 22, 2010 at 10:45 AM, Deniz Rende <[email protected]>wrote: > >> Hi >> >> 13. How to use charts in Hobo applications, or better yet a graphics >>>> library or plugin integrated with hobo out of the box. The FusionChart >>>> tutorial is very confusing and not easy to integrate. >>>> >>> >>> Personally, I'm inclined to use the Google Charts API anywhere I can, >>> subject to the client's level of paranoia. But here again, I'm not sure what >>> would differentiate a Hobo solution for this from a Rails solution. >>> >> >> Ok, so is there any example for a "Rails" solution? How about Google >> Charts API example for Hobo? >> >> On Mon, Mar 22, 2010 at 5:21 AM, Tiago Franco <[email protected]>wrote: >> >>> Hi, >>> >>> > 12. How to install and use the Hobo Cookbook locally using SQLite3. >>> >> Is there a significant difficulty here? Never tried it, but I'd assume >>> >> it's just like bootstrapping any other Rails app locally. >>> I've done it, not a big deal. It's not different than setting up >>> SQLite3 in a pure rails app. >>> >>> I think we can drop it. >>> >>> TF >>> >>> On Mar 22, 12:19 am, Matt Jones <[email protected]> wrote: >>> > Ref: >>> http://groups.google.com/group/hobousers/web/advanced-hobo-recipes-re... >>> > >>> > A quick introductory comment: >>> > >>> > My personal vision for "Advanced Hobo Recipes" is to spotlight the >>> > "Hobo way" of doing things, using examples drawn from production code >>> > as much as possible. I don't see the book spending much time on >>> > subjects where Hobo doesn't offer a material difference to vanilla >>> > Rails. >>> > >>> > Some notes on the things posted there: >>> > >>> > > 1. How to set up secure multi-tenancy. >>> > > Some guidance can be found here: >>> > > >>> http://aac2009.confreaks.com/06-feb-2009-14-30-writing-multi-tenant-a... >>> > > >>> http://stackoverflow.com/questions/1970564/rails-migrations-for-postg... >>> > >>> > > 2. How to set up subscription management for multi-tenancy. (I know >>> > > this has been covered elsewhere for standard Rails, but perhaps this >>> >>> > > is easier using Hobo?). >>> > >>> > Not sure if this is something that could be covered well - I did some >>> > Googling and mostly found very wonkish CS papers on this. If someone >>> > who has actually done this wants to write something up, I'd love to >>> > have it. But it seems likely to be either exceptionally complicated or >>> >>> > exceptionally vague depending on how specific the writeup is. >>> > >>> > > 3. Recommended options and implementations for easy, full featured >>> > > report writing and printing to PDF. eg: PdfLib, PD4ML etc. >>> > >>> > This is an example of the "vanilla Rails" solution; I'm not aware of >>> > anything specific Hobo offers here. Now, if someone out there has >>> > figured out how to make DRYML emit LaTeX, that would be different. :) >>> > >>> > > 4. How to protect code/intellectual property when deploying to >>> > > customer's servers (JRuby?). >>> > >>> > As my note on Google says, this isn't really a technical problem so >>> > much as a licensing problem. I'm also somewhat opposed to telling >>> > readers, "this will make your code secure" without some serious >>> > analysis and testing. Any volunteers? >>> > >>> > > 5. How to allow Facebook Connect as an alternative way sign-up & >>> > > login. >>> > >>> > A good idea; it's another option to add to palette of user >>> > authentication methods (OAuth, OpenID, etc). >>> > >>> > > 6. Integrating Google Maps with Hobo, including geocoding >>> > >>> > I'm working on a project right now that will do at least some stuff >>> > along these lines; the big win with Hobo is being able to whack the >>> > whole chunk of JS that Google wants you to use into a tag. >>> > >>> > > 7. Using JRuby with Hobo >>> > >>> > Going back to the note at the start, I'm not sure what the book could >>> > offer along these lines. Bryan would know more - are there any Hobo- >>> > specific issues with JRuby? The only thing I can think of is some sort >>> >>> > of potential interaction between generate_taglibs and running from >>> > a .jar file, but I'm not at all familiar with the JRuby stuff. >>> > >>> > > 8. Using the jQuery Plugin with Hobo. A detailed list of examples >>> > > • Create a record: Submit form with jQuery and update a div. >>> > > (record has been created or validation error) >>> > > • Read records: Display a list of records with pagination. Only >>> > > refresh the collection with jQuery when a page number/next is clicked >>> > > • Update a record. (record has been updated or validation error) >>> > > • Delete a record with jQuery - fade away / your record was >>> deleted >>> > >>> > A section on "using hobo-jquery" would likely cover most of this. >>> > >>> > > 9. Multi-Model forms and Hobo >>> > >>> > This *might* be worth avoiding until we've officially dropped support >>> > for Rails 2.2; right now, there are several different mechanisms for >>> > doing this. >>> > >>> > > 10. Integrating a payment/subscription system such as Spree, >>> > > ActiveMerchant, Paypal with Hobo. >>> > >>> > The one thing I'd really like to see on this is handling a CC >>> > transaction during a lifecycle transition; I've got a use case in one >>> > of my apps for this, and right now it's a hacktacular piece of code. >>> > Not sure if the existing lifecycle stuff can even handle it, but worth >>> >>> > looking into. Note that the more general "hook up payment" stuff is >>> > again essentially identical to standard Rails. >>> > >>> > > 11. How to create an invoice in Hobo. Requires master/detail lines >>> > > and iine-by-line calculations. >>> > >>> > I'd love to see somebody write this up, but it may be too application- >>> > specific to offer much detail. Anybody got some code to volunteer? >>> > >>> > > 12. How to install and use the Hobo Cookbook locally using SQLite3. >>> > >>> > Is there a significant difficulty here? Never tried it, but I'd assume >>> >>> > it's just like bootstrapping any other Rails app locally. >>> > >>> > > 13. How to use charts in Hobo applications, or better yet a graphics >>> >>> > > library or plugin integrated with hobo out of the box. The >>> > > FusionChart tutorial is very confusing and not easy to integrate. >>> > >>> > Personally, I'm inclined to use the Google Charts API anywhere I can, >>> > subject to the client's level of paranoia. But here again, I'm not >>> > sure what would differentiate a Hobo solution for this from a Rails >>> > solution. >>> > >>> > > 14. How to use a css framework with Hobo (such as Blueprint or >>> > > something similar) for customizations to the UI. >>> > >>> > This would be helpful; actually, I'm hoping to take the time at some >>> > point to split the structual/functional CSS (things like putting the >>> > search box in the right place over table-plus) away from the >>> > presentational CSS (the particular font/size/color choices in Clean), >>> > as it drives the designers I work with crazy when Hobo drops a stack >>> > of overrides on top of their nice clean reset. >>> > >>> > > 15. How to use Single Table Inheritance in Hobo. >>> > >>> > This is a good idea, but the API is still somewhat evolving. I'm *not* >>> >>> > a fan of the hackery required to get STI models with lifecycles >>> > working, even though I wrote a good bit of it. :) >>> > >>> > > 16. Security best practices to prevent data on a Hobo site from >>> > > being hacked. eg sql injection etc >>> > >>> > Once again, not sure what makes Hobo different here. Some tips on >>> > making DRYML behave with the rails_xss plugin would be helpful. >>> > >>> > I've got a stack of things to add to that list; look for another mail >>> > shortly. >>> > >>> > --Matt Jones >>> > >>> > >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Hobo Users" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<hobousers%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/hobousers?hl=en. >>> >>> >> >> >> -- >> Deniz Rende >> E-mail: [email protected] >> Phone: +1 (224) 789-UNIX (8649) >> Mobile: +1 (816) 213-2139 >> Web: http://www.deniz-rende.com/blog >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Hobo Users" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<hobousers%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/hobousers?hl=en. >> > > > > -- > Thanks, > - Owen > > -- > You received this message because you are subscribed to the Google Groups > "Hobo Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<hobousers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/hobousers?hl=en. > -- Deniz Rende E-mail: [email protected] Phone: +1 (224) 789-UNIX (8649) Mobile: +1 (816) 213-2139 Web: http://www.deniz-rende.com/blog -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
