1,847
edits
Short projects: Difference between revisions
Jump to navigation
Jump to search
Add note do Developer FAQ.
(→Missing functions / feature requests: add bug #57699) |
(Add note do Developer FAQ.) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
* in a reasonable amount of time (a few hours) and | * in a reasonable amount of time (a few hours) and | ||
* without Octave development knowledge. | * without Octave development knowledge. | ||
{{Note|If you never contributed to Octave before, we suggest to start with our [[Developer FAQ]].}} | |||
{{warning|Please do not submit patches/fixes to the Octave mailing lists. Upload your work at the respective Savannah bug tracker pages. Of course you may always ask questions related to your work on the mailing list.}} | {{warning|Please do not submit patches/fixes to the Octave mailing lists. Upload your work at the respective Savannah bug tracker pages. Of course you may always ask questions related to your work on the mailing list.}} | ||
| Line 30: | Line 32: | ||
* {{bug|41844}} - GUI Debug Menu could offer "Stop If..." | * {{bug|41844}} - GUI Debug Menu could offer "Stop If..." | ||
* {{bug|47239}} - calling system without shell | * {{bug|47239}} - calling system without shell | ||
* {{bug| | * {{bug|57699}} - 'clipboard' function to interact with clipboard contents | ||
* {{bug|39439}}, {{bug|39434}} - Use non-empty identifiers in all warnings and errors issued by Octave | * {{bug|39439}}, {{bug|39434}} - Use non-empty identifiers in all warnings and errors issued by Octave | ||
** You may tackle as many or as few IDs as you have time for. As it is a widespread issue, finding occurrences in the source code should give you valuable knowledge about the way Octave files are organized. When raising errors and warnings try to use the ids that are documented in the functions {{manual|warning_005fids|warning_ids}} and {{manual|error_005fids|error_ids}}. If you really need a new id (please, first read the ones already there!), please add it to those functions as well. If you see other ids used in core that are not given by the functions mentioned above, please, report or submit patch for them, in addition to the patch to the calling functions as well. | ** You may tackle as many or as few IDs as you have time for. As it is a widespread issue, finding occurrences in the source code should give you valuable knowledge about the way Octave files are organized. When raising errors and warnings try to use the ids that are documented in the functions {{manual|warning_005fids|warning_ids}} and {{manual|error_005fids|error_ids}}. If you really need a new id (please, first read the ones already there!), please add it to those functions as well. If you see other ids used in core that are not given by the functions mentioned above, please, report or submit patch for them, in addition to the patch to the calling functions as well. | ||
* Lists of missing functions for [[:Category:Missing functions|several packages]]. | * Lists of missing functions for [[:Category:Missing functions|several packages]]. | ||
** It would help to group the missing functions in the [[image package]], as per [ | ** It would help to group the missing functions in the [[image package]], as per [https://www.mathworks.com/help/images/referencelist.html] (similar to what was done in the [[signal package]] wiki page); please keep the original alphabetical list intact. | ||
== Function Compatibility == | == Function Compatibility == | ||
| Line 42: | Line 42: | ||
A number of functions are implemented, but may have known incompatibilities to Matlab or only partially handled option sets, etc. | A number of functions are implemented, but may have known incompatibilities to Matlab or only partially handled option sets, etc. | ||
* | * griddata: Octave's griddata functions are only partly Matlab compatible. There are three un-implemented interpolation methods: 'v4', and 'cubic' for 2D and 'natural' for 2D and 3D. The 2D cases should be straightforward once the correct algorithm is determined. But 3D cases are handled by passing to griddata3 and griddatan, and griddatan does not have a requirement to handle 'natural', so some thought will need to go into how to implement that one. It may involve removing the griddata3 passthrough altogether. {{bug|33539}} {{bug|35178}} {{bug|57323}} {{bug|57835}} | ||
== Review or create changesets == | == Review or create changesets == | ||
| Line 62: | Line 62: | ||
* Use "units.h" from [http://www.gnu.org/software/units/ GNU units] in [http://octave.sourceforge.net/miscellaneous/function/units.html function units] (from the Octave-Forge [http://octave.sourceforge.net/miscellaneous/ miscellaneous package]) rather than making a system call and parsing its output (and having to handle multiple versions of it). This change will make it much more robust. It likely will alleviate the requirement of having [http://www.gnu.org/software/units/ GNU units] installed in the system separately by the user. This requires knowledge of C (units is written on C) and C++ to write its Octave interface. It can be very easy if the units.h truly allows to be used as library or maybe impossible if it does not. This has not been investigated yet. | * Use "units.h" from [http://www.gnu.org/software/units/ GNU units] in [http://octave.sourceforge.net/miscellaneous/function/units.html function units] (from the Octave-Forge [http://octave.sourceforge.net/miscellaneous/ miscellaneous package]) rather than making a system call and parsing its output (and having to handle multiple versions of it). This change will make it much more robust. It likely will alleviate the requirement of having [http://www.gnu.org/software/units/ GNU units] installed in the system separately by the user. This requires knowledge of C (units is written on C) and C++ to write its Octave interface. It can be very easy if the units.h truly allows to be used as library or maybe impossible if it does not. This has not been investigated yet. | ||
* Review old bugs: The [http://bugs.octave.org Octave bug tracker] has over 1,000 reports dating all the way back to 2010. Some have patches submitted but can no longer be directly applied to the current codebase. Some have never had patches developed. Some are old, unfulfilled wish list or missing function requests. And some may no longer be bugs, having been fixed or rendered irrelevant due to other changes code changes over the years. Reviewing these old bugs, testing the original bug report to see if the same results still occur, if Matlab compatibility has changed, or if submitted patches can still be applied cleanly (and potentially cleaning up patches so they can apply cleanly), can help update and clean up the bug database. | |||
[[Category:Development]] | [[Category:Development]] | ||
[[Category:Project Ideas]] | [[Category:Project Ideas]] | ||
[[Category:Missing functions]] | [[Category:Missing functions]] | ||