From: Tim P. <ti...@pa...> - 2004-03-01 20:41:21
|
On Monday 01 March 2004 4:30 pm, Keats wrote: > From: "Tim Pizey" <ti...@pa...> > > > In particular the removal of the > > org.webmacro.Template(FastWriter, WebContext) method > > has me at a loss. > > Sorry you're having such trouble. Believe it or not, the FastWriter > changes were an attempt to simplify things. It just seemed like an ext= ra > level of complexity that could be complete hidden from the users.=20 > Generally you should be able to replace reference to FastWriter with > references to the underlying OutputStream. I think the problem is about ordering. Magically Melati was able to write to the underlying output stream at the= =20 right moment.=20 I cannot understand how that used to work.=20 > IMHO, the problem appears to be that Metali is too tightly coupled to t= he > internals of WebMacro. =20 I agree, and said so at the time, but understanding and writing this code= =20 (and the Velocity and JTemplater code) was TimJ 'at the top of his game'=20 it was the best and most difficult coding he had done.=20 Undoing it appears to be beyond me. > I'd suggest keeping it simple and just use trivial > adapters around the WebMacro API. > > I'm happy to try and help any way I can. I have a feeling that I am making a mountain out of a molehill,=20 and after this many years I get a bit upset with myself that I can't=20 'just do it' . I don't know what your setup is, but Melati is meant to be=20 easy to download, compile and run. Currently if you download from CVS,=20 cd build ant go http://localhost:8080/ You will find that the example works but that=20 the inner templets are rendered to the output stream before the=20 main template is rendered. > > Is there any interest in Freezing the 1.1 API and maintaining that? > > This is a good idea, but probably not realistic for us. We can at leas= t > keep the source available and post any usefull patches that come along. > > > (To be honest the last version that worked for me was 0.98) > > Any particular bugs in 1.1 that we can help with? I'm not aware of any > serious outstanding bugs. No 'bugs', but the white space eating behaviour was changed,=20 correctly I can see for non HTML rendering applications,=20 but my templates no longer produce the pretty HTML they used to. I am sure that there are improvements and features that have been=20 added since that time, but as far as I know I have no need of any of them= =2E > > The 2.0 API appears to have lost vital elements of the API and gained > > a raft of stuff that shouldn't be in a template engine, > > moving more and more towards a framework. > > Please be specific, so we can decide if your critiques have merit. > > Actually one of the objectives of the new release was to provide a mini= mal > configuration for folks who don't want "a raft of stuff". Most of the > changes have been to streamline and simplify the code. Yeah, I know, sorry, just been wasting precious time for nearly a week=20 now without doing paying work.=20 > > Good luck. Thanks Tim > > Keats > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick > _______________________________________________ > Webmacro-user mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webmacro-user |