From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <moeller0@gmx.de>
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(Client CN "mout.gmx.net",
	Issuer "TeleSec ServerPass DE-1" (verified OK))
	by huchra.bufferbloat.net (Postfix) with ESMTPS id 29B4A21F1C7
	for <cerowrt-devel@lists.bufferbloat.net>;
	Sat, 22 Mar 2014 13:24:39 -0700 (PDT)
Received: from hms-beagle.home.lan ([84.172.116.169]) by mail.gmx.com
	(mrgmx003) with ESMTPSA (Nemesis) id 0MSutp-1WYmcT3IXt-00RrQi;
	Sat, 22 Mar 2014 21:24:36 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <8738iat48q.fsf@alrua-x1.karlstad.toke.dk>
Date: Sat, 22 Mar 2014 21:24:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <77DEDFA5-7908-491F-BF45-84F404C6194A@gmx.de>
References: <CAA93jw6Y3V29Ynk+2DE+5RrPzSe7X6WeoJK9CcPAHPTRUBsCdQ@mail.gmail.com>
	<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>
	<8738iat48q.fsf@alrua-x1.karlstad.toke.dk>
To: =?windows-1252?Q?Toke_H=F8iland-J=F8rgensen?= <toke@toke.dk>
X-Mailer: Apple Mail (2.1510)
X-Provags-ID: V03:K0:AYog1wkNw8r+dRoUTG283KFDALPUXcRVuJTz+TDl/LRlE8r4ZZn
	jEpPVjBT533nKVPwSOYvt/ESkDhJ1Rm+qS9KwDExL2ykl2lyEyhbTvwn84Gqcwom2THPhvQ
	2PRK4QPQSQYb9jzj/E1m2eMddOdZpS/yAIdRqg0z1SGu76mZWSh0lBtzMH6Ittt2CMR4n9j
	LkwTr+Ez4ERiKzv0aDK4Q==
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
	<cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Sat, 22 Mar 2014 20:24:40 -0000

Hi Toke,


On Mar 22, 2014, at 20:36 , Toke H=F8iland-J=F8rgensen <toke@toke.dk> =
wrote:

> Sebastian Moeller <moeller0@gmx.de> writes:
>=20
>> 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.
>=20
> Cool; FWIW, I think it's the javascript you need to look at :)

	I hope to avoid that, I have zero contact with javascript so far =
and if I can avoid the learning curve I happily do so ;) But eta see =
whether I can fake it in luci/lua=85

Best Regards
	Sebastian

>=20
> -Toke