From 1db5affc8396e741adb1445a7ee6cd577b20224a Mon Sep 17 00:00:00 2001 From: Moc Date: Tue, 27 Nov 2012 15:35:45 -0800 Subject: [PATCH] Updated e107 Coding Standard (markdown) --- e107-Coding-Standard.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/e107-Coding-Standard.md b/e107-Coding-Standard.md index d0fa66e..51221d0 100644 --- a/e107-Coding-Standard.md +++ b/e107-Coding-Standard.md @@ -76,7 +76,8 @@ Always use e107's form handler for form elements in the front-end. $frm = e107::getForm(); $frm->select($name,$value); $frm->checkbox($name,$value,$checked); - $frm->selectbox($name,$array,$currentValue); // full SELECT tag with OPTIONs. + $frm->selectbox($name,$array,$currentValue); // full SELECT tag with OPTIONs. + $frm->admin_button($name, $value, $action, $label); ### Globals Avoid the use of global variables, especially as an alternative to parameter passing. (We'll always need some globals - but the less there are, the smaller the chance of a clash). In v2.0 use the e107::getxxx syntax to get pointers to 'global' functions and objects like $sql, $tp @@ -343,4 +344,4 @@ Note and use the class-based structure introduced in v2.0 - with this it should Parameter standards (see eHelper::scParams() and eHelper::scDualParams() ) ## Recommended Code Editors -We recommend [Aptana Studio](http://www.aptana.com/products/studio3) as an editor. We may release e107-specific code-assistance in future. +We recommend [Aptana Studio](http://www.aptana.com/products/studio3) as an editor. We may release e107-specific code-assistance in future. \ No newline at end of file