I'm in the process of trying to make Vixen 3 more accessible to everyone -- this includes users and any developers that are keen on helping out. There's lots to do, and it's a big project that can use help from anyone -- testing, documentation, writing code, coming up with ideas and fleshing them out -- so if you'd like to help out, we'd love to have you!
Developer Documentation
As part of that, I'm planning on putting together a bit of a crash-course on module development, and information that people might need to get started. It's a huge, daunting task, and I have no idea where to start.... so I'm wondering if I can ask you, as a developer (or any other sort of helper) what information you want to see? Where can I start? What do you want to know?
We're starting up a wiki to put information into, so I'll hopefully be able to put a lot of it up there. If you can let me know what you want, I'd be happy to oblige!
Developer discussion group & email list
Also, for the last year or two we were using a google group as an email list for developers to discuss things, bounce ideas around, etc. I'm trying to get it going again, since I'm finding that I'm replying to a lot of PMs and private emails -- and if there's a chance that sharing with one person can help others, then it's worth doing so.
You can find the VixenDev google group here. (At least, I hope that's the right link! Let me know if there's problems signing up). If you sign in with a google account, you should be able to request membership to the group, and I'll approve them ASAP. Then, it's a handy email list which we can use for discussion, help, and collaboration.
The group isn't intended for coding discussion only -- hopefully we can get testers, documenters, etc. in there as well. (sure, 80% is probably going to be software/code talk, but hopefully there's other stuff that's useful as well.) I want it to be for anyone that is interested in the 'behind the scenes' of Vixen.
Where to get the code
The modules repository (which is 90% of the functionality in Vixen) is open source on Github. The repository can be found here:
https://github.com/sall/vixen
I know some of you might not be used to Git as source code management, or GitHub specifically, so I'll try to write up some documentation about how to get the code, how to get it working, how to commit stuff and merge in changes, etc. (Or if someone else wants to volunteer, that would be great too!) If you're new to Git, I'd strongly recommend getting TortoiseGit to help manage it; I use it, and it's fantastic.
--
Thanks for any help you're able to provide! Looking forward to your help in making Vixen a fantastic product that people can do _really cool stuff_ with!
Developer Documentation
As part of that, I'm planning on putting together a bit of a crash-course on module development, and information that people might need to get started. It's a huge, daunting task, and I have no idea where to start.... so I'm wondering if I can ask you, as a developer (or any other sort of helper) what information you want to see? Where can I start? What do you want to know?
We're starting up a wiki to put information into, so I'll hopefully be able to put a lot of it up there. If you can let me know what you want, I'd be happy to oblige!
Developer discussion group & email list
Also, for the last year or two we were using a google group as an email list for developers to discuss things, bounce ideas around, etc. I'm trying to get it going again, since I'm finding that I'm replying to a lot of PMs and private emails -- and if there's a chance that sharing with one person can help others, then it's worth doing so.
You can find the VixenDev google group here. (At least, I hope that's the right link! Let me know if there's problems signing up). If you sign in with a google account, you should be able to request membership to the group, and I'll approve them ASAP. Then, it's a handy email list which we can use for discussion, help, and collaboration.
The group isn't intended for coding discussion only -- hopefully we can get testers, documenters, etc. in there as well. (sure, 80% is probably going to be software/code talk, but hopefully there's other stuff that's useful as well.) I want it to be for anyone that is interested in the 'behind the scenes' of Vixen.
Where to get the code
The modules repository (which is 90% of the functionality in Vixen) is open source on Github. The repository can be found here:
https://github.com/sall/vixen
I know some of you might not be used to Git as source code management, or GitHub specifically, so I'll try to write up some documentation about how to get the code, how to get it working, how to commit stuff and merge in changes, etc. (Or if someone else wants to volunteer, that would be great too!) If you're new to Git, I'd strongly recommend getting TortoiseGit to help manage it; I use it, and it's fantastic.
--
Thanks for any help you're able to provide! Looking forward to your help in making Vixen a fantastic product that people can do _really cool stuff_ with!
Last edited: