Jørn Wildt

Pagesetter 1.0.0 had some small bugs (like the small rectangle for html fields in Mozilla).
Now we have version 2, with support for pnRender, and of course without the built-in direct smarty support.

There is any chance to have a 1.0.1 version with only the bug fixes?

No, I'm not going to spend time on that, and I don't think there's any specific place in the CVS history where you can find it. Sorry.

But it is rellatively easy to remove the use of pnRender. Look for $smarty in 1.0.0 - see what the code looks like in 2.0.0 around those places, and fix it back. Hopefully.

There is no use in this -- pnRender does nothing more (well a bit, but not substantial) than adding Smarty support. So why do you not just install pnRender?

J?rg

I see pnRender can be installed without Xanthia. So far so good.

I'm curious why a module needs to rely on a particular theme engine? I thought one of the design goals of CMSs in general was to separate templating and the content. A module that requires a particular theme engine seems to be a step in the wrong direction.

I'm guessing there is a valid reason for this. Care to share what that reason is? What functions would not be available with another theme engine, such as AutoTheme?

I am a MD-Pro user, and I love the AutoTheme engine that comes with that. I do have another app installed on my site that uses Smarty (aMemberPro). By installing pnRender to make use of your module, it looks like I will be installing a second copy of Smarty to the system. Is this safe?


- Alan

Now, pnRender is *not* a theme engine - it's a templating engine. It is required by the theme engine Xantia. pnRender is nothing but an extension of Smarty.

Pagesetter might as well use Smarty (which the first version did). But since PN .8 is expected to by completly "pnRendered" then the move to pnRender was quite natural. The use of pnRender should, to my knowledge, not influence the use og AutoTheme.

Just to confirm: I had that doubt when I first open the topic.

But after some investigation I discovered that pnRender could be considered a way to call Smarty from different "processes" at the "same time", to incorporate Smarty in the api's.

So I tried to install pnRender without the Xanthia engine in my testbox, and it worked fine with the new versions of Pagesetter AND with Autotheme.

For your information, it could help to know that I have 3 sites where I stayed at .714 after the big bangs of 18 months ago (envo and xaraya).
Now for a new project I converted myself to .726 with pnRender, Autotheme and (of course) pagesetter.

Any chance that there will be a future release that is more aimed for MD-pro installation or is this mainly a Postnuke project?

Kindly,
Mikael

There you are. Xanthia needs pnRender (that's wha we ship them together for .726), but pnRender works perfectly without Xanthia.


J?rg

Right, but I heard that pnRender SLOWS down the performance, hence my question about any future release aimed directly for the MD-pro community ;)

pnRender will be a core component in .8 -- If md pro won't include it, so I wouldn't use md Pro ;)

Now, unless J?rg went around and put some MS Windows code into the pnRender class, it will work exactly as good as Smarty. As far as I can see it adds two or three extra file existence checks (not complete loads) on top of Smarty, but nothing more.

So what do you compare pnRender to? Let's compare it to a non-templating (and non-caching) module. Such a module *must* make a couple of database look-ups on *every* page view. A pnRender/Smarty may use caching and only do database lookups *once and for all*. Pagesetter is in the last category. So, no, pnRender is *not* slower - it can be faster than a non-pnRender module!

Yep - choose whatever fits your needs best. I have tons of stuff to do even without having to support multiple Content Management Systems.

??? :o

The main difference (rep. enhancement) of pnRender over pure Smarty is that all paths are derived automatically (especially the template's paths).

It was a joke J?rg, sorry if I insulted your proffesional feelings (or whatever you say in english).