Thank you John
!well, at the beginning i thought that wire was going to resolve ids sniffing some process.env ...
but that would obviously not have been a flexible solution..
My opinion about the 3 options you suggest:
2nd one is most flexible..
1st is most straightforward,
3rd one is the last resort.
as i think that the beauty of wire is the chance to build a complete app architecture in a declarative way!
that's why i begun (and will try always to) declaring specs in JSON!
you know,
i've been attempting to start a veeery simple, personal, "wire-ish" module because i really wished to separate architecture from implementation,
I've been so happy when i found cujo/wire..
and so surprised too, because i found many features and how tos that i was trying to achieve!
i can't wait to get into all other cujo modules too:
cola : seems powerful but it is lacking for docs, or did i miss them?
jiff : awesome :)
meld : great in combination with wire!!
msgs : didn't read enough to grab the potentiality
anyway ..
i'll take the chance here to put a couple of Qs:
- i didn't try yet as theese days i'm moving(home): my sample is flattened in the same dir, but i believe that after the first main wire call,
all the subsequent module ids are resolved against the preceeding(the caller's) module path in a require flavour, true?
- curl-amd is supposed to be used especially for remote specs?
Thank you!
Alec