From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 31 Aug 2009 07:28:53 +0200 From: Andrew Lunn Message-ID: <20090831052853.GQ16067@lunn.ch> References: <20090830013647.GA26017@Linus-Debian> <20090830195553.GA2410@pandem0nium> <20090830214719.GA3905@Linus-Debian> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090830214719.GA3905@Linus-Debian> Subject: Re: [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking Hi Linus, Simon One of the things on the TODO list for mainline is to strip out all the graphvis/JSON formatting done by the kernel and put it into user space, probably batctl, or another standalone tool, or maybe even a little library... Why: 1) No other file in /proc does any special formatting. 2) What happens when one tool wants graphvis and another JSON, at the same time? 3) What happens when you want a third, forth, fifth format etc... Are either of you interested on working on this? I guess the first step is to design a file format for vis in proc. I would suggest space separated values. Maybe one line per vis_into_entry? I would also suggest the quality value is 0-255, not a real number. User space, which has float support, can then turn it into a float if need be. Andrew