-
Notifications
You must be signed in to change notification settings - Fork 16
Please accept ownership of diagrams-gi-cairo #76
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
Comments
Thanks! Hope to take a look soon. |
I've forked diagrams-gi-cairo into the diagrams organization. It might take me a bit longer to get a chance to look through it, make any adjustments, and release it. (Though it doesn't have to be me.) |
Pretty sure the Can you look at getting this fixed up and merged? I want to try |
@YellowOnion well, you can already use There is a point to be made that Also, last time I tried the GI version (about a year ago) there were problems in particular for text. Haven't gotten around to looking closer into that (not sure if it's actually the fault of gi-cairo or I was just doing something nonstandard that just happened to work in |
Oh sorry, I see no references to this sub project in the main documentation, and somehow missed that it's on hackage, saw this thread, so I assumed the sub project was abandoned based on this open bug report...I guess I was getting tired. I'll have test of that, Still brain storming ways to get variable width strokes (trying to do some calligraphic rendering from a graphics tablet). |
Can this issue be closed, if the diagrams group has taken ownership? |
Yes, I think I just forgot to close this issue. And good point about updating documentation to refer to |
I've created diagrams-gi-cairo, a fork of the diagrams-cairo repository to work with haskell-gi instead of gtk2hs. As you might expect, the actual code changes are quite minor, mostly it's wrangling packages and modules.
It seems to work with the one diagram I tried.
Please accept ownership of the project. Think of this as a PR for the addition of an entire repository.
The text was updated successfully, but these errors were encountered: