This is a demonstration app that provides you a starting point for building your first video conferencing application using rtc.io. The demo aims to ease you into working with rtc.io through using the prebuilt rtc.js bundle.
If you are comfortable using with browserify then you should be able to dig and use some of the lower-level packages such as rtc-quickconnect and others after playing with this demo.
If you just want to create a Zip file without installing gulp, that's possible, too. Read the below secion on "Creating a zip file without node, npm and gulp".
To have a play with this demo application, simply do the following:
- git, node and npm
- gulp:
npm install -g gulp
git clone https://github.com/rtc-io/demo-helloworld.git
cd demo-helloworld
npm install
gulp
This will provide you information on the various build options available to you that have been provided in the gulpfile. This should be something similar to what is displayed below:
Usage
gulp [task]
Available tasks
help Display this help text.
package Package for upload to build.rtc.io
serve Serve the local files using a development server
vendor Rebuild vendor scripts from node package dependencies
vendor-rtc
vendor-rtc-ios
This is a demo that has been constructed from the ground-up to be compatible with a hosted build service that will produce WebRTC enabled iOS applications in process similar to (and inspired by) PhoneGap build.
Make sure to use your own domain value in the domain attribute of the <bundle> element of the config.xml file as app ID's must be unique with Apple.
To use this application with build.rtc.io, prepare a zip file and upload it there.
You can use the gulp package command - it will include only those files required to build the application.
You can also use zip directly - use the extended command as below.
build.rtc.io generates an Apple package (.ipa or .app) which is ready to install on an iPhone/iPad or to publish on the Apple App Store.
To package an archive ready for upload to the service, use the following command:
gulp package
The archive.zip file will in the demo-helloworld directory ready for upload.
git clone https://github.com/rtc-io/demo-helloworld.git
cd demo-helloworld
zip -r archive.zip . -x *.git* -x *.zip -x gulpfile.js -x package.json -x "node_modules/*"
The archive.zip file will in the demo-helloworld directory ready for upload.
When you have built it and installed on an iOS device, you can connect with it via http://rtc-io.github.io/demo-helloworld/#yourRoom (make sure to use the same room in the URL fragment that you've chosen in the iOS app).
The config.xml is a regular XML-File. It has a strict structure like described here.
<config>
<name>HelloWebRTCWorld</name>
<author email="[email protected]" href="http://rtc.io">Damon Oehlman</author>
<content path="/" src="index.html"/>
<bundle domain="io.rtc.helloworld" version="1.0" />
<ios>
<build version="1.2" sdkversion="7.1" config="release"/>
<icons>
<icon size="29x29" file="icons/Icon-Small.png" idiom="ipad" />
<icon size="40x40" file="icons/Icon-Small-40.png" idiom="all" />
<icon size="58x58" file="icons/[email protected]" idiom="iphone" />
<icon size="58x58" file="icons/[email protected]" idiom="ipad" />
<icon size="76x76" file="icons/Icon-76.png" idiom="ipad" />
<icon size="80x80" file="icons/[email protected]" idiom="all" />
<icon size="120x120" file="icons/[email protected]" idiom="iphone" />
<icon size="152x152" file="icons/[email protected]" idiom="ipad" />
</icons>
</ios>
</config>The config.xml file must have a name-tag, which gives the ipa package its name.
The content-tag must have a path attribute that defines the correct directory where the html start page can be found. By default, the application will try to load a index.html file from the path directory. You can change the start page's name by setting the src attribute.
The config.xml file must have a 'bundle'-tag which defines the app's reverse-domain identifier in the domain attribute and it's version number expressed in major/minor notation.
The ios-tag defines the requirements for an iOS build. The build-tag is mandatory and defines the minimum system sdkversion and a config for release/debug build. The version attribute defines the build version.
The icons structure contains a list of icons of different pixel dimensions used for the app on different iOS version. All icon-tags must have a size attribute which adhere to fixed values. If the Web developer uploads an icon mismatching the given size, it could result in iOS ignoring it and replacing it with the white default icon.
The file attribute provides the file name for the icon. If the app is only built for one device, it can be a empty string to show it is not supported.
The idiom attribute must be given for showing which device will use this icon.
This demo is licensed under the MIT LICENSE