https://htmx.org logo
Powered by
# htmx-general
  • f
    I have a question about hyperscript and htmx. It seems like you could write some (all?) htmx features as hyperscript. Is there a lot of overlap between the two? I haven't used either yet, so I am in the "get my head wrapped around what they're trying to do" phase of this.
  • g
    In a way, yes. But htmx is declarative, and hyperscript is imperative.
  • g
    Htmx is just new attributes in existing tags, and loading partial html fragments into the page.
  • g
    Hyperscript implements client side logic - it’s a better JavaScript than JavaScript.
  • g
    The two work wonderfully together.
  • m
    htmx is the primary technology I would recommend for most web applications: you drive server interactions using HTML-based attributes, and stay within the HTML model. Very simple and you can accomplish a lot (see https://htmx.org/examples) hyperscript is a more speculative project for doing pure front end scripting. it is event-oriented and thus plays very well with htmx (which has an extensive event model: https://htmx.org/reference/#events) I reach for it when I want to do something purely client side. You can consider it a modern alternative to jQuery if you like. I would not build an entire app in hyperscript, but rather would use it to embellish an existing app with light front end code.
  • f
    Let me see if I get this right. If i have a table, and an edit button on each row in the last cell, when they click the edit button I want to swap out all the static values in the table for editable inputs, and swap out the edit button for save and cancel buttons, so I'd use htmx to attach a click event handler to the edit button that would pass back some basic context (like which id # that row represents) and the server would return an entirely new table row's html with all editable inputs and save and cancel buttons, and we'd swap out the old static row and replace it with this new editable one. How does that sound?
  • m
    Yep sounds right
  • m
  • m
    but with ``'s rather than ``'s
  • m
    maybe if you are being fancy, on mouse in to the row, show the edit button 🙂
  • f
    Thanks that example is exactly what I was trying to describe, lol. I'm firing up a new .net razor pages project to see how this jives with my usual world of asp.net, mvc, blazor, jquery, etc.
  • m
    good luck!
  • a
    @User let us know how it goes!
  • f
    My first real hurdle is to figure out how to return snippets of html from asp.net razor pages, i am used to using fragments of html, but only from within a larger parent page or component, convincing asp.net to return a fragment of html from a get or post feels awkward, it's probably super simple but i honestly don't think i've ever done it before 🙂
  • m
    is there a notion of a controller in razor?
  • f
    There is but honestly i am trying to move away from them. With asp.net mvc i totally fell into the fat controllers pit. The newer razor components style feels more comfortable. You prefix a page with an 
    @page
    directive to give it a url path, then dip into code with 
    @code{...}
    as needed. It's really just controllers embedded within the page markup. But it keeps you a bit more honest. When either the code or the markup extends over a page, it's time to decompose. At least that's how we've been approaching the blazor apps we've written. I haven't written any "vanilla" razor components pages like i am doing here for this exercise.
  • m
    Roger, OK
  • m
    Can you use an @page directive to assign a URL to a given bit of HTML and still include it?
  • m
    in other pages?
  • m
    If so, we are good to go
  • f
    It works just fine. Remove the 
    Layout="_Layout"
    from the 
    _ViewStart.cshtml
    page so that not every page gets wrapped in boilerplate 
    <html>...
    but only the pages that you actually want to be pages. Then just drop 
    blah.cshtml
    into the project, give them appropriate 
    @page
    directives, and they render fragments of html with no worries. 
    hx-trigger="load"
    did exactly what I thought it might. So there's zero friction so far.
  • f
    I haven't tried including it, but in asp.net you can pretty much 
    Html.Partial(...)
    most things you'd expect to be able to, in my experience. So I would guess the existence of the 
    @page
    wouldn't affect that. I can't confirm though as I haven't done it yet. Just speculating.
  • f
    I tried it for fun, and yes it does, if you 
    @Html.Partial("Whatever.cshtml", null, null)
    then asp.net 5 just embeds your 
    .cshtml
    file that has an 
    @page
    directive into the other page. I'm not sure what else I would expect it to do, but I can confirm it doesn't mind the 
    @page
    being there, so you'd be free to use fragments directly in htmx workflows, or as fragments when building up larger pages, either way.
  • m
    sweet
  • m
    sounds like it will work really well
  • m
    if you have any free time, I would love to get a tutorial up somewhere on this!
  • f
    oh sure do you have a format or media you prefer? like markdown or github pages or what?
  • m
    I don't, matbe https://dev.to/ ?
  • m
    Anyone else have suggestions?
1...333334335...1146Latest