-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add to hackage & stackage #15
Comments
Indeed it isn't published. There're things, mostly about the C dependencies
that I'm not entirely sure how to package and didn't have the time to
polish.
But I'd like to. I'd also like for libui itself to progress a bit before
putting more work; I've to check on it.
But you may use it as is with stack by adding the repository as an extra
package, if I'm not wrong.
…On Sun, 8 Jan 2017 at 09:23 flip111 ***@***.***> wrote:
Hello, i searched on hackage for this package but i couldn't find it.
Would you consider adding this package to hackage? Also adding it to
stackage would be nice so that it can be installed with the stack tool.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#15>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ADvexsGyFkCjx27kG-V1qQBu-jQ67g4cks5rQMdDgaJpZM4Ldqmv>
.
|
Looks like a nice library 😄 I understand your reasons, would be nice to have some more exposure |
Thanks... What I'd tell you is I put a non negligible amount of hours into
it and I think it's (by design) aiming to be a dead simple solution for
building GUIs in Haskell.
That being said, with what libui currently supports, the ability to build
complex production apps is really limited; right now, I'd say it's just a
platform one could use to build simple GUIs instead of terminal interfaces
(which I'm personally 100% for).
I'm going to take a look into getting exposure and feedback on this; I'd
like for it to move further.
There's so much great work in the Haskell community (things like
inline-obj-c) that it's tricky to feel really confident about suggesting a
library to people.
The n° reason I'm not working on publishing or getting exposure is that, as
stated on the README, I'm not using this right now. I don't feel good about
pushing something I don't use to people, so that's how it is right now.
But really let's see, it's a new year 🙂
…On Sun, 8 Jan 2017 at 10:17 flip111 ***@***.***> wrote:
Looks like a nice library 😄 I understand your reasons, would be nice to
have some more exposure
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADvexr86aE-484uqGWn7qvpBT7HAchr_ks5rQNPTgaJpZM4Ldqmv>
.
|
@yamadapc Can you elaborate on what the limitations are that you know of? Would be very good to know.
Nonono! :) Just because you're not using something doesn't mean others would't find it hugely useful! UI libaries in Haskel are sorely needed, please do go ahead and make the Hackage/Stackage releases. There's no point feeling under self-pressure that something is not good enough, it may well be good enough for others' use cases. If you're explicit about whether you plan to change things a lot, nobody will complain to you to make something available before you think it's ready. 👍 |
Hello, i searched on hackage for this package but i couldn't find it. Would you consider adding this package to hackage? Also adding it to stackage would be nice so that it can be installed with the stack tool.
The text was updated successfully, but these errors were encountered: