https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    I'm interested to know that too.
  • f
    @User Thank you .. I'm going to take a look at it.
  • g
    Hey @User I just remembered that the SSE code might already trigger events. Look for 
    htmx:sseMessage
    events whenever you receive an SSE message. I was going to come here and say that it should be easy to add to htmx, but then found that we may have already done that.
  • g
    If it works, I'll act like I knew it all along... 😉
  • f
    @User ... No dice. I tried
    Copy code
    'on htmx:sseMessage call alert("SSE!")'
    and nothing happened
  • f
    I'm going to try to write my own SSE connection outside of HTMX for the moment ... it seems simple enough.
  • l
    So. I now have a rough draft of HypertextLiteral to Julia (https://github.com/clarkevans/HypertextLiteral.jl) for server-side HTML construction. It has special plugin system so I could make it very smart about hx-* tags and such.
  • l
    @future-boots-43048 let me know if you get it to work
  • m
  • m
    @User maybe some of the speculative stuff should be moved there?
  • g
    Yes. That sounds good.
  • g
    I’ve written two or three suggestions about reworking placement of various kinds of discussions (like splitting discord into dev and help sections)
  • g
    But every time, it just doesn’t seem right.
  • g
    I’m glad to follow your lead in this. I’ll move the GitHub issues over.
  • m
    Let's see how it works
  • m
    this appears to be a new feature
  • b
    @User I'd be careful of adding yet another place to discuss things. Very easy for conversations to become scattered around multiple places.
  • m
    you think that issues are the best place for that stuff?
  • m
    I suppose as long as we keep the flags straight
  • m
    I sometimes want issues to just be bugs
  • b
    Just my opinion, but I think that one place to discuss things asynchronously and one synchronously should be sufficient.
  • b
    Interestingly, Yii just opened Github discussions (https://github.com/yiisoft/app/discussions/107) even they they have their own forums at https://forum.yiiframework.com/ Sounds like a headache waiting to happen.
  • m
    🤔
  • l
    I see it as more github ecosystem lockin.
  • l
    Works for me either way.
  • m
    that's another good argument against it @User
  • m
    how do people feel about sr.ht?
  • m
  • g
    I'm not familiar with source hut. In a sense, it's all about the same to me. Personally, I don't mind "github lock-in" although I understand why it's good to not be stuck with one provider.
  • g
    For me, the most important thing is to have specific places to discuss specific topics (dev / help / integration / etc) and that those areas be well labeled and easy to find. It's probably easier to minimize the number of distinct services that we use, but split out different kinds of discussions into their own areas on each service.
1...888990...1146Latest