Turning som FIXMEs into one-liners.

git-svn-id: https://svn.code.sf.net/p/squirrelmail/code/trunk/squirrelmail@13867 7612ce4b-ef26-0410-bec9-ea0150e637f0

diff --git a/templates/default/read_menubar_buttons.tpl b/templates/default/read_menubar_buttons.tpl
index 7ea9a13ac0bafae5af8096e0c4a057922cc188c7..d2e51f4f980ccfc4bb9973914925c8e0323aa24f 100644 (file)
--- a/templates/default/read_menubar_buttons.tpl
+++ b/templates/default/read_menubar_buttons.tpl
@@ -62,16 +62,7 @@
 /** extract template variables **/
 extract($t);
 
-/*FIXME: This is a place where Marc's idea for putting all the buttons and 
-         links and other widgets into an array is sorely needed instead of
-         hard-coding everything.  Whomever implements that, PLEASE, PLEASE
-         look at how the preview pane plugin code is used in this same template
-         file for the *default_advanced* set to change some links and buttons 
-         and make sure your implementation can support it (tip: it may or may 
-         not be OK to let a plugin do the modification of the widgets, since 
-         a template set can turn on the needed plugin, but that might not be 
-         the most clear way to solve said issue).*/
-
+/*FIXME: This is a place where Marc's idea for putting all the buttons and links and other widgets into an array is sorely needed instead of hard-coding everything.  Whomever implements that, PLEASE, PLEASE look at how the preview pane plugin code is used in this same template file for the *default_advanced* set to change some links and buttons and make sure your implementation can support it (tip: it may or may not be OK to let a plugin do the modification of the widgets, since a template set can turn on the needed plugin, but that might not be the most clear way to solve said issue).*/
 
 /** Begin template **/
 if ($nav_on_top) {

diff --git a/templates/default/read_menubar_nav.tpl b/templates/default/read_menubar_nav.tpl
index 80f5f98e6f27355a6471398bef4bb00887706a5e..87d73f92ce45ede4dd705d7af1846503b60f958f 100644 (file)
--- a/templates/default/read_menubar_nav.tpl
+++ b/templates/default/read_menubar_nav.tpl
@@ -49,16 +49,7 @@
 /** extract template variables **/
 extract($t);
 
-/*FIXME: This is a place where Marc's idea for putting all the buttons and
-         links and other widgets into an array is sorely needed instead of
-         hard-coding everything.  Whomever implements that, PLEASE, PLEASE
-         look at how the preview pane plugin code is used in this same template 
-         file for the *default_advanced* set to change some links and buttons 
-         and make sure your implementation can support it (tip: it may or may 
-         not be OK to let a plugin do the modification of the widgets, since 
-         a template set can turn on the needed plugin, but that might not be 
-         the most clear way to solve said issue).*/
-
+/*FIXME: This is a place where Marc's idea for putting all the buttons and links and other widgets into an array is sorely needed instead of hard-coding everything.  Whomever implements that, PLEASE, PLEASE look at how the preview pane plugin code is used in this same template file for the *default_advanced* set to change some links and buttons and make sure your implementation can support it (tip: it may or may not be OK to let a plugin do the modification of the widgets, since a template set can turn on the needed plugin, but that might not be the most clear way to solve said issue).*/
 
 /** Begin template **/
 

diff --git a/templates/default_advanced/read_menubar_buttons.tpl b/templates/default_advanced/read_menubar_buttons.tpl
index 68b1cba08af92ba0230466aec2e3bf9b7498de3f..f8ab8b7d22d7bc6be183e3cb63e935f65bd047ed 100644 (file)
--- a/templates/default_advanced/read_menubar_buttons.tpl
+++ b/templates/default_advanced/read_menubar_buttons.tpl
@@ -63,15 +63,7 @@
 extract($t);
 
 
-/*FIXME: This is a place where Marc's idea for putting all the buttons and 
-         links and other widgets into an array is sorely needed instead of
-         hard-coding everything.  Whomever implements that, PLEASE, PLEASE
-         look at how the preview pane plugin code is used here to change
-         some links and buttons and make sure your implementation can support
-         it (tip: it may or may not be OK to let a plugin do the modification
-         of the widgets, since a template set can turn on the needed plugin,
-         but that might not be the most clear way to solve said issue).*/
-
+/*FIXME: This is a place where Marc's idea for putting all the buttons and links and other widgets into an array is sorely needed instead of hard-coding everything.  Whomever implements that, PLEASE, PLEASE look at how the preview pane plugin code is used here to change some links and buttons and make sure your implementation can support it (tip: it may or may not be OK to let a plugin do the modification of the widgets, since a template set can turn on the needed plugin, but that might not be the most clear way to solve said issue).*/
 
 /** preview pane prep */
 global $data_dir, $username, $base_uri;

diff --git a/templates/default_advanced/read_menubar_nav.tpl b/templates/default_advanced/read_menubar_nav.tpl
index 3ad5fb98ce50ab088a02cc4f84f405f23245ee1a..ca6a4267039256f07f71744a3d1b493e7c53e6f7 100644 (file)
--- a/templates/default_advanced/read_menubar_nav.tpl
+++ b/templates/default_advanced/read_menubar_nav.tpl
@@ -50,15 +50,7 @@
 extract($t);
 
 
-/*FIXME: This is a place where Marc's idea for putting all the buttons and 
-         links and other widgets into an array is sorely needed instead of
-         hard-coding everything.  Whomever implements that, PLEASE, PLEASE
-         look at how the preview pane plugin code is used here to change
-         some links and buttons and make sure your implementation can support
-         it (tip: it may or may not be OK to let a plugin do the modification
-         of the widgets, since a template set can turn on the needed plugin,
-         but that might not be the most clear way to solve said issue).*/
-
+/*FIXME: This is a place where Marc's idea for putting all the buttons and links and other widgets into an array is sorely needed instead of hard-coding everything.  Whomever implements that, PLEASE, PLEASE look at how the preview pane plugin code is used here to change some links and buttons and make sure your implementation can support it (tip: it may or may not be OK to let a plugin do the modification of the widgets, since a template set can turn on the needed plugin, but that might not be the most clear way to solve said issue).*/
 
 /** preview pane prep */
 global $data_dir, $username, $base_uri;