Sunday, June 22, 2008 10:56 AM
We exhibited at the Special Libraries Association conference in Seattle last week and greatly enjoyed meeting many of our clients at the booth and at the Inmagic customer appreciation reception.
Inmagic released a flurry of announcements in conjunction with the conference:
The announcement that Genie will soon be available on the DB/Text platform is welcome news as it should mean a simpler install and upgrade path. Clients with non library related textbases will no longer have to convert these to the CS version.
Check out the new Inmagic blog and subscribe to their feed to keep up to date with news and announcements. You can of course also contact us if you have any questions.
Sunday, June 22, 2008 10:23 AM
As well as adding canned queries to Inmagic Genie search results elsewhere on your web site, you can also add them right into the heading area on your query screens.
In this example above we have added links to a Journals List and to Recent Acquisitions.
The code to add the View All Journals link is the canned search syntax added to the Heading = parameter in your MyQueries.config file.
You can also move the links between Simple and Advanced searches to this Heading area instead of using the default drop down.
Don't forget to change the section at the bottom of the config file that lists which search screens display. We usually comment this out rather than remove it.
(Thanks to Lisa and Jean at Inmagic for these tips.)
Friday, June 13, 2008 11:34 PM
As reported in my last post, Inmagic Webpublisher 11 broke some of our utility scripts. This release is compatible with WPP 11, and is still backwards-compatible with earlier versions.
Download them from our demo site at ask.andornot.com:
Andornot Search Utilities 1.9
Andornot Result Utilities 1.11
Friday, June 13, 2008 10:22 AM
is NOT recommended.
Usually not added when you first install WPP, check your DBTWPUB.ini file in your WPP installation folder on your web server. Make sure that you do not have the line of code "WebCSSOpt=2" as our ASK web forms will not display properly.
You can edit the DBTWPUB.ini file in Notepad and either change it to WebCSSOpt=0 or delete that line entirely.
Below is the DB/TextWorks Help file article for more information....
WebPublisher PRO: Form layout
By default, WebPublisher version 4.1 and later uses Cascading Style Sheets (CSS) and absolute positioning, so that report, display, and edit forms look as much as possible as they would look in DB/TextWorks.
WebPublisher detects whether the browser supports Cascading Style Sheets. If not, WebPublisher uses simple HTML (boxes will be left-justified, box labels will appear on top rather than to the left, and so forth).
Forms that contain Raw HTML or inline images are incompatible with absolute positioning. Forms containing these elements will have overlapping text unless very carefully designed. Therefore, simple HTML is used for this type of form unless you explicitly set WebCSSOpt=2 in your DBTWPUB.INI file (see below).
Note: DB/TextWorks tabular forms do not use absolute positioning, so this issue does not affect them.
You can use picture boxes in place of inline images to retain CSS formatting. The Image size option specified using Box Properties>Position in the Form Designer is used. In order for the image sizing to work properly, the images must reside either in the textbase folder (for example, C:\CATALOG\) or the folder specified in the Image field in the record (for example, C:\IMAGES\COYOTE.JPG).
To control whether the site uses CSS, set the WebCSSOpt= parameter in the [WebPublisher] section of your DBTWPUB.INI file equal to one of the following:
0 = do not use CSS 1 = the default behavior 2 = use CSS regardless of whether forms contain Raw HTML or inline images
Note: The WebCSSOpt= parameter affects all forms and all textbases, unless you override it using the CS= parameter in an individual query screen.
Tuesday, June 10, 2008 10:51 AM
Inmagic Webpublisher 11, just released, breaks some Andornot Utility scripts that rely on the dbtw_params variable: Rewind, Next/Previous, and Change Form On Dropdown Value are affected. Possibly others.
A fix will be released as soon as possible, and I will update this post and provide download links to the script files at that time.
UPDATE Jun 13 2008: Fix released.