Hi Don,
I guess it would not be that hard for ETP 2. I will bring this up with Luke. Currently all ETP cr_items uses the a cr_folder as a parent_id. So there is nothing stoping us using the parent_id to another cr_item. Then build upon the interface.
Right now the current direction of ETP 2 is use a more simple UI or specific for a content type rather than the extensible ETP 1 UI. The plus of this is that we will have a better interface. This is also a proof why mmbase does not have a good interface (but good enough) since the editor is a jack of all trades content editor.
