phil

@Xavier Thanks for the tip! Maybe you could add it to the documentation.

@Cédric Same here! I’m not convinced by the default ruleset but as I say, the possibility of defining custom rules is one of the greatest key of this project.
I can see with FlexPMD some great opportunities. Ex: Define a ruleset to encourage good practises with a framework. At this time, AS3 language features can’t totally secure developers from using bad practises to work with an architecture. FlexPMD with an intelligent ruleset and some comprehensive warnings could be one key to lead them along their learning curve. Last but not least, warnings and inconsitencies detections inside the framework could be less verbose and resulted binaries should be more optimized (with less statements to detect developers pitfalls).

Sur la doc il y a une petite erreur :

c’est 1.0.RC3 sinon il trouve pas les fichiers

Sinon le projet est bien sympa !

I just tested FlexPMD as well, it’s really promising thanks to the ruleset creator.

However I really doubt some of the « good practices » they try to taught us. Such as the clone method on events : Why locking dispatched events in the first place ?
Or concerning the use of the * type : Why not providing generics or covariant typing to ensure strong typing and flexibility ?

Now, with a more pertinent ruleset I think it could be really useful :)

About the ruleset, if you don’t specify any ruleset, the default will be loaded.

Xavier

Now we need a Flex integration to get a report in the Problems Report window to have « go to line » support etc… :) Hope that Adobe planned to work on this.