HTML布局技术（用于管理面板）-HTMLlayouttechniques(foradminpanel)

0  

Well, it seems to me that having a hundred pages with PrintMenu() is a good thing, in that you only need to change the content of that function to update the look of hundreds of pages, at least as long as you are sure that all pages use the menu. Now maybe if you passed an argument, let's say an array (so that you can update its properties later on) which contains for instance the page characteristics, then this would make a more flexible model. Or you could pass an object too if you so wanted.

好吧,在我看来,使用PrintMenu()有一百页是一件好事,因为你只需要更改该函数的内容来更新数百页的外观,至少只要你确定所有页面都使用菜单。现在也许如果你传递一个参数,让我们说一个数组(以便你以后可以更新它的属性),其中包含例如页面特征,那么这将使一个更灵活的模型。或者,如果你愿意,也可以传递一个物体。

pageCOnfig= new oPageConfig

PrintMenu (pageConfig);
PrintHeader (pageConfig);
PrintLeftBox (pageConfig);

Also passing a variable to your functions, you could choose to not display a menu (for a special page with no menu for instance).

同时将变量传递给您的函数,您可以选择不显示菜单(例如,对于没有菜单的特殊页面)。

0  

Using Template Engine can be quite helpeful under this situation. Choose one of the following two solutions as you like.

在这种情况下,使用模板引擎可能非常有用。根据需要选择以下两种解决方案之一。

1. in backend, try Jade(Node.js), TWIG(PHP)...

   在后端,尝试Jade(Node.js),TWIG(PHP)......

   You can find more here:http://en.wikipedia.org/wiki/Comparison_of_web_template_engines;

   你可以在这里找到更多:http://en.wikipedia.org/wiki/Comparison_of_web_template_engines;

   The Menu, Header, Footer will be seperated in different files, and can be included in other html files which will be rendered by template engine at server part.

   菜单,页眉,页脚将分隔在不同的文件中,并且可以包含在其他html文件中,这些文件将由服务器部分的模板引擎呈现。

2. in frontend, try Angular.js or other web MVC frameworks,

   在前端,尝试Angular.js或其他Web MVC框架,

   the disadvantage of this solution is that you may need spend more time on providing a stable restful api, because all the rendering works are finished by the Angular.js at client part.

   这个解决方案的缺点是你可能需要花更多的时间来提供稳定的restful api,因为所有的渲染工作都是由客户端的Angular.js完成的。