Posted: Tue Apr 10, 2007 2:26 pmi was playing around with the recordnavmenu.
technically it works great!
but i noticed a minor annoyance (only endusers would would be confused).
consider this test situation:
we have our known "getting started" tables:
program (with a relationship set to course via programcourses)
course (with a relationship set to program via programcourses)
programcourses (links program and course together)
the relationships are set both ways so we can add programs to courses but we can also add courses to programs in the gui.
now if we add a program to a course and check out the very cool recordnavmenu (while viewing course details or program details) then it can be exanded infinitely because the expand functionality is smart, but in a generic way
maybe it would be good not to be able to expand a node that represents the record we are currently seeing in the details.
so for instance when we are in the program details screen viewing a program record:
1- we expand the prgram's "courses" in the recordnavmenu.
2- then we see a list of courses attached this program.
3- these courses can be expanded too and we get a list of programs
4- these program nodes should be able to be expanded too, EXCEPT if it represents the program we are looking at in the details.
in short, a childnode which represents the "current record" should not be expandable imho.
technically it works great!
but i noticed a minor annoyance (only endusers would would be confused).
consider this test situation:
we have our known "getting started" tables:
program (with a relationship set to course via programcourses)
course (with a relationship set to program via programcourses)
programcourses (links program and course together)
the relationships are set both ways so we can add programs to courses but we can also add courses to programs in the gui.
now if we add a program to a course and check out the very cool recordnavmenu (while viewing course details or program details) then it can be exanded infinitely because the expand functionality is smart, but in a generic way
maybe it would be good not to be able to expand a node that represents the record we are currently seeing in the details.
so for instance when we are in the program details screen viewing a program record:
1- we expand the prgram's "courses" in the recordnavmenu.
2- then we see a list of courses attached this program.
3- these courses can be expanded too and we get a list of programs
4- these program nodes should be able to be expanded too, EXCEPT if it represents the program we are looking at in the details.
in short, a childnode which represents the "current record" should not be expandable imho.