SecureFormSwitcher

[serechai99]

Are you sure you wish to enable notification of new replies for this topic

[Argos]

An instruction manual is planned, but it needs a little time.

Great!

About the Lower-/Upercase naming:
we startet this with view to the future. So we adapt a big part of the original Zend-Coding-Standards for the 2.9.

Actually I was talking not about class or file names, but directory/folder names. All folder names in WB are lower case, so the new capitalized folder name stands out. Maybe it's totally silly and unimportant, but I just don't like the look of it and like I said I believe I remember that it could cause problems sometimes. I'm not sure about that though.

[DarkViper]

An instruction manual is planned, but it needs a little time. (unfortunately our days also have 24 hours only)

About the Lower-/Upercase naming:
we startet this with view to the future. So we adapt a big part of the original Zend-Coding-Standards for the 2.9.

Class names may only contain alphanumeric characters. Numbers are permitted in class names but are discouraged in most cases. Underscores are only permitted in place of the path separator; the filename "Zend/Db/Table.php" must map to the class name "Zend_Db_Table".

If a class name is comprised of more than one word, the first letter of each new word must be capitalized. Successive capitalized letters are not allowed, e.g. a class "Zend_PDF" is not allowed while "Zend_Pdf" is acceptable.

Zend Naming Conventions

[Argos]

I had a look at the new SecureFormSwitcher in the backend, and while I applaude the fact that it's there, I think the support info is way too technical and way to little. Only hardcore coders will have a clue what it's all about. It really needs some support info for ordinary users. I really don't understand most of it.

I also think the directoryname should be in lowercase only. Using uppercase letters in module directoy names look bad. It also can cause problems on some servers I believe.