Re: patch for IT.php

One more small thing about this...I realize this feature is up in the air and is "outside" of the model (although I believe it is the one case where the model fails) and that you don't want to add it, but let's go from this angle. I need this one critical feature and I don't want to abandon the PEAR class and maintain it on my own over one stupid little feature like this. Could it at least be like a hidden or non-documented feature if up to this point you still don't find it necessary to add. I mean, the point of the PEAR classes after all is to use them and this class has not recieved an extremely wide base of usage (athough it should because its abilities are quite amazing and I am willing to put together some clear examples from my code) and I want to make use of it. Dan Bertrand Mansion (bmansion@mamasam.com) wrote: > le 21/05/02 2:56, Dan Allen à dallen@bsiweb.com a écrit : > > > You can throw it back in my face if you don't like it, but here is > > the patch to add a delimiter option in the blocks so that the > > template may take on this sort of functionality > > > > --------------------------------- > > > > <!-- BEGIN block_name {<br />} --> > > {foo} > > <!-- END block_name --> > > > > result | result | result > > > > --------------------------------- > > This is model business. > IMO, in an application using ITX, it is better to separate what you do with > your raw data and how you will display them. ITX is not Smarty and only > handles display, not application logic. > > In your suggestion, why would I want to have: > link1 | link2 | link3 > and not: > link1 | link2 | link3 | > or even something like: > > Link1 > Link2 > Link3 > > What you do with your data is up to you and should not be handled by IT. > This is in more conform to the Model-View-Controller paradigm and IMO is a > good habit. > > Bertrand Mansion > Mamasam -- It is not enough to succeed. Others must fail. -- Gore Vidal