SUGGESTION: Make a two-level TDD file structure
"Colbert Philippe" <[email protected]> Tue, 18 Jul 2006 14:26:36 -0400
| Newsgroups | gmane.comp.text.fmpp |
|---|---|
| Message-ID | <002b01c6aa97$b4741d50$6601a8c0@ml300> |
This is a multi-part message in MIME format. --===============1650296315== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01C6AA76.2CF9A960" This is a multi-part message in MIME format. ------=_NextPart_000_0028_01C6AA76.2CF9A960 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SUGGESTION: Make a two-level TDD file structure for more abstraction = power. The TDD feature is one of the most powerful features of FMPP. TDD = hierarchical structure lends itself to complex applications. That's = great! However, I find myself wanting a little bit more. I would like to see = a two-level TDD file setup. That is I want to see two (2) different TDD = files. The values of the first TDD file beeing used in the second TDD = file (property interpolation) and the second TDD being the final TDD = file to be used with FMPP. This would greatly increase the power of FMPP. It's a natural = extensition. For instance, my application simply create XML = configuration files using FMPP. I have wrapped each reusable XML = section into an FMPP macro. So values are replaced directly into the = macro. My TDD file separates parameters by macros. I would need a = second TDD file to have "application specific concept abstraction". = That is grouping values by application concepts. This second two-level = concept can be reused in any application and would make things easier = and cleaner. Let me go even one step further by generalizing this concept of levels = of TDD file. Let me suggests that FMPP supports any number of = cascading TDD files. Instead of limiting ourselves to two-leve, let's = make it n-level TDD file cascading. TDD file1 --> TDD file 2 --> ... TDD file N ---> Used by FMPP The TDD file N is used by FMPP. The other files are forgotten. This = would allow any number of levels of abstraction. Colbert Philippe ------=_NextPart_000_0028_01C6AA76.2CF9A960 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.5450.4" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>SUGGESTION: Make a two-level TDD file = structure for=20 more abstraction power.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>The TDD feature is one of the most = powerful=20 features of FMPP. TDD hierarchical structure lends itself to = complex=20 applications. That's great!</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>However, I find myself wanting a little = bit=20 more. I would like to see a two-level TDD file setup. = That is=20 I want to see two (2) different TDD files. The values of the = first=20 TDD file beeing used in the second TDD file (property interpolation) and = the=20 second TDD being the final TDD file to be used with FMPP.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>This would greatly increase the power = of=20 FMPP. It's a natural extensition. For instance, my = application=20 simply create XML configuration files using FMPP. I have = wrapped=20 each reusable XML section into an FMPP macro. So values are = replaced=20 directly into the macro. My TDD file separates parameters by = macros. I would need a second TDD file to have "application = specific=20 concept abstraction". That is grouping values by application = concepts. This second two-level concept can be reused in any = application and would make things easier and cleaner.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Let me go even one step further by = generalizing=20 this concept of levels of TDD file. Let me suggests that = FMPP=20 supports any number of cascading TDD files. Instead of limiting = ourselves=20 to two-leve, let's make it n-level TDD file cascading.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>TDD file1 --> TDD file 2 --> ... = TDD file N=20 ---> Used by FMPP</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>The TDD file N is used by = FMPP. The=20 other files are forgotten. This would allow any number of = levels of=20 abstraction.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Colbert = Philippe</FONT></DIV></BODY></HTML> ------=_NextPart_000_0028_01C6AA76.2CF9A960-- --===============1650296315== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV --===============1650296315== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ fmpp-open mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fmpp-open --===============1650296315==--