Well, would still be a step ahead having an 'import from html' option, let's say the user has many external sources (ex. employee's curricula CV_emp1, CV_emp2, ...) he wants to collapse into a PB note.
Instead of pasting a link (the curriculum would be available only opening with browser), the user selects the source file from PB note menu, then a snapshot of the content is taken. In later utilizations, the user could navigate through employees nodes visualizing their data on the fly. After selecting a node he is interested in, if he wants to get recent information, he could press an 'update' button on the related note, so PB shouln't be forced to update on the fly all the links at startup. The more, it could be useful (ex. for those who have to collect many info on the same subject together, as bloggers or news writers) to collapse many sources into the same note (ex. different variations on 'spaghetti al pesto' for a chef, or different chronicals on the 'hubble repair' for a news writer, etc.). Other ideas could be found, but the key point is that the user should not be charged with composing personally the .html files, like he had not to do before with external .rtf files or OLE objects, or pasting manually the html code from a source, which has no 'memory' of the source itself. Then, if someone likes, we could speak of mono or bi-directionality of information flux, that is how much PB should be considered a collector of information, and how much a modifier (always of external sources, obviously) bye
Is this your house?
I'm Wiston Wolf, I solve problems.