W3C home > Mailing lists > Public > www-amaya@w3.org > April to June 2013

Re: When will the next release be posted?

From: laurent carcone <laurent.carcone@orange.fr>
Date: Tue, 09 Apr 2013 11:54:09 +0200
Message-ID: <5163E541.70404@orange.fr>
To: Stanimir Stamenkov <s7an10@netscape.net>
CC: www-amaya@w3.org, Steven Pemberton <Steven.Pemberton@cwi.nl>, alfredovogel@gmail.com

Indeed, there are no internal developments on Amaya currently. Irene and 
Vincent retired and both W3C and Inria stopped their involvment in the 
project. I work partial time at W3C but I have no assignment to work on 
new developments.
Amaya has always been an open source project and I created a github 
repository [1] to get a broader audience.
Some works have been done recently on HTML5 support, I hope to be able 
to integrate them and create a specific snapshot.
But Amaya is a very complex project, used for both production and 
research purposes.
As Stanimir said, the main problem is the rendering engine. Amaya uses 
it's own engine which is the most complex (and biggest) part of the 
code. I don't know this part very well and it would require a huge work 
to be able to maintain it. There was a project two years ago to work on 
the separation of the editor part and the rendering part and use Gecko 
for that, unfortunately this project didn't succeed.
To my point of view, this separation is essential if we want Amaya 
continue to evolve, but as I said, it would require a lot of time. I can 
help on some points but cannot lead.
Nevertheless, I'd like to see a first support of HTML5 on Amaya and I 
think it's possible with the work that has been done on it.


[1] https://github.com/W3C/Amaya

Le 06/04/13 23:53, Stanimir Stamenkov a écrit :
> Wed, 3 Apr 2013 15:44:46 -0700 (PDT), /alfredo87/:
>> amaya is dying... is there any way we can make it come back to live?
>> Can somebody of the contributors post the requirements for continuing 
>> the
>> amaya development  so that the community can organise something to raise
>> funds or contribute to it to keep it open source and develop it 
>> further for
>> at least one or two OS!!
>> It is a super editor and it should not disappear for lack of funds or
>> dedication!!
> Yes, it is a super editor, but its rendering engine lacks behind 
> latest browsers development.  May be the best thing is to try to port 
> it using one of the actively developed open source browser engines 
> (Gecko or WebKit).  I don't think it is feasible to try to develop and 
> maintain a browser engine independently in order to have a great Web 
> authoring tool.
Received on Tuesday, 9 April 2013 09:54:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:44 UTC