UI Prototype for Search tool
Mar. 22nd, 2002 05:47 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ravencallscrowsThis is a prototype of the tool i was talking about yesterday.
My thought processes now are to try doing it with a Visual Basic wrapper for the SQL calls, but since i'm not a programmer i'm leaving it open to input from anyone with programming skills who might be inclined to help out.
Just a few notes of clarification- this is presently contingent upon being already logged in, and will then query for the user's interests to populate the search drop-downs, and the ComboBox will also allow for text entry (so a user isn't locked into just things on hir interest list- and in the case of NOTs it'd be weird to search on one item in hir list but force the second element to also come from that list). Boolean is also a dropdown, the checkbox should be pretty self-explanatory- and unless it's checked, will need to run some sort of command on the backend to drop the results table from each query just to clean up after itself and keep the database uncluttered.
Presently, i'm thinking about developing this for Win32 and then perhaps expanding to encapsulate it into a web form, simply because making it a standalone application lets me control who has access to it during testing, and if something is fouled up is less likely to be a big mess than opening it up to everyone right away.
My thought processes now are to try doing it with a Visual Basic wrapper for the SQL calls, but since i'm not a programmer i'm leaving it open to input from anyone with programming skills who might be inclined to help out.
Just a few notes of clarification- this is presently contingent upon being already logged in, and will then query for the user's interests to populate the search drop-downs, and the ComboBox will also allow for text entry (so a user isn't locked into just things on hir interest list- and in the case of NOTs it'd be weird to search on one item in hir list but force the second element to also come from that list). Boolean is also a dropdown, the checkbox should be pretty self-explanatory- and unless it's checked, will need to run some sort of command on the backend to drop the results table from each query just to clean up after itself and keep the database uncluttered.
Presently, i'm thinking about developing this for Win32 and then perhaps expanding to encapsulate it into a web form, simply because making it a standalone application lets me control who has access to it during testing, and if something is fouled up is less likely to be a big mess than opening it up to everyone right away.
