When will the next release be posted?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

When will the next release be posted?

WebsterJoe
Hi,

Has development on Amaya stopped? The current release is dated Dec.
2009. I thought new versions were to be released approx. 3 times per
year.



Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

Jeff Hunt-5
This is a concern to me. The project seemed to die when Irene Vatton
left it at the end of 2009. Fortunately Amaya had just become a useful
wsywig editor and validator at that time and I continue to use it
regularly. But it seems it will get so far behind its real purpose
that it will fade away.

It has already been removed from the Ubuntu repositories.

W3C should have made an announcement by now about whether there is any
expectation of continuing.

On 6/24/11, Joe Webster <[hidden email]> wrote:
> Hi,
>
> Has development on Amaya stopped? The current release is dated Dec.
> 2009. I thought new versions were to be released approx. 3 times per
> year.
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

Cay Horstmann
Agreed. I am using Amaya every day right now for writing a textbook
(using a microformat and PrinceXML as the backend). It has a tolerable
"what you see is what you need" display and great keyboard shortcuts,
but it also has stability issues that obviously aren't getting
addressed.

2011/6/24 Jeff Hunt <[hidden email]>:

> This is a concern to me. The project seemed to die when Irene Vatton
> left it at the end of 2009. Fortunately Amaya had just become a useful
> wsywig editor and validator at that time and I continue to use it
> regularly. But it seems it will get so far behind its real purpose
> that it will fade away.
>
> It has already been removed from the Ubuntu repositories.
>
> W3C should have made an announcement by now about whether there is any
> expectation of continuing.
>
> On 6/24/11, Joe Webster <[hidden email]> wrote:
>> Hi,
>>
>> Has development on Amaya stopped? The current release is dated Dec.
>> 2009. I thought new versions were to be released approx. 3 times per
>> year.
>>
>>
>>
>>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

Christopher Evans-2
I agree with both the comments below, but would add that W3C, as the body which sets the standards for the web, should have it's own publically available, dedicated editor to demonstrate the full functionality of the web as designed, without proprietary add-ons.



On Fri, 24 Jun 2011 00:50:15 +0100, Cay Horstmann <[hidden email]> wrote:

> Agreed. I am using Amaya every day right now for writing a textbook
> (using a microformat and PrinceXML as the backend). It has a tolerable
> "what you see is what you need" display and great keyboard shortcuts,
> but it also has stability issues that obviously aren't getting
> addressed.
>
> 2011/6/24 Jeff Hunt <[hidden email]>:
>> This is a concern to me. The project seemed to die when Irene Vatton
>> left it at the end of 2009. Fortunately Amaya had just become a useful
>> wsywig editor and validator at that time and I continue to use it
>> regularly. But it seems it will get so far behind its real purpose
>> that it will fade away.
>>
>> It has already been removed from the Ubuntu repositories.
>>
>> W3C should have made an announcement by now about whether there is any
>> expectation of continuing.
>>
>> On 6/24/11, Joe Webster <[hidden email]> wrote:
>>> Hi,
>>>
>>> Has development on Amaya stopped? The current release is dated Dec.
>>> 2009. I thought new versions were to be released approx. 3 times per
>>> year.
>>>
>>>
>>>
>>>
>>
>>
>
>


--
知足无求

Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

Charles McCathieNevile-2
On Fri, 24 Jun 2011 08:01:30 +0200, Christopher Evans  
<[hidden email]> wrote:

> I agree with both the comments below,

I agree that Amaya is a reasonably useful product (it's what I use to  
create documents, since I find HTML an incredibly useful, compact,  
portable and versatile format).

> but would add that W3C, as the body which sets the standards for the  
> web, should have it's own publically available, dedicated editor to  
> demonstrate the full functionality of the web as designed, without  
> proprietary add-ons.

That would be lovely. Unfortunately, I don't think W3C has the funding to  
make it possible - and there are other things I think are even more  
important. (I guess you would need a couple or three full-time people to  
do some development as well as maintenance of the code and the project).

