Hi, all! Now, in plugin list we can see such list:
- afd - allowedMethods - archiveDotOrg - bing_spider - content_negotiation ... We can see 2 different naming styles here. Also in code we can see the same: some methods called as foo_action_ff() and some in camelcase convention. As I think it's of course not so important as other bugs in w3af but also not good =) What I suggest is to start writting "W3AF Dev Guide" and follow it. It also will help new developers of w3af and w3af plugins to start quickly. I can prepare lite draft version. What do you think about it? On Sun, 28 Mar 2010 17:27:25 +0000 andresrian...@users.sourceforge.net wrote: > Revision: 3439 > http://w3af.svn.sourceforge.net/w3af/?rev=3439&view=rev > Author: andresriancho > Date: 2010-03-28 17:27:24 +0000 (Sun, 28 Mar 2010) > > Log Message: > ----------- > Changing the name of the plugin a little bit. Two reasons: > - BingSpider started with a capital letter, this "breaks" the > A-Z order in pyGTK and shows it at the top > - I'm trying to start naming all variables and plugins with > lowercase and underscore. > > Modified Paths: > -------------- > trunk/profiles/OWASP_TOP10.pw3af > trunk/scripts/script-bing_spider.w3af > > Added Paths: > ----------- > trunk/bing_spider.py > > Removed Paths: > ------------- > trunk/plugins/discovery/BingSpider.py ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
