Re: Handle graphics plotting functions

Petr Mikulik <[email protected]> Wed, 15 Feb 2006 15:52:12 +0100 (CET)
Newsgroups gmane.comp.gnu.octave.graphics
Message-ID <[email protected]>
>> Try it on an image of 512x512, 1024x1024 or larger. It takes dozens of
>> seconds by the .m code, and that's why the C++ improvement is a must.
>> 
> You must convince John of this if the code is to go into octave itself. Its 
> probbaly not a good idea to include a function with the same name and 
> function as an existing function in octave, as the politic at the moment is 
> to remove such things by migrating them back to octave or dropping them. 
> Though inclusion in octave-forge under another name is possible.

I thought current Octave politics goes to Matlab compatibility, and to speed 
improvements. If my histogram implementation coincides with them, then it is 
up to Octave maintainers to decide whether my code should replace the 
current implementation. I don't think it makes any sense to provide the same 
function under different name.

>> >> I would recommend that you contribute them to octave-forge,
>> >> probably in the main/general directory.
>> 
>> No, I'm not on the list.
>> 
> Do you want to be? If the answer is yes,

No. As it seems to me, other people have different ideas what kind of code 
should go into those projects. I don't want to spend time convincing people 
what is better. If nobody is using Octave for image processing for 
histogramming images larger cca >100^2 pixels, then my hist.cc has really no 
considerable impact.

>> I don't have and won't have time to maintain gnuplot subsystem in Octave,
>> sorry. But that project would need someone to check/update the code for
>> gnuplot 4.0 features, and it was what I have asked in my earlier mails.
>> That person can get support from gnuplot developers from this or from
>> gnuplot-beta mailing list.
>> 
> Would you maintain hist, histc, and ginput? Maintaining your own code is all 
> anyone can ask for..

I do maintain hist.cc and ginput.m, and with Daniel Sebald also imagegp.m. 
This work is done. Again, whether those codes go to Octave or Octave-forge, 
is up to their responsibles. Until now, they have not decided any of these 
codes will be accepted.

---
Petr Mikulik