框架具有您可能需要的一些功能。您可能需要某种具有内置排序机制的数组。或者，您可能需要一个窗口，您想在其中放置一些控件，所有这些都可以在框架中找到。这是一种跨越你自己作品框架的作品。

编辑: 好吧，我将要挖掘你们试图告诉我的东西;)你可能没有注意到“跨越一个框架的工作……”这行之间的信息。 在它越陷越深之前。我试着给它一个地板，希望你优雅地: 我在这里找到了一个很好的解释“库和框架的区别”的问题 http://ifacethoughts.net/2007/06/04/difference-between-a-library-and-a-framework/

I'm very late to answer it. But, I would like to share one example, which I only thought of today. If I told you to cut a piece of paper with dimensions 5m by 5m, then surely you would do that. But suppose I ask you to cut 1000 pieces of paper of the same dimensions. In this case, you won't do the measuring 1000 times; obviously, you would make a frame of 5m by 5m, and then with the help of it you would be able to cut 1000 pieces of paper in less time. So, what you did was make a framework which would do a specific type of task. Instead of performing the same type of task again and again for the same type of applications, you create a framework having all those facilities together in one nice packet, hence providing the abstraction for your application and more importantly many applications.

除了定义(有时只有在你已经理解的情况下才能理解)之外，还有一个例子帮助了我。

I think I got a glimmer of understanding when loooking at sorting a list in .Net; an example of a framework providing a functionality that's tailored by user code providing specific functionality. Take List.Sort(IComparer). The sort algorithm, which resides in the .Net framework in the Sort method, needs to do a series of compares; does object A come before or after object B? But Sort itself has no clue how to do the compare; only the type being sorted knows that. You couldn't write a comparison sort algorithm that can be reused by many users and anticipate all the various types you'd be called upon to sort. You've got to leave that bit of work up to the user itself. So here, sort, aka the framework, calls back to a method in the user code, the type being sorted so it can do the compare. (Or a delegate can be used; same point.)

我算对了吗?

一般来说，框架作品是真实的或概念性的结构，旨在作为建筑的支撑或指南，将结构扩展为有用的东西……

我不确定“框架”是否有一个明确的定义。有时，一组很大的库被称为框架，但我认为这个词的典型用法更接近于aioobe带来的定义。

这篇非常好的文章总结了一组库和一个框架之间的区别:

框架可以定义为一组库，它们说“不要给我们打电话，我们会给你打电话”。

框架如何帮助您?因为您不需要从头开始编写一些东西，基本上只需扩展一个给定的工作应用程序。通过这种方式，您可以获得很高的生产率——有时最终得到的应用程序可能比您在相同时间内自己所做的要复杂得多——但您通常会牺牲很多灵活性。

已经有很多很好的答案了，但让我看看我是否能给你另一个观点。

为了简化事情，您可以将框架视为一个除了实际功能之外完整的应用程序。你插入功能和PRESTO!你有一个应用程序。

Consider, say, a GUI framework. The framework contains everything you need to make an application. Indeed you can often trivially make a minimal application with very few lines of source that does absolutely nothing -- but it does give you window management, sub-window management, menus, button bars, etc. That's the framework side of things. By adding your application functionality and "plugging it in" to the right places in the framework you turn this empty app that does nothing more than window management, etc. into a real, full-blown application.

对于web应用程序，服务器端应用程序等也有类似类型的框架。在每种情况下，框架提供了大量乏味、重复的代码(希望如此)，而您提供了实际的问题域功能。(这是理想状态。当然，在现实中，框架的成功有很大的变数。)

我再次强调，这是对框架的简化观点。我没有使用像“控制反转”之类的可怕术语，尽管大多数框架都内置了这样可怕的概念。既然你是初学者，我想我就不给你行话了，用一个简单的比喻。