Eric
Posts: 5561
Joined: 10/10/2003 From: Seattle, WA Status: offline
|
The major feature here is a significant upgrade to the Dymo label printing functionality: HIGHLIGHTS - Print labels from FireFox (new) or IE on Windows.
- No longer required to download and run BARCODE.EXE. Templates are fetched from the web.
- Better printing performance—no more recalibration between each label.
- Support for new dual barcode labels with a tear-off tab. Really cool!
Please see the rewritten FAQ which details everything: http://www.cellartracker.com/ow.asp?BarcodeProcedures DETAILS - Rewrote all client-script in JavaScript instead of VBScript, ensuring that IE support still works.
- Added a new user-agent flag for FireFox for Windows. Show the Dymo buttons for this and IE.
- Label printing script uses FireFox-friendly XPCOM object.
- Re-worked validation code to detect IE/ActiveX/template or FireFox/XPCOM/template.
- Reworked BINLABEL.ASP in the same vein as PRINTLABELS.ASP.
- Added a new options dialog so that users can choose their template drive and default label template. Also expose the bin and price display settings in this dialog.
- Reworked code to respect these new options.
- Fallback to URL based loading of all template files if local templates are not installed
- Use the new Start/EndPrintJob methods for better performance.
- Create a template file for the new LazarLabelâ„¢.
- Directly host unzipped templates on the server for default case.
- Updated client script to set the second barcode when the LazarLabel is the default.
- Repackaged BARCODE.EXE with this new template file and update on server.
- Worked up a new FAQ page on the Wiki to discuss UPS versus CellarTracker barcoding. Breaking out installing instructions including a link to the XPCom install.
In addition to the label upgrades, I have made a number of other recent changes: - Some UI bug fixes around wishlist editing.
- Upgraded the Wiki to MSXML6 for better security, reliability and performance.
- Troubleshooted and mitigated a denial of service issue where malformed WikiText could bring the webserver to its knees.
- Shifted to WebGarden hosting in IIS and enabled a number of recycling options. (At first before uncovering the aforementioned denial of service issue, I assumed there was a memory/resource leak. That was not the case in the end, but I kept these IIS options running.)
_____________________________
Cheers! -Eric LeVine
|