[Pkg-e-commits] [SCM] Enlightenment DR17 toolkit based (based on the EFL) branch, upstream-vcs, updated. 447de88121d145a078f1754a0cfebb704d363821
pfritz
pfritz at alioth.debian.org
Sat Jun 7 18:34:18 UTC 2008
The following commit has been merged in the upstream-vcs branch:
commit 741e8ee52c66bef6998d8872197e42f18e148ea9
Author: pfritz <pfritz>
Date: Sat Apr 26 17:41:07 2008 +0000
add a guideline for containers' sizing
Note: not all containers are following them yet, hopefully this will be fixed in
the near future.
diff --git a/doc/tutorials/fill_policies.dox b/doc/tutorials/fill_policies.dox
index afbb9b2..c10fd11 100644
--- a/doc/tutorials/fill_policies.dox
+++ b/doc/tutorials/fill_policies.dox
@@ -6,6 +6,8 @@ adjust the widget sizes as needed to make everything fit. The fill
policies of Ewl can be a bit confusing for the first time user, hell,
I still have problems at times.
+ at section fill_users Using the fill policy
+
The basis for how fill policies fit together is shown the following image.
@image html object_sizing.png
@@ -33,4 +35,36 @@ EWL_FLAG_FILL_FILL | Fill both horizontally and vertically
EWL_FLAG_FILL_ALL | Shrink or fill as needed
@endverbatim
+ at section fill_guide Guidelines for container authors
+
+As you have seen in the previous section fill policies and the three different
+sizes are very closely connected. As a container author you have to set them
+to proper values in particular for the preferred size. Of course you do not
+have to overwrite them if you are inheriting this feature from the parent
+widget, as long it fits your needs.
+
+ at note The following guidelines are only commendations and not strict rules.
+ There maybe good reason for some containers to not follow them.
+
+ at subsection fill_guide_min The minimum size
+A container should set a minimum size for any components it displays
+beyond the children packed inside of it. For example if you write a scrollpane,
+the minimum size should contain the scrollbars, but not the content added by
+the user of the container.
+
+ at subsection fill_guide_pref The preferred size
+Every child of the container should be visible if the container has the size of
+its preferred size. Your container should respect the fill policy of the
+children, so if a child is set to SHRINK the user don't want it necessarily
+to be drawn in its full preferred size. For the calculation of the preferred
+size, it is advisable to use, what is returned from
+ewl_object_minimum_size_get(). If the child is not set to shrink the return
+value is the same like the return value of ewl_object_preferred_size_get(),
+but if the child is set to shrink it will return the minimum size.
+
+ at subsection fill_guide_max The maximum size
+You do not need to set this value. By default it is set to a very big number
+which should be sufficient in most cases. But, of course, you can set it if you
+need to.
+
*/
--
Enlightenment DR17 toolkit based (based on the EFL)
More information about the Pkg-e-commits
mailing list