两分钟让你明白什么是ERP

老段子了,但是很浅显易懂,还是分享下。(^ ^)

?ERP(Enterprise Resource Planning)企业资源计划系统,是指建立在信息技术基础上,以系统化的管理思想,为企业决策层及员工提供决策运行手段的管理平台。?

  ?
  一天中午,丈夫在外给家里打电话:“亲爱的老婆,晚上我想带几个同事回家吃饭可以吗?”(订货意向)   
  妻子:“当然可以,来几个人,几点来,想吃什么菜?”?
  丈夫:“6个人,我们7点左右回来,准备些酒、烤鸭、番茄炒蛋、凉菜、蛋花汤……。你看可以吗?”(商务沟通)?
  妻子:“没问题,我会准备好的。”(订单确认)?
  妻子记录下需要做的菜单(MPS计划),具体要准备的东西:鸭、酒、番茄、鸡蛋、调料……?(BOM物料清单),发现需要:1只鸭蛋,5瓶酒,4个鸡蛋……(BOM展开),炒蛋需要6个鸡蛋,蛋花汤需要4个鸡蛋(共用物料)。?
  打开冰箱一看(库房),只剩下2个鸡蛋(缺料)。?
  来到自由市场,妻子:“请问鸡蛋怎么卖?”(采购询价)?
  小贩:“1个1元,半打5元,1打9.5元。”?
  妻子:“我只需要8个,但这次买1打。”(经济批量采购)?
  妻子:“这有一个坏的,换一个。”(验收、退料、换料)?
  回到家中,准备洗采、切菜、炒菜……(工艺线路),厨房中有燃气灶、微波炉、电饭煲……(工作中心)。妻子发现拨鸭毛最费时间(瓶颈工序,关键工艺路线),用微波炉自己做烤鸭可能来不及(产能不足),于是在楼下的餐厅里买现成的(产品委外)。?
  下午4点,电话铃又响:“妈妈,晚上几个同学想来家里吃饭,你帮忙准备一下。”(紧急订单)?
  “好的,你们想吃什么,爸爸晚上也有客人,你愿意和他们一起吃吗?”?
“菜你看着办吧,但一定要有番茄炒鸡蛋,我们不和大人一起吃,6:30左右回来。”(不能并单处理)?
  “好的,肯定让你们满意。”(订单确定)?
  鸡蛋又不够了,打电话叫小贬送来。(紧急采购)?
  6:30,一切准备就绪,可烤鸭还没送来,急忙打电话询问:“我是李太,怎么订的烤鸭还不送来?”(采购委外单跟催)?
  “不好意思,送货的人已经走了,可能是堵车吧,马上就会到的。”?
门铃响了。“李太太,这是您要的烤鸭。请在单上签一个字。”(验收、入库、转应付账款)?
  6:45,女儿的电话:“妈妈,我想现在带几个朋友回家吃饭可以吗?”(呵呵,又是紧急订购意向,要求现货)?
  “不行呀,女儿,今天妈已经需要准备两桌饭了,时间实在是来不及,真的非常抱歉,下次早点说,一定给你们准备好。”(哈哈,这就是ERP的使用局限,要有稳定的外部环境,要有一个起码的提前期)?
  送走了所有客人,疲惫的妻子坐在沙发上对丈夫说:“亲爱的,现在咱们家请客的频率非常高,应该要买些厨房用品了(设备采购),最好能再雇个小保姆(连人力资源系统也有接口了)。?
  丈夫:“家里你做主,需要什么你就去办吧。”(通过审核)?
  妻子:“还有,最近家里花销太大,用你的私房钱来补贴一下,好吗?”(最后就是应收货款的催要)?

现在还有人不理解ERP吗?记住,每一个合格的家庭都是生产厂长的有力竞争者!

使用 CC Cleaner Tool 来解决安装问题 | CC、CS3-CS6

原文:http://helpx.adobe.com/cn/creative-suite/kb/cs5-cleaner-tool-installation-problems.html

Adobe Creative Cloud (CC) Cleaner Tool 可帮助解决 Adobe Creative Cloud 和 Adobe Creative Suite (CS3-CS6) 应用程序的安装问题。该工具可删除 Creative Cloud 或 Creative Suite 应用程序预发布安装的安装记录。它不影响 Creative Cloud 或 Creative Suite 应用程序早期版本的现有安装。

