Forums / Suggestions / Dependancy on system generated ID's is bad design

Dependancy on system generated ID's is bad design

Next topic

Author	Message
Willie Seabrook	Thursday 28 August 2003 2:31:36 am In my opinion, the dependance on system generated (essentially) random id numbers is bad. This goes for sections, folders, nodes etc. For example, if your coding to show different things in your main template based upon section, then you must compare with section id. This is fine untill you have to swap over to a new version or someone changes something. You should be able to access a sections name (that can be kept constant) and hence won't need to make changes to template code all the time. Regards, Willie
Jan Borsodi	Thursday 28 August 2003 3:59:28 am A good point, you can already do this for content classes but it should be extended to other areas of eZ publish as well. For instance being able to give an object or node a unique on the site which can be used in the template would be nice. Makes it easier to move the item around as well. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
Volker Lenz	Wednesday 03 September 2003 2:55:43 pm Isn't the new explicit naming of navigationpart identifiers an approach to resolve this ID-based design from ezp3.2 on (at least in the case of sections ?)

Author

Message

Thursday 28 August 2003 2:31:36 am

In my opinion, the dependance on system generated (essentially) random id numbers is bad. This goes for sections, folders, nodes etc.

For example, if your coding to show different things in your main template based upon section, then you must compare with section id. This is fine untill you have to swap over to a new version or someone changes something. You should be able to access a sections name (that can be kept constant) and hence won't need to make changes to template code all the time.

Regards,
Willie

Jan Borsodi

Thursday 28 August 2003 3:59:28 am

A good point, you can already do this for content classes but it should be extended to other areas of eZ publish as well.
For instance being able to give an object or node a unique on the site which can be used in the template would be nice. Makes it easier to move the item around as well.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Volker Lenz

Wednesday 03 September 2003 2:55:43 pm

Isn't the new explicit naming of navigationpart identifiers an approach to resolve this ID-based design from ezp3.2 on (at least in the case of sections ?)