>> It would be nice, if some people (Doug??))), would pick some part of >> the GUI and expand it, so that fewer questions arise. Just copy that >> part and send me the expanded part. >> Thanks. > > Who? Me? > > I'll see what I can do. :o)
Being a rather new to ASSP, I will take a look at the interface as well and point out where I find/found it unclear. Maybe someone else will be able to pick up on the thread afterwards for additional clarification. Overall, however, I have to say that in general, I didn't find the descriptions confusing, as much as I found I was missing a document / instructions that explain how everything ties together. On its own, each description was rather clear, once you understood what the general concept of the parameter was for. An immediate example I can think of is something like the red list. The descriptions for the different redlists options are clear, but the whole concept of the redlist is/was still a bit hazy, and thus I needed some clarification (I'm still a bit grey on it, but I have a better understanding at the moment). I think either building a more complete FAQ, or even better some form of a flowchart (I know this is going to be very complex) that explains the processing might be more helpful. I think a flowchart existed in the original ASSP doc pages, but isn't complete based on today's featureset. The other thing that I think can be extremely useful to newcomers (again, like myself), would be an example set of real-world values for the config files. I know Fritz was kind enough to provide a whole bunch of screen shots a month back or so when I had asked (thank you so much), but if we could take that kind of information and provide it either in the ASSP package itself, or as a startup-example-config package, that might go a long way. Especially for people who - a) don't know what settings are "good" settings, b) who are rusty with regexs, etc. Finally, something else that would be great (long term again), would be an ability to share / communicate with others the lists/regexs that people use for blacklists, no-delaylists, spam/script-bombs, etc.. Given that those are lists that need to be kept up-to-date, etc, a way to communally share them would probably be useful. Those are a few thoughts off the top of my head as to what would make the learning curve easier. Gimme a couple of days and I'll go through it as well, and post back my comments/thoughts here. Thanks, Eric _________________________________________________________________ Download now! Visit http://www.telusmobility.com/msnxbox/ to enter and see how cool it is to get Messenger with you on your cell phone. http://www.telusmobility.com/msnxbox/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