On the other hand Amaya has been open source for a long time. I personally  
don't believe that will make it a better project, or make people take it  
up, but given how often it has demonstrated smart ways to do  
standards-compliant WYSIWYG editing years before the competition I think  
it is a shame that so few people contribute to it.

(Including me. I don't think much of what I did is still there at all -  
maybe some bits of documentation...)

cheers

Chaals

> On Fri, 24 Jun 2011 00:50:15 +0100, Cay Horstmann  
> <[hidden email]> wrote:
>
>> Agreed. I am using Amaya every day right now for writing a textbook
>> (using a microformat and PrinceXML as the backend). It has a tolerable
>> "what you see is what you need" display and great keyboard shortcuts,
>> but it also has stability issues that obviously aren't getting
>> addressed.
>>
>> 2011/6/24 Jeff Hunt <[hidden email]>:
>>> This is a concern to me. The project seemed to die when Irene Vatton
>>> left it at the end of 2009. Fortunately Amaya had just become a useful
>>> wsywig editor and validator at that time and I continue to use it
>>> regularly. But it seems it will get so far behind its real purpose
>>> that it will fade away.
>>>
>>> It has already been removed from the Ubuntu repositories.
>>>
>>> W3C should have made an announcement by now about whether there is any
>>> expectation of continuing.
>>>
>>> On 6/24/11, Joe Webster <[hidden email]> wrote:
>>>> Hi,
>>>>
>>>> Has development on Amaya stopped? The current release is dated Dec.
>>>> 2009. I thought new versions were to be released approx. 3 times per
>>>> year.
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


--
Charles McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com

Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

Laurent Carcone-4
In reply to this post by Jeff Hunt-5
Hello,

Amaya has been mainly funded by INRIA (a French national research
institute) in collaboration with the W3C.
Unfortunately, Irene Vatton has not been replaced and there is no
full-time people working on Amaya currently. With Vincent, we try to
dedicate some time to maintain it, there are some pending modifications
in the cvs base and we'll try to make a release soon. But more important
developments will depend on new funds or external contributions.
Maybe Vincent has more recent infos.

Thanks,
Laurent Carcone


Le 23/06/11 21:22, Jeff Hunt a écrit :

> This is a concern to me. The project seemed to die when Irene Vatton
> left it at the end of 2009. Fortunately Amaya had just become a useful
> wsywig editor and validator at that time and I continue to use it
> regularly. But it seems it will get so far behind its real purpose
> that it will fade away.
>
> It has already been removed from the Ubuntu repositories.
>
> W3C should have made an announcement by now about whether there is any
> expectation of continuing.
>
> On 6/24/11, Joe Webster<[hidden email]>  wrote:
>> Hi,
>>
>> Has development on Amaya stopped? The current release is dated Dec.
>> 2009. I thought new versions were to be released approx. 3 times per
>> year.
>>
>>
>>
>>
>


Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

alfredo87
Hello all,
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!!
Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

Steven Pemberton-3
Good idea!

But can we first ask Laurent what he thinks the basic tasks are (compiling  
for different releases of OSs, packaging, etc, identifying and repairing  
bugs...) and what he thinks the workload is for those tasks.

One possibility is that we identify separable tasks, and distribute them  
over the community.

Steven




On Thu, 04 Apr 2013 00:44:46 +0200, alfredo87 <[hidden email]>  
wrote:

> Hello all,
> 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!!
>
>
>
>
> --
> View this message in context:  
> http://w3-org.9356.n7.nabble.com/When-will-the-next-release-be-posted-tp203030p251098.html
> Sent from the w3.org - www-amaya mailing list archive at Nabble.com.
>

Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

Stanimir Stamenkov-3
In reply to this post by alfredo87
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.

--
Stanimir

Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

Laurent Carcone-4
Hello,

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.

Regards,
Laurent

