Re: UI Committee Round 2
- Posted by xecronix Dec 13, 2015
- 3901 views
At this time there are 131 views and 1 response. I’m not sure how to interpret these numbers except to conclude that as a community, we are not interested in a fully integrated UI/Editor solution.
If that’s true this is good news for several reasons:
- The development team can focus on new features the community actually wants. Like mem- structs?
- I was wrong about the failure of the committee idea. In fact the committee idea was a huge success and was able to drill down to the heart of the problem very quickly.
- Ed can be dropped and consequently less code/docs maintained.
Maybe we should turn our focus towards creating a “General Best Practices” documentation on developing and deploying applications that use community provided DLL wrappers? While we’re at it, some “Best Practices” guide on packaging DLL wrappers for cross platform development? Such training/guides could be beneficial beyond the UI discussions we’ve had recently.
I’ve learned a lot about this problem domain and some of that knowledge will serve me well while working on my EuDrop Project. Additionally, I feel like my experience with this committee will benefit me if I’m involved in another one in the future.
