[snippet] ChildDocumentMapper

Same here, I’d like to know what bit of code has to be added to have it work... Having the abilitie to parse TVs is great !

To answer your question I guess your idea of having a customapi.inc.php file is probably how it should be done.

Quote from: wendy at Nov 30, 2005, 10:41 PM

Could you explain it further on how to install this on a MODx? For example, include the necessary code that need to be added to the MODx API, and where it’s suppose to be added.

I also wonder about v1.2, what does it mean by excluding tv?

Thanks...

This is something we’ve talked about a bit but as far as I know we havn’t really come up with a good solution. Personally, I like the idea of being able to extend the core class and override certain methods if needed but I’d really love to see API extenders built into the plugin system.

I do know that work is being done on separating out the API into a few classes instead of the one monster document parser class. So a method to extend those classes may be handled at the same time.

Could somebody illustrate in ABC-manner possible usage of this "wonderful" snippet? May be some tutorial would be extremly useful  ::) I feel I’m missing something great 

It will be great as well, when there is a customization vars to make the snippet behave just like the one on newslisting, with sort ability, maximum listing ability, pagination and etc.

Well, that’s just my wish list...

Nice snippet guys...

Great to see such enthousiasm from ones proto-snippet. Regretfully I don’t have much time to play with MODx at the moment, but this version looks great.

Thanks for your first post as well Olaf.

I just want to bump up this post, maybe theo had come up with something.


Regards,
Wendy Novianto

I read the comments in the snippet by Theo, and it says it has sorting and max. functionality, so most of the requests on your wishlist have already been granted.

I know Mark is working on the NewsListing snippet to work with TV’s. Any progress there Mark?

My major concern is the API function. There’s some serious limitations in there. I’m working on a new function that doesn’t have these limitations.

At the same time I’ll move the functionality from the API to the snippet code so that it’ll be more easy to implement.

I’m still working on the implimentation but I have already figured out how I’m going to do it.

How are you going to do it?

I just started rewriting the function using ’getDocumentChildren’ and ’getDocumentChildrenTVarOutput’.