Frequently Asked Questions
You know, questions some people did or might ask. Please feel free to ask your own questions (for that matter, feel free to ask them frequently if that's your thing.)
- Aren't there already enough file converters? I have several programs that can import and ...
- Why the name VectorSection?
- When will it be done?
- Can I help?
- In which programming language is VectorSection written?
- Can I write connectors in language X?
- I don't have a subversion client. Do you have snapshots?
- Is there a C API?
- There should be a C API.
- Will Perl/Python/Ruby code be fast enough?
A: No. There may be a lot of converters, but we wanted some quality with our quantity. If conversion is done only from an import/export menu in software with a graphical interface, this makes it difficult to create automated processes and distracts you from the task at hand. VectorSection is built from reconfigurable components, so it can be included in GUI menus as easily as in a batch process.
A: Never. This project is completely ongoing. It is usable now, and always will be. Because of its distributed, modular design, VectorSection is able to grow without destabilizing any of the existing connectors.
A: Yes! There are even more ways to help with VectorSection than with typical open-source projects. If you can write code, you can write a connector. It doesn't matter what language you know. See the task list for open items.If you are not a programmer, you can certainly help with testing or documentation. We could also use help with building binary packages and other distribution stuff. Just ping me or one of the mailing lists and tell us how you want to help. Of course, donations and sponsorship are always welcome.
A: Lots. Due to the loosely-coupled architecture, any language is fair game (though choosing a language with YAML libraries makes things easier.) Given the cross-platform and open-source nature, a connector is most useful if the language has a well-supported open-source toolchain. The project maintainers speak Perl, Python, Ruby, C, C++, Fortran, Lisp, and Objective C. Java and C# might work, but you have to prove that we won't have trouble integrating it with our test and install setups.
A: File conversion is not a highly interactive operation, so waiting 5 seconds is certainly tolerable and that is a really large file in most practical applications. Average times run in the neighborhood of ~0.5s. The primary goal of this project is to provide as much functionality as soon as possible. If something is really too slow, we will cross that bridge when we come to it. Better to wait 15 seconds for a big job than to wait 15 years for it to run in 5.