From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [IPv6:2a01:4f8:200:3141::101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 1BF8421F1D6 for ; Sat, 22 Mar 2014 12:36:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at example.com Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 05ABE1BDC7; Sat, 22 Mar 2014 20:36:39 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toke.dk; s=201310; t=1395516999; bh=jHf7jEJzjZpipPA+rx1fpOgufGWXVGPrFHmAiyoiG7w=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=bJHpIVaGIccxqHn3/eR5q7HrrVDTfOsLzT43rHdXocLh/7khjR9UhfD2w/LqdfD+R 4YQq6NZsNn9mWDSh5WAs9J5ELlWK/w93ubXN5ulbmXRq+qGJTmKlWj3QyyDi6NK84Q HURxmxTRS+wWq01wV5zlCpM50YBeDUbseVWqlnC0= From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Sebastian Moeller References: <3F98D180-3AF8-4AFA-80B4-A13E55CAA03A@gmx.de> <87mwgjtb8z.fsf@alrua-x1.karlstad.toke.dk> <7F1EA8E6-0C2E-471D-A24F-8D08A10998FC@gmx.de> <87ior7t9ov.fsf@alrua-x1.karlstad.toke.dk> <608F3E46-3D81-48A3-B60C-E90661DD3AB2@gmx.de> <87eh1utrqu.fsf@alrua-x1.karlstad.toke.dk> <6D237658-E6E9-4985-AAFD-8A87256E1D77@gmx.de> Date: Sat, 22 Mar 2014 20:36:37 +0100 In-Reply-To: <6D237658-E6E9-4985-AAFD-8A87256E1D77@gmx.de> (Sebastian Moeller's message of "Sat, 22 Mar 2014 20:23:59 +0100") Message-ID: <8738iat48q.fsf@alrua-x1.karlstad.toke.dk> Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-12 released X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Mar 2014 19:36:47 -0000 --=-=-= Content-Type: text/plain Sebastian Moeller writes: > I thought a bit about this, and I think there might be a way to use > the available widgets in a way that emulates consistency ;) (well at > least in theory) If the first entry would not hog the singleton entry > field with the add button, but would spawn a new empty field with an > add button, while the just entered (and saved & applied) entry would > be followed by the delete button, he whole thing would be consistent > enough to not confuse the user. I will see whether I can implement > that in the luci code. Cool; FWIW, I think it's the javascript you need to look at :) -Toke --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCAAGBQJTLeZFAAoJEENeEGz1+utPCWUH/AmirqrgJdeFUVdzEfhrb962 FspoTbaiJGvSsRWIFkuaD0AgU3nQ1rr4H3EmiV7g/h7eaAK438g9HqYMUMaJlc6X ZBhZWXijAHDAhCae50TfEUbeG0pq2ntN6cObbNhBHkFvFVrFVgm6GPfYxxTqQgKW E6KUigdXJZgj3UWqZIxR40N53IYt775Hr8lSG5ZVhL06GrrBsGsLFxz52ggE2+VO AjXijbk/by+MesSdKp5wMIImb40vpyVjY1FIve1CnSOtQ5G0fg3ZusL/uhiU11JJ YBx4g3qydl2JVp1hn/bbWMfgJ1+VgqLe3bn7uLTBwVKXrVzv8DbUrSYXGOa/HlY= =3O94 -----END PGP SIGNATURE----- --=-=-=--