EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #05248

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: Perl question

The short answer is yes, there has been thinking.  It's hard because if we move over to some kind of MVC Nirvana, we have to make sure all the existing bazaar packages keep working.  We also have to provide an upgrade path for everyone's bespoke functionality.

I remember how big EPrints 2 to 3 migrations were 10 years ago.  3 to 4 (which is really what you're talking about) sounds an order of magnitude bigger.

We should evolve rather than change.

--
Adam Field
Business Relationship Manager and Community Lead
EPrints Services
+44 (0)23 8059 8814





On 4 Dec 2015, at 07:52, Ian Stuart wrote:

> 
> 
> On 03/12/15 13:39, John Salter wrote:
>> Hi,
>> Bit of a random question - around the code in some Metafield modules.
>>> From these two examples:
>> https://github.com/eprints/eprints/blob/3.3/perl_lib/EPrints/MetaField/Id.pm#L26-L31
>> https://github.com/eprints/eprints/blob/3.3/perl_lib/EPrints/MetaField/Date.pm#L25-L37
> 
> Has there been any consideration to a re-write of the code-base - moving 
> to a modern OO framework - or possibly a complete MVC system?
> 
> I'm thinking, in particular of Moose & Catalyst.
> 
> All the database interactions would become SO much easier with Moose, 
> and creations of objects & sub-objects is handled for you.
> 
> -- 
> 
> Ian Stuart.
> Developer: ORI, RJ-Broker, and OpenDepot.org
> Bibliographics and Multimedia Service Delivery team,
> EDINA,
> The University of Edinburgh.
> 
> http://edina.ac.uk/
> 
> This email was sent via the University of Edinburgh.
> 
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
> 
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/