by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Jorge Fuertes
    @jorgefuertes
    • We need a good websockets implementation, and, most important: well documented.
    • I can't recommend to use grape with padrino, its a madness, but that is a very personal opinion. It works for an small project, but in that case you don't need padrino with grape.
    Jorge Fuertes
    @jorgefuertes
    At the end of the day, I insist, Padrino is great, is the best framework to use even in big projects, and nobody is charging a dollar here for this amazing work. So, thanks to all, and don't pay too much attention to me.
    Jorge Fuertes
    @jorgefuertes
    I've done this solution to use sassc and delete ruby-sass gem from my project:
    # Gemfile
    
    group :development do
      gem 'guard-livereload'
      gem 'guard-shell'
      gem 'sassc'
    end
    
    # Guardfile
    
    require 'sassc'
    
    group :frontend do
      directories %w[app config lib]
      guard :livereload do
        # app
        watch(%r{app/views/.+\.(md|txt|html|haml|erb|slim)$})
        watch(%r{app/controllers/.+\.rb})
        watch(%r{app/helpers/.+\.rb})
        watch(%r{app/locale/.+\.yml})
        watch(%r{config/.+\.yml})
        # Assets
        watch(%r{app/sass/.+\.sass})
        watch(%r{public/.+\.(css|js|html)$})
      end
    
      guard :shell do
        watch(%r{app/sass/.+\.sass}) do |m|
          puts "Sass changed: #{m[0]}"
          Dir.foreach('app/sass') do |sass_file|
            next if sass_file.match(/\A[_\.]+/)
    
            css_file = File.basename(sass_file, '.sass') + '.css'
            puts "Compiling #{sass_file} --> #{css_file}"
    
            begin
              css = SassC::Engine.new(
                IO.read(Dir.pwd + '/app/sass/' + sass_file, encoding: Encoding::UTF_8),
                style: :compressed,
                load_paths: [
                  Dir.pwd + '/app/sass',
                  Dir.pwd + '/node_modules/materialize-css/sass',
                  Dir.pwd + '/node_modules/materialize-css/sass/components'
                ],
                source_map_file: '.',
                source_map_embed: false,
                source_map_contents: false
              ).render
            rescue StandardError => e
              puts %(SASS Rendering ERROR: #{e.class}\n#{e.message})
              css = <<~ERROR
                /*
                  -----------------------------------------------------------------
                  SASS Rendering ERROR: #{e.class}
    
                  #{e.message}
                  -----------------------------------------------------------------
                */
    
                *{ background-color: white; color: black; }
    
                #slide-out {
                  display: none;
                }
    
                body:before {
                  background-color: red;
                  color: white;
                  font-size: 20px;
                  font-family: monospace;
                  padding: 10px;
                  display: block;
                  content: "*** SASS ERROR: #{e.class} ***";
                }
              ERROR
            end
    
            File.write(Dir.pwd + '/public/css/app/' + css_file, css, mode: 'w+')
          end
        end
      end
    end
    
    # Execute in console
    #> bundle exe guard -i
    Then I use livereload javascript in my main layout and guard is compiling and reloading the browser when I change a sass file. It works like a charm.
    Christoph Haas
    @Softener_gitlab
    Is padrinorb.com just down for me? Or have the devs now officially killed the project?
    Christoph Haas
    @Softener_gitlab
    Would be a bummer. Just finished an API and tried several frameworks and found Padrino the best of them by far.
    Christoph Haas
    @Softener_gitlab
    I'd love to help but I don't think that my Ruby skillz are l33t enough to adopt such a complex project yet. Watching the activity on Twitter, here and Gitlab it seems like time to evaluate frameworks again.
    Jorge Fuertes
    @jorgefuertes
    @Softener_gitlab It depends on the project, I guess. Anyway I can recomend Padrino without reserves, way easier than Rails, and one advice, outside Rails and Padrino all the other is dead, maybe Sinatra (included here), but nothing else.
    I would love to know if I'm wrong.
    Ask any thought, I'll try to answer when I can.
    Christoph Haas
    @Softener_gitlab
    @jorgefuertes It would be very unfortunate indeed if Padrino died. At least the web site is back up. Glad it was just a hickup.
    Unfortunately a web framework that is not developed any more is a major problem. Not just because of funny futuristic features but very basically due to security issues and even dependent packages like Bundler that advanced and now Padrino needs to be fixed up.
    Christoph Haas
    @Softener_gitlab
    As a last resort there is Hanami. But I haven't used it yet. I'd like to stay with Padrino.
    Jorge Fuertes
    @jorgefuertes
    @Softener_gitlab I don't think padrino is dead, not yet. Hanami... I haven't tried it, but in a first approach it lacks from ODM support, yeah, you can delete the ORM support and make your own way. I don't know, its not so agnostic as Padrino.
    Yes, you are right, Padrino needs some cleanup and modernization, but in today, its working and I have a ton of projects built on it.
    Jorge Fuertes
    @jorgefuertes
    And Padrino has features that are from the past, at least for me, are useless, but they need a lot of effort for the core devs, I'm talking about Admin stuff, model, pages, css, forms generation for several ORMs, ODMs, CSS framewors, even JS... its a madness and a waste of time. This kind of generators inherit from Django era.
    I don't know @Softener_gitlab, I'm finishing a project right now, in Padrino, and I need to think next move carefully.
    Jorge Fuertes
    @jorgefuertes

    We need take the big question too: Ruby has a future? Or its Go and JS (vue, react, etc) to eat all the backend and frontend pie?

    There's a lot of old gems without updates.

    Marwan Rabbâa
    @waghanza
    @jorgefuertes Ruby has a future ? What do yo mean by that
    Any future are decided by users, it seems that ruby have a great community
    Jorge Fuertes
    @jorgefuertes

    @waghanza Well... yeah, RPG and Modula2 has a future, out of the question. I mean as a main language for web development, with an strong community and an updated gemset covering all the new technologies. That's my wish, but I'm not sure.

    I'm watching how the new thins are created for nodejs and go, even they are replicated in python, but I don't see the same response in ruby.

    Understand me, please, just sharing my thoughts, I'm not sure and I'm not abandoning ruby or padrino.
    Marwan Rabbâa
    @waghanza
    @jorgefuertes questioning ... is a safe and sane way to go to the future, but not very about technologies or frameworks. I mean each language is more or less suitable for various needs, and every frameworks has feature for future, for example, https://rubyonrails.org/ has https://stimulusjs.org/ or https://github.com/rails/webpacker allowing that we can use some technologies for what they fit for. ruby fit more for backend and vue/react for frontend.
    I don't think we have to talk about end of road, but how we can adapt :heart:
    Jorge Fuertes
    @jorgefuertes
    Yeah, of course, I agree. But I'm my case is dangerous path. I have projects to keep up and running, I can't migrate them, they are "padrino" untill the end of the World. Its supposed to don't be worried? I'm worried.
    I'm paranoic? May I be, I want to hear that.
    Marwan Rabbâa
    @waghanza
    yeah, you are :stuck_out_tongue:
    at least more gems you use, more you are frightened
    I understand
    Jorge Fuertes
    @jorgefuertes
    @waghanza Loving stimulusjs, I don't know it, thanks.
    @waghanza Haha, thank you.
    Christoph Haas
    @Softener_gitlab
    I would be very disappointed in humanity (even more than now) if Ruby would go away. Developing both in Python and Ruby I must say that Ruby is the only language not getting in my way. I've tried NodeJS/JS and that's even worse than Python. Nah… Ruby needs to stay. Or I'll switch jobs to something with wood and flowers.
    Marwan Rabbâa
    @waghanza
    ruby has so many variants that I do not think it would perish, there is crystal and elixir with the same fun coding, but having a slightly different purpose
    Christoph Haas
    @Softener_gitlab
    It's crazy how many programming languages emerge. I even mix up Python and Ruby. Maybe I'm getting old but running after every hype makes me tired. Go might be interesting but I don't even feel an urge to learn that.
    Marwan Rabbâa
    @waghanza
    yeah, there is a lot of languages to emerge
    Christoph Haas
    @Softener_gitlab
    Besides in a job context it's pretty pointless to use anything "unusual". Some of our devs are slowly moving from PHP to JS… most stay in the old world. My sysadmin coworkers even frown upon my use of Ruby. They believe that Python is "crazy already".
    Marwan Rabbâa
    @waghanza
    most of it are hypes in deed, but their are some values (for example, crystal is compiled but have a ruby syntax)
    Christoph Haas
    @Softener_gitlab
    At least in "big data" stuff they use Python so that's okay. But if I have worked Ruby for a while I can't stand how unnecessarily complicated Python makes my life. :)
    Marwan Rabbâa
    @waghanza
    :-)
    Jorge Fuertes
    @jorgefuertes
    @Softener_gitlab I understand you, I love ruby.
    José Santos Martins Pereira
    @jsmpereira
    Hello :wave:
    José Santos Martins Pereira
    @jsmpereira
    I'm having an issue with params expansion in routes with mustermann. With the old router I have no issues. With mustermann a call like absolute_url(:posts, :index) resolves to a more specific route like /posts/:year/:monthand errors out with Mustermann::ExpandError: cannot expand with keys [], possible expansions: [:year, :month]. Apologies if there is some documentation/migration guide out there that I missed that addresses this. Thank you for your time.
    José Santos Martins Pereira
    @jsmpereira
    Do I maybe need to have distinct name routes for disambiguation?
    Because previously I could name all routes :index and the old router it seems would disambiguate based on request method and params?
    José Santos Martins Pereira
    @jsmpereira
    Because I could have , for example
    Demo::App.controllers :posts do
      get :index do; end # /posts
      get :index, with: :id do; end # /posts/:id
      get :index, with: [:year, :month] do; end # /posts/:year/:month
      post :index do; end # /posts
      patch :index, with :id do; end # /posts/:id
      delete :index, with: :id do; end # /posts/:id
    end
    And there was no issue for absolute_url(:posts, :index) to resolve to /posts
    Nagesh Vanam
    @ngshvanam
    Hi, Can anybody help me with when will be the padrino 0.11.4 will get to EOL ?
    Where Can I find that information?