My rule of choice is as follows If preexecute can be replaced by regular blockmarks, blockmarks If preexecute can be replaced by regular rendertags, rendertags If preexecute can be replaced by JavaScript, JavaScript If preexecute can be replaced by custom rendertag, custom rendertag
The problem with preexecute, besides being slow and hard to troubleshoot, hard to quickly teach someone else about the preexecute in the project. I hope best practice for custom rendertag would emerge one day to address the existing usage problems of preexecute. For now, it is just a slightly better replacement for end user, well, not for developer (being C#, and having an IDE and debugger). On Monday, August 26, 2013 7:04:16 AM UTC-4, Boris Crismancich wrote: > > Hi, > > another thread already stated quite like this but went in a different > direction. > > So, what are your examples and ideas for custom render tags? > Does it simply replace PreExecute or does it go further? > > My first custom Rendertag is TimeStampWithMilliseconds. > For a performance analysis, I wanted to tell the exact execution start and > end time of PageBuilder, Navi Manager, PreExecute and RdExecute of a single > page. > I used a Database Element and a View to get the Timestamp for the > PageBuilder, a custom Rendertag for Navi Manager and PHP for the rest. > Afterwards, I could tell by millisecond, which SQL statements in my trace > were related to pagebuilder and so on. > > What do you do with custom rendertags? > > Cheers, > Boris > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
