Update VS build configuration.

[hintjens]

I really like how you're using GSL to generate the Nuget packaging... :)

On Wed, Apr 9, 2014 at 11:42 AM, evoskuil notifications@github.com wrote:

---

You can merge this Pull Request by running

git pull https://github.com/evoskuil/czmqpp master

Or view, comment on, or merge it at:

https://github.com/zeromq/czmqpp/pull/4 Commit Summary

• Update VS build configuration.

File Changes

• M builds/msvc/vs2013/czmq.import.propshttps://github.com/zeromq/czmqpp/pull/4/files#diff-0(11)
• M builds/msvc/vs2013/czmq.import.xmlhttps://github.com/zeromq/czmqpp/pull/4/files#diff-1(3)
• M builds/msvc/vs2013/czmqpp/czmqpp.propshttps://github.com/zeromq/czmqpp/pull/4/files#diff-2(2)
• M builds/msvc/vs2013/libsodium.import.propshttps://github.com/zeromq/czmqpp/pull/4/files#diff-3(13)
• M builds/msvc/vs2013/libsodium.import.xmlhttps://github.com/zeromq/czmqpp/pull/4/files#diff-4(3)
• M builds/msvc/vs2013/libzmq.import.propshttps://github.com/zeromq/czmqpp/pull/4/files#diff-5(19)
• M builds/msvc/vs2013/libzmq.import.xmlhttps://github.com/zeromq/czmqpp/pull/4/files#diff-6(20)
• M packaging/nuget/package.gslhttps://github.com/zeromq/czmqpp/pull/4/files#diff-7(2)

Patch Links:

• https://github.com/zeromq/czmqpp/pull/4.patch
• https://github.com/zeromq/czmqpp/pull/4.diff

Reply to this email directly or view it on GitHubhttps://github.com/zeromq/czmqpp/pull/4 .

[evoskuil]

Thanks, it's really handy. I've worked a lot with T4 but this is simpler and more portable.

I'd like to use it in more contexts. You may have noticed that there's a lot of duplication in the project files and imports across platform versions. I have this partially automated locally and would like to fully automate it, but there's a trade-off...

The main downside is that the source document has to be escaped, and in the case of a structured encoding like XML, the structure is invalidated by template markup, which prevents use of validating editing tools. These make editing a bit tedious and fragile. Is there any way to mitigate this using the tool?

[hintjens]

I've no solution for creating valid XML mixed with templating commands. Something like XSTL does that but it's very nasty to work with.

For escaping, what do you mean exactly? Slashes, or < and >?

On Wed, Apr 9, 2014 at 11:11 PM, evoskuil notifications@github.com wrote:

Thanks, it's really handy. I've worked a lot with T4 but this is simpler and more portable.

I'd like to use it in more contexts. You may have noticed that there's a lot of duplication in the project files and imports across platform versions. I have this partially automated locally and would like to fully automate it, but there's a trade-off...

The main downside is that the source document has to be escaped, and in the case of a structured encoding like XML, the structure is invalidated by template markup, which prevents use of validating editing tools. These make editing a bit tedious and fragile. Is there any way to mitigate this using the tool?

Reply to this email directly or view it on GitHubhttps://github.com/zeromq/czmqpp/pull/4#issuecomment-40016990 .

[evoskuil]

I'm assuming you meant XSLT. I've done a lot there and it's an absolute nightmare to work in.

The technique used by knockout.js is slick. In the context of HTML it's soooo much better than other HTML template systems precisely because it allows the developer the benefit of remaining in the HTML development environment while working with template bindings, as opposed to staring at a block or proprietary markup. The downside I suppose is that it's language-specific. But any markup language with attribution should be able to accommodate additional markup (for the purpose of templating) in a similar manner.

By escaping (in my current usage) I mean that every \ turns into \\ and every $(...) turns into $\(...).

[hintjens]

Sorry, XSLT of course, yes.

To fix $() and \ we would have to change gsl to allow these to be set to other sequences on a per-script basis.

[evoskuil]

That would help a lot. The remaining problem (in my usage) would be that control instructions must reside outside of the markup, which invalidates the XML document.

[hintjens]

OK, I've made this change to gsl, it's pending in a pull request. Seems to work fine except you can't set it in a script, to affect the script (obvious, but annoying).

On Wed, Apr 9, 2014 at 11:39 PM, evoskuil notifications@github.com wrote:

That would help a lot. The remaining problem (in my usage) would be that control instructions must reside outside of the markup, which invalidates XML document.

Reply to this email directly or view it on GitHubhttps://github.com/zeromq/czmqpp/pull/4#issuecomment-40019850 .

[evoskuil]

Is it possible to set the switches in a parent GSL script (to affect an imported script), or does it have to be set on the GSL command line?

[hintjens]

I don't see any examples of GSL code setting a value in switches, but it should work. However it's probably better practice to set a value in the parent XML and use that in imported scripts.

On Tue, Apr 15, 2014 at 11:24 AM, evoskuil notifications@github.com wrote:

Is it possible to set the switches in a parent GSL script (to affect an imported script), or does it have to be set on the GSL command line?

— Reply to this email directly or view it on GitHubhttps://github.com/zeromq/czmqpp/pull/4#issuecomment-40461574 .