On 11/10/10 03:43 PM, Drew Fisher wrote:
On 11/10/10 4:36 PM, Shawn Walker wrote:
On 11/10/10 03:31 PM, Alok Aggarwal wrote:
On Wed, 10 Nov 2010, Dave Miner wrote:
On 11/ 8/10 06:14 PM, Alok Aggarwal wrote:
Hi Karen,
On Mon, 8 Nov 2010, Karen Tung wrote:
When I was talking to Alok last Friday on the phone about these 2
comments,
he mentioned that he is going to add the ssh entry and the 2
accessibility
entries into the Live CD's manifest. From your response above, it is
not
clear to me whether you added them to the manifest or to the code.
Can you elaborate?
They'll be added to the code so as to ensure
that the two accessibility entries are always
the last ones in the menu.lst.
Adding them to the manifest makes it harder to
ensure that they're always the last entries
specified.
This does seem to point to a potential deficiency in not being able to
specify positions of entries. Perhaps an RFE to allow this in the
manifest is in order?
The code does honor the "position" attribute for
a grub_entry, today.
But I think Karen's point is that no matter what
position is specified for a given grub entry, the
accessibility entries must be the last ones (probably
some A11Y requirement?). It seems that the only sure
fire way to ensure that is by embedding the accessibility
entries into the code.
Why not allow negative position numbers so they always stay last
relative to other entries?
-Shawn
Technically, we do. The python code behind the grub_setup.py checkpoint
would fully allow negative numbers. The problem is that negative values
as a position variable for people not necessarily versed in python
development may not understand what a negative value means without a lot
of extraneous comments in the manifest.
Wouldn't extraneous comments in the manifest be preferable to
hard-coding handling of accessibility entries?
-Shawn
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
