octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GSoC - Octave code sharing


From: Sahil
Subject: Re: GSoC - Octave code sharing
Date: Thu, 19 Apr 2018 07:52:20 -0700 (MST)

Thanks a lot, Kai and Ankit for your valuable comments and suggestions. I've
changed the timeline a bit with needed changes. 
Now for  the summary part:

> Sahil,
> 
> Thank you for the detailed timeline.  I added some comments.  A short
> summary:
> 
> - Devote more time (> 4 weeks) to the implementation of the libCURL
> wrapper,
> weboptions.m, webread.m, webwrite.m, websave.m (in the given order).  The
> communication with the MediaWiki (login, etc.) relies on those functions
> to
> work.

The second week that you see (point 3) has which adds the "wiki" as an
output_format in publish() will not exactly span the complete week and so
libCURL will effectively get almost two weeks there. I do not think that I
should be giving the first two weeks only to libCURL wrapper because from
June 1 to June 10, there won't be any progress and so I think there should
at least be something significant work done before the first evaluation.
Maybe I'll start early with the implementation of wrapper before May 13
itself so that I get more time to focus on the wrapper? 


> - We need to setup a test MediaWiki (I can provide some installation, when
> you start testing).

What exactly are we trying to do here? Will it be setting up a new wiki page
on wiki.octave.org or has it something to do with this kind of MediaWiki[3]
installation? If latter, how will we be communicating to the wiki pages on
wiki.octave.org then? I'm sorry but I'm a bit confused here.


> Another thing I did not mention is, that we need to handle JSON-data. 
> Currently Octave does not support `json(en/de)code` [1] and (bug #53100),
> but we can make use of jsonlab in the meantime [2], which is pure m-code,
> thus easily replaceable but not high-performance.
> 
> Kai.

Should I add this to timeline to implement jsonencode and jsondecode because
these look like a higher priority than the RESTful MATLAB compatible
interface functions? 

And kindly mark the comments on Google doc as 'resolved' if you think the
query is resolved.

[1] https://www.mathworks.com/help/matlab/ref/jsondecode.html
[2] https://github.com/fangq/jsonlab
[3]
https://siko1056.github.io/blog/2017/03/10/getting-to-know-the-mediawiki-api.html#prerequisites-and-preparation


--
Sent from:
http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html





--
Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html



reply via email to

[Prev in Thread] Current Thread [Next in Thread]