X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from ncopa-desktop.alpinelinux.org (3.203.202.84.customer.cdi.no [84.202.203.3]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nc@alpinelinux.org) by mail.alpinelinux.org (Postfix) with ESMTPSA id 2A51ADC00D4; Thu, 29 Nov 2012 14:23:20 +0000 (UTC) Date: Thu, 29 Nov 2012 15:23:17 +0100 From: Natanael Copa To: Alpine ACF , Alpine Developers Subject: [alpine-devel] Ideas for a new config framework, ACF2 Message-ID: <20121129152317.69585a4f@ncopa-desktop.alpinelinux.org> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.13; x86_64-unknown-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, Me and Kaarle have been playing with the idea "what if we started with ACF from scratch today, how would it be?". We collected some ideas and have now come up with a fairly detailed plan for an ACF2. Some of the goals: * better security design * remove unnecessary complexity from modules * organize the libs better * fix concurrency - no race conditions * improve CLI interface * modernize web GUI (write the gui in javascript) For web frontend we have been talking of using existing frameworks like Backbone.js and RequireJS. For backend we have been talking about using things like augeas and using Lua tables to create data models. Kaarle has written are more detailed plan: http://www.datakunkku.fi/acf/ This will require some massive work but I think we can do it. Hopefully it will be simpler to write models once the basic framework is in place. What do you think? -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---