Difference between revisions of "Connected Open Source"
From Audacity Wiki
m (Text replace - "http://manual.audacityteam.org" to "https://manual.audacityteam.org")
|Line 39:||Line 39:|
Latest revision as of 20:26, 19 February 2021
|Applications often grow so they contain a script engine, an FTP client, a text editor, a kitchen sink.... We're fighting back against that trend. We have to. We're a small team. The idea instead is connected open source - where possible, re-use existing applications.
Generic GUI Code
- Some of our code is 'framework' code that belongs back in wxWidgets. To allow for that, certain files in the Audacity project CVS are marked as under the wxWidgets license. This is a more permissive license than the GPL. As a result, we can release Audacity as GPL and at the same time, the widget-related framework code is available to the wxWidget project under its own license.
FTP Client (for Podcasting)
- Insert text here
- We don't yet have a text editor, however there has been some talk of an XML editor to edit the project files. It will be needed as Audacity develops, for similar reasons that Inkscape needs a text-based XML editor for editing its SVG files. is one good open source XML editor, or maybe we could use a variant of . Maybe a DOM interface will suffice for talking between the editor and Audacity.
- We don't want to build a MIDI sequencer into Audacity. There are good open source ones out there already. We do want to build good bridges to them.
- For some of our plans we need translucency and anti-aliased lines. For LV2 we need to render 'SVG Icons', so will we become an SVG editor too? Most likely we'll solve it by using as our render library, or perhaps find a higher level SVG abstraction and use that.
Open (Audio) Standards
Where possible our bridges to other applications should be using (open) standards rather than ad-hoc interfaces.