Hi Kim,

> Here's a new version that has this [F8] fixed...

Hmmmm... While F8 works (yay!) to do the whole history browsing thing,
something else has changed, too.

I use a multiline search bar. It's got room for about three lines of
displayed text. I frequently (read: 50+ times a day) use URLs in there
that have literal breaks in them and they are added to the history as a
single complete entry. Now, those same entries are broken on each
carriage return inside the history. Here's an example:

https://example.com/folder/tbl_change.php?
is_js_confirmed=1
&db=database
&table=table
&token=123456789123456789123456789123456789
&pos=0
&goto=tbl_properties.php
&sql_query=SELECT * FROM `table` WHERE ID=19
&show_query=0
&SQL=Go

This SINGLE URL placed in DQSD formerly was added as a single entry in
the history cache. Noiw it is divided into ten entries. If I F8 "tab"
only lines 3, 4 and 8 show up, and they show up separately, so I cannot
easily re-issue this exact URL (or a modified version of it). This is
true of browsing back individually (up and down) through the history as
well - all of these lines have become split on their carriage returns
within DQSD. :((

It might sound nuts, but it's SO much easier to edit multiple parameter
URLs in notepad and then copy/paste them into DQSD to test them; then
modify them directly in DQSD with use of "'home','left'" and
"'end','right'" keys to step to the next parameter. DQSD has always
reunited the URL correctly and treated it as a single line when issuing
the URL to the actual browser. It still does this part right, but it's
added to the history incorrectly, so it's consumed wrong when browsing
the history.

Any chance the previous behaviour can be restored? What changed to make
it work differently now?


As for 98 and 95 with 3.2... the original 98 (not SE) /out of the box/,
and 95 do not work. I suspect it is an IE thing, as 95 has IE3 and 98
has IE4. 98 SE works just fine, however.


> How do you all feel about adding features to
> window.external? Can you see any problems with it?

My fear with overloading window.external is the potential accessibility
issues of the existing search structure to future implementations. If we
add custom objects to window.external and these are then used within
searches, if someone (like me) ever gets around to implementing a DQSD
search box on a website, the searches created for DQSD using the
overloaded external will either simply fail or raise errors or do
something else "funky" depending on the usage of the accessory object.

If we go the route of overloading window.external, we need to wrap the
functionality directly within exposed JS methods in a separate file so
the objects are called within searches via a JS routine exposed from an
external library of some sort that can be easily replaced with a
different mechanism. I confused myself when I wrote that. Here's a
code-level breakdown:


'// ========================================================
The wrong way:

Somewhere in the code of sample.xml (a "search"):

  window.external.mapKeyCode("WIN+I", sample_keyhandler);

...which calls window.external.mapKeyCode() directly. This method breaks
the ability to use the search-level code block within a browser
(testing) or within a third-party utility that doesn't expose
window.external.mapKeyCode().


'// ========================================================
The right way:

Somewhere in the code of sample.xml (a "search"):

  mapKeyCode("WIN+I", sample_keyhandler);

And tools.js includes the following function:

function mapKeyCode(keyBinding,functionCall)
{
  var bReturn;
  try
  {
    bReturn = window.external.mapKeyCode(keyBinding,functionCall);
  }
  catch (e)
  {
    alert('Unable to map key binding:\n' + e.description);
    bReturn = false;
  }
  return (bReturn);
}
'// ========================================================

We can later replace the mapKeyCode() function contents with anything we
need based on the situation and the searches don't have to be touched to
do it. It's safer this way.

Regards,

Shawn K. Hall
http://12PointDesign.com/



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel

Reply via email to