Warren Turkal wrote:
On Friday 22 September 2006 17:44, Philipp von Weitershausen wrote:
Nope.
And to answer some of your follow-up questions:
* No, this probably isn't going to be implemented (it's very much
non-trivial)
* Yes, you have to restart the server, though we recommend writing unit
Hello everyone,
Does anyone know the easiest way to let people (principals of a site)
develop their own pages with no knowledge about zop3 structure? AFAIK
The users need to make their own pages with HTML (more generally ZPT)
and upload them as a ZPT page.
I dont want my whole website skin t
Hi,
I am trying to be a good programmer and create pure Zope packages instead of
Plone products when possible.
How do dotted package names (like plone.portlets or dotted.name) work? In
\zopeinstance\lib\python, is the package actually in
\zopeinstance\lib\python\dotted.name, or is it in
\zopeinst
George Lee wrote:
I am trying to be a good programmer and create pure Zope packages instead of
Plone products when possible.
That's great! Note that you will either need Zope 2.10 or Zope 2.9 +
Five 1.4 for this.
How do dotted package names (like plone.portlets or dotted.name) work? In
\zop
> > What is the purpose of using the dotted name?
>
> Short answer: package namespaces.
>
> Long answer: Say you're creating a widget library. You could call your
> package simply "widget". But then if I create a widget library and
> called it "widget", too, we'd have a conflict and couldn't us
What is the best practice for where to put interface definitions? Inside an
interfaces.py, a browser/interfaces.py?
In Zope2 often I had used an "interfaces" (with an s) directory. Should a
directory be called "interface" instead, as it is in zope.app?
What is the logic of the choice of using int
George Lee wrote:
What is the purpose of using the dotted name?
Short answer: package namespaces.
Long answer: Say you're creating a widget library. You could call your
package simply "widget". But then if I create a widget library and
called it "widget", too, we'd have a conflict and couldn'
George Lee wrote:
What is the best practice for where to put interface definitions? Inside an
interfaces.py, a browser/interfaces.py?
We prefer to put public interfaces into package.interfaces. Other
modules can also define interfaces, but they wouldn't be considered to
be part of a public AP
> That entirely depends on how independent you want to keep philikon.a
> from philikon.b. But that question also arises when having just a and b.
Is it possible/typical/advised to have a base set of functionality in philikon,
and then be developing separate packages philikon.a and philikon.b down
George Lee wrote:
That entirely depends on how independent you want to keep philikon.a
from philikon.b. But that question also arises when having just a and b.
Is it possible/typical/advised to have a base set of functionality in philikon,
and then be developing separate packages philikon.a and
Hi,
Your problem is
in /home/hassan/HOMEPAGE2/modules/ISI/skin/template_tablelayout.pt and
UnauthenticatedPrincipal does not have attribute 'title'.
Check Boston skin template which first tests for authenticated user
before calling request/principal/title.
Regards,
Darryl
On Sun, 2006-09-24 at
Olha pq não estava rolando os nossos pontos!
/me precisamos corrigir o agx para gerar os nomes de pacotes com
pontos. Hoje ele está substituindo para ponto.
abraços
On 9/23/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
George Lee wrote:
> I am trying to be a good programmer and crea
I am trying to write a test for a view, and making sure that an object I've
created is associated with the correct view. But either of these lines fails
with a ComponentLookupError "Couldn't find view":
view = getView(self.event1, 'daterange_display', self.request)
view = getViewProviding(self.eve
George Lee wrote:
I am trying to write a test for a view, and making sure that an object I've
created is associated with the correct view. But either of these lines fails
with a ComponentLookupError "Couldn't find view":
view = getView(self.event1, 'daterange_display', self.request)
view = getVi
Fabio Rizzo Matos wrote:
Olha pq não estava rolando os nossos pontos!
/me precisamos corrigir o agx para gerar os nomes de pacotes com
pontos. Hoje ele está substituindo para ponto.
English, please.
abraços
On 9/23/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
George Lee wrote:
On Sun, 2006-09-24 at 01:37 +0200, Philipp von Weitershausen wrote:
> George Lee wrote:
> > I am trying to write a test for a view, and making sure that an object I've
> > created is associated with the correct view. But either of these lines fails
> > with a ComponentLookupError "Couldn't find vie
Philipp von Weitershausen wrote:
Consider buying my book: http://worldcookery.com
t'is great and will be greater still ;-)
Also consider reading the docs that are there. Zope 3 has lots of docs
(see http://localhost:8080/++apidoc++ after enabling devmode). There are
also a couple of tutoria
Thanks Darryl
you were right about the title attribute of unauthenticated principals.
they don't have it.
I made another ZCML principal with a title and it works fine.
The problem still remains the same though for the principals in the PAU.
I always thought they do have a "title" bacause it i
Hi again Darryl,
just to check something real quick,
does Boston skin really check for authenticated principals??? I checked
the main template and it looks like Boston is getting the
request/principal/title in the same way as every other skin:
User:
U
19 matches
Mail list logo
