Orchard is missing a 'protocol' to insert an Orchard object inside a BodyPart

description

May be I missed it but I don't found a module to do this.
We should be able to:

invoke all extensions (html, url, display) to secure path to files and images for <a> and <img> (kind of razor parsing/translating tool)

insert any shape prepared for this bodypart, or the keyword used , this could solve many problems as floating menu. form-posting, dynamic content client-side, etc

To do this today, the only solution I found is writing a dedicated module to replace body part, and for each demand building a new module ????

As far as on some other issues some are speaking about replacing or upgrading the text-editor, this could be a door to allow insertion of dedicated shapes that could be analyzed and converted inside the body shape builder code ? I am interested to work on this.

@znowman yes excatly.
Not necessarly the great armada or razor, may be something more soft and fast,
May be a filter dedicated to this new flavor for body, a dedicated keyword esay to detect in the xml nodes of the body ( I see Bertrand doing this for url in vandely extensions)
Only problem I see is pluggin the filter to the shape using its name and parameters (parts?) sent ?