Spinning off a new thread from the previous one, I’ll remind here that our next call is on Monday 25th of May at 13:00 UTC.
As suggested by @JordanMartinezhere, let’s use this thread to have some organization prior to meeting up.
If you plan on coming, post in this thread 1 thing that you want to get out of this meetup. For example, what’s something you want to learn? or discuss? or work on together?
Sharing this info publicly will allow us to reduce the amount of time making intros and figuring out which breakout rooms to create because everyone will be familiar with what others are doing / want to talk about / their background.
Hi, I’d like to continue the discussion about audio/midi/opengl and procedural art, perhaps even start working on something. Though I’m really a beginner and learning about other things is also great.
The only thing I’ve done since our talk is opened issues in other repos about porting some of my guides. I will try to submit PRs for the repos where I’ve gotten a response, but I’m not sure whether I’ll have the time this week.
For my takeaway, I want to know whether anyone has any other ideas for hooks that I can add to halogen-hooks-extra.
Also, I could explain some of the internals behind Halogen Hooks for those who are interested.
I would be interested to see very common patterns you use day to day. There is also foreign function interface which is still not super clear for me how to create correct types for function which creates promises etc. I would like to see some quick walk-through over it.
I want to reserve a time slot in the ecosystem room for a broad topic of a codegen in PureScript. @jvliwanag is preparing a small presentation (thanks a lot in advance!) so we would have some background for the discussion
We want to also share the progress which has recently been done by @srghma in the community driven purescript-codegen org.
Additionally I want to reserve a few moments for a discussion around latest initiatives related to purescript-node-contrib and @Woody88wai and warp libs and more… I hope that we can also exchange some experience and thoughts about the state of the PureScript on the backend.
@f-f Mind if we create a poll where each choice represents what a room could be and who would be interested in being a part of it?
Looking through this thread, I think the potential rooms (bolded names) would be the following list. I’ve tried to group similar things together:
Doc Updates - discuss doc updates since last week / next steps for improving docs and new-user experience (@milesfrain)
Pain Points - how people are using PureSciprt and what their pain points are (@hdgarrood)
Halogen Hooks - explain how it works and discuss ideas for contributions to halogen-hooks-extra (@JordanMartinez). Note: the explanation on hooks will likely be rough due to lack of preparing anything.
Code Generation - presentation and discussion on current status of code generation (@paluh, @jvliwanag, and @srghma)
State of Backend - initiatives on purescript-node-contrib, status of wai/warp libraries, etc. (@paluh, @Woody88)
Art - audio/midi/opengl and procedural art (@tristanC)
Sorry, didn’t notice the FFI part of this message earlier. I recently rewrote Ch10 to cover FFI in greater detail (PR pending), so let me know if that has the answer you’re looking for. I hope the new exercises and tests improve clarity. When you wrote “primeses” did you mean “primes”?
@JordanMartinez yeah a poll sounds good, please go ahead if you’d like to make one, otherwise we can just go with the flow of the moment. I mean, empty rooms are also fine and people will be able to move around anyways
In general I’d like this happening to be as “crowdsourced” as possible, so pretty much everything is welcome
For those voting, keep in mind that rooms which don’t get a lot of votes this time can always be done another time. We can use this poll to help gauge people’s interest in later meetups.
Doc Updates - discuss doc updates since last week / next steps for improving docs and new-user experience (@milesfrain)
Pain Points - how people are using PureSciprt and what their pain points are (@hdgarrood)
Halogen Hooks - explain how it works and discuss ideas for contributions to halogen-hooks-extra (@JordanMartinez). Note: the explanation on hooks will likely be rough due to lack of preparing anything.
Code Generation - presentation and discussion on current status of code generation (@paluh, @jvliwanag, and @srghma)
State of Backend - initiatives on purescript-node-contrib , status of wai / warp libraries, etc. (@paluh, @Woody88)
Art - audio/midi/opengl and procedural art (@tristanC)
I don’t think there should be a whole room dedicated to what I said. I don’t want to direct any discussion really, I just want to listen and hear from others.
Since I just registered and for the past month or so got somewhat more acquainted with Purescript, I’d also like to come for the ride. I can’t contribute with presentations cause I’m such a n00b, but I’m interested in listening on into doc updates, paint points & art (specifically opengl).
@hdgarrood no worries, I was also interested in talking about this. I was thinking we could just use the “main lounge” for things like helping beginners, discussing pain points, general talks, etc. Maybe we can also have some chatting about the registry, as I’d like to bounce some ideas around about that too.
I’d like to maximize time spent in other rooms besides documentation, and so I’m hoping to make the documentation discussion as efficient as possible. I think we could keep it under 10 minutes if we show-up organized with the topics we want to cover. Here are mine:
I’m very late here, but I’ll try anyway. I’ll be happy to discuss anything but I’d like to focus on areas of improvement in the language server/editor integration.
