Hi Paul!
I just read:
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/SiteThemes
I think that you mentionned it in a previous mail on z3lab and now I
think that I understand what you meant, my impression is that cpsskins
can be used to generate the "themes" that you are mentionn
Stephan Richter wrote:
>On Friday 02 September 2005 04:20, Jean-Marc Orliaguet wrote:
>
>
>>this only solution I found was to write:
>>
>>tal:define="getDisplay nocall:context/displayable/getDisplay;
>> display python: getDisplay(param);&q
Stephan Richter wrote:
>On Sunday 11 September 2005 11:32, Jean-Marc Orliaguet wrote:
>
>
>>it there any technical reason why:
>>
>> tal:define="displayable nocall:context/displayable"
>>
>>could not return the adapted object based on the
Jim Fulton wrote:
> Jean-Marc Orliaguet wrote:
>
>> Stephan Richter wrote:
>>
>>
>>> On Sunday 11 September 2005 11:32, Jean-Marc Orliaguet wrote:
>>>
>>>
>>>
>>>> it there any technical reason why:
>>>>
>
Hi!
is the order of the list of interfaces implemented by an object subject
to internal changes?
I have identified the need for such a pattern:
iface = object.interface()
with:
class someObject(object):
implements(IMainInterface, ISecondaryInterface, ...)
def interface():
Philipp von Weitershausen wrote:
>Jean-Marc Orliaguet wrote:
>
>
>>is the order of the list of interfaces implemented by an object subject
>>to internal changes?
>>
>>I have identified the need for such a pattern:
>>
>>iface = object.interf
Janko Hauser wrote:
>
> Am 13.09.2005 um 12:43 schrieb Jean-Marc Orliaguet:
>
>> But where do you put the 'directlyProvides' statement? in the class :
>
>
> Can't this be put in the interface definition module for
> IContentType? You mark other
Philipp von Weitershausen wrote:
>Florent Guillaume wrote:
>
>
>>Philipp von Weitershausen wrote:
>>
>>
>>
>>> >>> from zope.app.content.interfaces import IContentType
>>> >>> from zope.app.file.interfaces import IFile
>>> >>> from zope.interface import directlyProvides
>>> >>> directlyP
Gary Poster wrote:
>
> On Sep 16, 2005, at 5:20 PM, Garrett Smith wrote:
>
>> That's right. But the view can solve these problems easily without a
>> lot of other stuff like yet-another-ZCML directive and automagical
>> transformation of the HTML head element.
>
> ...
>
>>
>> This is a trivial c
FYI, there is a typo in:
Index: zope/app/i18n/browser/synchronize.py
===
--- zope/app/i18n/browser/synchronize.py(revision 38532)
+++ zope/app/i18n/browser/synchronize.py(working copy)
@@ -117,7 +117,7 @@
if c
Hi! I'm having trouble getting strings to be translated using
tal:content="variable" or tal:replace="variable"
Everybody
yield (in French):
Tous
but:
gives:
Everybody
which means that the content is not translated.
as a workaround:
works, since it yields:
Tous
accordin
Fred Drake wrote:
>On 9/19/05, Jean-Marc Orliaguet <[EMAIL PROTECTED]> wrote:
>
>
>>Hi! I'm having trouble getting strings to be translated using
>>tal:content="variable" or tal:replace="variable"
>>
>>
>...
&g
Roger Ineichen wrote:
>Hi together
>
>I added a proposal where is important for the CPSSkin work and the
>zope.app.viewlet implementation.
>Can you take a look at it and tell me what do you think about.
>
>I hope it will be possible to implement a generic lookup concept
>in page templates where we
Roger Ineichen wrote:
>Hi Jean Marc
>...
>
>
>
>
Hi Roger,
>I propose,
>
>"Regions and their lookup are a concept on the ZPT level,
> implementations like CPSSkin or viewlets use this ZPT API"
>
>Let's say a region defines a area in a page template. This area
>will lookup 'html fragment' and
Hi!
does anyone have the same trouble running i18nextract.py on the trunk
since about 4-5 days?
/JM
traceback log:
python2.4 ~/Zope3/utilities/i18nextract.py -d cpsskins -p ./ -o ./locales/
base path: '/home/jmo/Zope3/'
search path: '/home/jmo/Zope3/src/cpsskins'
domain: 'cpsskins'
output file
Hi!
I've encountered a problem when trying to render views (there is no
problem with rendering pages), but for instance with the '+' view that
is defined in app/container/browser/configure.zcml
when called with:
markup = view()
['view' being the 'view' variable gotten f
Jim Fulton wrote:
> Jean-Marc Orliaguet wrote:
>
>> ...
>>
>> With the '+' view described above, there is a default page attribute to
>> use for displaying the view ('index.html') and but no page attribute
>> explicitly assigned.
>>
Hi!
the '+' view now works fine in cpsskins :-), the only problem is that it
also reveals a user interface issue nicely "hidden" in the original
Rotterdam skin :-) namely that the menu actions are still visible when
the url ends with .../@@+ and the action item urls are not normalized. A
second c
Jim Fulton wrote:
> Jean-Marc Orliaguet wrote:
>
>> Jim Fulton wrote:
>>
>>
>>> Jean-Marc Orliaguet wrote:
>>>
>>>
>>>> ...
>>>>
>>>> With the '+' view described above, there is a default
Tonico Strasser wrote:
> Michael Jansen schrieb:
>
>> Hi
>>
>> Is there anywhere an explanation how the rotterdam skin works. Some
>> insight's to how an when which parts are selected?
>>
>> How to use and expand it?
>>
>> I think i'm making progress in understanding how the parts click
>> togethe
Tonico Strasser wrote:
> Jean-Marc Orliaguet schrieb:
>
> Yes, and the ZMI-"design" is also broken IMHO. Actions below tabs is
> not intuitive, the navtree does not feel good etc. I find the classic
> ZMI much better in this respect.
>
> I guess I'm conf
Jim Fulton wrote:
> Jean-Marc Orliaguet wrote:
>
>>
>> Hi!
>> the problem is not in the skin itself, but in the model used to create
>> "skins". Filesystem-based skins that depend on ZPT macros are doomed by
>> definition, unless they are designed to
Jim Fulton wrote:
> Paul Winkler wrote:
>
>> Hi Jim, just de-lurking for a moment:
>>
>> On 10/24/05, Jim Fulton <[EMAIL PROTECTED]> wrote:
>> > I think the biggest problem with the ZPT macro approach to look
>> and feel
>>
>>> concerns are not separated. CPSSkins deals with this in it's own way
Dmitry Vasiliev wrote:
> Jim Fulton wrote:
>
>>
>> IMO, if a template an element with both i18n:translate and tal:content
>> and the value inserted is not a message id, the template's domain will
>> be used. This seems like a bad idea. It can hide failures to provide
>> message ids because every
Jim Fulton wrote:
> Jean-Marc Orliaguet wrote:
> ...
>
>> there are cases where you need to evaluate an expression to get the
>> msgid for instance in:
>>
>> there is a workaround, but it is very inelegant:
>> http://svn.nuxeo.org/trac/pub/changeset/27505
>detail, the main point being just that I wanted to have
>something simple that is nevertheless flexible enough to
>accommodate to various needs.
>
>So I came up with the following stuff (mainly combining concepts
>by Jean-Marc Orliaguet and implementation ideas from Archet
Reinoud van Leeuwen wrote:
>On Fri, Nov 11, 2005 at 03:50:25PM +0100, Helmut Merz wrote:
>
>
>>A relation is an object providing the IRelation interface. This
>>has got two attributes ('first', 'second' - dyadic relation) or
>>
>>
>
>I've done this kind of thing in relational databases. Pr
Reinoud van Leeuwen wrote:
>On Fri, Nov 11, 2005 at 04:44:47PM +0100, Jean-Marc Orliaguet wrote:
>
>
>>Reinoud van Leeuwen wrote:
>>
>>
>>
>>>On Fri, Nov 11, 2005 at 03:50:25PM +0100, Helmut Merz wrote:
>>>
>>>
>>>
Helmut Merz wrote:
>Am Freitag, 11. November 2005 16:11 schrieb Jean-Marc Orliaguet:
>
>
>
>>Hi Helmut!
>>
>>
>
>Hi Jean-Marc,
>
>thanks for your remarks,
>
>just before going into more detail: My primary concern was the
>API - it woul
Helmut Merz wrote:
>Am Freitag, 11. November 2005 18:00 schrieb Jean-Marc Orliaguet:
>
>
>
>>I was thinking more about the policy of assigning unique ids
>>to objects in a relation. It's the application that really
>>should decide about that policy.
>>
Helmut Merz wrote:
>Am Samstag, 12. November 2005 18:00 schrieb Jean-Marc Orliaguet:
>
>
>
>>My
>>impression is that you are thinking of a reference engine
>>rather than a relation engine
>>
>>
>
>Maybe I just don't see the differ
Helmut Merz wrote:
>
>OK - then I'm not talking about references, though we still mean
>different things when talking about 'relation':
>
>Mine goes like this: A relation object R providing
>ITriadicRelation and connecting A, B and C involves three
>references:
>
>R with A
>R with B
>R with C
Helmut Merz wrote:
>Anyway, what we are talking about are not "references".
>
>
The approach is quite different: references start from the objects
themselves that they connect to other objects using one-way relations (a
pointer, an arrow). The application has to know how to interpret the
refere
Hi!
are there any guidelines / best practises for setting the contents of
__init__.py, interfaces.py, and the packages that they import or that
they expose? there are too many alternatives and too many ways of ending
up doing circular imports and I'd like to have a consistent pattern for
red
Martijn Faassen wrote:
Hi there,
Hi Martijn,
Jean-Marc Orliaguet wrote:
some packages have an interfaces.py file others have a "interfaces"
folder, others have the interface definitions in the implementation
code itself ...
The pattern changed over time during Zope 3 devel
OK, so to summarize this thread:
- __init__.py files are empty
unless for the convenient import of other modules located in the same
package or in a subpackage?
- public interfaces are stored in interfaces.py
- private interfaces are written along with the implementation code
- what abo
Jim Fulton wrote:
Jean-Marc Orliaguet wrote:
OK, so to summarize this thread:
- __init__.py files are empty
unless for the convenient import of other modules located in the
same package or in a subpackage?
Actually, primarily for convenient import by external packages.
yes indeed
Jim Fulton wrote:
yes indeed, but no "cross" imports between packages that are siblings.
Huh? Why? I'm not at all sure I know what you mean.
the question is what relation between the importer and the imported are
OK: if I add such imports in __init__.py, I should only import from
pack
There is another place where there seems to be two different patterns too:
sometimes we have:
import zope.schema
name = zope.schema.TextLine(...)
and sometimes:
from zope.schema import TextLine
name = TextLine(...)
any reason to use one or the other (speed, verbosity, avoiding circul
Hi!
what is the rationale between the unique integer ids utility and the
usage policy?
more specifically: why are newly added objects registered in *all*
IntIds utilities? It does not make sense if the utility is registered
locally. If they are local they should not be concerned with object
j.kartnaller wrote:
This has already been added to the bug collector :
http://www.zope.org/Collectors/Zope3-dev/466
Jürgen
Jean-Marc Orliaguet wrote:
Hi!
what is the rationale between the unique integer ids utility and the
usage policy?
more specifically: why are newly added objects
the page composition is done
entirely TTW. So the need for a template to create an manage entire
sites disappears.
see for instance:
"Unified model for managing application resources"
http://www.z3lab.org/sections/blogs/jean-marc-orliaguet/2005_11_10_unified-model-for
The separat
Martijn Faassen wrote:
...
Outside the Zope community Zope 3 doesn't have such a great image
indeed. It's either ignored, or it's actively rejected. There is a lot
of competition with other frameworks. Zope 3 is currently not doing
particularly well in this competition, something we need to f
Martijn Faassen wrote:
my impression is that if you want TTW editing you'll have to do it on
an application level using what's available in the framework
(utilities, ZPT, ...) Zope3 allows you to do this already and in a
much cleaner way than with zope2..
That's great! How to make this wo
Martijn Faassen wrote:
Jean-Marc Orliaguet wrote:
[snip]
It is a bit like this: the zope2 community wants the zope3 technology
and zope3 wants the zope2 community.
I like this analysis. :)
I think the question about the technology should be treated as such
on a technical level, by
Martijn Faassen wrote:
Jean-Marc Orliaguet wrote:
Martijn Faassen wrote:
my impression is that if you want TTW editing you'll have to do it
on an application level using what's available in the framework
(utilities, ZPT, ...) Zope3 allows you to do this already and in a
much c
Martijn Faassen wrote:
Jean-Marc Orliaguet wrote:
[snip]
I think you're mixing the notions of "community" and of "community of
interests".
I don't think that the goal is to merge communities, the goal is to
make good software and not have different entities fi
Laurence Rowe wrote:
Jean-Marc,
Just trying to understand your scheme here, but taking Martin's
example of a current zpt macro, how would I replace the macro with a
view and retain the ability to customise it TTW?
From my limited understanding of your cps skins package it seems that
it is
erik wrote:
Hi,
HI!
I'm just a tiny little bit confused here, what is a view and what is a resource
- in Zope2 and in Zope3 ? ;-)
there's a notion of resource already in Zope3 that encompasses: images,
files and templates
in cpsskins (zope3) the notion also encompasses more cpsski
Martin Aspeli wrote:
A lot of people go with Plone initially based strongly on how easy it is to
customise and re-use elements of the UI. I really don't want to take that
incentive away from them. Yet, as I understand, if global_contentmenu.pt was
implemented as a View, they couldn't customise
Martin Aspeli wrote:
On 24 Nov 2005, at 18:53, Jean-Marc Orliaguet wrote:
Martin Aspeli wrote:
A lot of people go with Plone initially based strongly on how easy
it is to
customise and re-use elements of the UI. I really don't want to
take that
incentive away from them. Yet,
Martin Aspeli wrote:
I think there are two cases: The first is the "tinkerer", who
wants to customise primarily the template as easily as possible,
preferably TTW.
OK, I buy this. You want to be able to modify resources, try
different options ... Then you might want to export them th
Dominik Huber wrote:
2. A subtype of IObjectModifiedEvent is cluttering because of
redundant modification events. The modification is caused by the
containment.
Regularly the dispatching related to the containment hierarchy tries
to emulate an information flow from *parent -> child*, because
Florent Guillaume wrote:
Well I don't want to appear to defend Apple Mail too much here, but
splitting a URL after a / can be seen as a natural location.
And in any case this wouldn't be a problem if Mozilla coders weren't
lazy :-) (decoding rfc3676 (which is nearly 2 years old now) is
tr
Florent Guillaume wrote:
Redirecting to a relative url is illegal in the HTTP spec. You must
always use a fully qualified url.
Florent
+redirect_url = REQUEST['HTTP_REFERER'] or '.'
+RESPONSE.redirect(redirect_url)
OK, but can you raise that one zope3-dev? It is used all over th
Jean-Marc Orliaguet wrote:
Florent Guillaume wrote:
Redirecting to a relative url is illegal in the HTTP spec. You must
always use a fully qualified url.
Florent
+redirect_url = REQUEST['HTTP_REFERER'] or '.'
+RESPONSE.redirect(redirect_url)
OK, but ca
Hi!
I'm about to write an xml importer for importing simple data
(properties, dictionaries). Exporting is easy, importing is trickier
because a parser is required.
Is there any prefered framework for doing such things in zope3 (zope2)?
CMFSetup uses sax, GenericSetup uses sax too. ZCML relie
Tarek Ziadé wrote:
Florent Guillaume wrote:
Tarek Ziadé wrote:
Hi all,
Some UI works have been done lately around and in Zope 3. I am thinking
about the work that has been done at Neckar sprint (Zope3.org website,
Viewlets, etc..), and on projects like CPSSkins for Z3 at ECM.
I a
Andreas Jung wrote:
--On 6. Dezember 2005 16:46:02 +0100 Jean-Marc Orliaguet
<[EMAIL PROTECTED]> wrote:
Hi!
I'm about to write an xml importer for importing simple data
(properties,
dictionaries). Exporting is easy, importing is trickier because a parser
is required.
I
Martijn Faassen wrote:
Andreas Jung wrote:
I'm about to write an xml importer for importing simple data
(properties,
dictionaries). Exporting is easy, importing is trickier because a
parser
is required.
Is there any prefered framework for doing such things in zope3 (zope2)?
Sax or DOM..
Stephan Richter wrote:
On Saturday 31 December 2005 18:58, Hector Miuler Malpica Gallegos wrote:
Hi friends, i have a problem actually use cpsskins of svn.z3lab.org
and the zope3 of svn (svn.zope.org), whenever I want to create a
subject shows the following error:
You might have more
based on the current perspective. Panels can load pages from
other panels and perspectives can be nested.
the animation:
http://www.z3lab.org/sections/front-page/design-features/sub-perspectives-panels
the explanation:
http://www.z3lab.org/sections/blogs/jean-marc-orliaguet/2006_01_05_panels
Jim Fulton wrote:
See:
http://dev.zope.org/Zope3/ZConfigAndOtherFormatsForZCML
Comments and volunteers welcome.
Jim
What is the fundamental difference between ZConfig and ZCML apart from
the esthetic appearance that everyone seems to be so concerned with? I
see that all the attribute
Hi!
Here is an implementation of "compound storages" in CPSSkins (this
concerns the CPSSkins AJAX toolkit only so it also applies to Zope3 in
general, or to any other server that can handle JSON requests and
responses).
First of all, this is a great step towards simplifying the development
o
Hi!
I've being working on integrating Balazs Ree's CTAL interpreter recently
(added tests, fixes, etc.). CTAL is the equivalent of TAL but for
javascript. For the record MochiKit also has something equivalent called
"MochiTAL" that supports "tal:content" and "tal:repeat".
Anyway, CTAL imple
Balazs Ree wrote:
Sat, 11 Feb 2006 21:03:21 +0100 keltezéssel Jean-Marc Orliaguet azt
írta:
I almost felt that something was missing, because I'm so used to inserting
"tal:define" in page templates. But now I realize that this is a mistake.
There was a discussion recently on
kit BLAKE wrote:
In 'normal' tal we often refactor our defines to improve efficiency.
When something is called more than once in a template, we define it at
the beginning, and then use it multiple times. This improves
performance dramatically of course.
kit
--
kit BLAKE
Infrae · infrae.com · +
Andreas Jung wrote:
--On 12. Februar 2006 19:18:51 +0100 Max M <[EMAIL PROTECTED]> wrote:
Title
I could write this:
Title
That's really syntactical sugar. The purpose of the tal: names is clearly
to tell the parser to do _something_ with the value of an attribute. Now
should a parser
Tonico Strasser wrote:
Hi Jean-Marc!
I agree that a view should not be able to modify the data model. But I
think tal:define is a must have :)
For example: I need tal:define to define names for generic macros:
The 'li_repeat' macro expects the name 'list'.
Tonico
That's exactly wh
Tonico Strasser wrote:
(Again with the right quote, sorry.)
Jean-Marc Orliaguet wrote:
That's exactly what I'm saying: if templates did not try to create
their own data layer, the 'li_repeat' macro could get the data from
the model (instead it has to rely on cross-te
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tonico Strasser wrote:
I'm interested in your opinion about parameters for macros.
Do you think this is explicit enough?:
Or do you think explicit parameters would make things clearer?:
I don't favor "expli
Martijn Faassen wrote:
Jean-Marc Orliaguet wrote:
I've being working on integrating Balazs Ree's CTAL interpreter
recently (added tests, fixes, etc.). CTAL is the equivalent of TAL
but for javascript.
I just googled around for this, and couldn't find it, but I'm
intr
101 - 172 of 172 matches
Mail list logo
