Previously Alexander Limi wrote:
> Does anyone have any idea what approach people like Google (Gmail etc) use
> for their implementation? It certainly seems like the most sensible
> implementation out there wrt. to end-user usability - and I'm pretty sure
> it scales too.
Judging from how I'
Alec Mitchell wrote:
Great analysis. I'm looking forward to my beer.
Wow, someone made it. :)
For me the big difference between these approaches is that one
requires changing many of the templates in Plone so that the rendered
results includes a bunch of fancy inline js that does all sorts
Just a heads up to let you know that I won't be able to look into the
review bundles I'm responsible for until Friday evening or the weekend.
Where did we put the list of bundles and people responsible anyway?
--
Helge Tesdal
Plone Solutions
___
Fra
Previously Martin Aspeli wrote:
> Alec Mitchell wrote:
>
> >Great analysis. I'm looking forward to my beer.
>
> Wow, someone made it. :)
At least two people actually :)
> >For me the big difference between these approaches is that one
> >requires changing many of the templates in Plone so that
Previously Helge Tesdal wrote:
> Just a heads up to let you know that I won't be able to look into the
> review bundles I'm responsible for until Friday evening or the weekend.
>
> Where did we put the list of bundles and people responsible anyway?
Email from Martin from August 30. Your bits we
Wichert Akkerman schrieb:
Previously Martin Aspeli wrote:
Alec Mitchell wrote:
Great analysis. I'm looking forward to my beer.
Wow, someone made it. :)
At least two people actually :)
me too, me too, but don't worry Martin, you don't need
to buy me a beer in Seattl
Hi,
Also (although I'm not sure how relevant that is for us) the KSS
approach might be more portable to other rendering systems. It sounds
like KSS will work fine with something like meld3, but Bling will have
a much harder time supporting that due to the lack of TAL-attributes
there.
The Blin
Hey guys,
So, prepare yourselves. :) I'm going to try to break down the Bling and
KSS conundrum in a few different sections below. I think it's important
that we think through these issues, and that we get some debate going
fairly quickly. This is holding up other work, as you know.
First of al
I'd say that if you have the time to look at this Friday, that's still
fine (there are still many outstanding bundles, unfortunately). I'm
sure Alec will be able to pitch in with some insights as well, as he's
familiar with CMFEditions and I know he's taken a quick look at
iterate and the locking
On Wed, 2006-09-13 at 00:38 -0300, Sidnei da Silva wrote:
> On Tue, Sep 12, 2006 at 08:19:21PM -0700, Alexander Limi wrote:
> | On Tue, 12 Sep 2006 13:15:08 -0700, wichert
> | wrote:
> |
> | >+Using sessions means that ZEO clusters will not work out of the box: the
> | >+session storage is not
Wichert Akkerman schrieb:
Previously Alec Mitchell wrote:
It's not possible to start Plone if PIL is not installed currently
(due to the member image fix). PIL is included in all the installers
AFAIK, and is a package in every distro I've known. So installing PIL
is generally as easy as instal
Martin Aspeli schrieb:
[..]
- An just in passing: is there really no sane way to fix
'installTypes' from Archetypes.Extensions.utils?
This will break **a lot** of 3rd-party products!
What exactly is the problem here? We cannot have installTypes() not
work, it'll break *everything*
Previously Raphael Ritz wrote:
> 2. Switch to using GS for AT at least internally now!
>
> Anyone up for 2?
Do we have a list of what is missing for that?
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make
Thanks for the summary, Raphael,
1. try by any means to support the "old" behavior (maybe
the fti registering could be done by AT's process_types
instead of CMF's ContentInit (I might actually try that
- time permitting)
2. Switch to using GS for AT at least internally now!
Anyone up for 2?
Martin Aspeli schrieb:
Thanks for the summary, Raphael,
1. try by any means to support the "old" behavior (maybe
the fti registering could be done by AT's process_types
instead of CMF's ContentInit (I might actually try that
- time permitting)
2. Switch to using GS for AT at least internally n
Hi Raphael,
> Switching all content types to use GS is fairly nasty. If they would
> all break anyway for various other reasons, fine, but then we're
> saying that 95% (or so) of third party products available today will
> not work with Plone 3.0. That's fairly depressing.
>
noticed I said _in
On 9/13/06, Martin Aspeli <[EMAIL PROTECTED]> wrote:
Thanks for the summary, Raphael,
> 1. try by any means to support the "old" behavior (maybe
> the fti registering could be done by AT's process_types
> instead of CMF's ContentInit (I might actually try that
> - time permitting)
>
> 2. Switch
Hi,
> As I said, I'm still wary of using GS as the main install mechanism,
> even if the quickinstaller can now find them thanks to Hanno. The
> uninstall question is still unresolved as far as I can see, in cases
> where you need custom cleanup code, and the
> re-run-all-import-steps-every-time
On 9/13/06, Martin Aspeli <[EMAIL PROTECTED]> wrote:
Hi,
> > As I said, I'm still wary of using GS as the main install mechanism,
> > even if the quickinstaller can now find them thanks to Hanno. The
> > uninstall question is still unresolved as far as I can see, in cases
> > where you need cust
On 9/13/06, Raphael Ritz <[EMAIL PROTECTED]> wrote:
Wichert Akkerman schrieb:
> Previously Alec Mitchell wrote:
>> It's not possible to start Plone if PIL is not installed currently
>> (due to the member image fix). PIL is included in all the installers
>> AFAIK, and is a package in every distro
Hi Alec,
> I don't think Hanno's solution has an uninstall script (yet). As I
> understood it, it can deal with the case where QI auto-uninstalls
> things like FTIs and workflows, but not where you need to write an
> uninstall() method of your own.
Perhaps not, but it's not as if this is a diff
Alec Mitchell wrote:
> On 9/13/06, Raphael Ritz
> <[EMAIL PROTECTED]> wrote:
>>
>> that's what I meant by saying earlier that PIL isn't necessarily
>> trivial to install. But anyway, I consider my original question
>> answered: it wasn't introduced on purpose in the first place but
>> now that a se
i think i need to clear up a misconception that...
On Sep 13, 2006, at 11:40 AM, Martin Aspeli wrote:
Basically, GS makes the re-install button a bit meaningless. If you
re-install a traditionally installed product, it calls
uninstall(reinstall=True); install(reinstall=True). If you re-install
a
On 9/13/06, Martin Aspeli <[EMAIL PROTECTED]> wrote:
Indeed. My feeling is that GS has some evolution to do before it's
truly a solid replacement for what we currently do (which grantely
isn't so solid) - maybe we're just replacing one set of design
problems with another; not because GS is badly
Hi Rob,
On 9/13/06, Rob Miller <[EMAIL PROTECTED]> wrote:
i think i need to clear up a misconception that...
On Sep 13, 2006, at 11:40 AM, Martin Aspeli wrote:
> Basically, GS makes the re-install button a bit meaningless. If you
> re-install a traditionally installed product, it calls
> uninst
Previously Martin Aspeli wrote:
> Hi Rob,
>
> On 9/13/06, Rob Miller <[EMAIL PROTECTED]> wrote:
> >i think i need to clear up a misconception that...
> >
> >On Sep 13, 2006, at 11:40 AM, Martin Aspeli wrote:
> >> Basically, GS makes the re-install button a bit meaningless. If you
> >> re-install a
> I assume this applies to base and extension profiles equally, then?
> So, it won't re-run the base CMFPlone profiles 'types.xml' if we
> activate Poi as an extension profile, nor will it re-run
> RichDocument's types.xml even if RichDocument was the previously
> installed/activated profile?
Cor
On Sep 13, 2006, at 12:41 PM, Martin Aspeli wrote:
Hi Rob,
On 9/13/06, Rob Miller <[EMAIL PROTECTED]> wrote:
i think i need to clear up a misconception that...
On Sep 13, 2006, at 11:40 AM, Martin Aspeli wrote:
> Basically, GS makes the re-install button a bit meaningless. If you
> re-install
Introduction
This PLIP covers two different issues:
- implement support for replaceable comment implementations using adapters
and interfaces
- add a new comment implementation which adds the moderate comments and
filter their html
Both are implemented in the easycommenting pro
Hi.
Martin Aspeli wrote:
>> > I assume this applies to base and extension profiles equally, then?
>> > So, it won't re-run the base CMFPlone profiles 'types.xml' if we
>> > activate Poi as an extension profile, nor will it re-run
>> > RichDocument's types.xml even if RichDocument was the previousl
Hanno Schlichting wrote:
Hi.
Martin Aspeli wrote:
I assume this applies to base and extension profiles equally, then?
So, it won't re-run the base CMFPlone profiles 'types.xml' if we
activate Poi as an extension profile, nor will it re-run
RichDocument's types.xml even if RichDocument was the p
31 matches
Mail list logo
