Hello all, Sorry I've been so absent lately - I hope to be able to dedicate more time to DQSD from now on.
Now that we've started putting the custom host stuff together, and fixed a couple of bugs in the 4.0-branch, I think we should try and get the stuff out the door, so people can start using DQSD properly with SP2. Maybe we should merge the changes to dqsd-40 back into the mainline, add the new DQSDHost project, clean up whatever issues remaining and keep working from the mainline branch? That way, dqsd-40 can still serve as a research/concept testing branch, and when/if we reach something we're happy with we can merge back into the main release branch again. I don't know how familiar with/interested in release management you all are, but do you have any opinions on how we should handle the respective branches? I think it makes sense to merge the experiments from dqsd-40 back into the mainline if we think they are shippable. Here are the issues I know of before we can release a proper 3.2 version: - Help window - there's still an InfoBar popup when the help window is invoked - XmlHttp doesn't seem to work in XP SP2, I don't know if there's a workaround short of writing our own. - Remove the keyboard hook stuff for accelerators, since the new host handles that transparently, and keeping the hooks in place will mean some keyboard accelerators are executed twice (Del, Shift+Ins, etc) - John Bairen had problems with a yellow bar even with the new host, on his work PC - did you ever manage to fix that, John? - Security - evaluate any security risks of having the new host installed. Does having DQSD installed mean malign code can get a chance to execute through the DQSD host, due to the custom DQSD security policy? - Any pending user contributions of searches should be added - Installer - the NSIS script needs to copy in DQSDHost.dll and register it. The custom registry twiddling to setup the current toolbar should be removed - Platform testing - we should make sure the new DLL runs on all target platforms (Win98, 2000, XP SP2, any more?) Do you have any other favorite problems? Also, as of the latest DQSDTools revision in dqsd-40, the project can only be built using VS.NET 2003, since I resorted to using newly-added helper classes to fix the WriteFile problem. Any problems with that? Cheers, - Kim ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
