Open Sourcing Studio components
Posted: 06 September 2020, 15:37
I've sifted a bit through this forum and found other threads on open sourcing individual games or all of BGA, but not on this topic specifically. I understand that there are no plans to open source *all* of BGA, but I'm curious to know if just the studio components that are mentioned on the wiki could be made available?
Here is the specific case I'm encountering right now. I'm working on a card game and thought I'd use the Deck component. It turns out that though it has some features I'd like, it's a bit too rigid for my use case. So I'd like to make my own deck-like class that does. But I'm not really sure how Deck is doing shuffle, and there are enough warnings elsewhere on the wiki about randomness, that I'm wary of coming up with my own solution. I'd like to be able to use the Deck's source code as a starting point to create my custom component, but it doesn't seem to be available.
However, my Deck problem is just a specific case that shouldn't distract from a more general issue. Most of the documentation for these types seems incomplete. Some of it even sounds like the author had to to reverse engineer many of the features they describe. Other features (e.g., Draggable) have requests for documentation but no clear pathway for how one would contribute to it.
So would it be possible that just these components be made available somewhere for developers to reference? The code wouldn't need to be functional, just readable. It would also give game developers an opportunity to fill in the gaps in the current documentation.
Here is the specific case I'm encountering right now. I'm working on a card game and thought I'd use the Deck component. It turns out that though it has some features I'd like, it's a bit too rigid for my use case. So I'd like to make my own deck-like class that does. But I'm not really sure how Deck is doing shuffle, and there are enough warnings elsewhere on the wiki about randomness, that I'm wary of coming up with my own solution. I'd like to be able to use the Deck's source code as a starting point to create my custom component, but it doesn't seem to be available.
However, my Deck problem is just a specific case that shouldn't distract from a more general issue. Most of the documentation for these types seems incomplete. Some of it even sounds like the author had to to reverse engineer many of the features they describe. Other features (e.g., Draggable) have requests for documentation but no clear pathway for how one would contribute to it.
So would it be possible that just these components be made available somewhere for developers to reference? The code wouldn't need to be functional, just readable. It would also give game developers an opportunity to fill in the gaps in the current documentation.