[ previous ] [ next ] [ threads ]
 
 From:  Adam Nellemann <adam at nellemann dot nu>
 To:  Manuel Kasper <mk at neon1 dot net>
 Cc:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Beta 1.1b10
 Date:  Sun, 30 May 2004 06:02:34 +0200
Manuel Kasper wrote:
> Changes since 1.1b9:
> 
> - upgraded base system to FreeBSD 4.10
> 
> - added Wake on LAN client
> 
> - webGUI error page no longer shows the name "m0n0wall"
> 
> - shaper rules can now be temporarily enabled/disabled too
> 
> - filter and shaper rules enable/disable status may be toggled by
> clicking the action/direction icon
> 
> - updated MPD to 3.18

Great work Manuel, you really are on a coding spree at the moment, 
aren't you, I can hardly keep up with all these betas (but that's how 
I like it!)

VERY nice with the click-to-toggle feature for the firewall/shaper rules!

I'm looking forward to test the WOL feature as soon as my new WOL 
capable hardware has been installed...


A few (very minor and primarily cosmetic) issues:

- The disabled color of block rules look VERY similar to the (enabled) 
color of reject rules. Perhaps making all the disabled rules a bit 
more "transparent" (lighter) would help (and also help distinguish 
enabled and disabled rules more easily).

- I've recently disabled (un-assigned) my wireless card (in preference 
of an AP on the LAN), but I still see a "Wireless" entry in the 
"Status" section. It would be nice if this was only shown when needed 
(like the "Captive Portal" entry in the same section).

- In the last couple of betas (don't remember when I first noticed 
it?) there has been only two CPU load numbers on the "Status/System" 
page, is this intentional?

- I've noticed that you use POST in (some of?) your form submits. 
While I'm aware that there are some advantages to this, it would be 
somewhat simpler when scripting changes to the m0n0wall configuration 
if GET submits could be used instead. That is if there aren't a good 
reason for your choice of POST?

- It is still quite cumbersome to move rules up and down as typically 
you need to move several rules several positions, which takes forever 
(in fact sometimes I actually find it quicker to download the 
config.xml, cut'n'paste the rules and then upload it again!) While not 
of great importance, it is something which most users will be bothered 
by from time to time (to a greater or lesser extent depending on their 
m0n0wall usage, of course).

Perhaps, instead of the up/down buttons, a "move" button could be 
shown. When one of these are clicked, the page would reload with a 
"here" button beside all entries but the one just clicked (optionally 
the "move" buttons could still be shown, allowing several rules to be 
selected for movement). When one of these "here" buttons are clicked, 
the "moving" rule(s) would be placed just above (below?) its rule.

While this would require two clicks (and reloads) when moving a rule 
just one position, as opposed to one click now, any other kind of move 
would also require only two clicks (and reloads), as opposed the large 
number of clicks currently required.


Well, as I said, not very important things, but to some extent it is 
the small details that makes m0n0wall the great piece of software it is ;)


Adam.