Re: [actf-dev] Validation component

[Kentarou Fukuda <KENTAROU@xxxxxxxxxx>]

Hi Yelize,

Please excuse me for this late response.

>> These are the two main reasons why we have decided to use aDesigner.
>> Can you please confirm that aDesigner validation component will
>> continue to be part of Actf?

As Mike wrote, aDesigner component will continue to be part of ACTF. ACTF 
is now owned by community, and we will support ACTF as one of community 
members. If community members use/develop Java based (aDesigner) Web 
validation, we are happy to enhance it with you. 


> MAS: I'm sure it will be but Fukuda-San will need to confirm. Also, keep 
in
> mind that, so far as I know, ADesigner's rules cannot be extended 
without
> writing your own Java code and contributing to the ADesigner codebase. 
If
> you're going to write code, you could just as easily implement the
> requisite API that I discussed in my presentation. Of course, the choice 
is
> yours.

In aDesigner case, most of HTML validation code are separated from 
aDesigner and visualization engine.

As you know, validation code are now in 
org.eclipse.actf.examples.adesigner.eval.html plugin, but it does not 
depend on aDesigner itself. It can be re-used from other 
implementation/application, and developers can add their own validation 
code by using Eclipse extension mechanism (extension point: 
org.eclipse.actf.visualization.eval.checkers). So, developers don't need 
to contribute their code to Eclipse. Of course, we hope they will 
contribute the code to ACTF and improve validation code with community!

In addition to this, when Weblo covers our IE browser component, of course 
we can use it from aDesigner by using this extension mechanism. We will 
provide a sample then.

We are now refactoring visualization part for a preparation of ACTF 
release. We might be able to do some enhancements through this work.

Best regards,
Kentarou
---
Kentarou Fukuda, Ph.D.
Tokyo Research Laboratory, IBM Japan
Tel: +81-46-215-4659
E-mail: kentarou@xxxxxxxxxx