Hi everyone! Imanol Alvarez and me have worked a bit on upgrading to Rails 5 in the last couple of months. The Erubis/ERB issue is now solved, and a few other issues are solved. Still, there is work to be done. I hope we make it happen :).
Warm regards, Ignacio On 6 June 2018 at 03:38, Ed Gomolka <[email protected]> wrote: > I considered Angular, Elm, and React before settling on Vue.js. > > I did not try using Angular because I got the impression that it would be > too restrictive for the hybrid approach that I wanted, and it seemed to > have a significant learning curve. I may be doing it an injustice, since I > never actually tried it. I experimented directly with Elm, React, and > Vue.js. Vue.js struck me as being the simplest to learn and use. Also, it > has the reputation of being one of the fastest frameworks available: > https://www.stefankrause.net/js-frameworks-benchmark6/ > webdriver-ts-results/table.html > React would have been my second choice. > > With regard to the problem of impatient agents, you could disable the > submit button after the agent presses it, and then re-enable the button > when the information comes back from the server. > > Ed > > > On Tuesday, June 5, 2018 at 5:24:38 PM UTC-6, donz wrote: > >> Hi Ed, et al! >> >> I have given up on DRYML and like you I am switching to a TypeScript >> framework (Angular 6). The problem I am trying to fix is one of latency. >> My daughter owns a real-estate company, and I handle all of her IT needs. >> I developed a website that our agents use while on the road. >> Unfortunately, once they get into the rural areas, the cell signals are >> weak and the connection latency is very high. This totally hoses the >> utility of our website. (I have the same problem with other websites, but >> not as bad since the clients don't usually leave the suburbs.) >> >> I ran some experiments with a test website using rails and angular. >> While the latency is noticable, it doesn't cripple the app like using hobo >> and ajax ( >> The agents are impatient and keep clicking away even though the waiting >> spinner is showing. The result is a whole bunch of queries in progress >> with the results coming back out of order). >> >> What I need is the ability to use other parts of Hobo. Particularly the >> models with incorporated data descriptions and the User model with its hobo >> lifecycle (to handle invited users and users who forget their password - >> almost all of them at one time or another :-D.) >> >> I am trying to keep the existing data intact as much as possible. I was >> able to download the active database from Heroku and use it to initialize >> the database in my test app. Now I am implementing the new version of the >> web site one page at a time. Like you found, this is very time-consuming, >> but the payoff will be worth it. >> >> Good luck, >> >> Don >> >> >> On 06/05/2018 07:02 PM, Ed Gomolka wrote: >> >> I asked a status question a while back. At the time, Ignacio Huerta was >> the primary maintainer, and he indicated that he didn't have much time to >> do other than fix major bugs. >> >> I spent a couple of days trying to figure out how upgrade Hobo so that it >> could handle Rails 5, but I quickly got lost in the weeds. Looking at my >> old notes, some of the issues that I came across were: >> >> >> 1. Rails 5 forces the use of strong parameters. This was already >> deprecated in Rails 4, but Hobo got around it by using the >> "protected_attributes" gem; however, that gem won't work under Rails 5. >> This means that Hobo and all apps using Hobo need to be changed. >> 2. Hobo uses the Erubis ERB template engine to compile the dryml >> files, while Rails 5 uses The Erubi engine. The two engines conflict. >> 3. Hobo uses "raise_in_transactional_callback", which was deprecated >> in Rails 4, and removed in Rails 5. >> >> I would be interested in helping to upgrade Hobo as a junior partner. I >> feel that it would take me much too long on my own. >> >> In the meantime, I have worked out a plan that allows me to gradually >> move off Hobo if necessary. I have a version that runs on top of Rails >> 4.2.10, which supports the Webpacker gem, which allows me to run a >> JavaScript framework in place of DRYML. The main Hobo repository has the >> 4.2.10 specification, which supports Webpacker, but the Hobo 2.2.6 gem >> supports an older version of Rails, which does not support Webpacker. >> >> I am using Vue.js as my JavaScript framework. Whenever I need to touch a >> DRYML page, I convert it to Vue.js. The conversion amounts to quite a bit >> of work per page.In those cases where I use Vue.js: >> >> 1. I create new index/show/new/create/destroy methods in place of the >> Hobo controller methods. >> 2. I use strong parameters in the controllers >> 3. I use Pundit for authorization >> 4. I write Vue.js components (which amounts to a lot of code) >> >> Using Vue.js requires a reasonable understanding of the JavaScript world >> (node, npm, yarn, etc). Creating the Vue.js pages is much more labor >> intensive than using DRYML, but Vue.js is more stable, and faster. It also >> gives me more control over the page. >> >> Hopefully, Hobo will get upgraded, but if it doesn't get upgraded, I will >> eventually be able to move off it. By converting the pages as described >> above, I will have taken care of everything except for authentication. >> Once I have all the pages converted, I will be able to eliminate Hobo and >> use Devise for authentication in its place.I am still hoping that I won't >> have to do that, but this gives me a plan to execute on. >> >> Ed G >> >> On Tuesday, June 5, 2018 at 3:21:50 PM UTC-6, Daniel M wrote: >>> >>> Good question! >>> Same situation here! >>> >>> On Monday, June 4, 2018 at 8:49:39 PM UTC+1, donz wrote: >>>> >>>> Hi All! >>>> >>>> It's been a long time ;-). I have been maintaining my websites without >>>> updating Ruby or Rails for the past year. Now I need to upgrade and I >>>> wonder if Hobo is up to speed with Ruby 2.5.1 and Rails 5.2? >>>> >>>> I hope everyone has been well. >>>> >>>> Don Ziesig >>>> >>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "Hobo Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/hobousers. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Hobo Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/hobousers. > For more options, visit https://groups.google.com/d/optout. > -- +45 42 997 196 -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/d/optout.
