Build 1.0.3 of nhaystack fixes a bug that a couple of people found: now you can name a slot "haystack" even if its not a BHDict (a.k.a collection of zinc tags).
There are a couple of other minor changes, most notably that the nav tree that was once called "comp:/" is now called "slot:/".
P CWed 3 Jul 2013
Great work. Thanks
New to Haystack, just started playing with the module, any reason why the site and equip ids are encoded or need to be encoded?
Mike JarmyWed 3 Jul 2013
The IDs for AX Components in nhaystack are base-64 encoded versions of the slotPath, with a prefix of "@c.". The spec for Refs requires that we use a restricted set of URI-friendly characters, so they can be used in a URL without mangling or escaping any characters.
So I chose to just base-64 encode the slotPath as a way to uniquely identifiy a Component within an AX station. I actually considered several different possibilities, but in the end this seemed the most straightforward.
Jason BriggsWed 3 Jul 2013
What we did was in the tool we base-64 de-code it so you can see the slotPath. You should ever have to read the actual ID. That's just for computers to read.
P CWed 3 Jul 2013
Thanks for the quick reply.
The reason I am asking is I saw the following example in the spec:
Let's look a simple example for an entity describing a site:
Mike Jarmy Tue 4 Jun 2013
Build 1.0.3 of nhaystack fixes a bug that a couple of people found: now you can name a slot "haystack" even if its not a BHDict (a.k.a collection of zinc tags).
There are a couple of other minor changes, most notably that the nav tree that was once called "comp:/" is now called "slot:/".
P C Wed 3 Jul 2013
Great work. Thanks
New to Haystack, just started playing with the module, any reason why the site and equip ids are encoded or need to be encoded?
Mike Jarmy Wed 3 Jul 2013
The IDs for AX Components in nhaystack are base-64 encoded versions of the slotPath, with a prefix of "@c.". The spec for Refs requires that we use a restricted set of URI-friendly characters, so they can be used in a URL without mangling or escaping any characters.
So I chose to just base-64 encode the slotPath as a way to uniquely identifiy a Component within an AX station. I actually considered several different possibilities, but in the end this seemed the most straightforward.
Jason Briggs Wed 3 Jul 2013
What we did was in the tool we base-64 de-code it so you can see the slotPath. You should ever have to read the actual ID. That's just for computers to read.
P C Wed 3 Jul 2013
Thanks for the quick reply.
The reason I am asking is I saw the following example in the spec:
Let's look a simple example for an entity describing a site:
id: @whitehouse dis: "White House" site area: 55,000 ft² geoAddr: "1600 Pennsylvania Avenue NW, Washington, DC" tz: "New_York" weatherRef: @weather.washington
P C Wed 3 Jul 2013
Jason, 10-4. Thanks