-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I am currently trying to get a working version of ARFilePreview
running under Plone 4.1. What is the current state of codebase?
There is a branches/2.2.2 (which should likely be branches/2.0
instead) that does not work with Plone 4 and ther
Hi,
ARFilePreview is an abandonware. The authors refactored this old style
product into atreal.richfile.preview. It is actively mainained and I use in
two production sites.
http://pypi.python.org/pypi/atreal.richfile.preview/0.2.0
It always requires AROfficeTransforms
Cheers
--
Gilles Lenfant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ahathanks...
Perhaps on could update the documentation on PyPI with a pointer
to the new add-on for Plone 4.
Andreas
Florent MICHON wrote:
> Hi Andreas,
>
> ARFilePreview is not maintained anymore.
>
> Take a look at http://pypi.python.org/pyp
Hi Andreas,
ARFilePreview is not maintained anymore.
Take a look at http://pypi.python.org/pypi/atreal.richfile.preview and
http://plone.org/products/atreal.richfile.preview which is a complete
rewriting of ARFilePreview and currently maintained. It is Plone 4.0
compliant.
AROfficeTransforms is
Hi Fellows,
I just noticed that there has been some discussion about merging
sauna.reload with plone.reload (or replacing plone.reload completely).
As a sauna.reload's maintainer, I think, it would be nice to have
sauna.reload functionality as a feature of plone.reload, but I can't see
it re
Hi Asko
For the reasons you give, I agree that replacing plone.reload with
sauna.reload would not be workable.
However I think it's unfortunate that the distinguishing part of the
name ("plone" vs "sauna") is meaningless. The only thing that you can
get out of it is that the "plone" one looks mor
On 24 October 2011 11:56, Jean Jordaan wrote:
> Hi Asko
>
> For the reasons you give, I agree that replacing plone.reload with
> sauna.reload would not be workable.
>
> However I think it's unfortunate that the distinguishing part of the
> name ("plone" vs "sauna") is meaningless. The only thing
>> plone.reload.addons
>> plone.reload.coredev
>
> -1 for nesting namespaces and replacing renaming plone.reload, which is in
> wide use.
> How about plone.autoreload or something like that?
I still don't grok what the issue with nested namespaces is. To avoid
nesting, one could do:
plone.reload_
Martin Aspeli wrote:
How about plone.autoreload or something like that?
Or
plone.autorestart
plone.deltarestart
because technically sauna.reload is more about restarting than reloading.
Btw, would renaming something to plone.* require moving copyrights to
Plone Foundation (and valid contrib
On 24 Oct 2011, at 13:00, Asko Soukka wrote:
> Martin Aspeli wrote:
>> How about plone.autoreload or something like that?
>
> Or
>
> plone.autorestart
+1
> plone.deltarestart
>
> because technically sauna.reload is more about restarting than reloading.
>
> Btw, would renaming something to
On 24 Oct 2011, at 12:37, Jean Jordaan wrote:
>>> plone.reload.addons
>>> plone.reload.coredev
>>
>> -1 for nesting namespaces and replacing renaming plone.reload, which is in
>> wide use.
>> How about plone.autoreload or something like that?
>
> I still don't grok what the issue with nested
11 matches
Mail list logo