[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.
>


Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

Frédéric WANG

On 09/04/2013 11:54, laurent carcone wrote:

> Hello,
>
> 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.
>
> Regards,
> Laurent
>
> [1] https://github.com/W3C/Amaya

Hi all,

Gecko C++ code has a rendering engine but also a core editor (the one
used for example by Thunderbird or by the "contenteditable"
implementation. See http://html5demos.com/contenteditable). This editor
gives basic features like cursor navigation, entering text, selection,
copy and paste etc Additionally, some projects (Thunderbird, SeaMonkey,
KompoZer, BlueGriffon) add a user interface for more advanced operations
like inserting an image, a link etc At the moment, it seems that there
are not a lot of developments in the core editor, Thunderbird, SeaMonkey
or KompoZer (because mostly done by volunteers) while BlueGriffon is
actively developed by Daniel Glazman (but some of the features are
proprietary extensions). I think Fabien Cazenave wanted to modify the
Mozilla source to easily build a standalone editor
(https://bugzilla.mozilla.org/show_bug.cgi?id=477845) and that he is
willing to continue his KompoZer editor. I also believed he was hired by
Mozilla to work on the editor at some point. However, I think he now
works essentially on the B2G project (I think during a period he also
worked at WAM, is related to the effort you are mentioning?)

So I'm wondering if Amaya should go further than just use the rendering
engine by Gecko and also consider using its core editor. I did some
experiments a long time ago and that seemed to work, I was able to get a
program with the same UI as Amaya, that uses Gecko's layout engine and
the core editor (I still have the code, but haven't tried to compile it
with recent version of Gecko). But it remains to reimplement the whole
Amaya UI (save menu, css editor, HTML/SVG/MathML palette etc) in
XML+Javascript and perhaps contribute/modify Gecko's core editor. I
agree that maintaining the old and huge Amaya code is probably
impossible without Irène and Vincent's knowledge of the code. Personally
I'd like to improve Gecko-based editors because Amaya does some things
better (e.g. the navigation and copy and paste of MathML). I think if
Amaya shares a base code with all the other Gecko projects, that would
definitely help the maintenance. Also, working with XML+Javascript for
the UI would be much convenient (for example to get contributions from
people without knowledge of C/C++) and stable (Amaya has always had many
crashes) .

--
Frédéric Wang
maths-informatique-jeux.com/blog/frederic


Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

HiddenId
Hello all,
I'm not coder but I'm one of the happy Amaya users group.
The only thing I can do is to encourage you.
It will be so unbelievably great if all of what you mentionned could be done.
Again, from my point of you, Amaya is my preferred html /css editor.
Anyway again, thanks a lot to Irene, Vincent, Laurent, W3C, Inra and any else for the big job done and this very useful tool !!!
So freely,
Antoine


De : Frédéric WANG <[hidden email]>
À : laurent carcone <[hidden email]>
Cc : Stanimir Stamenkov <[hidden email]>; [hidden email]; Steven Pemberton <[hidden email]>; [hidden email]
Envoyé le : Mardi 9 avril 2013 13h15
Objet : Re: When will the next release be posted?


On 09/04/2013 11:54, laurent carcone wrote:

> Hello,
>
> 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.
>
> Regards,
> Laurent
>
> [1] https://github.com/W3C/Amaya

Hi all,

Gecko C++ code has a rendering engine but also a core editor (the one used for example by Thunderbird or by the "contenteditable" implementation. See http://html5demos.com/contenteditable). This editor gives basic features like cursor navigation, entering text, selection, copy and paste etc Additionally, some projects (Thunderbird, SeaMonkey, KompoZer, BlueGriffon) add a user interface for more advanced operations like inserting an image, a link etc At the moment, it seems that there are not a lot of developments in the core editor, Thunderbird, SeaMonkey or KompoZer (because mostly done by volunteers) while BlueGriffon is actively developed by Daniel Glazman (but some of the features are proprietary extensions). I think Fabien Cazenave wanted to modify the Mozilla source to easily build a standalone editor (https://bugzilla.mozilla.org/show_bug.cgi?id=477845) and that he is willing to continue his KompoZer editor. I also believed he was hired by Mozilla to work on the editor at some point. However, I think he now works essentially on the B2G project (I think during a period he also worked at WAM, is related to the effort you are mentioning?)

So I'm wondering if Amaya should go further than just use the rendering engine by Gecko and also consider using its core editor. I did some experiments a long time ago and that seemed to work, I was able to get a program with the same UI as Amaya, that uses Gecko's layout engine and the core editor (I still have the code, but haven't tried to compile it with recent version of Gecko). But it remains to reimplement the whole Amaya UI (save menu, css editor, HTML/SVG/MathML palette etc) in XML+Javascript and perhaps contribute/modify Gecko's core editor. I agree that maintaining the old and huge Amaya code is probably impossible without Irène and Vincent's knowledge of the code. Personally I'd like to improve Gecko-based editors because Amaya does some things better (e.g. the navigation and copy and paste of MathML). I think if Amaya shares a base code with all the other Gecko projects, that would definitely help the maintenance. Also, working with XML+Javascript for the UI would be much convenient (for example to get contributions from people without knowledge of C/C++) and stable (Amaya has always had many crashes) .

-- Frédéric Wang
maths-informatique-jeux.com/blog/frederic




Reply | Threaded
Open this post in threaded view
|

RE: When will the next release be posted?

Jean N Koster

Please remove my name/email from the distribution listthank you

Jean koster

 

From: HiddenId [mailto:[hidden email]]
Sent: Tuesday, April 09, 2013 10:40 AM
To: Frédéric WANG; laurent carcone
Cc: Stanimir Stamenkov; [hidden email]; Steven Pemberton; [hidden email]
Subject: Re: When will the next release be posted?

 

Hello all,
I'm not coder but I'm one of the happy Amaya users group.
The only thing I can do is to encourage you.
It will be so unbelievably great if all of what you mentionned could be done.
Again, from my point of you, Amaya is my preferred html /css editor.
Anyway again, thanks a lot to Irene, Vincent, Laurent, W3C, Inra and any else for the big job done and this very useful tool !!!
So freely,

Antoine

 


De : Frédéric WANG <[hidden email]>
À : laurent carcone <[hidden email]>
Cc : Stanimir Stamenkov <[hidden email]>; [hidden email]; Steven Pemberton <[hidden email]>; [hidden email]
Envoyé le : Mardi 9 avril 2013 13h15
Objet : Re: When will the next release be posted?



On 09/04/2013 11:54, laurent carcone wrote:


> Hello,
>
> 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.
>
> Regards,
> Laurent
>
> [1] https://github.com/W3C/Amaya

Hi all,

Gecko C++ code has a rendering engine but also a core editor (the one used for example by Thunderbird or by the "contenteditable" implementation. See http://html5demos.com/contenteditable). This editor gives basic features like cursor navigation, entering text, selection, copy and paste etc Additionally, some projects (Thunderbird, SeaMonkey, KompoZer, BlueGriffon) add a user interface for more advanced operations like inserting an image, a link etc At the moment, it seems that there are not a lot of developments in the core editor, Thunderbird, SeaMonkey or KompoZer (because mostly done by volunteers) while BlueGriffon is actively developed by Daniel Glazman (but some of the features are proprietary extensions). I think Fabien Cazenave wanted to modify the Mozilla source to easily build a standalone editor (https://bugzilla.mozilla.org/show_bug.cgi?id=477845) and that he is willing to continue his KompoZer editor. I also believed he was hired by Mozilla to work on the editor at some point. However, I think he now works essentially on the B2G project (I think during a period he also worked at WAM, is related to the effort you are mentioning?)

So I'm wondering if Amaya should go further than just use the rendering engine by Gecko and also consider using its core editor. I did some experiments a long time ago and that seemed to work, I was able to get a program with the same UI as Amaya, that uses Gecko's layout engine and the core editor (I still have the code, but haven't tried to compile it with recent version of Gecko). But it remains to reimplement the whole Amaya UI (save menu, css editor, HTML/SVG/MathML palette etc) in XML+Javascript and perhaps contribute/modify Gecko's core editor. I agree that maintaining the old and huge Amaya code is probably impossible without Irène and Vincent's knowledge of the code. Personally I'd like to improve Gecko-based editors because Amaya does some things better (e.g. the navigation and copy and paste of MathML). I think if Amaya shares a base code with all the other Gecko projects, that would definitely help the maintenance. Also, working with XML+Javascript for the UI would be much convenient (for example to get contributions from people without knowledge of C/C++) and stable (Amaya has always had many crashes) .

-- Frédéric Wang
maths-informatique-jeux.com/blog/frederic



Reply | Threaded
Open this post in threaded view
|

Re: When will the next release be posted?

d.j.a.y
Hello there,

I can't say more than all this great discussions and encouragement;...
but a big thank's to those who make it run to here!

In my case, i have knowledge in coding, could help in some part....
maybe nice bug report ;-)
-- 
Http://transmission-libre.org

Formation
Expertise    } Logiciels Libre
Déploiement

 

From: HiddenId [mailto:[hidden email]]
Sent: Tuesday, April 09, 2013 10:40 AM
To: Frédéric WANG; laurent carcone
Cc: Stanimir Stamenkov; [hidden email]; Steven Pemberton; [hidden email]
Subject: Re: When will the next release be posted?

 

Hello all,
I'm not coder but I'm one of the happy Amaya users group.
The only thing I can do is to encourage you.
It will be so unbelievably great if all of what you mentionned could be done.
Again, from my point of you, Amaya is my preferred html /css editor.
Anyway again, thanks a lot to Irene, Vincent, Laurent, W3C, Inra and any else for the big job done and this very useful tool !!!
So freely,

Antoine

 


De : Frédéric WANG <[hidden email]>
À : laurent carcone <[hidden email]>
Cc : Stanimir Stamenkov <[hidden email]>; [hidden email]; Steven Pemberton <[hidden email]>; [hidden email]
Envoyé le : Mardi 9 avril 2013 13h15
Objet : Re: When will the next release be posted?



On 09/04/2013 11:54, laurent carcone wrote:


> Hello,
>
> 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.
>
> Regards,
> Laurent
>
> [1] https://github.com/W3C/Amaya

Hi all,

Gecko C++ code has a rendering engine but also a core editor (the one used for example by Thunderbird or by the "contenteditable" implementation. See http://html5demos.com/contenteditable). This editor gives basic features like cursor navigation, entering text, selection, copy and paste etc Additionally, some projects (Thunderbird, SeaMonkey, KompoZer, BlueGriffon) add a user interface for more advanced operations like inserting an image, a link etc At the moment, it seems that there are not a lot of developments in the core editor, Thunderbird, SeaMonkey or KompoZer (because mostly done by volunteers) while BlueGriffon is actively developed by Daniel Glazman (but some of the features are proprietary extensions). I think Fabien Cazenave wanted to modify the Mozilla source to easily build a standalone editor (https://bugzilla.mozilla.org/show_bug..cgi?id=477845) and that he is willing to continue his KompoZer editor. I also believed he was hired by Mozilla to work on the editor at some point. However, I think he now works essentially on the B2G project (I think during a period he also worked at WAM, is related to the effort you are mentioning?)

So I'm wondering if Amaya should go further than just use the rendering engine by Gecko and also consider using its core editor. I did some experiments a long time ago and that seemed to work, I was able to get a program with the same UI as Amaya, that uses Gecko's layout engine and the core editor (I still have the code, but haven't tried to compile it with recent version of Gecko). But it remains to reimplement the whole Amaya UI (save menu, css editor, HTML/SVG/MathML palette etc) in XML+Javascript and perhaps contribute/modify Gecko's core editor. I agree that maintaining the old and huge Amaya code is probably impossible without Irène and Vincent's knowledge of the code. Personally I'd like to improve Gecko-based editors because Amaya does some things better (e.g. the navigation and copy and paste of MathML). I think if Amaya shares a base code with all the other Gecko projects, that would definitely help the maintenance. Also, working with XML+Javascript for the UI would be much convenient (for example to get contributions from people without knowledge of C/C++) and stable (Amaya has always had many crashes) .

-- Frédéric Wang
maths-informatique-jeux.com/blog/frederic