Hi Anto,
Have a look at the way ooo-build's bin/ooinstall does it
(http://cvs.gnome.org/viewcvs/ooo-build/bin/ooinstall?view=markup)
--
Michael Leibowitz
Software Engineer, Channel Platform Solutions Group
Intel Corporation
michael.leibowitz at intel.com
+1 503 264 7621
-Original
Nathan,
I am also looking into this.
My feeling is that it should be in the standard office installation, not
an extension.
Reason: If I attach a license to my document, I want that everybody is
aware of that when opening the doc, not just people who have the extension.
License must be
My feeling is that it should be in the standard office installation, not
an extension.
Well that would obviously be preferred, we were just trying to go for
the shortest time to implement/deploy (path of least resistance, if you
will). Is there a formalized mechanism for suggesting features
I took a quick look into the MS solution:
They simply place some text and links into the document, that's all.
This, of course, can be done as a component, and people w/o that
component will also see the license.
Such a component shouldn't be to hard to implement - any volunteers? ;)
Malte.
Actually they also embed information in the document, albeit not in the
greatest way. If you go to File - Creative Commons a second time (in
the same document), you'll notice that it warns you that you have
previously selected a license and asks if you'd like to overwrite it.
If you go to File -
Yes, they also embed, but the point is that the display of the license
is normal text/graphic in the document content, so people don't need the
component to be aware of that...
Malte.
Nathan R. Yergler wrote, On 07/07/06 16:16:
Actually they also embed information in the document, albeit not in
Ah, yes, very true.
Malte Timmermann wrote:
Yes, they also embed, but the point is that the display of the license
is normal text/graphic in the document content, so people don't need the
component to be aware of that...
Malte.
Nathan R. Yergler wrote, On 07/07/06 16:16:
Actually they
