4 ms·
No Documentation? Documentation as an afterthought is not a good sign that this was well thought out. How about a white paper? A tutorial? Just code?
by waynecochran 8y ago
No Documentation? Documentation as an afterthought is not a good sign that this was well thought out. How about a white paper? A tutorial? Just code?
- vortico 8y agoWhy would you need an entire whitepaper for wrapping OS widgets in a window? The API is the documentation, and the example code gives you everything you need to get going. Why would you need anything else?
- pacaro 8y agoI’m mixed on whether api docs are needed, if you have them, they have to be kept in sync, if you don’t then examples have to cover as much of the api surface area as possible Higher level docs would be nice though, goals and non-goals, high level feature roadmap etc. For example a cursory reading of the code suggests that there is no a11y support, which is a deal breaker for some projects and not so important for others, it would be nice to know where that sits on the roadmap
- vultour 8y agoA whitepaper for some dude’s personal project, the sense of entitlement is astonishing.
- waynecochran 8y agoI am sorry -- I assumed since this reached the top page of HN that this was a bit more serious that just some dude's personal project. This portable graphics API thing has been tried 10000x and they are almost never useful for any significant app you want to write. I see one of these and I hope that maybe someone has figured it out -- one glance and I see no documentation nor any rational as to why this effort is unique, then I know this is not a serious offering.
- andlabs 8y agoI do intend on this being a serious offering; it just wasn't an offering I was ready to make yet when people jumped on it. What have people not yet figured out about cross-platform graphics? If we knew exactly what was wrong, we could fix it...