From owner-freebsd-arch@FreeBSD.ORG Sun Oct 7 20:49:30 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4879B1065687; Sun, 7 Oct 2012 20:49:30 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0AE0E8FC12; Sun, 7 Oct 2012 20:49:28 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so3823044pbb.13 for ; Sun, 07 Oct 2012 13:49:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=krORJAlJvVYIxvy0l2cZ/t4z/GXf7pP7PuqkNDifWaY=; b=J927MNEPZlSyKwdRt5nhZNyWk680kmtCNnwQmohKidzoRQT/nYZKxThuzp3Uc1QLrE EOEHlkNfUWXRYeR2Zs1uWaLsInMsUQzvdDtnvzugHOozEZtNzVW9VX+Ret7fA6OnARj8 cJBLs1CIaACjwwtKcEwmJVZ7AuCja0WXwNgNxxr7Qm+fS7gbvRzlMMtm/vOLf3rDA+Po o3WztUI8ykV1HbI0/5KM1EwEHBoLbqOs1kbfCL7EG83hji1EVV8JpQmEf4RPGUnof13Q lpn1HIq3ya0ebkUPEB8PQvW8DdtETGET07FfVPufaG+xoGk1Td2OszX2nmwsEB3hRO7V dUgA== Received: by 10.68.132.40 with SMTP id or8mr32610221pbb.63.1349642968079; Sun, 07 Oct 2012 13:49:28 -0700 (PDT) Received: from fuji-wireless.local (c-24-19-191-56.hsd1.wa.comcast.net. [24.19.191.56]) by mx.google.com with ESMTPS id vi9sm9545853pbc.41.2012.10.07.13.49.25 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 07 Oct 2012 13:49:27 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1283) From: Garrett Cooper In-Reply-To: <0CB9F1EA-2176-4AE9-B899-6E8744D06DC7@fisglobal.com> Date: Sun, 7 Oct 2012 13:50:12 -0700 Message-Id: References: <0655B56F-AD43-402B-872C-568378E650F9@fisglobal.com> <86k3v21qsx.fsf@ds4.des.no> <3EB58454-7820-43C4-911E-7DEF2D02C880@fisglobal.com> <86fw5q15f9.fsf@ds4.des.no> <0CB9F1EA-2176-4AE9-B899-6E8744D06DC7@fisglobal.com> To: Devin Teske X-Mailer: Apple Mail (2.1283) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , freebsd-arch@freebsd.org Subject: Re: New Boot Loader Menu X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 20:49:30 -0000 On Oct 7, 2012, at 1:36 PM, Devin Teske wrote: > On Oct 7, 2012, at 12:52 PM, Garrett Cooper wrote: >=20 >> - Have you considered high resolution screens/fonts; there are some = already in FreeBSD hooked into syscons, but that's available later on at = boot? I mention this because there's a lot of wasted real estate on my = 30" or 24" LCDs when I boot up FreeBSD. >=20 > Adding screen real-estate won't help. Menus (and any of the maximum = 65535 submenus) are always limited to 9 maximum menu items. >=20 > A significant overhaul of the Forth code would be required to = accommodate more than 9 menu items per-menu. >=20 > Currently, if a 10th menuitem were rendered (assuming I lifted the = boundary-checks), it would be rendered as such: >=20 > =85 > 8. Eighth Item > 9. Ninth Item > 1. Tenth item > =85 >=20 > Worse, you press "8" to invoke the 8th item, "9" to invoke the 9th = item, but ":" to invoke the 10th item (wait, what?) >=20 > Yes, ":" to invoke the 10th item. Because currently ASCII keycodes are = used to associate menu items. The next character after "9" is ":". :(=85 Understood. >> I'd like to see sketches or a general idea of what you have in mind = before investing too much time in a direction that doesn't bear a lot of = fruit. I'm sure others here agree. >=20 > Sorry, but I'm the infrastructure guy. I provide the framework. I'll = leave it to the community to decide how to use that framework. I'm = leaving it in jpaetzel's, avg's, and mav's very capable hands to utilize = my framework in whatever way they see fit. >=20 > They came to me with a need. I filled that need. If the community = doesn't want it, I'll just dump it into DruidBSD and use it there until = someone wants it. Ok. I wasn't aware of the language constraints with Forth (I've dabbled = very briefly in it, but I am by no means even a novice), and now I = better understand some of the issues you're facing. Thanks for the explanation! I'll try to be more less critical next time. -Garrett=