Difference between revisions of "Roadmap"

From ZoneMinder Wiki
Jump to navigationJump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
The following are the main major features that are intended to be included in the next few versions. There are a large number of more minor enhancements that are also scheduled but which are too numerous to mention below.
The following are the main major features that are intended to be included in the next few versions. There are a large number of more minor enhancements that are also scheduled but which are too numerous to mention below.


Next major version (1.24.0)...
Next major version (1.25.0)...


* Add support for MPEG4 as camera sources.
* Structural rewrite of image classes leading to much improved (but simpler to configure) motion detection
* Allow mapped memory instead of shared memory
* Support multicast or unicast streaming of captured of analysed streams using MPEG4/H.264 over RTP. This will reduce the load when many clients are moniutoring the streams and improve the real-time immediacy of the stream contents.
* Support Video For Linux 2


Thereafter in no particular order...
Thereafter in no particular order...
Line 12: Line 11:
* Detach video specific detail from events to allow events to relate to other stimuli. This will lead to...
* Detach video specific detail from events to allow events to relate to other stimuli. This will lead to...
* Add support for audio monitors and audio events.
* Add support for audio monitors and audio events.
* Link into Darwin Streaming Server or similar to allow ZM feeds to be multicast and sent in different methods and more realtime (e.g. using 3GP type RTSP streams for streaming on mobile phones).
* Finish implementation of 'zone sets' allowing different zone configuration to be applied to monitors at different times (e.g. day and night sets).
* Finish implementation of 'zone sets' allowing different zone configuration to be applied to monitors at different times (e.g. day and night sets).
* Modify the motion detection mechanism to allow chained lists of rules. This would make it easier to support user defined plugins for motion detection and other image analysis functions.
* Modify the motion detection mechanism to allow chained lists of rules. This would make it easier to support user defined plugins for motion detection and other image analysis functions.
* Rewrite the existing HTML web interface as xHTML with CSS and remove use of tables for positioning. Also remove most frames and make more use of Ajax.
* Restructure the web files into distinct interfaces (instead of HTML and xHTML as at present use 'classic' and 'mobile' for example). This will also allow additional interfaces to be developed.
* Move event images above the web root to prevent direct browsing which can sometimes bypass the user permissions mechanism. Access will then always be via zms or lighter weight method.
* Move event images above the web root to prevent direct browsing which can sometimes bypass the user permissions mechanism. Access will then always be via zms or lighter weight method.
* Break out all 'branding' styling in each interface into CSS in skin directories. This will then allow support for custom skins for each interface.
* Replace all tabs with 4 spaces!
* Replace all tabs with 4 spaces!

Latest revision as of 08:19, 22 June 2009

The following are the main major features that are intended to be included in the next few versions. There are a large number of more minor enhancements that are also scheduled but which are too numerous to mention below.

Next major version (1.25.0)...

  • Structural rewrite of image classes leading to much improved (but simpler to configure) motion detection
  • Support multicast or unicast streaming of captured of analysed streams using MPEG4/H.264 over RTP. This will reduce the load when many clients are moniutoring the streams and improve the real-time immediacy of the stream contents.

Thereafter in no particular order...

  • Change multi-language support to use gettext. This will provide a more standardised method of adding languages.
  • Detach video specific detail from events to allow events to relate to other stimuli. This will lead to...
  • Add support for audio monitors and audio events.
  • Finish implementation of 'zone sets' allowing different zone configuration to be applied to monitors at different times (e.g. day and night sets).
  • Modify the motion detection mechanism to allow chained lists of rules. This would make it easier to support user defined plugins for motion detection and other image analysis functions.
  • Move event images above the web root to prevent direct browsing which can sometimes bypass the user permissions mechanism. Access will then always be via zms or lighter weight method.
  • Replace all tabs with 4 spaces!