Re: [dev-context] Mac installation package
Am 22.08.2009 um 13:47 schrieb Oliver Buerschaper: What's more important, the exit status of the context command is 0 (via echo $?) indicating that there was no problem at all! This might turn out problematic as soon as documents are processed in a batch run ... (like e.g. a regression test suite ;-) *You* want to write a test suite for ConTeXt? Perhaps one could even integrate this requirement check into the module loading code of the kernel. For example, one might enforce that each valid module has to declare a field like minkernelversion in its header ... just thinking out loud. The problem with such systems is they lead always to incompatibilities with older ConTeXt installations (think about TeXLive) and we had one at the end of last year when Hans changed the multilingual interface to allow a persian interface. Wolfgang ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] Mac installation package
On Sun, 23 Aug 2009, Wolfgang Schuster wrote: Am 22.08.2009 um 13:47 schrieb Oliver Buerschaper: What's more important, the exit status of the context command is 0 (via echo $?) indicating that there was no problem at all! This might turn out problematic as soon as documents are processed in a batch run ... (like e.g. a regression test suite ;-) *You* want to write a test suite for ConTeXt? The test suite is there. There is even a script in the test suit that compares the outputs of two versions at pixel level. All we need is people to submit tests and then someone to monitor the test suite. See http://wiki.contextgarden.net/Test Perhaps one could even integrate this requirement check into the module loading code of the kernel. For example, one might enforce that each valid module has to declare a field like minkernelversion in its header ... just thinking out loud. The problem with such systems is they lead always to incompatibilities with ConTeXt installations (think about TeXLive) and we had one at the end of last year when Hans changed the multilingual interface to allow a persian interface. Loading of lua files has this feature. For modules, asking for a minimum kernel version is no guarantee that the module will work with future versions of ConTeXT :-) Aditya ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] Mac installation package
What's more important, the exit status of the context command is 0 (via echo $?) indicating that there was no problem at all! This might turn out problematic as soon as documents are processed in a batch run ... (like e.g. a regression test suite ;-) *You* want to write a test suite for ConTeXt? Well, not exactly ... this might be too ambitious an endeavour for one person alone ;-) I'm trying though to store a bunch of test cases locally which I sporadically collect from the main mailing test whenever a bug report shows up. If only to have something I can test my installation package against ... For the moment I'm mainly interested in whether these test cases compile at all hence my remark about the exit status ... (After all, if that can't be automated any further verification steps will be pretty much useless I guess.) Perhaps one could even integrate this requirement check into the module loading code of the kernel. For example, one might enforce that each valid module has to declare a field like minkernelversion in its header ... just thinking out loud. The problem with such systems is they lead always to incompatibilities with older ConTeXt installations (think about TeXLive) and we had one at the end of last year when Hans changed the multilingual interface to allow a persian interface. I agree that my suggestion would sacrifice backwards compatibility. At the same time I'm not sure how much change to the MkIV kernel is desirable given that MkII is considered frozen. I'm really in no position to have an educated opinion on whether there should be as few changes as possible or rather the occasional clear cut. It's just that if you guys think that some clear cuts are due for MkIV anyway then there will probably be never a better time than now to make module loading more bullet-proof. As I was saying, I'm just thinking out loud ;-) Oliver ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] Mac installation package
Am 23.08.2009 um 17:22 schrieb Aditya Mahajan: *You* want to write a test suite for ConTeXt? The test suite is there. There is even a script in the test suit that compares the outputs of two versions at pixel level. All we need is people to submit tests and then someone to monitor the test suite. See http://wiki.contextgarden.net/Test Is this still alive and used? Wolfgang ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] Mac installation package
Am 23.08.2009 um 17:52 schrieb Oliver Buerschaper: I agree that my suggestion would sacrifice backwards compatibility. At the same time I'm not sure how much change to the MkIV kernel is desirable given that MkII is considered frozen. I'm really in no position to have an educated opinion on whether there should be as few changes as possible or rather the occasional clear cut. It's just that if you guys think that some clear cuts are due for MkIV anyway then there will probably be never a better time than now to make module loading more bullet-proof. As I was saying, I'm just thinking out loud ;-) MkIV is ConTeXt’s feature without an doubt but it's not so easy as you think. I have myself two modules which work only with MkIV (simplefonts and games) but bigger ones like simpleslides or letter are just complexer styles and you can't expect from a user to upgrade to MkIV just to make a presentation or to write a short letter. I thought about integrating the version check into \setupmodule because the command is only used in modules and available in MkII and MkIV but Thomas and Aditya use it in the simpleslides module to pass parameters to the module and this a few times at different places and not only at the start of the file. Wolfgang ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] Mac installation package
On Sun, 23 Aug 2009, Wolfgang Schuster wrote: Am 23.08.2009 um 17:52 schrieb Oliver Buerschaper: I agree that my suggestion would sacrifice backwards compatibility. At the same time I'm not sure how much change to the MkIV kernel is desirable given that MkII is considered frozen. I'm really in no position to have an educated opinion on whether there should be as few changes as possible or rather the occasional clear cut. It's just that if you guys think that some clear cuts are due for MkIV anyway then there will probably be never a better time than now to make module loading more bullet-proof. As I was saying, I'm just thinking out loud ;-) MkIV is ConTeXt’s feature without an doubt but it's not so easy as you think. I have myself two modules which work only with MkIV (simplefonts and games) but bigger ones like simpleslides or letter are just complexer styles and you can't expect from a user to upgrade to MkIV just to make a presentation or to write a short letter. I thought about integrating the version check into \setupmodule because the command is only used in modules and available in MkII and MkIV but Thomas and Aditya use it in the simpleslides module to pass parameters to the module and this a few times at different places and not only at the start of the file. If you have a suggestion that will make things cleaner, we (Thomas and I) can easily change the internals of simple slides to accomodate that. Aditya___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
