Hi Rob, I've upadated my Cheetah template to backport your modifications. Generated libs are the same (except a carriage return). I tried to simplify the template too: it's the same as your pwm_ccpx.jal, except it's surrounded by a "main" function, called to activate/display the content. It should be easier to modify.
Cheers, Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org 2009/8/30 Sebastien Lelong <[email protected]> > >> > I've seen you released new PWM libs so updating cheetah template is >> becoming >> > urgent... How do we proceed ? Do I have to diff, for instance >> pwm_ccp1.jal, >> > before and after your changes ? Will I get all differences ? >> >> I'll attach the file from which I generated the pwm_ccpx.jal files. The >> only thing needed is to replace all occurences of string '$x' (without >> the quotes) by the sequence number (1..10). Shouldn't be too difficult >> to convert it back to a .tmpl file. > > > OK I'll have a look. > > >> >> > Ideally, pwm libs should tested from this template generation, just to >> make >> > sure we won't have any surprise later. >> >> Agreed (although it seems more complicated than my method!). >> >> > Did you try ? There's also a shell script for autogenerating everything you > need. That said, I'm not bind to Cheetah template, it's just that I know it > and use it, so it was quicker for me, as at the beginning jallib I wanted to > produce code asap. But it's like JSON file format, we may need a common way > for templating code in jallib, to avoid wasting time converting two formats. > I'm open to suggestions :) > > > Cheers, > Seb > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
