Some cases of regression in ArchGenXml ?

[Giovanni Toffoli]

AGX continues to be a very effective operational guide when creating,
maintaining or restructuring a Plone product. But sometimes I find things
that no more work in new versions. I give 2 examples.

1. Support for inverse relations

In AGX version 2.3 it seems that the tag "inverse_relation_name" is not
fully honoured:
- it affects the generation of the file relations.xml
- but, in the schema, the fields at both ends have the same (unmodified)
value for the property "relationship" in the AT schema.
Please, tell me if I'm missing something or I should post an issue in some
bug tracker.
I remember that in version 1.5 inverse_relation_name was ok, and in version
1.4 this tag wasn't necessary since the inverse relation name was postfixed
by "_inverse" as default.

Also, I cannot understand how "options" are specified in AGX: I tried to set
the value of the tag "old_inversion_relation_name" in the root element of
the ArgoUML model, without results.

References:
http://plone.org/documentation/manual/archgenxml2/3rdparty/relations
http://plone.org/products/archgenxml/issues/139

2. Generating catalog indexes

In previous versions, the "index" tag was enough to create a portal_catalog
index on install and to declare it inside the AT schema.
Now 2 tags are necessary ("catalog:index" and "index:type"), or more, and
this is ok, since this makes the mechanism more flexible. The related info
is put inside the catalog.xml file.
The presence of an "index" tag produces a warning and no "index" property in
the schema.
But, in programmatically generating search forms and related code, I (only I
?) was relying on the inspection of the AT schema to know that an index of a
certain type was associated to a field. How can I recover that behaviour ?

Thank you very much in advance for any suggestions.

Giovanni



------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Archetypes-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/archetypes-users

[Jens W. klein-2]

Am Fri, 13 Mar 2009 10:44:27 +0100 schrieb Giovanni Toffoli:

> AGX continues to be a very effective operational guide when creating,
> maintaining or restructuring a Plone product. But sometimes I find
> things that no more work in new versions. I give 2 examples.

the major problem with archgenxml is, its a huge code monster with
minimal test coverage. but it works. almost.

while refactoring part we now have a problem, because its impossible to
test all features manually.

its very helpful to get bug report on this. also it helps providing an
example model to make it simple for me or other to reproduce it. and last
but not least: i love bugfixes and commits :-)

With AGX 3 the testcoverage will be much better and easier to implement
(see other postings on this list). But AGX 3 will be a complete rewrite.
We will keep the base-concepts, but we chnage a lot. We will stick on AGX
2 for a long time, because I doubt we will implement all features of AGX2
in AGX3 and I doubt it would make sense to do so.

Thanks for reporting, unfortunally at the moment I dont have much time to
step on it. Maybe we have some volunteer around?

> 1. Support for inverse relations
>
> In AGX version 2.3 it seems that the tag "inverse_relation_name" is not
> fully honoured:
> - it affects the generation of the file relations.xml - but, in the
> schema, the fields at both ends have the same (unmodified) value for the
> property "relationship" in the AT schema. Please, tell me if I'm missing
> something or I should post an issue in some bug tracker.
> I remember that in version 1.5 inverse_relation_name was ok, and in
> version 1.4 this tag wasn't necessary since the inverse relation name
> was postfixed by "_inverse" as default.
>
> Also, I cannot understand how "options" are specified in AGX: I tried to
> set the value of the tag "old_inversion_relation_name" in the root
> element of the ArgoUML model, without results.
>
> References:
> http://plone.org/documentation/manual/archgenxml2/3rdparty/relations
> http://plone.org/products/archgenxml/issues/139

Looks like the feature broke. Needs a fix.
 
> 2. Generating catalog indexes
>
> In previous versions, the "index" tag was enough to create a
> portal_catalog index on install and to declare it inside the AT schema.
> Now 2 tags are necessary ("catalog:index" and "index:type"), or more,
> and this is ok, since this makes the mechanism more flexible. The
> related info is put inside the catalog.xml file.

Yes, I refactored this part for AGX2

> The presence of an "index" tag produces a warning and no "index"
> property in the schema.

indeed, but it should appear in the catalog.xml file.

> But, in programmatically generating search forms and related code, I
> (only I ?) was relying on the inspection of the AT schema to know that
> an index of a certain type was associated to a field. How can I recover
> that behaviour ?

the class does not need to know about its indexes, this are two different
things.

> Thank you very much in advance for any suggestions.>

best regards
Jens
--
Jens W. Klein, BlueDynamics Alliance, http://bluedynamics.com


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Archetypes-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/archetypes-users