On 02/11/2011 09:23 AM, Vito Impagliazzo wrote:
AFAIK AGLP inherits all rules of GPL, adding one more,
i.e. even in case you
don't redistribute the software, but make it available through a "web
service", you are still constrained by the GPL license, i.e. make the whole
source code available, of the AGPL component and any other linked piece of
code (thus incompatible with any proprietary software, even if just part of
the "web service")
Indeed, AGPL is even more viral than GPL. So we can't really use it in
the default distribution of XWiki, not even as a remote service. We can
provide a module and make it available as an optional extension, since
users can choose to use it privately, like we do for the PHP macro (GPL
requires code availability only when distributing the software, and
private use is not redistribution).
On Fri, Feb 11, 2011 at 9:00 AM, Marius Dumitru
Florea<
mariusdumitru.florea(a)xwiki.com> wrote:
> On 02/11/2011 02:25 AM, Jerome Velociter wrote:
>> Slightly off-topic : I've seen a presentation of WebODF (
>>
http://www.webodf.org/) at FOSDEM, which would allow to create an office
>> viewer macro that does not require an OOo server. Drawback is that it
> does
>> not support MS Office files, just ODF files.
>
> There are other drawbacks too:
>
> * AGPL licence. If I understood correctly AGPL licence extends GPL only
> with the ability to use the code for creating a service over a network.
> So AGPL licence is still viral if you want to distribute the code. This
> makes WebODF suited for creating web services rather than for being
> packaged in a web application.
>
> * it relies on JavaScript and thus on client machine. Some of the
> examples from their demo page make my Firefox hang for a while. For some
> I even get the popup to stop the script because it runs for too long.
>
> * it relies heavily on CSS to make the result look as much as possible
> like the original ODF document. Because of this the result looks
> different across different browsers. Combined with the fact that they
> sink the XML content of the ODF document in the HTML content it makes
> the page heavy.
>
> * doesn't work in IE at all and some examples don't work in Chrome.
>
> Besides this, one advantage of using the OpenOffice server (our current
> approach) is that the result is better integrated into the wiki page.
> Office viewer relies on office importer. When you view an office
> document using the office viewer macro you view in fact how the office
> document would look like if it were imported into the wiki page.
>
> Thanks,
> Marius
>
>>
>> Jerome
>>
>> On Thu, Feb 10, 2011 at 11:08 PM, Marius Dumitru Florea<
>> mariusdumitru.florea(a)xwiki.com> wrote:
>>
>>> On 02/10/2011 10:50 PM, Vito Impagliazzo wrote:
>>>> Thanks a lot!
>>>>
>>>
>>>> Does Office macro also import pdf files?
>>>
>>> No. Office macro uses jodconverter which in turn uses OpenOffice server
>>> to convert between different office file formats. OpenOffice currently
>>> can only export an office file to pdf.
>>>
>>> Hope this helps,
>>> Marius
>>>
>>>>
>>>> Vito
>>>> On Feb 10, 2011 9:26 PM, "Vincent
Massol"<vincent(a)massol.net> wrote:
>>>>> Hi Vito,
>>>>>
>>>>> It's now been fixed by Jerome.
>>>>>
>>>>> Thanks for reporting it
>>>>> -Vincent
>>>>>
>>>>> On Feb 4, 2011, at 12:00 PM, Vito Impagliazzo wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> I am trying to download the Google Document Viewer Macro from
the
>>>> extensions
>>>>>> wiki:
>>>>>>
>>>>
>>>
>
http://extensions.xwiki.org/xwiki/bin/view/Extension/Google+Document+Viewer…
>>>>>>
>>>>>> however the download link still refers to the old code wiki (as
in
> many
>>>>>> other extensions). Where can I find the installation file?
>>>>>>
>>>>>> thanks
--
Sergiu Dumitriu
http://purl.org/net/sergiu/