public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Harvey <chris@basementcode.com>
To: gentoo-soc@lists.gentoo.org, Luis Araujo <araujo@gentoo.org>
Subject: [gentoo-soc] ventoo weekly report
Date: Mon, 02 Aug 2010 01:54:39 -0400	[thread overview]
Message-ID: <4C565D9F.2090409@basementcode.com> (raw)

This week I added a system to ventoo that highlights parts of a file 
when ventoo thinks they are invalid and should not be saved back into 
the file. The code that does the checking are external python scripts 
that users can easily add to ventoo without changing any other code. The 
reason this was added is that up until now as the user is editing a file 
he/she had no idea if the file was valid until a diff or a save was 
requested. Now SOME (or even most) errors can be caught with a python 
script that validates user input in the background. Even nicer is that 
well written scripts can catch errors that augeas can't. (augeas is the 
library I use to move the files in and out of memory and manipulate the 
file structure) For example, if the user enters /dev/sdf12, but that 
device doesn't exist, the cell lights up bright red. The user can still 
save, so it's really only a warning. Warnings like this can typically be 
checked in about 2-4 lines of python. Augeas already did a pretty good 
job of catching a lot of invalid config files, but this system makes it 
easier for the user and can catch errors that augeas wasn't designed to 
catch.

Next week:
Remote editing of other computers.



             reply	other threads:[~2010-08-02  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02  5:54 Christopher Harvey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-07-27  1:56 [gentoo-soc] Council Webapp Progress Report Wei Xie
2010-07-27  3:33 ` [gentoo-soc] ventoo weekly report Christopher Harvey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C565D9F.2090409@basementcode.com \
    --to=chris@basementcode.com \
    --cc=araujo@gentoo.org \
    --cc=gentoo-soc@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox