> my concern is - in case user will not use bundling feature at all, on > what places can bubble up bugs caused by embeding code. only InsetBibtex > usage? what kind of bugs?
The bugs are related to latex output, which only show up in InsetBibtex right now. As I have said, the bugs themselves are easy to fix but we disagreed on how to fix them. Note that for a new feature of this scale, I certainly expect a lot of bugs to be found and fixed. Using a few bugs to accuse the current implementation is pointless. > in case (when no bundling used by user) the impact and imported problems is > rather small i would say lets have the Bo's petty feature survive, we have no > other working code allowing embedding. possibly we can say its experimental > feauture, > users have been warned. It is not only about 'my petty feature'. The disagreements are *fundamental*. In the unbundled mode, I do not expect many problems caused by the embedding code. > in the oposite case it is no more only your pet feature and other people will > be affected or forced to fix imported and hard-to-understand bugs. then i do > not agree with JMarc suggestion 'Have mercy and and do whatsoever monster you > want.' If you read the EmbeddedFiles.h, I gave a long description of what this feature is and how it is implemented. The amount of comments I gave in the code is above average. The core parts of code appear in EmbeddedFiles.h/cpp, and about four relevant functions in InsetGraphics, InsetExternal, InsetBibtex and InsetInclude. > i would like to have clarified from people actually studied the code which > case > is more to be expected. Only Richard had studied the code, and he disliked it. Cheers, Bo
