how to for making a commercial library for runrev (barcode analysis)
janschenkel at yahoo.com
Wed Jul 2 09:22:33 EDT 2008
--- "runrev at animabit.de" <runrev at animabit.de> wrote:
> Hello colleagues,
> I have made a program in runrev which gets the jpg
> data of 5 scanservers with scanned labels and
> analyses the 2 to 4 barcodes 39. After a testing
> phase with permanent improvement it now works 8
> hours a day connecting to 3-5 scanservers stable.
> The project was part of quality assurance in an
> industrial environment.
> In another project (an older one) a runrev prog
> looks permanently to a directory where scanned
> images are stored by a scanner, and moves and
> analyses and comments on these images.
> The barcode analysis is completely programmed in
> transcript (500-700 msec per scan with 4 to 30
> captures of subareas of the image - black/white
> conversions with different filters and barcode
> analysis). The quality of the jpgs is 150 dpi
> (normally 300 dpi is the starting point of doing
> barcode scans ...) where one small barcode line (one
> modul) is about one pixel - hard task, but there are
> millions of those jpgs a month and storage over
> years should not explode ...
> A test for 128 barcode (possible only with higher
> resolution starting about 200 dpi) had been
> successful, but was not finally needed for this
> project and must be improved for final application.
> Now I think about making a commercial barcode
> analysis library for runrev.
> Does there exist any standards how to make
> commercial libraries in runrev?
> How to spread a password protected library stack in
> the community?
> Mit freundlichen Grüßen
> Franz Böhmisch
As a provider of Revolution add-ons, I'd advise you
- contact Heather Nagey <heather at runrev.com> for more
information about the RevSelect program
- join the RevInterop group
<http://groups.yahoo.com/group/revInterop/> to find
out more about packaging and metadata
Generally, I ship my libraries as a self-contained
stack that people can 'start using' and then
initialize with their license key before they can
actually use the commands and functions.
For instance, the PDF library has the API help
built-in as a substack, as well as a separate substack
with demo scripts. When you open the library stack, it
has the copyright information and buttons to take you
to the demo and documentation substacks.
By the way, congratulations with your project: I can't
help but thinking of how one could use this with
Revolution to create a cross-platform alternative to
the excellent Mac-only Delicious Library.
Anyway, I hope this helped,
Quartam Reports & PDF Library for Revolution
"As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld)
More information about the use-livecode