Dave and Stuart, would you imagine your micro basket as an additional minicart module, as a replacement or as an integration with an option in the settings ?

Is it easy to integrate into the present project ?

Speaking for myself I've made my Micro Basket / Micro Cart a really simple Module. I imagine it as an addition to the existing modules rather than a replacement for anything. Personally I think it fits nicely above the Catalogue 'menu' module.

I think it's trivial to integrate into the present project - there's 4 files (ascx, ascx.cs & ascx.designer.cs, and the htm file for the template), and an additional section for the dnn file (there's a text file in my .zip source download which has the extra folder element for the MicroCart module.

Here's a link to more explanation and a download of the source. Use it as you see fit - happy for it to be integrated or mashed up into the main code.

http://www.amphlett.net/Dave/Blog/tabid/55/EntryID/40/Default.aspx

I see it in the code base - never looked in the SkinObject section before. Definitely think it's a good idea to be a module for most users won't be in a position to start messing with the skins, but the skin object is a real good idea too (although I think I'd want to be a bit more agressive with optimisation and caching on something that would be part of the skin!). Probably worth having both I'd say. No reason why they can't share the same control though is there.