Hi Leandro,
I think it's a good approach and it's really perfect for a warmup task. You
will be able to get to know the different components and help us get rid of
the php code. Although if you decided to use scala, please refactor the
code in such a way that you can make it an Extractor and place it in
/mappings .Please keep us up to date with your progress.
Cheers,
Alexandru
On Mon, Mar 31, 2014 at 3:17 PM, Leandro Doctors <[email protected]> wrote:
> 2014-03-21 18:20 GMT+01:00 Leandro Doctors <[email protected]>:
> > The ticket is:
> > https://github.com/dbpedia/extraction-framework/issues/196
>
> Hi,
>
> Just for the record, I have just pushed my first iteration [0].
>
> The code is still incomplete, and it does not complile yet (I'm still
> researching on how to rewrite some functions still to be rewritten),
> but it is a beginning.
>
> You will notice that I have respected the original design as much as
> possible. My plan is to first rewrite flickrwrappr in Scala still
> following the original PHP logic as much as possible, and only then
> change it into a Scala-like one (make it work, make it right, make it
> fast...).
>
> What do you think about this strategy?
>
> Cheers,
> Leandro
>
> flickrwrappr (first iteration) [0]:
>
> https://github.com/allentiak/extraction-framework/commit/4683cf212e30dfed49a78a9a7c7f646932268d03
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Dbpedia-gsoc mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dbpedia-gsoc
>
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Dbpedia-gsoc mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-gsoc
