Threads for dickdavis

1. 1. 3

      dickdavis 1 year ago | on: Turbo Stream and personalized content

      Interesting, I haven’t experienced that problem yet, but my approach seems to slightly differ from yours. I’ve found that including the turbo_stream.* actions within the controller can get messy quick, so I’ve been putting them all in *.turbo_stream.erb templates. I wonder if refactoring the provided example to something like what I have below might work.

      The refactored controller action:

        # app/controllers/messages_controller.rb
        def create
          @message = Message.create!(params.require(:message).permit(:content))
      
          respond_to do |format|
            format.turbo_stream { render :create_success }
            format.html { redirect_to messages_url }
          end
        end
      

      The turbo stream action extracted to a template:

      <!-- app/views/messages/create_success.html.erb -->
      <%= turbo_stream.append :messages do %>
        <%= render partial: "messages/message", locals: { message: @message, user: current_user })
      <% end %>
      

      The message partial, adjusted to reference the user local instead of the current_user:

      <!-- app/views/messages/_message.html.erb -->
      <div id="<%= dom_id message %>">
        <span class="from">
          <% if message.user == user %>
            You
          <% else %>
            <%= message.user.name %>
          </span>:
        <%= message.content %>
      </div>
      

      The stimulus controller was an interesting hack, but probably not ideal as your codebase grows as it would result in a lot of one-off stimulus controllers that only serve as workarounds.
   2. 30

      vincent 3 years ago | on: algoheader: Programmatically generate beautiful header images for blogs or social media accounts

      I feel like the repository (and docs) could use examples.

      1. 14

         hauleth edited 3 years ago | on: algoheader: Programmatically generate beautiful header images for blogs or social media accounts

         Promoting tool that creates “beautiful” graphic without any showcase is at least weird.

         EDIT: Assuming that author uses this tool on their own blog it looks like that.

         1. 3

            khm 3 years ago | on: algoheader: Programmatically generate beautiful header images for blogs or social media accounts

            I think it is more like that, given that the autor has mentioned the author of the original idea (???) in a tweet, and I have found this repo under that name. And the graphic seems pretty similar to the one shown in the original repo.

            But how did it all happen, is this copied or what… I do not have an idea…

            1. 1

               dickdavis 3 years ago | on: algoheader: Programmatically generate beautiful header images for blogs or social media accounts

               algoheader is a CLI frontend to the ascii-to-svg library that does a couple things that simplify/automate using that library. It’s listed in the dependencies, but I’ll update the README to feature that gem more prominently so that there’s no confusion.
         2. 1

            dickdavis 3 years ago | on: algoheader: Programmatically generate beautiful header images for blogs or social media accounts

            Haven’t had a chance to update my blog with any of the generated images yet, but I’ll be sure to add examples to the README.
      2. 4

         freddyb 3 years ago | on: algoheader: Programmatically generate beautiful header images for blogs or social media accounts

         Yes. Was also looking for screenshots.
      3. 2

         dickdavis 3 years ago | on: algoheader: Programmatically generate beautiful header images for blogs or social media accounts

         I’ll definitely add screenshots–apologies for the oversight!
   3. 1

      dickdavis 5 years ago | on: foss.technology - A pleroma instance for FOSS projects to announce news and updates

      Nice, this seems to be a great idea. I’ve struggled to find a good instance to join, but this looks promising. I really like how the post rules state: “All top-level posts must be directly related to FOSS development.” I think this will serve to maintain a better signal-to-noise ratio. I sent my request to join to the operator.