下载地址:点此下载

备份地址:百度网盘(密码: 6hjp)

【转】远景(PCbeta)和驱动之家(mydrivers)广告过滤规则

来源:http://bbs.maxthon.cn/thread-519173-1-1.html

远景论坛 广告过滤
远景论坛 广告过滤规则
! Maxthon AdHunter
! site pcbeta.com
! author ·oVo·
! date 2014-04-02
! feedback http://is.gd/Filter_PCBeta
*baidu*/?.js*
*on/cf/*
*union*
*/biz/*
*cnzz*
##[style*='9px;width:980px;'] {height:auto !important}
###sitefocus,[style*='height:169px;'],[style*='height:171px;']
##[style*=';height:91px;b'],[class*=a_p],#weixinqr
###nv_forum>#wp>style[type='text/css']+div>div
###nv_forum>#wp>style[type='text/css']+div {height:auto !important;padding:0px !important}
!首页临时显示部分-2014开发者大会
###banner
!
!论坛(板块+帖子)推荐区域   2014-04-02
###nv_forum>#wp>[style^='width:998px;height:75px;']
###nv_forum>#wp>style[type='text/css']+div
!隐右拉宽(仅限文章页)
##.mn {width:auto !important;float:none !important}
###ct>.pb_ptr.pb_bdt2
!bbs拉宽
###nv_forum>#wp {width:95% !important}
##[style*='height:75px;b'],[style*='height:437px;o'] {margin:5px auto !important}
!
! Maxthon AdHunter
! site mydrivers.com
! author ·oVo·
! date 2014-05-08
! feedback http://is.gd/Filter_PCBeta
*baidu*/?.js
*/inc/*
*ad.gif
http://11.mydrivers.com/drivers/drivers*.js
##table[height='90'],.baidu_box,[id^=ad_],[id*=_ad]
##[id^=code_],.adggg1
##.down_in_url_left,.down_in_url_right
##.down_in_url_center>:not(.download_url)
##.down_in_url {height:auto !important}
!

 

Adobe与Google推出开源字体——思源黑体(Source Han Sans)

来源:http://store1.adobe.com/cfusion/store/html/index.cfm?event=displayFontPackage&code=1967

字体指导设计师:Ryoko Nishizuka

格式:OpenType?(Windows and Macintosh Platforms)

包含语种:Adobe Western 2,?Adobe-Korea 1-2,?Chinese Simplified,?Chinese Traditional,?Pr6N Japanese,?Symbol/Pi,?Vietnamese

下载地址:

https://sourceforge.net/adobe/source-han-sans/wiki/Home

http://font.chinaz.com/140717378230.htm#down

示例:

Source Han Sans ExtraLight

Source Han Sans ExtraLight

Source Han Sans Light

Source Han Sans Light

Source Han Sans Normal

Source Han Sans Light

Source Han Sans Regular

Source Han Sans Normal

Source Han Sans Medium

Source Han Sans Medium

Source Han Sans Bold

Source Han Sans Bold

Source Han Sans Heavy

Source Han Sans Heavy

百度贴吧过滤规则

经常逛着百度贴吧,最近发现贴吧越来越“无耻”了,各种广告,无奈之下只有动手清理了。贴上我自己的傲游浏览器过滤规则,主要是屏蔽了一些和贴吧内容不吻合的帖子,边栏广告等。

!含游戏
##[class*="game"]
!贴吧首页,贴吧视频互动
##div[class="item live_show"]
!贴吧首页,滚动条
##div[class="top-sec clearfix"]
!贴吧首页,中部滚动广告
##div[class="platact_bigouter"]
!贴吧首页 豪友俱乐部
##div[class="member_rank"]
!贴吧内容条目
##div[class*="dasense"]
##li[class*="dasense"]
!本吧福利彩蛋
##div[id="tbmall_score_region"]
!幸运投注
##div[class*="lot_wrap"]
!广告
##[class*="_ad"]

 

《高效 XML》第5部分 Something went really wrong – OutOfMemoryException and StackOverflowException thrown when using XslCompiledTransform

来源:http://blogs.msdn.com/b/xmlteam/archive/2011/09/26/effective-xml-part-5-something-went-really-wrong-outofmemoryexception-and-stackoverflowexception-thrown-when-using-xslcompiledtransform.aspx

So, your application is crashing and it is crashing in?the?bad way. After spending hours of debugging and trying different things you figured out that this is this Xslt stylesheet that causes all the problems. How come? XslCompiledTransform is a compiler. It’s a bit different from C# or VB.NET compilers because it runs at runtime but the result of the compilation is basically the same – IL (Intermediate Language) code. One of disadvantages of running compilation at runtime is that compilation issues may have impact on the running application. In the “offline” scenario compiler would just return an error (the one I hate the most is “Internal Compiler Error” – still it will not affect my app at runtime ?? at worst there is no app). So, compilation may be one source of problems. The other source of problems can be the IL code the stylesheet was compiled to. Here there is not much difference between code generated from Xslt, C# or VB. In any case it is easy to write a program that compiles correctly but misbehaves at runtime (bugs anyone?). Let’s take a look at two most common unexpected exceptions you may hit when working with XslCompiledTransform and ways to resolve them.

继续阅读《高效 XML》第5部分 Something went really wrong – OutOfMemoryException and StackOverflowException thrown when using XslCompiledTransform

《高效 XML》第4部分 Let me project this (Xml file) for you

来源:http://blogs.msdn.com/b/xmlteam/archive/2011/09/26/effective-xml-part-4-let-me-project-this-xml-file-for-you.aspx

Xml is ubiquitous. No doubt about it. It is being used almost everywhere and almost by everyone. This includes places where huge amounts of data are being processed. This means xml files (or streams) used there are also huge. And the bigger the Xml file the harder it is to process. The two biggest problems are:

  • You need to query the document with a couple of XPath expressions or transform it with an Xslt file but the document is too big to be even loaded (the rule of thumb is that an Xml document needs up to 5 times memory of its size on the disk). When you try to load the document you get OutOfMemoryException and that’s about where your Xml processing ends.
  • You are able to load the document but all the queries or transformations are sloooow (and I assume it’s not because the queries or Xslt stylesheets are poorly written – if you are not sure see Effective Xml Part 3)

继续阅读《高效 XML》第4部分 Let me project this (Xml file) for you

《高效 XML》第3部分 Didn’t you say XslCompiledTransform was fast?

来源:http://blogs.msdn.com/b/xmlteam/archive/2011/09/26/effective-xml-part-3-didn-t-you-say-xslcompiledtransform-was-fast.aspx

“XslCompiledTransform is fast.”

“Really?”
“Yeah, XslCompiledTransform is fast… if used correctly.”

Indeed, depending on how you use XslCompiledTransform API your transformations can be really fast or not-that-fast (to say the least). The key to understanding where this difference comes from is to understan what XslCompiledTransform.Load() method actually does. The name of the method indicates that it is just used to load Xslt stylesheets. In reality the method does much more than this. It not only loads the Xslt stylesheet but it also compiles it to IL (Intermediate Language). Yes, after the stylesheet has been “loaded” somewhere there in memory is the real code built based on the provided stylesheet. Generating this code (i.e. “loading” the stylesheet) is costly but it allows for fast transformations – when you start a transformation in your app it no longer deals with the stylesheet, it just invokes the code the Xslt stylesheet was compiled to.

继续阅读《高效 XML》第3部分 Didn’t you say XslCompiledTransform was fast?

《高效XML》第2部分 How to kill the performance of an app with XPath…

来源:http://blogs.msdn.com/b/xmlteam/archive/2011/09/26/effective-xml-part-2-how-to-kill-the-performance-of-an-app-with-xpath.aspx

XPath expressions are pretty flexible. This flexibility allows for very creative ways of using XPath. Unfortunately some of them are suboptimal and cause bad performance of apps. This is especially visible in Xslt transformations where stylesheets contains tens if not hundreds of XPath expressions. Here is the list of the most common bad practices (or even anti-patterns) I have seen:

继续阅读《高效XML》第2部分 How to kill the performance of an app with XPath…