[TASK] Set version to 4.1.0 beta
[TASK] Changed instructions how to include content elements
[TASK] Instructions on how to use own Extbase controller
Merge pull request #137 from benjaminrau/development

[TASK] Instructions on how to use own Extbase controller
[FEATURE] TYPO3 application context support (6.2+)

Circumvents caching of FCE definitions if TYPO3_CONTEXT is other than Production. On systems not supporting contexts, Production is assumed.
[TASK] Use ApplicationContext when available
Merge pull request #139 from hmspl/freedom

[TASK] Use ApplicationContext when available
[BUGFIX] Fix namespace in use statement
Merge pull request #141 from coding46/patch-1

[BUGFIX] Fix namespace in use statement
[FEATURE] Support flux:form options.Fluidcontent.sorting

Setting options on FCEs for fluidcontent now sorts the elements in the new content wizard (per-group, thus not allowing you to mix groups):

```xml
<flux:form ... options="{Fluidcontent: {sorting: 1234}}"> ... </flux:form>
```

Note the use of an ExtensionName convention root-level option container - this is done to avoid collisions and confusion regarding consumers.
[FEATURE] Support white/blacklist allowed FCE types

The same as the `allowedContentType` and `deniedContentTypes` feature in Flux:

```xml
<flux:grid.column variables="{Fluidcontent: {allowedContentTypes: 'fluidcontent_bootstrap:Alert.html'}}" />
```

And the same for `deniedContentTypes`. The setting is inherited from page column to container elements' columns, but not from container element to nested container element. Which means you can filter the allowed content types in both page template's Grid and FCE's content area.