Hi,

I was just wondering about the testing tools (dx101 and dx201) that were
mentioned in this email.   We are very interested in testing our reader
against these.  I had a look around the cvs tree and couldn't find them.
I was just wondering if there was any more information about them
anywhere (what exactly they test, and how to use them).

Thanks,
Kyle Neumeier

On Tue, 2007-07-31 at 18:56 -0700, Gordon Waidhofer wrote:
> Howdy LTK folks,
> 
>  
> 
> We’ve internally been chewing on the repository organization for a
> couple or three days.
> 
>  
> 
> Below is a tree(1) output showing a proposed new organization.
> 
> There would be only one CVS module called “LTK”.
> 
>  
> 
> Some brief notes:
> 
>       * Should there be a Lib/ and Include/ directory for each tool
>         kit? We bounce around on this and decided to see what others
>         think.
>       * dx101 is a self test that verifies frame decode, frame encode,
>         and xml encode within an implementation. LTK/Tests/ contains
>         golden files.
>       * dx201 is a test that talks to an actual reader and is probably
>         overkill in the interests of coverage
>       * Examples/example1 implements the “LLRP Hello World” recently
>         posted (by link) by Rifidi
>       * John H. says he will work toward all three in Perl as he has
>         time (estimate 2-3 weeks)
>       * I believe all LTK implementations should implement the same
>         (dx101, dx201, example1) as demonstration of compatibility,
>         completeness, and as a primer.
>       * The Documentation/ preferred format is HTML because a browser
>         is handy on all platforms. Next choice is plain text. There
>         are no restrictions, though.
>       * LTK/LTKCPP/gencode.bat invokes MSXSL.EXE to generate code on
>         Windows. Gencode.bat must be run by hand. It contains as a
>         comment instructions for obtaining (for free) MSXSL.EXE.
>       * LTK/LTKCPP/VS_LTKCPP is for MS Visual Studio. It builds
>         ltkcpp.lib, and as console applications each dx101, dx201 and
>         (soon) example1.
>       * We don’t think it is necessary to have LTKC work under Visual
>         Studio or Windows.
>       * The Definitions/Acme.com and Definitions/SkyHigh.edu are just
>         for demonstrating the idea, there are no such files really.
> 
>  
> 
> None of this is cast in stone. Feedback is eagerly invited and
> appreciated.
> 
>  
> 
> As soon as we can settle the CVS repository reorganization I’ll
> check-in the LTKC and LTKCPP toolkits.
> 
>  
> 
> Regards,
> 
>             -gww
> 
>  
> 
>  
> 
>  
> 
> LTK
> 
> |-- Definitions/
> 
> |   |-- Acme.com/
> 
> |   |   |-- acme-1x0-def.xml
> 
> |   |   `-- acme-1x0.xsd
> 
> |   |-- Core/
> 
> |   |   |-- llrp-1x0-def.xml
> 
> |   |   `-- llrp-1x0.xsd
> 
> |   |-- SkyHigh.edu/
> 
> |   |   |-- skyhigh-1x0-def.xml
> 
> |   |   `-- skyhigh-1x0.xsd
> 
> |   `-- llrpdef.xsd
> 
> |-- LTKC/
> 
> |   |-- Documentation/
> 
> |   |-- Examples/
> 
> |   |   |-- Makefile
> 
> |   |   `-- example1.c
> 
> |   |-- INSTALL.TXT
> 
> |   |-- Makefile
> 
> |   |-- README.TXT
> 
> |   |-- Tests/
> 
> |   |   |-- Makefile
> 
> |   |   |-- dx101.c
> 
> |   |   `-- dx201.c
> 
> |   |-- ltkc.h
> 
> |   |-- ltkc_array.c
> 
> |   |-- ltkc_base.h
> 
> |   |-- ltkc_connection.c
> 
> |   |-- ltkc_connection.h
> 
> |   |-- ltkc_element.c
> 
> |   |-- ltkc_encdec.c
> 
> |   |-- ltkc_error.c
> 
> |   |-- ltkc_frame.h
> 
> |   |-- ltkc_framedecode.c
> 
> |   |-- ltkc_frameencode.c
> 
> |   |-- ltkc_frameextract.c
> 
> |   |-- ltkc_gen_c.xslt
> 
> |   |-- ltkc_gen_h.xslt
> 
> |   |-- ltkc_genout.c
> 
> |   |-- ltkc_hdrfd.c
> 
> |   |-- ltkc_platform.h
> 
> |   |-- ltkc_prxml.h
> 
> |   |-- ltkc_prxmlencode.c
> 
> |   `-- ltkc_typeregistry.c
> 
> |-- LTKCPP/
> 
> |   |-- Documentation/
> 
> |   |-- Examples/
> 
> |   |   |-- Makefile
> 
> |   |   `-- example1.cpp
> 
> |   |-- INSTALL.TXT
> 
> |   |-- Makefile
> 
> |   |-- README.TXT
> 
> |   |-- Tests/
> 
> |   |   |-- Makefile
> 
> |   |   |-- dx101.cpp
> 
> |   |   `-- dx201.cpp
> 
> |   |-- VS_LTKCPP/
> 
> |   |   |-- Library/
> 
> |   |   |   |-- Debug/
> 
> |   |   |   |-- Library.vcproj*
> 
> |   |   |   |-- ReadMe.txt*
> 
> |   |   |   `-- Release/
> 
> |   |   |-- VS_LTKCPP.ncb*
> 
> |   |   |-- VS_LTKCPP.sln*
> 
> |   |   |-- VS_LTKCPP.suo*
> 
> |   |   |-- dx101/
> 
> |   |   |   |-- Debug/
> 
> |   |   |   |-- ReadMe.txt*
> 
> |   |   |   |-- Release/
> 
> |   |   |   |-- dx101.vcproj*
> 
> |   |   |   |-- stdafx.cpp*
> 
> |   |   |   `-- stdafx.h*
> 
> |   |   `-- dx201/
> 
> |   |       |-- Debug/
> 
> |   |       |-- ReadMe.txt*
> 
> |   |       |-- Release/
> 
> |   |       |-- dx201.vcproj*
> 
> |   |       |-- stdafx.cpp*
> 
> |   |       `-- stdafx.h*
> 
> |   |-- gencode.bat
> 
> |   |-- ltkcpp.h
> 
> |   |-- ltkcpp_array.cpp
> 
> |   |-- ltkcpp_base.h
> 
> |   |-- ltkcpp_connection.cpp
> 
> |   |-- ltkcpp_connection.h
> 
> |   |-- ltkcpp_element.cpp
> 
> |   |-- ltkcpp_encdec.cpp
> 
> |   |-- ltkcpp_error.cpp
> 
> |   |-- ltkcpp_frame.h
> 
> |   |-- ltkcpp_framedecode.cpp
> 
> |   |-- ltkcpp_frameencode.cpp
> 
> |   |-- ltkcpp_frameextract.cpp
> 
> |   |-- ltkcpp_gen_cpp.xslt
> 
> |   |-- ltkcpp_gen_h.xslt
> 
> |   |-- ltkcpp_genout.cpp
> 
> |   |-- ltkcpp_hdrfd.cpp
> 
> |   |-- ltkcpp_platform.h
> 
> |   |-- ltkcpp_prxml.h
> 
> |   |-- ltkcpp_prxmlencode.cpp
> 
> |   `-- ltkcpp_typeregistry.cpp
> 
> |-- LTKPerl/
> 
> |   |-- ChangeLog
> 
> |   |-- Contrib.txt
> 
> |   |-- Documentation/
> 
> |   |   |-- Builder.html
> 
> |   |   |-- Helper.html
> 
> |   |   |-- Link.html
> 
> |   |   `-- Schema.html
> 
> |   |-- Examples/
> 
> |   |   |-- inventory_example.pl*
> 
> |   |   `-- simple_encode_decode.pl*
> 
> |   |-- INSTALL.TXT
> 
> |   |-- README.TXT
> 
> |   |-- RFID/
> 
> |   |   `-- LLRP/
> 
> |   |       |-- Builder.pm*
> 
> |   |       |-- Helper.pm
> 
> |   |       |-- Link.pm
> 
> |   |       |-- Schema.pm*
> 
> |   |       `-- llrpdef2llrp1.xslt
> 
> |   `-- gen_pod.pl*
> 
> `-- Tests/
> 
>     `-- dx101/
> 
>         |-- dx101_a_in.bin
> 
>         `-- dx101_a_out.txt
> 
>  
> 
> 29 directories, 95 files
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________ llrp-toolkit-devel mailing 
> list [email protected] 
> https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel

Reply via email to