From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mungu-0007Dy-C7 for mharc-grub-devel@gnu.org; Mon, 05 Oct 2009 09:33:28 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mungs-0007DG-Td for grub-devel@gnu.org; Mon, 05 Oct 2009 09:33:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mungr-0007Ce-Ty for grub-devel@gnu.org; Mon, 05 Oct 2009 09:33:26 -0400 Received: from [199.232.76.173] (port=57905 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mungr-0007CP-Mq for grub-devel@gnu.org; Mon, 05 Oct 2009 09:33:25 -0400 Received: from fg-out-1718.google.com ([72.14.220.157]:14962) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mungq-0005VK-LC for grub-devel@gnu.org; Mon, 05 Oct 2009 09:33:25 -0400 Received: by fg-out-1718.google.com with SMTP id 22so1022191fge.12 for ; Mon, 05 Oct 2009 06:33:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=pj7+2Ges5MhYQJITkaBd6EM3dSHdGMgHTGDNJDqqyDk=; b=VuEej2pPJL5jgATN9iHkvIQ9tDqBc5BhWJliX7m+lpk0iMQv2s5CFoslBLyvuJ6I8B ekq4CORqCgeE+XHj/qW+LuHR0zZBnQBHkKZI9vCQuMKwhe8/TvGRQ5KV8rH8doK1bz3b z8/2Bf/J/cfXB8qBbQlgBA5ve48GB0Ve40qkc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=ggsWgFzUVId8i8MVfwZAt0sB0uftXrKJBZqtyxHaCZPI4i0URmGhnCdebEfQ3YHckn RZQS1WyQ9L/J67cTp/DKDhh02dTLeSnO58MwDML4ehEEW2hS42t3fQbss1/LLECPMeAs daoQPob0c6BoZZ5pUOoZtDXs3YE/SCB9AgBB4= MIME-Version: 1.0 Sender: hramrach@gmail.com Received: by 10.86.242.15 with SMTP id p15mr12088fgh.14.1254749603505; Mon, 05 Oct 2009 06:33:23 -0700 (PDT) In-Reply-To: References: <2e59e6970910040906o4cd536bancb2655c7301d69ec@mail.gmail.com> Date: Mon, 5 Oct 2009 15:33:23 +0200 X-Google-Sender-Auth: eb20ea76f667b51f Message-ID: From: Michal Suchanek To: The development of GRUB 2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: [GITGRUB] New menu interface (implementation) X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2009 13:33:27 -0000 2009/10/5 Bean : > On Mon, Oct 5, 2009 at 5:07 PM, Michal Suchanek wro= te: >> A panel should never be removed from layout management, it then >> becomes pointless. >> >> A top-aligned panel should be done with alignment, and should be only >> possible in horizontal panels like this: >> >> panel{ >> =C2=A0direction =3D left_to_right >> =C2=A0panel{ id =3D"bb" ;valign =3D center} >> =C2=A0panel{ id =3D"bb" ; valign =3D top} >> =C2=A0panel{ id =3D"bb" ; valign =3D bottom} >> =C2=A0} >> } >> >> In a top to bottom or bottom to top the first panel is aligned to >> bottom/top side of the panel automatically. > > Hi, > > Actually, I just through of a possible issue with children assigned > alignment. For the parent panel, there is a halign property, For > example, if parent width is 50, each child's width is 10, there are > three halign values: > > halign =3D right > b1 =C2=A0b2 =C2=A0b3 =C2=A0empty > 10 =C2=A010 =C2=A010 =C2=A020 > > halign =3D center > b1 =C2=A0empty b2 =C2=A0empty =C2=A0b3 > 10 =C2=A0 =C2=A010 =C2=A0 =C2=A010 =C2=A0 =C2=A0 10 =C2=A0 =C2=A0 10 This can be done with b1 hspace b2 hspace b3 20% 20% 20% 20% 20% but why would you want such spacing? Normally you would want the panels take up most space possibly with some small spacing or the outer panel shrink around the inner panels. > > halign =3D right Perhaps use direction? Why do you want the empty space there? There are infinite possibilities of alignment so we should choose an alignment method that allows for commonly used alignments and perhaps some less common but useful, not all alignments that somebody can possibly think of. > empty b1 =C2=A0b2 =C2=A0b3 > 20 =C2=A0 =C2=A0 =C2=A010 =C2=A010 =C2=A0 10 > > halign is obviously not belonged to children, so you might write it as: > > panel{ > =C2=A0direction =3D left_to_right > =C2=A0halign =3D center > =C2=A0panel{ id =3D"bb" ;valign =3D center} > =C2=A0panel{ id =3D"bb" ; valign =3D top} > =C2=A0panel{ id =3D"bb" ; valign =3D bottom} > =C2=A0} > } > > But then there is problem, as panel can be children as well, for example: > > panel { > =C2=A0id =3D "top" > =C2=A0direction =3D top_to_bottom > > panel{ > =C2=A0id =3D "aa" > =C2=A0direction =3D left_to_right > =C2=A0halign =3D center > =C2=A0panel{ id =3D"bb" ;valign =3D center} > =C2=A0panel{ id =3D"bb" ; valign =3D top} > =C2=A0panel{ id =3D"bb" ; valign =3D bottom} > =C2=A0} > } > } > > In this case, should halign of aa be used to control its own alignment > from top, or that of its children ? It should be used to align itself, obviously as you want to control the alignment of each child separately and if halign =3D center was applied to all this would not be possible. Thanks Michal