Suggestion: Related objects

Previous topic

Suggestions

Next topic

Author	Message
Daniel Staver	Monday 18 August 2003 10:20:56 am I would like to be able to specify the relations allowed for a class better than what is possible today. Example: I'd like to create a relation for the class Project to the node Employees. When editing a new Project the relation would then fetch all the Employees from that node and present them as a multi-selectbox where the user could select one or more related employees to a project. Theoretically this is already possible through today's related object functionality, but it's too open, as the user can relate to any type of object he has read access to. It's also easier for the user to directly be able to select the employees from a list rather than having to navigate through the whole node tree to find the right object. This would also simplify template creation as it would be much easier to create a separate display for related employees as opposed to other types of related objects. Suggested selection methods: - Checkbox - Radio buttons - Drop-down list - Multiselect box Suggested relation filters: - Class - Section - Node - Subtree (subtree would only make sense for drop-down list and multi-selectbox I think) It would be nice to be able to specify the sorting medthod for a relation as well. Daniel Staver http://daniel.staver.no
Kai Duebbert	Tuesday 26 August 2003 12:42:59 am It is already possible to do everything of what you suggest through template programming. (See e.g. http://ez.no/developer/ez_publish_3/forum/developer/select_field_for_object_relation ) It would be nice to have these features directly in the datatype though.

Author

Message

Daniel Staver

Monday 18 August 2003 10:20:56 am

I would like to be able to specify the relations allowed for a class better than what is possible today.

Example:
I'd like to create a relation for the class Project to the node Employees. When editing a new Project the relation would then fetch all the Employees from that node and present them as a multi-selectbox where the user could select one or more related employees to a project.

Theoretically this is already possible through today's related object functionality, but it's too open, as the user can relate to any type of object he has read access to. It's also easier for the user to directly be able to select the employees from a list rather than having to navigate through the whole node tree to find the right object.

This would also simplify template creation as it would be much easier to create a separate display for related employees as opposed to other types of related objects.

Suggested selection methods:
- Checkbox
- Radio buttons
- Drop-down list
- Multiselect box

Suggested relation filters:
- Class
- Section
- Node
- Subtree (subtree would only make sense for drop-down list and multi-selectbox I think)

It would be nice to be able to specify the sorting medthod for a relation as well.

Daniel Staver
http://daniel.staver.no

Kai Duebbert

Tuesday 26 August 2003 12:42:59 am

It is already possible to do everything of what you suggest through template programming. (See e.g. http://ez.no/developer/ez_publish_3/forum/developer/select_field_for_object_relation )

It would be nice to have these features directly in the datatype though.

eZ debug

Timing:	Jan 18 2025 04:59:08
Script start
Timing:	Jan 18 2025 04:59:08
Module start 'layout'
Timing:	Jan 18 2025 04:59:08
Module start 'content'
Timing:	Jan 18 2025 04:59:08
Module end 'content'
Timing:	Jan 18 2025 04:59:08
Script end

Main resources:

Total runtime	0.4094 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0059	589.0313	152.6250
Module start 'layout'	0.0059	0.0029	741.6563	39.4453
Module start 'content'	0.0087	0.3983	781.1016	524.3828
Module end 'content'	0.4070	0.0024	1,305.4844	8.1641
Script end	0.4094		1,313.6484

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.8087	16	0.0002
Check MTime	0.0014	0.3454	16	0.0001
Mysql Total
Database connection	0.0011	0.2662	1	0.0011
Mysqli_queries	0.3650	89.1567	54	0.0068
Looping result	0.0005	0.1176	52	0.0000
Template Total	0.3823	93.4	2	0.1911
Template load	0.0021	0.5136	2	0.0011
Template processing	0.3802	92.8500	2	0.1901
Template load and register function	0.0001	0.0227	1	0.0001
states
state_id_array	0.0006	0.1522	1	0.0006
state_identifier_array	0.0010	0.2506	2	0.0005
Override
Cache load	0.0017	0.4163	23	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1649	2	0.0003
Fetch class attribute name	0.0013	0.3063	3	0.0004
XML
Image XML parsing	0.0006	0.1384	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0015	3	0.0000
General
dbfile	0.0007	0.1723	16	0.0000
String conversion	0.0000	0.0022	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 13 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs