> > if its problem to address in the anonymous way you have written before, > > probably some warning dialog before saving could be one way how to > > 'address' it. > > I do not know. But again, however you address it, this is not a > problem with embedding.
technically you are right, that this problem was there before. but there is one big difference with emebdding. when you have used different directories before you woulnd't send such file to your coauthor, it will be impossible for him to install all the files properly. so you had to take care about placing files together with the lyx file and thus the filepath was not saved inside and the privacy problem was not there. with automatical embeding this problem appears. so philosophically 'it is the problem with embedding' although you are not responsible for that flaw. anyway its not important whether its problem with embedding or not. what is important is that this problem should be solved before embedding is oficially released. > > i'm not happy to say it, but it can happen again. there are always things > > which are not clear when only proposal is given. so basically no "Period." > > exists. > > The basic idea of using a zip format, and in-place bundle/unbundle > were announced from the very beginning. You do not really need to see > the code to know how it works. i remember three issues for example - the code was intrusive - ie there appeared bugs in code which has not much to do with embedding itself. secondly Richard claimed the code was hard to understand. thirdly the privacy concerns. all these things were not clear in the time of proposal, yet they are serious enough to consider rejection of the patch. pavel
