How can I display an entire page at a specific path/url in a block? I am using the HomeBox Module which outputs a page with a "Dashboard" like functionality. However I would like to be able to take this functionality from the page and turn it into a block, so that I could then add this functionality to any node/content type I would need.

What I have tried:

Nodes In Block, Node Blocks, Node As Block modules - these modules would do the trick if the page outputted by HomeBox was actually a proper node. In actual fact it cannot be edited as a node and so the additional options the above modules provide are not available in the page edit form.

Views module - when creating a View, I have tried filtering only by the url/path to show everything from the particular HomeBox page url. However this doesn't seem to be possible in Views. Since the page can't be tagged with taxonomy, isn't a content type, and (as far as I know) doesn't have a node id; by specifying the url and showing the page inside a View I could then make a block display and be done. But there doesn't seem to be general path/url filter in Views.

Does anyone have any suggestions as to what else I should try?
If you do something like this...

D6:

$foo=menu_execute_active_handler('path/to/the/homebox/page');


D7:

$foo=menu_execute_active_handler('path/to/the/homebox/page', FALSE);


...$foo should include either all of the html or a renderable array of the path/page content in question so in theory you could then stuff that in a block, either via a custom module or (ick) using the standard block interface and the (double ick) php input filter.

MORE THOUGHTS:

My basic thought above was to try to get to the menu handler for the page/path in question with as little custom code as possible.  But, if you look in the HomeBox module, all it is doing for each page/path is calling homebox_build() along with a page argument that is easily crafted up.  So, if you are comfortable with coding, you could write a custom module that uses that function within its block hooks to create the content.

Also, not sure about any css/js that would be needed but that could be hand crafted I suppose if necessary.