Taras,
On Thu, May 6, 2010 at 5:43 PM, Taras wrote:
> Hi, all!
>
> I started W3AF Developers Guide [0]. Now it is in 90% copy of
> PEP8 (Style Guide for Python Code).
> Guide always contains Plugins and Packaging W3AF sections.
Thanks for a good start, we needed this. Something I would do is
Hi, all!
I started W3AF Developers Guide [0]. Now it is in 90% copy of
PEP8 (Style Guide for Python Code).
Guide always contains Plugins and Packaging W3AF sections.
Let's discuss and approve naming conventions for new code.
I suggest:
- CamelCase for class names (current state as I see is mixe
List,
On Tue, Dec 23, 2008 at 7:14 PM, Steve Pinkham wrote:
> Taras P. Ivashchenko wrote:
>> Hello, list!
>>
>> Now W3AF is not small project. As I know at the moment we already have
>> user's guide
>> but may be it's time to begin some dev docs (in what format?)? =)
>> Of course it's not so pri
Taras P. Ivashchenko wrote:
> Hello, list!
>
> Now W3AF is not small project. As I know at the moment we already have user's
> guide
> but may be it's time to begin some dev docs (in what format?)? =)
> Of course it's not so priority as developing new features anf fixing bugs.
> For the first we
2008/12/23 Taras P. Ivashchenko
> Hello, list!
>
> Now W3AF is not small project. As I know at the moment we already have
> user's guide
> but may be it's time to begin some dev docs (in what format?)? =)
> Of course it's not so priority as developing new features anf fixing bugs.
> For the first
Hello, list!
Now W3AF is not small project. As I know at the moment we already have user's
guide
but may be it's time to begin some dev docs (in what format?)? =)
Of course it's not so priority as developing new features anf fixing bugs.
For the first we can approve some code convention and clas
