Reprinted from Http://www.cnblogs.com/gaochundong/p/opensource_ip_video_surveillance_system_part_1_introduction.html
Open source dedicated series of links
- Open Source dedication: based on. NET build IP Intelligent Network Video Surveillance System (i) Open source code
- Open Source dedication: based on. NET Building IP Intelligent Network Video Surveillance System (ii) Introduction of basic class Library
- Open Source dedication: based on. NET build IP Intelligent Network Video Surveillance System (iii) command line toolset
- Open Source dedication: based on. NET Building IP Intelligent Network Video Surveillance System (IV.) service-side introduction
- Open Source dedication: based on. NET build IP Intelligent Network Video Surveillance System (v) Client Introduction
What kind of system is this?
Optimalvision (OV) Network video Surveillance System (surveillance) is a set of IP network video surveillance systems based on. NET, C #, WCF, WPF and other technologies. The design and implementation of the system is intended to deploy the system in home computers, connected to local or LAN devices, through the browser or mobile phone clients to browse the baby live video, known as the "Baby online" or "home care."
For details, refer to the blog post "based on. NET to build IP Intelligent Network Video Surveillance system.
For more systems, please refer to the blog post "based on. NET to build IP Intelligent Network Video Surveillance system.
Why open source?
Since spare time is always limited, after completing the service, configuration, collection, transmission and desktop GUI parts of the system, the motivation and interest of continuing to complete the following mobile client are significantly weakened, especially after the baby is born for a long period of time basically no progress, gradually evolved into drilling and testing the focus of technology and model of the experimental project.
Summarizes some of the reasons for open source code:
- Community sharing. Alone Lele is not as many lele, lonely rotten code meaningless, and community sharing and discussion is also a pleasure.
- Limited energy. The use of spare time to build systems, time crowding is to accompany family and children time, or will not accumulate for three years.
- Knowledge accumulation. It is said that I look at the code written six months ago, if the feeling needs improvement, then grew up, I am now unable to improve.
- Expand your horizons. Personal perspective is always short-sighted, accept more people's criticism and correction, can promote faster learning and broaden their horizons.
Where's the code?
The code is hosted on the GitHub Web site, and all code is compiled based on the Microsoft. NET Framework 4.0.
- Https://github.com/gaochundong/Gimela
- GitHub One-click Download
- Star code, thanks for supporting
Code directory structure
Here is the source code directory structure:
- Assets-resources used by the system, examples, etc.
- Bin-System compiled output directory
- Debug-debug Mode Output Directory
- Build-Compile system scripts
- Docs-system Design and documentation
- Lib-class library referenced by system
- SRC-system code
- CRUST-MVVM model Frame (adapted from MVVM light Toolkit)
- Foundation-System base Class library (refer to open source dedication: based on. NET build IP Intelligent Network Video Surveillance System (ii) Basic Class Library Introduction ")
- Knifer-command-line toolset (refer to open source dedication: based on. NET to build IP Intelligent Network Video Surveillance System (iii) command line toolset ")
- Rukbat-Video Surveillance system code
- Common-front-end and back-end common code
- SERVICE-WCF Service Code (refer to open source dedication: based on. NET build IP Intelligent Network Video Surveillance System (four) service End Introduction "
- GUI-WPF client code (see Open Source: Based on. NET build IP Intelligent Network Video Surveillance System (v) client Introduction ")
- tests-various tests
- Tools-various utilities such as clean-up compiled directory scripts, etc.
Which class libraries are referenced?
The following lists the incomplete list of open source class libraries that the system learns, references, references, adaptations, extracts.
- Aforge.net
- Accord.net
- Naudio
- Nvlc
- Speex
- C # WebServer
- Ffmpeg
- Ffmpeg.net
- FlowPlayer
- ISpy
- ZoneMinder
- ONVIF Device Manager
- Google GData
- Gmap.net
- Json.NET
- Dynamic Json
- Hammock
- AutoMapper
- Socialkit/lightrest
- Microsoft Enterprise Library
- Microsoft Unity
- System.Data.SQLite
- RavenDB
- Raptordb
- Mongodb
- MongoDB C # Driver
- Windows Presentation Foundation (WPF)
- MVVM Light Toolkit
- Caliburn.micro
- Mefedmvvm
- MVVM Foundation
- Phoenix MVVM
- WPF Mediakit
- WPF multiple Document Interface (MDI)
- MDI Container for WPF
- Avalondock
- WPF Google Map Control
- Wpfspark
- WPF 3DTools
- Odyssey WPF Controls
- Extended WPF toolkit™community Edition
- Calendar Control in WPF
- Patterns & Practices:prism
- Facebook Developer Toolkit
- Microsoft Health Common User Interface (CUI)
- Mahapps.metroa UI Toolkit for WPF
- Spark View Engine
- Reactiveui
- Commonservicelocator
- Ninject
- StructureMap
- Netmq
- Funnelweb
- Quartz.net
- Task Scheduler Engine
- SuperSocket
- Commonlibrary.net
- Nsubstitute
Copyright and License
Copyright (c) 2011-2013 Dennis Gao
All rights reserved.
Licensed under the BSD License.
Redistribution and use of source and binary forms, with or without
modification, is permit Ted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. redistributions in binary form must reproduce the above COPYRIGHT
notice, this list of conditions and the following disclaimer in THE
documentation A nd/or other materials provided with the distribution.
3. The name of the author May is used to endorse or promote PRODUCTS
derived from this software without specific prior written permission.
This software are provided by the AUTHOR "as is" and any EXPRESS OR
Implied warranties, including, but not LIMITED to, the implied warranties
of merchantability and FITNESS for A particular PURPOSE is disclaimed.
In NO EVENT shall the AUTHOR is liable for any DIRECT, INDIRECT,
Incidental, special, exemplary, OR consequential damages (including, but
Not LIMITED to, procurement of substitute GOODS OR SERVICES; LOSS of Use,
DATA, OR profits; OR business interruption) however caused and on any
Theory of liability, WHETHER in contract, STRICT liability, OR TORT
(including negligence OR OTHERWISE) arising in any to
This software, even IF advised of the possibility of SUCH DAMAGE.
GitHub is on the list this week and thank you for your support.
Open Source dedication: based on. NET to build IP Intelligent Network Video Surveillance System