Hi, Ettore To make things more clearly, I draw an diagram . Hope to be helpful. Please see the attachment. gilbert On Thu, 2003-05-29 at 13:34, henry jia wrote: > Hi, Ettore, > > You may have received 2+ such mails. Here is a summary of the > accessibility work. 6+ engineers will work on this. 3+ have begun the > work. 3 more engineers will begin the work from the middle of next > month, June. The work is planned to be finished in early of December. > For the resources, 2.5+ engineers will focus on gal + evolution > contacts, near 2 engineers will focus on gtkhtml + evolution mail/shell, > and near 2 engineers will focus on evolution calendar. > > Here is the brief plan about how to do the work. > > 1. code location > For gal & gtkhtml, we'll put the code in the current a11y directories. > For evolution, we need to create the related 'a11y' directories. For > example, we'll try to create 'a11y' under 'calendar'. > > 2. code review > We'll be sure to ask for code review from the module owners/experts > before we put the code in. We'll obey the community rules. Since there > will be lots of code generated, to accelereate the process, do you think > if we need fixed contact(s) for the code review? > > 3. keep evolution stability > To keep evolution stabe and not make evolution affected by the new code > of a11y, we try to use a compiler switch '--enable-a11y=on/off'. It's > 'off' by default, if someone wants to build the evolution with a11y > support, he can make the switch 'on'. After the main work is done and > evolution is tested throughly with a11y support, we can then try to > remove this compiler switch. > > Any suggestions are appreciate. >
Attachment:
evo_acc_architecture_20030529.GIF
Description: GIF image
