Hi all! Is possible to create an object (for example a Page Template) and make it catalog aware? I wonder why the objects aren't catalogable by default (I need all my object catalogables) Any Idea? -- Mis Cosas http://blogs.sistes.net/Garito
--On 18. Juli 2006 15:14:54 +0200 Garito <garito@sistes.net> wrote:
Hi all!
Is possible to create an object (for example a Page Template) and make it catalog aware?
Look at the CatalogAware mixin class.
I wonder why the objects aren't catalogable by default (I need all my object catalogables)
Because Zope is not CMF and Zope is not Plone. Because you need this feature it does not mean that everyone needs this feature by default. -aj
Andreas Jung escribió:
--On 18. Juli 2006 15:14:54 +0200 Garito <garito@sistes.net> wrote:
Hi all!
Is possible to create an object (for example a Page Template) and make it catalog aware?
Look at the CatalogAware mixin class.
But with this class I could create a new class of PT Catalog aware, isn't it? I would like to convert a normal PT is this possible?
I wonder why the objects aren't catalogable by default (I need all my object catalogables)
Because Zope is not CMF and Zope is not Plone. Because you need this feature it does not mean that everyone needs this feature by default.
-aj Sure but Is the cost so big?
-- Mis Cosas http://blogs.sistes.net/Garito
--On 19. Juli 2006 09:34:58 +0200 Garito <garito@sistes.net> wrote:
Andreas Jung escribió:
--On 18. Juli 2006 15:14:54 +0200 Garito <garito@sistes.net> wrote:
Hi all!
Is possible to create an object (for example a Page Template) and make it catalog aware?
Look at the CatalogAware mixin class.
But with this class I could create a new class of PT Catalog aware, isn't it? I would like to convert a normal PT is this possible?
It makes little sense to index the contents of PTs. PTs are used to present a view on a particular instance of your class but not for providing content itself.
I wonder why the objects aren't catalogable by default (I need all my object catalogables)
Because Zope is not CMF and Zope is not Plone. Because you need this feature it does not mean that everyone needs this feature by default.
-aj Sure but Is the cost so big?
This is not the question. If you need catalog awareness, either implement it as stated above or use one of the frameworks....little need to discuss the pros and cons...by default Zope default content-types don't depend on the catalog. CMF and Plone depend on the catalog for various reasons. If you have the requirement to use a catalog you have the mentioned options. -aj
Andreas Jung escribió:
--On 19. Juli 2006 09:34:58 +0200 Garito <garito@sistes.net> wrote:
Andreas Jung escribió:
--On 18. Juli 2006 15:14:54 +0200 Garito <garito@sistes.net> wrote:
Hi all!
Is possible to create an object (for example a Page Template) and make it catalog aware?
Look at the CatalogAware mixin class.
But with this class I could create a new class of PT Catalog aware, isn't it? I would like to convert a normal PT is this possible?
It makes little sense to index the contents of PTs. PTs are used to present a view on a particular instance of your class but not for providing content itself.
I wonder why the objects aren't catalogable by default (I need all my object catalogables)
Because Zope is not CMF and Zope is not Plone. Because you need this feature it does not mean that everyone needs this feature by default.
-aj Sure but Is the cost so big?
This is not the question. If you need catalog awareness, either implement it as stated above or use one of the frameworks....little need to discuss the pros and cons...by default Zope default content-types don't depend on the catalog. CMF and Plone depend on the catalog for various reasons. If you have the requirement to use a catalog you have the mentioned options.
-aj
Yes but what about something like if self.default_catalog != '': self.reindex_object() ? I think it's a question of preferences Then can I "inject" Catalog awarness to an object? -- Mis Cosas http://blogs.sistes.net/Garito
Garito wrote:
Andreas Jung escribió:
--On 19. Juli 2006 09:34:58 +0200 Garito <garito@sistes.net> wrote:
Andreas Jung escribió:
--On 18. Juli 2006 15:14:54 +0200 Garito <garito@sistes.net> wrote:
Hi all!
Is possible to create an object (for example a Page Template) and make it catalog aware?
Look at the CatalogAware mixin class.
But with this class I could create a new class of PT Catalog aware, isn't it? I would like to convert a normal PT is this possible?
It makes little sense to index the contents of PTs. PTs are used to present a view on a particular instance of your class but not for providing content itself.
I wonder why the objects aren't catalogable by default (I need all my object catalogables)
Because Zope is not CMF and Zope is not Plone. Because you need this feature it does not mean that everyone needs this feature by default.
-aj Sure but Is the cost so big?
This is not the question. If you need catalog awareness, either implement it as stated above or use one of the frameworks....little need to discuss the pros and cons...by default Zope default content-types don't depend on the catalog. CMF and Plone depend on the catalog for various reasons. If you have the requirement to use a catalog you have the mentioned options.
-aj
Yes but what about something like
if self.default_catalog != '': self.reindex_object()
?
I think it's a question of preferences
Then can I "inject" Catalog awarness to an object?
Yes you can. Its possible with so called monkeypatching. However if you can do that, you better just write a product w/ subclasses of the standard zope objects and your CatalogAwareness. Its easy and clean and you dont interfere with further development of zope. Regards Tino
Tino Wildenhain escribió:
Garito wrote:
Andreas Jung escribió:
--On 19. Juli 2006 09:34:58 +0200 Garito <garito@sistes.net> wrote:
Andreas Jung escribió:
--On 18. Juli 2006 15:14:54 +0200 Garito <garito@sistes.net> wrote:
Hi all!
Is possible to create an object (for example a Page Template) and make it catalog aware?
Look at the CatalogAware mixin class.
But with this class I could create a new class of PT Catalog aware, isn't it? I would like to convert a normal PT is this possible?
It makes little sense to index the contents of PTs. PTs are used to present a view on a particular instance of your class but not for providing content itself.
I wonder why the objects aren't catalogable by default (I need all my object catalogables)
Because Zope is not CMF and Zope is not Plone. Because you need this feature it does not mean that everyone needs this feature by default.
-aj Sure but Is the cost so big?
This is not the question. If you need catalog awareness, either implement it as stated above or use one of the frameworks....little need to discuss the pros and cons...by default Zope default content-types don't depend on the catalog. CMF and Plone depend on the catalog for various reasons. If you have the requirement to use a catalog you have the mentioned options.
-aj
Yes but what about something like
if self.default_catalog != '': self.reindex_object()
?
I think it's a question of preferences
Then can I "inject" Catalog awarness to an object?
Yes you can. Its possible with so called monkeypatching. However if you can do that, you better just write a product w/ subclasses of the standard zope objects and your CatalogAwareness. Its easy and clean and you dont interfere with further development of zope.
Regards Tino Sure, but I can't create a new product for every product I'll use only to do it catalog aware, isn't it?
Can you say more about monkeypatching? Thanks! -- Mis Cosas http://blogs.sistes.net/Garito
Garito wrote:
Tino Wildenhain escribió:
Garito wrote:
Andreas Jung escribió:
--On 19. Juli 2006 09:34:58 +0200 Garito <garito@sistes.net> wrote:
Andreas Jung escribió:
--On 18. Juli 2006 15:14:54 +0200 Garito <garito@sistes.net> wrote:
> Hi all! > > Is possible to create an object (for example a Page Template) and > make it > catalog aware?
Look at the CatalogAware mixin class.
But with this class I could create a new class of PT Catalog aware, isn't it? I would like to convert a normal PT is this possible?
It makes little sense to index the contents of PTs. PTs are used to present a view on a particular instance of your class but not for providing content itself.
> > I wonder why the objects aren't catalogable by default (I need > all my > object catalogables) >
Because Zope is not CMF and Zope is not Plone. Because you need this feature it does not mean that everyone needs this feature by default.
-aj Sure but Is the cost so big?
This is not the question. If you need catalog awareness, either implement it as stated above or use one of the frameworks....little need to discuss the pros and cons...by default Zope default content-types don't depend on the catalog. CMF and Plone depend on the catalog for various reasons. If you have the requirement to use a catalog you have the mentioned options.
-aj
Yes but what about something like
if self.default_catalog != '': self.reindex_object()
?
I think it's a question of preferences
Then can I "inject" Catalog awarness to an object?
Yes you can. Its possible with so called monkeypatching. However if you can do that, you better just write a product w/ subclasses of the standard zope objects and your CatalogAwareness. Its easy and clean and you dont interfere with further development of zope.
Regards Tino Sure, but I can't create a new product for every product I'll use only to do it catalog aware, isn't it?
Yes you can. Why not? I mean you are using them - so you can use your products instead as well.
Can you say more about monkeypatching?
If you cant figure out (google, imagination) you better dont do it :-) The code to monkey-patch is roughly the same as subclassing. So you better just subclass and use your products. Hint: you can use loops in python too .-) Kind regards Tino
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
Garito wrote:
Andreas Jung escribió:
--On 19. Juli 2006 09:34:58 +0200 Garito <garito@sistes.net> wrote:
Andreas Jung escribió:
> --On 18. Juli 2006 15:14:54 +0200 Garito <garito@sistes.net> wrote: > > >> Hi all! >> >> Is possible to create an object (for example a Page Template) and >> make it >> catalog aware? >> > Look at the CatalogAware mixin class. > But with this class I could create a new class of PT Catalog aware, isn't it? I would like to convert a normal PT is this possible?
It makes little sense to index the contents of PTs. PTs are used to present a view on a particular instance of your class but not for providing content itself.
>> I wonder why the objects aren't catalogable by default (I need >> all my >> object catalogables) >> >> > Because Zope is not CMF and Zope is not Plone. Because you need this > feature it does not mean that everyone needs this feature by default. > > -aj > Sure but Is the cost so big?
This is not the question. If you need catalog awareness, either implement it as stated above or use one of the frameworks....little need to discuss the pros and cons...by default Zope default content-types don't depend on the catalog. CMF and Plone depend on the catalog for various reasons. If you have the requirement to use a catalog you have the mentioned options.
-aj
Yes but what about something like
if self.default_catalog != '': self.reindex_object()
?
I think it's a question of preferences
Then can I "inject" Catalog awarness to an object?
Yes you can. Its possible with so called monkeypatching. However if you can do that, you better just write a product w/ subclasses of the standard zope objects and your CatalogAwareness. Its easy and clean and you dont interfere with further development of zope.
Regards Tino
Sure, but I can't create a new product for every product I'll use only to do it catalog aware, isn't it?
Yes you can. Why not? I mean you are using them - so you can use your products instead as well.
Yes but what if tomorrow you create a product? need work to times: you first, me later In my opinion (is only an opinion) these is not the best situation in a future Sorry but is not so acceptable for me
Can you say more about monkeypatching?
If you cant figure out (google, imagination) you better dont do it :-)
The code to monkey-patch is roughly the same as subclassing. So you better just subclass and use your products.
Hint: you can use loops in python too .-)
Kind regards Tino
A! sure, I'll searched at google! -- Mis Cosas http://blogs.sistes.net/Garito
Garito wrote: ...
Sure, but I can't create a new product for every product I'll use only to do it catalog aware, isn't it?
Yes you can. Why not? I mean you are using them - so you can use your products instead as well.
Yes but what if tomorrow you create a product? need work to times: you first, me later
Who says you have a use for the product I create? Or if it makes sense to catalog it? If you want a cataloguing framework, why dont you use CMF or something?
In my opinion (is only an opinion) these is not the best situation in a future
Sorry but is not so acceptable for me
The point is, it makes no sense to catalog Pagetemplates, Python Scripts, Folders and ZSQL Methods, Mailhosts and Database connections. These are all standard zope objects, yet they make catalogable content only in derived work or when they play together - which is a custom solution anyway. There you can add whatever cataloguing awareness you want.
Can you say more about monkeypatching?
If you cant figure out (google, imagination) you better dont do it :-)
The code to monkey-patch is roughly the same as subclassing. So you better just subclass and use your products.
Hint: you can use loops in python too .-)
Kind regards Tino
A! sure, I'll searched at google!
great :-) Regards Tino
Tino Wildenhain escribió:
Garito wrote: ...
Sure, but I can't create a new product for every product I'll use only to do it catalog aware, isn't it?
Yes you can. Why not? I mean you are using them - so you can use your products instead as well.
Yes but what if tomorrow you create a product? need work to times: you first, me later
Who says you have a use for the product I create? Or if it makes sense to catalog it? If you want a cataloguing framework, why dont you use CMF or something?
I want to make every class catalogable only if I point a zcatalog id (with self.default_catalog) but If I point it I want to catalogue the object Now is a search era, isn't it? Use another framework only to do the objects catalogable? I love simple things
In my opinion (is only an opinion) these is not the best situation in a future
Sorry but is not so acceptable for me
The point is, it makes no sense to catalog Pagetemplates, Python Scripts, Folders and ZSQL Methods, Mailhosts and Database connections. These are all standard zope objects, yet they make catalogable content only in derived work or when they play together - which is a custom solution anyway. There you can add whatever cataloguing awareness you want.
And if I use them dinamically (a user with the role1 use the template Ver but a user with the role2 use the template Ver1 for the same context)? (I'm not sure if I understand you clear, sorry If I make a mistake, please
Can you say more about monkeypatching?
If you cant figure out (google, imagination) you better dont do it :-)
The code to monkey-patch is roughly the same as subclassing. So you better just subclass and use your products.
Hint: you can use loops in python too .-)
Kind regards Tino
A! sure, I'll searched at google!
great :-)
Regards Tino
-- Mis Cosas http://blogs.sistes.net/Garito
Garito wrote:
Tino Wildenhain escribió:
Garito wrote: ...
Sure, but I can't create a new product for every product I'll use only to do it catalog aware, isn't it?
Yes you can. Why not? I mean you are using them - so you can use your products instead as well.
Yes but what if tomorrow you create a product? need work to times: you first, me later
Who says you have a use for the product I create? Or if it makes sense to catalog it? If you want a cataloguing framework, why dont you use CMF or something?
I want to make every class catalogable only if I point a zcatalog id (with self.default_catalog) but If I point it I want to catalogue the object
And what of the object do you want to catalog? Which kind of indexes do you want it to support? What kind of questions do you expect your ZCatalog (hypothetically) answered? Could you give examples?
Now is a search era, isn't it?
Yes, search for what and by whom is the question here.
Use another framework only to do the objects catalogable?
I love simple things
So why are you trying to make standard zope objects more complicated? :)
In my opinion (is only an opinion) these is not the best situation in a future
Sorry but is not so acceptable for me
The point is, it makes no sense to catalog Pagetemplates, Python Scripts, Folders and ZSQL Methods, Mailhosts and Database connections. These are all standard zope objects, yet they make catalogable content only in derived work or when they play together - which is a custom solution anyway. There you can add whatever cataloguing awareness you want.
And if I use them dinamically (a user with the role1 use the template Ver but a user with the role2 use the template Ver1 for the same context)? (I'm not sure if I understand you clear, sorry If I make a mistake, please
This would not be supported by just adding indexing to the standard objects anyway. You would write a container which supports the bahavior you want - and while you are at it you can easily add catalogawareness to that - exactly where and in the way _you_ need it :-) Individual objects cataloguing themself would get in your way. Regards Tino Wildenhain
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
Garito wrote: ...
Sure, but I can't create a new product for every product I'll use only to do it catalog aware, isn't it?
Yes you can. Why not? I mean you are using them - so you can use your products instead as well.
Yes but what if tomorrow you create a product? need work to times: you first, me later
Who says you have a use for the product I create? Or if it makes sense to catalog it? If you want a cataloguing framework, why dont you use CMF or something?
I want to make every class catalogable only if I point a zcatalog id (with self.default_catalog) but If I point it I want to catalogue the object
And what of the object do you want to catalog? Which kind of indexes do you want it to support? What kind of questions do you expect your ZCatalog (hypothetically) answered? Could you give examples?
Is not important what I want to catalog, for me is important that the object *was* in the catalog (some catalogs indexes some properties some others other properties)
Now is a search era, isn't it?
Yes, search for what and by whom is the question here.
I don't thing so. The question is who is in the catalog
Use another framework only to do the objects catalogable?
I love simple things
So why are you trying to make standard zope objects more complicated? :)
More complicated? Sure, but I don't understand the cost to make every object in Zope catalogable. A class and a variable I don't thing is a big cost And I thing in Zope when I thing in keep it simple
In my opinion (is only an opinion) these is not the best situation in a future
Sorry but is not so acceptable for me
The point is, it makes no sense to catalog Pagetemplates, Python Scripts, Folders and ZSQL Methods, Mailhosts and Database connections. These are all standard zope objects, yet they make catalogable content only in derived work or when they play together - which is a custom solution anyway. There you can add whatever cataloguing awareness you want.
And if I use them dinamically (a user with the role1 use the template Ver but a user with the role2 use the template Ver1 for the same context)? (I'm not sure if I understand you clear, sorry If I make a mistake, please
This would not be supported by just adding indexing to the standard objects anyway. You would write a container which supports the bahavior you want - and while you are at it you can easily add catalogawareness to that - exactly where and in the way _you_ need it :-) Individual objects cataloguing themself would get in your way.
Regards Tino Wildenhain
Yes, I'm creating a specific container that works in a curious way. In that container I could catalog a Page Template when I'm adding it but perhaps sometimes I want to track its changes an so on -- Mis Cosas http://blogs.sistes.net/Garito
Garito wrote:
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
Garito wrote: ...
> Sure, but I can't create a new product for every product I'll use > only > to do it catalog aware, isn't it? > Yes you can. Why not? I mean you are using them - so you can use your products instead as well.
Yes but what if tomorrow you create a product? need work to times: you first, me later
Who says you have a use for the product I create? Or if it makes sense to catalog it? If you want a cataloguing framework, why dont you use CMF or something?
I want to make every class catalogable only if I point a zcatalog id (with self.default_catalog) but If I point it I want to catalogue the object
And what of the object do you want to catalog? Which kind of indexes do you want it to support? What kind of questions do you expect your ZCatalog (hypothetically) answered? Could you give examples?
Is not important what I want to catalog, for me is important that the object *was* in the catalog (some catalogs indexes some properties some others other properties)
Please read the catalog section again: there isnt the object in the catalog! Again: The object is _not_ in the catalog. Its all about usefull indexes and maybe object metadata. So again: _what_ actually do you expect to find?
Now is a search era, isn't it?
Yes, search for what and by whom is the question here.
I don't thing so. The question is who is in the catalog
Use another framework only to do the objects catalogable?
I love simple things
So why are you trying to make standard zope objects more complicated? :)
More complicated? Sure, but I don't understand the cost to make every object in Zope catalogable. A class and a variable I don't thing is a big cost And I thing in Zope when I thing in keep it simple
Yes, but its nonsense. You cant do anything more with the objects in Zope if they are catalogued.
In my opinion (is only an opinion) these is not the best situation in a future
Sorry but is not so acceptable for me
The point is, it makes no sense to catalog Pagetemplates, Python Scripts, Folders and ZSQL Methods, Mailhosts and Database connections. These are all standard zope objects, yet they make catalogable content only in derived work or when they play together - which is a custom solution anyway. There you can add whatever cataloguing awareness you want.
And if I use them dinamically (a user with the role1 use the template Ver but a user with the role2 use the template Ver1 for the same context)? (I'm not sure if I understand you clear, sorry If I make a mistake, please
This would not be supported by just adding indexing to the standard objects anyway. You would write a container which supports the bahavior you want - and while you are at it you can easily add catalogawareness to that - exactly where and in the way _you_ need it :-) Individual objects cataloguing themself would get in your way.
Regards Tino Wildenhain
Yes, I'm creating a specific container that works in a curious way. In that container I could catalog a Page Template when I'm adding it but perhaps sometimes I want to track its changes an so on
Yes, but who should know what _you_ want your objects to do? You cannot expect all people (especially the ones writing zope core) to guess your needs - you are the one to express your wishes in the form of code :-) If you end up having a general solution (like these frameworks are) you can share them with others. Regards Tino
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
Garito wrote: ...
>> Sure, but I can't create a new product for every product I'll >> use only >> to do it catalog aware, isn't it? >> > Yes you can. Why not? I mean you are using them - so you can use > your products instead as well. > Yes but what if tomorrow you create a product? need work to times: you first, me later
Who says you have a use for the product I create? Or if it makes sense to catalog it? If you want a cataloguing framework, why dont you use CMF or something?
I want to make every class catalogable only if I point a zcatalog id (with self.default_catalog) but If I point it I want to catalogue the object
And what of the object do you want to catalog? Which kind of indexes do you want it to support? What kind of questions do you expect your ZCatalog (hypothetically) answered? Could you give examples?
Is not important what I want to catalog, for me is important that the object *was* in the catalog (some catalogs indexes some properties some others other properties)
Please read the catalog section again: there isnt the object in the catalog! Again: The object is _not_ in the catalog. Its all about usefull indexes and maybe object metadata. So again: _what_ actually do you expect to find? When I talk about was in the catalog I mean the object is catalogued I expect to find *the object* in the catalog
For example: How do you know how many cousins you have? Because you are a catalog that catalog the number of cousins you have Another example: how much skills about computing do you have? Again your skills are objects that you need (as a catalog you are) to catalog Like an entity (a thing, and object) you need to know some data stored in your life added to you
Now is a search era, isn't it?
Yes, search for what and by whom is the question here.
I don't thing so. The question is who is in the catalog
Use another framework only to do the objects catalogable?
I love simple things
So why are you trying to make standard zope objects more complicated? :)
More complicated? Sure, but I don't understand the cost to make every object in Zope catalogable. A class and a variable I don't thing is a big cost And I thing in Zope when I thing in keep it simple
Yes, but its nonsense. You cant do anything more with the objects in Zope if they are catalogued.
Are you sure? I can find them!!! Then if I can find them I can count them, give to you (even if its don't depend on me, remember your skills or your cousins?) I want to create an object that acts like an entity (like a human or a mortage or a paper or a product -that you can sell) These entity need to know how is it (its properties, its characteristics) I ask myself if I know myself but I only know about myself all I can catalogue
In my opinion (is only an opinion) these is not the best situation in a future
Sorry but is not so acceptable for me
The point is, it makes no sense to catalog Pagetemplates, Python Scripts, Folders and ZSQL Methods, Mailhosts and Database connections. These are all standard zope objects, yet they make catalogable content only in derived work or when they play together - which is a custom solution anyway. There you can add whatever cataloguing awareness you want.
And if I use them dinamically (a user with the role1 use the template Ver but a user with the role2 use the template Ver1 for the same context)? (I'm not sure if I understand you clear, sorry If I make a mistake, please
This would not be supported by just adding indexing to the standard objects anyway. You would write a container which supports the bahavior you want - and while you are at it you can easily add catalogawareness to that - exactly where and in the way _you_ need it :-) Individual objects cataloguing themself would get in your way.
Regards Tino Wildenhain
Yes, I'm creating a specific container that works in a curious way. In that container I could catalog a Page Template when I'm adding it but perhaps sometimes I want to track its changes an so on
Yes, but who should know what _you_ want your objects to do? You cannot expect all people (especially the ones writing zope core) to guess your needs - you are the one to express your wishes in the form of code :-) If you end up having a general solution (like these frameworks are) you can share them with others.
Regards Tino
I don't expect anyone guess my needs (is for that I need to develop the class) :) I only ask if I can add some super classes to an object when I create it :) I know my needs are so particular but I want to create something new with a new perspective. If I can the result will be very curious (I suppose, I expect even) I choose Zope because is the most near to my finall result -- Mis Cosas http://blogs.sistes.net/Garito
On 7/20/06, Garito <garito@sistes.net> wrote:
Please read the catalog section again: there isnt the object in the catalog! Again: The object is _not_ in the catalog. Its all about usefull indexes and maybe object metadata. So again: _what_ actually do you expect to find? When I talk about was in the catalog I mean the object is catalogued I expect to find *the object* in the catalog
No, there are indexes in the catalog that point to the object. You will have to search for certain information that then points to certain objects. This can be the object Type, or the path, or the id. Note that objects do not need to be catalogue aware to be catalogueable; just use the find tab and the catalog will index them. Making all Zope objects catalog aware by default makes no sense though. You have yet to come with a compelling generic use-case, let alone with one that convinces me. Why catalog database connectors for example? What kind of search are you performing? Have you thought about the potential problems of making all objects catalog-aware by default, like potential conflicts and side-effects? I say a big -infinity from me on the whole idea. -- Martijn Pieters
Garito wrote:
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
Garito wrote: ...
>>> Sure, but I can't create a new product for every product I'll >>> use only >>> to do it catalog aware, isn't it? >>> >> Yes you can. Why not? I mean you are using them - so you can use >> your products instead as well. >> > Yes but what if tomorrow you create a product? need work to > times: you > first, me later > Who says you have a use for the product I create? Or if it makes sense to catalog it? If you want a cataloguing framework, why dont you use CMF or something?
I want to make every class catalogable only if I point a zcatalog id (with self.default_catalog) but If I point it I want to catalogue the object
And what of the object do you want to catalog? Which kind of indexes do you want it to support? What kind of questions do you expect your ZCatalog (hypothetically) answered? Could you give examples?
Is not important what I want to catalog, for me is important that the object *was* in the catalog (some catalogs indexes some properties some others other properties)
Please read the catalog section again: there isnt the object in the catalog! Again: The object is _not_ in the catalog. Its all about usefull indexes and maybe object metadata. So again: _what_ actually do you expect to find? When I talk about was in the catalog I mean the object is catalogued I expect to find *the object* in the catalog
For example:
How do you know how many cousins you have? Because you are a catalog that catalog the number of cousins you have
So you want to count objects based on their meta_type? Of what use would be such an information? What if you know how many pagetemplates you have? :-)
Another example: how much skills about computing do you have? Again your skills are objects that you need (as a catalog you are) to catalog
We have a skills object in plain zope now? Thats news for me.
Like an entity (a thing, and object) you need to know some data stored in your life added to you
Yes, but a zcatalog cannot work with "some data" - you need to specify exactly _which_ data you want to find. So what exacly is this on standard Zope objects? ..
Yes, but its nonsense. You cant do anything more with the objects in Zope if they are catalogued. Are you sure? I can find them!!! Then if I can find them I can count them, give to you (even if its don't depend on me, remember your skills or your cousins?)
Ah yes, which zope product stores cousin data?
I want to create an object that acts like an entity (like a human or a mortage or a paper or a product -that you can sell)
Yes, you crate it - you define its cataloguing. So what is your business with standard zope objects here?
These entity need to know how is it (its properties, its characteristics)
You cant barely catalog all properties - the catalog would not even know if this property is meant as keyword or fulltext or whatever...
I ask myself if I know myself but I only know about myself all I can catalogue ...
Regards Tino I don't expect anyone guess my needs (is for that I need to develop the class) :) I only ask if I can add some super classes to an object when I create it :)
You can, you just add it. Its there and you even know its name. So what was your problem again? :-)
I know my needs are so particular but I want to create something new with a new perspective. If I can the result will be very curious (I suppose, I expect even)
I choose Zope because is the most near to my finall result
Exactly :-) Regards TIno
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
Garito wrote:
Tino Wildenhain escribió:
> Garito wrote: > ... > > >>>> Sure, but I can't create a new product for every product I'll >>>> use only >>>> to do it catalog aware, isn't it? >>>> >>> Yes you can. Why not? I mean you are using them - so you can use >>> your products instead as well. >>> >> Yes but what if tomorrow you create a product? need work to >> times: you >> first, me later >> > Who says you have a use for the product I create? Or if it makes > sense to catalog it? If you want a cataloguing framework, why > dont you use CMF or something? > I want to make every class catalogable only if I point a zcatalog id (with self.default_catalog) but If I point it I want to catalogue the object
And what of the object do you want to catalog? Which kind of indexes do you want it to support? What kind of questions do you expect your ZCatalog (hypothetically) answered? Could you give examples?
Is not important what I want to catalog, for me is important that the object *was* in the catalog (some catalogs indexes some properties some others other properties)
Please read the catalog section again: there isnt the object in the catalog! Again: The object is _not_ in the catalog. Its all about usefull indexes and maybe object metadata. So again: _what_ actually do you expect to find? When I talk about was in the catalog I mean the object is catalogued I expect to find *the object* in the catalog
For example:
How do you know how many cousins you have? Because you are a catalog that catalog the number of cousins you have
So you want to count objects based on their meta_type? Of what use would be such an information? What if you know how many pagetemplates you have? :-) Why not? It depends on the nature of the entity If I know now many pagetemplates has an entity I could show it to the user Because I make some curious use of the objects of Zope, for me every object will be a functionality, something the object can do, then I want to know everything about the entity
Another example: how much skills about computing do you have? Again your skills are objects that you need (as a catalog you are) to catalog
We have a skills object in plain zope now? Thats news for me. not now but I can develep it if I need
Like an entity (a thing, and object) you need to know some data stored in your life added to you
Yes, but a zcatalog cannot work with "some data" - you need to specify exactly _which_ data you want to find. So what exacly is this on standard Zope objects? My entity has some default indexes like meta_type or owner, etc but you could be creative in order to create new ones. It only depends on your needs ..
Yes, but its nonsense. You cant do anything more with the objects in Zope if they are catalogued. Are you sure? I can find them!!! Then if I can find them I can count them, give to you (even if its don't depend on me, remember your skills or your cousins?)
Ah yes, which zope product stores cousin data? Do you want to store cousins data? you need to create an object that stores cousin data
I want to create an object that acts like an entity (like a human or a mortage or a paper or a product -that you can sell)
Yes, you crate it - you define its cataloguing. So what is your business with standard zope objects here? They are funcionality to my entity. If the entity has a functionality that sends mails the entity need to has a mail host object but It's not important where do you create it if the entity catalogue it (you can always find it if you ask to the entity catalog)
These entity need to know how is it (its properties, its characteristics)
You cant barely catalog all properties - the catalog would not even know if this property is meant as keyword or fulltext or whatever... don't worry! I want to find them. It's not important what they are or where they are
I ask myself if I know myself but I only know about myself all I can catalogue ...
Regards Tino I don't expect anyone guess my needs (is for that I need to develop the class) :) I only ask if I can add some super classes to an object when I create it :)
You can, you just add it. Its there and you even know its name. So what was your problem again? :-) They way to add it (but you point me to find at google monkeypatch isn't it? Thanks again)
I know my needs are so particular but I want to create something new with a new perspective. If I can the result will be very curious (I suppose, I expect even)
I choose Zope because is the most near to my finall result
Exactly :-)
Regards TIno
-- Mis Cosas http://blogs.sistes.net/Garito
On 7/19/06, Garito <garito@sistes.net> wrote:
Look at the CatalogAware mixin class. But with this class I could create a new class of PT Catalog aware, isn't it?
Yup.
I would like to convert a normal PT is this possible?'
Yes, with monkeypatches, but really, you don't want to go that way. This feels to me as a case of you asking the question you THINK is the problem, because thats the problem you have right now. But often when that happens you have been running in the wrong direction for a while. It's like somebody asking how to break down a wall to get to the mall on the other side, when the best way to get to the wall is to get out of the dead-end street and then take left. :) So in short: Why on earth would you want page templates to be catalogaware? :)
Sure but Is the cost so big?
Yes. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/
Lennart Regebro escribió:
On 7/19/06, Garito <garito@sistes.net> wrote:
Look at the CatalogAware mixin class. But with this class I could create a new class of PT Catalog aware, isn't it?
Yup.
I would like to convert a normal PT is this possible?'
Yes, with monkeypatches, but really, you don't want to go that way. This feels to me as a case of you asking the question you THINK is the problem, because thats the problem you have right now. But often when that happens you have been running in the wrong direction for a while.
It's like somebody asking how to break down a wall to get to the mall on the other side, when the best way to get to the wall is to get out of the dead-end street and then take left. :)
So in short: Why on earth would you want page templates to be catalogaware? :)
Sure but Is the cost so big?
Yes.
Ok, I'll rethink the question and try another aproach Thanks by now! (I'll ask you later if needed) -- Mis Cosas http://blogs.sistes.net/Garito
participants (5)
-
Andreas Jung -
Garito -
Lennart Regebro -
Martijn Pieters -
Tino Wildenhain