Recent Posts23476
FARR Plugins and Aliases / FARR Plugin Idea Holy Grail - DQSD (400 searches)
« Last post by mouser on May 06, 2008, 01:43 PM »im sorry czb, but hobby or not, you are a coder. and you should be proud of what you've created. of course there is always more to learn, that's true for every programmer.
as far as being confused by the the xml search files... there is nothing really to it once you understand the idea -- the xml file is just a couple of sections. some sections are just html code which describes the plugin -- that text would just be given to FARR function to display it when appropriate. And then the main section is just pure javascript -- there is nothing to be done with that except to "run" it. so the dq meta plugin really doesnt have to do anything clever here, just "execute" or eval() the javascript block when appropriate.
like i said it may be that ecaradec would want to write this dq meta plugin by writing it in c++ and executing the javascript the way he does it with his javascript sdk already. BUT i think you've really done more complicated plugins than this already, or at least very close.
i think the important thing to realize is that the dq metaplugin doesnt have to care very much at all what is in these xml files, there is very little in there that it has to be concerned with. it just has to read the xml files in to learn which search words are available, and then send certain blocks in the xml (there are xml helper functions built into JS) to the FARR memo mode (or html mode), and execute certain blocks using JS eval() command.
as far as being confused by the the xml search files... there is nothing really to it once you understand the idea -- the xml file is just a couple of sections. some sections are just html code which describes the plugin -- that text would just be given to FARR function to display it when appropriate. And then the main section is just pure javascript -- there is nothing to be done with that except to "run" it. so the dq meta plugin really doesnt have to do anything clever here, just "execute" or eval() the javascript block when appropriate.
like i said it may be that ecaradec would want to write this dq meta plugin by writing it in c++ and executing the javascript the way he does it with his javascript sdk already. BUT i think you've really done more complicated plugins than this already, or at least very close.
i think the important thing to realize is that the dq metaplugin doesnt have to care very much at all what is in these xml files, there is very little in there that it has to be concerned with. it just has to read the xml files in to learn which search words are available, and then send certain blocks in the xml (there are xml helper functions built into JS) to the FARR memo mode (or html mode), and execute certain blocks using JS eval() command.
