Hello SimonN,
php5 is not properly supprting type definitions of parameters, so better put that out
I found a bug in the parameter template for this that meant no space was generated between the hint and the name. This should be fixed for the next release. Is this what you were talking about? Hinting is in the spec. See http://ch2.php.net/language.oop5.typehinting. I didnt realized, that they really fixed type hinting in the last release. This feature was quite bug in earlier releases. So i deleted the parameter, instead of inserting a space. But i think this is great, as you did.
With the datatypes :
There is absolutely no standard for this, as it has been done manually by the developer in templates and there are NO RE tools. So i think, there should be no complaining, if you just decide to use on of these, and MAYBE can give an option. I think everyone is able to do a replace it in all files, if used another name.
The best solution is to make it configurable in the templates. Everyone is able to find tha "if == "@type" and change it as needed. When more and more people generating code with your app, the will keep that. And thats how standard made in common.
I think, there will be no one who set this standard until RE is widely used, so just keep that open.
If you wish to have types generated in the notes, you can modify the templates. With just a few small template modifications you could make EA generate types into your notes, and then you can model complete with types in EA.If i let generating the notes, he is somehow repeating the hole class definition every sync. So its then 3/4 time in the file. I`ve studied the documentation, but for me, it was not that crystal clear, why this happens. I could fix the other two bugs, but i just cannot do this, sorry. Maybe you could help.
The only thing you won't be able to do is reverse engineer. The current behaviour to override the type is because the reverse process is specifying a type (even if it is var) and in general when reverse engineering, the values specified in code should overwrite the values in the model. (Otherwise it wouldn't be much use) Lets devide this in two parts. If there is NO chance to include, that the PHPdoc defintion can be used for setting the type in the model, there should be just no changes be done on the model when synchronising. Cause if you sync, ANY datatypes are switched to "var". This makes the reverse-engeneering completely useless. Using your software just because of generating code, will not be in minds of people, which can get tools as Umbrello / ArgoUML for doing that, and they are for free.
So in conclusion, you just should take care of, that the datatype defintions of the model are NOT changed on sync,
never or you include setting them by reading out PHPdoc. The last part would be a absolety highlight, the first part is absolutely essential for even use your programm for developing PHP-Applications.
After all that "complaining" i want to add, that iam not angry or trying to do some presure over to the developers. Iam glad that you even have support in the forum, which tryies to react on the wishes/discussions of the people. Thats just great and iam getting closer and closer to buy your product. The second thing is, that you just had a great, needed, idea with include RE for PHP, and its nearly done. But this last steps are absoletly essential that developer choose your software for PHP-developing. And there are a lot waiting...
Best regards
E.Mayer