Re: Problem with inputParser and anonymous functions for validators

[Juan Pablo Carbajal]

On Sat, Sep 22, 2012 at 11:30 AM, Jose <address@hidden> wrote:
> On 09/22/2012 11:44 AM, Juan Pablo Carbajal wrote:
>>
>>
>> @Jose: You know you can edit the help of these functions yourself? Let
>> me know if you do not know and need some help to ge the hands on it.
>
>
> Let's say that I have an intuition about how to do it, but no "official"
> instructions (which I'd like to have, yes).
>
>
>> If we do this, then you can send us the respective correction. In that
>> way you will be helping GNU Octave to get better!
>> At the same time you will getting the hands of how to write
>> documentation and functions for Octave, with some luck we will have
>> you(!) among the usual contributors in no time.
>
>
> Even better than explaining me, it would be nice to write it down in a wiki
> or alike, so it can be used as a reference to others ;). And if that is
> available already, please point me to the right place so that I can read it
> :). Sometimes finding things about octave in the web pages is really tricky
> ;).
>
> BR
> Jose
>
>
>

Hi Jose,

Ok, if the help here helps than I will transcribe it to the wiki...
though you could also do it! ;)

== One shot contribution ==
- All forge packages (name will change as soon we have Agora online
running) are hosted here
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/
You can look for the package in question, get the latest version that
could be unreleased (that is, it is not yet listed in the OctaveForge
website anmd you will not ge tit by doing >pkg -forge install
my-package). You can use this function if you copy on top of the old
one (or rename the old one to *_old.m), but be careful because it may
require other new functions. Anyway, you can get the latest and
coolest version of any package from that site.
- Once you have the newest version of the function, check if it still
has the bug you found. If it doesn't somebody solved it already. If
the problem still there go on an fix it!
- Once you have fixed the bug, you can send a patch with your changes.
How do you this? Start another thread or read the relevant parts of
the documentation of "diff" and
"patch"(http://www.gnu.org/software/diffutils/manual/diffutils.html).

=== Another way ===
You can also checkout the package in question using svn. For example
if you wan to checkout the general package you would run
> svn co 
> https://octave.svn.sourceforge.net/svnroot/octave/trunk/octave-forge/main 
> general general_to_debug

This will create a folder "general_to_debug" in your current
directory. You can hack away as much as you can and then produce the
patch and send it to the mailing list.

=== New files or buch of files ===
There is a third way of contributing to Octave.Lets say you do not
want to be a developer but you have one or a bunch of functions you
want to share with us. You can use the Features request forum (this
willbe also replaced by Agora when it is up and running)
https://sourceforge.net/tracker/?group_id=2888&atid=352888
Upload your file (compressed if it is more than one) and lets us know
that you did it by sending a mail to the mailing list. If there is
anybody interested they will look at your code and give you
suggestions. Speed up that process by adding a GPL compatible license
(http://en.wikipedia.org/wiki/List_of_FSF-approved_software_licenses)

== Being a Forger ==
If you want to be one of us, you can also request to be a Forge
developer (name may change) following the instructions here
http://octave.sourceforge.net/developers.html

Let us know if there are more questions

Looking forward for your next contribution

-- 
M. Sc. Juan Pablo Carbajal
-----
PhD Student
University of Zürich
http://ailab.ifi.uzh.ch/carbajal/