Show
Ignore:
Timestamp:
08/24/02 05:51:53 (6 years ago)
Author:
rossbencina
Message:

- updated status of proposals 002, 015 and 016 to complete
- added link to possibilities.html

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • pa_proposals/trunk/index.html

    r21 r26  
    1616 
    1717<P><A href="http://www.portaudio.com/">PortAudio Home Page</A></P> 
    18 <P>Updated: August 20, 2002 </P> 
     18<P>Updated: August 24, 2002 </P> 
    1919 
    2020<H2>Introduction</H2> 
     
    2424Most of the proposals propose changes to the definition of the PortAudio API or to the 
    2525way that PortAudio behaves in specific circumstances, some proposals (such as the style guide)  
    26 are concerned with the way in which we implement PortAudio. 
     26are concerned with the way in which PortAudio is implemented. 
    2727</P> 
    2828 
    2929<P> 
    3030The 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.  
     31be 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.  
    3332</P> 
     33 
    3434 
    3535 
    3636<H2>Open Proposals</H2> 
    3737 
    38 <P> The following table lists all of the proposals currently under consideration.  
     38<P> The following table lists the proposals currently under consideration.  
    3939Unless otherwise noted, we are at the design stage with these proposals, even the 
    4040proposals that have been implemented should not be considered frozen yet. If you think  
    4141something 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> 
    4443 
    4544<TABLE BORDER CELLPADDING=2> 
     
    5251                <TD>complete - not implemented</TD> 
    5352        </TR> 
    54         <TR BGCOLOR="#FFCCCC"> 
     53        <TR> 
    5554                <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> 
    5756        </TR> 
    5857        <TR> 
     
    104103                <TD>stable but open for discussion - used in v19-devel</TD> 
    105104        </TR> 
    106         <TR BGCOLOR="#FFCCCC"> 
     105        <TR> 
    107106                <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> 
    109108        </TR> 
    110         <TR BGCOLOR="#FFCCCC"> 
     109        <TR> 
    111110                <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> 
    113112        </TR> 
    114113 
    115114</TABLE> 
    116115 
     116<P> 
     117Potential enhancements which have not yet been developed into 
     118proposals are listed  
     119<A href="possibilities.html">here</A>. 
     120</P> 
     121 
    117122 
    118123<H2>Status Summary</H2> 
    119124 
     125 
    120126<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.  
     127Due 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.  
    123128</P> 
    124129 
    125130<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  
     131All 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  
    133132 
    134133<A HREF="014-StyleGuide.html">014 - Implementation Style Guidelines</A> and  
    135134<A HREF="013-RefactorImplementationInfrastructure.html">013 - Refactor Implementation Infrastructure</A> 
    136135 
    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. 
     136proposals 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. 
    138137</P> 
     138 
    139139 
    140140<H2>Client Impact</H2>