 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Raghu Venkataramana - 21/Aug/06 01:03 PM
Actually, there are many more issues in doing this. We may end up having to rewrite the entire WET core layer in C# to accomplish this. Reason: The current way of accessing the DOM by the WET Core layer uses a lot of its internal DOM construction technique. And WET's DOM Construction methodology is pretty exhaustive and we should try to reuse it rather than reinvent.
Getting bitten by this once again. It appears that we are better off fixing this rather than being hit by a much bigger problem later on. It probably implies some additional effort but it may well be worth it.
As of now, I did find another workaround for the problem that I mentioned yesterday. Yes, I agree it is very important that we put a permanant fix for this (that is, resolve this issue). However given the fact that there is a workaround, this can probably wait for a bit more.
I keep going back and forth on whether or not to implement this. If we do implement this, we are likely to cause big time regressions. Since most of the methods for the dom traversal in ruby use the built in eval method, it may not be appropriate to reimplement this. Instead, try to stick to the current implementation and keep improvising it when we run into new issues.
The jury is finally out. This HAS to be done and HAS to be done now. In fact for the past month.5+ I have been working a lot towards this. At this stage I have completed implementation for most of the objects. What remains is the unit tests for each of these.
The RPC problem seems to be getting hotter. It is important that we fix this before 1.0
We are closer to getting this completed. Shruthi J is working hard towards this. Most of the tests are complete now. What remains is the tests for checking if definition is created correctly
I was wrong in my previous comment (about being close to getting this completed). We are now working on creating a browser dom wrapper for the simulated browser and this seems to be time consuming;
The implementation of this has been completed. We should now start opening separate issues for specific problems.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Closed
Critical
Create the Browser DOM Wrapper directly from C#
