[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [actf-dev] aDesigner question
|
Hi Eleni,
Sorry for this late reply.
> - How/Where do you access and extract DOM and CSS information. And where
> in the code you use this information as an output?
Currently, aDesigner uses HTML Parser
(org.eclipse.actf.model.dom.html.HTMLParser) to obtain the DOM and it does
not use CSS information directly. Instead of CSS, aDesigner uses
currentStyle information from the browser (IE).
(details about currentStyle)
http://msdn.microsoft.com/en-us/library/aa704104(VS.85).aspx
Before we moved to Eclipse, we used a Visual Basic component to obtain
these information. We planned to re-implement this function by using
ACTF's runtime DOM access mechanism (org.eclipse.actf.model.dom.dombycom).
I'm now working for this part as in bug [233615]
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=233615). After the IP
review of Eclipse, we can provide APIs to obtain current style
information.
BTW, even now, you can obtain IE's runtime DOM from
IWebBrowserACTF.getLiveDocument() function.
Elements within the DOM implement
org.eclipse.actf.model.dom.dombycom.IElementEx.
By using getStyle() function of this interface, you can access to CSS
style info (currentStyle) via org.eclipse.actf.model.dom.dombycom.IStyle.
Ex. IStyle.get("backgroundColor"), get("display"), etc.
> - How/Where is the heat-map/overlay visualization done?
> Based on previous discussion with Simon, you mentioned that you might
> extend the visualization. Is this under progress?
Yes. I'm now also implementing the overlay utility.
I plan to provide simple RCP example that includes access to DOM/style
info and overlay.
Best regards,
---
Kentarou Fukuda, Ph.D.
Tokyo Research Laboratory, IBM Japan
Tel: +81-46-215-4659
E-mail: kentarou@xxxxxxxxxx
