Django-CMS code Research (5)

Preface:

We have already done a good job in the foreplay. Next we will start to step into the topic.

 

Code structure:

CMS

| -- Admin (I guess it is the secondary development and improvement of the Admin Interface)

| -- Cache (the cache mechanism is used to handle the speculation)

| -- Extensions (presumably a support package for various extensions, such as video/picture/teaser)

| -- Forms (guess the set of all forms. py)

| -- Locale (International)

| -- Management (limited imagination, leave it blank here)

| -- Middleware (middleware)

| -- Migrations (Migration file)

| -- Models (model)

| -- Publisher (presumably the publishing Controller)

| -- Signals (limited imagination, left blank)

| -- Sitemaps (website map)

| -- Static (static file)

| -- Templates (Template)

| -- Templatetags (custom tags and filters)

| -- Toolbar)

| -- Utils (functions class/function package)

| -- Tests/test_utils (Test Module: omitted)

| -- API. py (I Don't Know What To Do)

| -- App_base.py (it seems to be the above base class)

| -- Apphook_pool.py)

| -- Appresolver. py (APP parser)

| -- Apps. py (app-related processing)

| -- Cms_plugins.py (the processing logic of the plug-in should be related to the toolbar above)

| -- Cms_toolbar.py (the toolbar should be related to the toolbar above)

| -- Contants. py (Constant ?!)

| -- Context_processors.py (context processor)

| -- Exceptions. py (CMS exception ?)

| -- Menu. py (processing of menu hooks)

| -- Menu_bases.py (basic class for menu processing)

| -- Plugin_base.py (plug-in base class)

| -- Plugin_pool.py (plug-in pool)

| -- Plugin_processors.py (plug-in processor)

| -- Plugin_rendering.py (rendering of the plug-in)

| -- Toolbar_base.py (tool bar base class)

| -- Toolbar_pool.py (toolbar pool)

| -- Views. py (view)

| -- URLs. py (route)

 

Next section:

In-depth analysis of plugin

 

Django-CMS code Research (5)