> Hi, > > I think you've overlooked a detail about grub's menu layout. The > smallest elements, text and image, both have fixed size, The largest > element, the screen, also have fixed size, therefore, we need to > adjust the middle layers to fit both ends, it's not as simple as it > seems. > > There are two method to calculate the size of window. It can be > calculate using children widget, with auto layout, or parent widget, > with x,y,width,height coordinate, as the smallest and largest element > are fixed, we need to switch from children determined size to parent > determined size at some point during the walk of ui tree. > > For operation system, the switch is at the window boundary. Consider > web browser. Inside the browser, elements are placed with layout > manager, no coordinate is needed, but the browser itself is placed on > the screen using x,y,width,height coordinate by the OS. For some OS > like chrome, it seems to incorporate the concept of using the whole > screen as browser. The menu system support both method, it's just a > matter of how you define the border, that's, when to switch from > x,y,width,height positioning to layout manager positioning. > > Therefore, it needs to have two set of margin properties: > > inner_*, outer_* : calculate from children to parent
I think that "margin" and "padding" are the standard names for this spacing measurements (distance from content to border) and (distance from border to bounding box), respectively. Also in some systems padding of adjacent elements can overlap. > attach_* : calculate from parent to children > > -- > Bean > > gitgrub home: http://github.com/grub/grub/ > my fork page: http://github.com/bean123/grub/ > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/grub-devel > _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
