Changeset 26 for pa_proposals/trunk
- Timestamp:
- 08/24/02 05:51:53 (6 years ago)
- Files:
-
- 1 modified
-
pa_proposals/trunk/index.html (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
pa_proposals/trunk/index.html
r21 r26 16 16 17 17 <P><A href="http://www.portaudio.com/">PortAudio Home Page</A></P> 18 <P>Updated: August 2 0, 2002 </P>18 <P>Updated: August 24, 2002 </P> 19 19 20 20 <H2>Introduction</H2> … … 24 24 Most of the proposals propose changes to the definition of the PortAudio API or to the 25 25 way that PortAudio behaves in specific circumstances, some proposals (such as the style guide) 26 are concerned with the way in which we implement PortAudio.26 are concerned with the way in which PortAudio is implemented. 27 27 </P> 28 28 29 29 <P> 30 30 The proposals are intended to capture the current state of discussions - when finalised they will 31 be treated as specifications that will guide implementation. The authors are the various members of the PortAudio 32 community and are too numerous to mention here. Please refer to the mailing list archives to see who said what. 31 be treated as specifications that will guide implementation. The authors are the various members of the PortAudio community and are too numerous to mention here. Please refer to the mailing list archives to see who said what. 33 32 </P> 33 34 34 35 35 36 36 <H2>Open Proposals</H2> 37 37 38 <P>The following table lists all ofthe proposals currently under consideration.38 <P>The following table lists the proposals currently under consideration. 39 39 Unless otherwise noted, we are at the design stage with these proposals, even the 40 40 proposals that have been implemented should not be considered frozen yet. If you think 41 41 something is missing, could be improved, or would just like to comment please do so on the 42 <A HREF="http://techweb.rfa.org/mailman/listinfo/portaudio">PortAudio mailing list</A>. 43 </P> 42 <A HREF="http://techweb.rfa.org/mailman/listinfo/portaudio">PortAudio mailing list</A>.</P> 44 43 45 44 <TABLE BORDER CELLPADDING=2> … … 52 51 <TD>complete - not implemented</TD> 53 52 </TR> 54 <TR BGCOLOR="#FFCCCC">53 <TR> 55 54 <TD><A HREF="002-ImproveDeviceFormatsQueryInterface.html">002 - Improve Device Formats Query Interface</A></TD> 56 <TD> open for discussion</TD>55 <TD>complete - not implemented</TD> 57 56 </TR> 58 57 <TR> … … 104 103 <TD>stable but open for discussion - used in v19-devel</TD> 105 104 </TR> 106 <TR BGCOLOR="#FFCCCC">105 <TR> 107 106 <TD><A HREF="015-ImproveCallbackTimestampInfo.html">015 - Improve Callback Timestamp Info</A></TD> 108 <TD> open for discussion</TD>107 <TD>complete - not implemented</TD> 109 108 </TR> 110 <TR BGCOLOR="#FFCCCC">109 <TR> 111 110 <TD><A HREF="016-UseStructsForOpenStreamParameters.html">016 - Use Structs for Pa_OpenStream() Parameters</A></TD> 112 <TD> open for discussion</TD>111 <TD>complete - not implemented</TD> 113 112 </TR> 114 113 115 114 </TABLE> 116 115 116 <P> 117 Potential enhancements which have not yet been developed into 118 proposals are listed 119 <A href="possibilities.html">here</A>. 120 </P> 121 117 122 118 123 <H2>Status Summary</H2> 119 124 125 120 126 <P> 121 The proposals range in complexity from clarifications of existing API functionality, through to renaming API functions for consistency, through to significant feature additions. Due to the interdependency of many of the proposed enhancements, we plan to introduce all API enhancements simultaneously as part of release 19. The CVS repository currently contains a branch named 122 portaudio-v19-devel where enhancements are being implemented. 127 Due to the interdependency of many of the proposed enhancements, we plan to introduce all currently proposed API enhancements simultaneously as part of release 19. The CVS repository currently contains a branch named portaudio-v19-devel where enhancements are being implemented. 123 128 </P> 124 129 125 130 <P> 126 The developer community is in the process of reviewing all proposals. Most proposals are defined in sufficient detail to be implemented, however some completed proposals are dependent on proposals that are still under construction. Of the remaining unfinished proposals, only 127 128 <A HREF="002-ImproveDeviceFormatsQueryInterface.html">002 - Improve Device Formats Query Interface</A> 129 and 130 <A HREF="015-ImproveCallbackTimestampInfo.html">015 - Improve Callback Timestamp Info</A> 131 132 require significant attention. Both the 131 All listed proposals have been reviewed and discussed by the PortAudio developer comunity. All proposals pertaining to API changes are defined in sufficient detail to be implemented. Both the 133 132 134 133 <A HREF="014-StyleGuide.html">014 - Implementation Style Guidelines</A> and 135 134 <A HREF="013-RefactorImplementationInfrastructure.html">013 - Refactor Implementation Infrastructure</A> 136 135 137 proposals only effect implementors and do not effect the API definition itself. Refinement of these proposals is desirable but not critical to the development of release 19. Interested readers are advised to consult the Dependencies section of each proposal for more detailed information.136 proposals only effect implementors and do not effect the API definition itself. Refinement of these proposals is desirable but not critical to the development of release 19. 138 137 </P> 138 139 139 140 140 <H2>Client Impact</H2>
