from my daily work with JQuery i have to things you may like to consider in the future:
a) CVS Updates
when updating code from the cvs, i am not sure how often the jquery update is called. one time i had the impression that whenever a single resource from the current factbase is cvs updated, a jquery factbase rebuild follows. that slows things down. maybe this can be left to the user for manual refresh later or done at the end of the cvs update. i am not sure if the eclipse resource change event would indicate the origin to be a cvs update.
b) Debug Perspective
whenever i set a breakpoint in the debugger, a jquery factbase build/update occurs. sometimes it is quicker sometimes slower. i dont think you include breakpoints in predicates at all. with breakpoint toggling every other minute Jquery slows runtime code analysis down. ok i need less runtime analysis with jquery. the jquery benefit is high for me. still i find the slowdown somewhat annyoing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
from my daily work with JQuery i have to things you may like to consider in the future:
a) CVS Updates
when updating code from the cvs, i am not sure how often the jquery update is called. one time i had the impression that whenever a single resource from the current factbase is cvs updated, a jquery factbase rebuild follows. that slows things down. maybe this can be left to the user for manual refresh later or done at the end of the cvs update. i am not sure if the eclipse resource change event would indicate the origin to be a cvs update.
b) Debug Perspective
whenever i set a breakpoint in the debugger, a jquery factbase build/update occurs. sometimes it is quicker sometimes slower. i dont think you include breakpoints in predicates at all. with breakpoint toggling every other minute Jquery slows runtime code analysis down. ok i need less runtime analysis with jquery. the jquery benefit is high for me. still i find the slowdown somewhat annyoing.