I'm searching for a way to build a silverlight client web application that connect toLync 2010 Online with audio, video, files and whiteboard features. Could anyone recommend some documentation?
This won't be easy... You could implement IM and presence fairly simply, but there is no support in Silverlight or the Lync APIs for the real-time AV protocols needed to support Audio and Video - it's a similiar story with sharing and whiteboarding.
Unless you have the time on your hands and are willing to attempt this without support/documentation, i'd recommend against it.
Edit: Have you taken a look at the web app and attendee client? The web app is the closest I think to what you want to achieve - I think you'd find it very difficult to improve on this.
If you think this is the right answer, please mark it as accepted, to help anyone else browsing the question. Thanks!
Related
I've never used Drupal, but have been looking up tutorials online. My client would really like the adaptability of React and to have more flexibility in terms of design. I could make my own database and React app, but I have not studied security (I'm a team of one, so no one for security on my end, either). Security and access to a content management system was the main reason we decided to go with Drupal. However, I would still like to be able to code in React/something I'm familiar with to produce a site I am proud to say I made.
I've been Googling and Youtubing tutorials and help, but not having anyone to ask specific questions is making this difficult.
If anyone knows of a relatively easy way to build a React app on Drupal, I would really appreciate the advice. Or if there is a better way I should go about beginning a project as I've briefly mentioned above, I would also be open to that. Thank you in advance and sorry for the long message!
What you are asking is quite broad in concept and not easy to answer in just one answer post. Try to look for Headless / Decoupled Drupal.
https://www.acquia.com/drupal/decoupled-drupal
What this essentially means is that all the services and the content management are handled by Drupal while the core user experience or the way the site is displayed in a browser is controlled via a JavaScript framework such as React.js or backbone.js. This is achieved via Drupal’s RESTful API service.
Hope this helps.
I've been really interested in making a walkie talkie wpf application, however I'm not too sure where to start. I was wondering what kind of technology would be needed to capture one person speaking and playing it back to someone else? Any resources available online to learn about the technology required etc. Thanks
For anyone who's interested in something like this too, I found that the makers of Zello the phone walkie talkie phone app also provide a SDK which can be used to integrate in a .NET application. It's also free for up to 5 people on your network. So I'm going to check it out and see how I can implement it in my app. Here's the link for anyone who's interested http://zello.com/sdk.htm
Since there are no answers yet, I'm going to rewrite this question in hopes of an answer (I don't mind discussion, but I know SO is about Q&A). It appears security checks/prompts make it unfeasible to use Flash Player. With this in mind, the question still stands, but please answer based on experience using AIR.
I have a Winforms app written in C# that I need to add VOIP to. I really like how well the Flash Player VOIP solution works, the AEC (echo cancel) is awesome. I know they use Speex, but the implementation is still a lot of work even using Speex, so I'd like to use Adobe's solution directly in my app.
Has anyone done this? What issues will I have? A few I can think of:
IPC between AIR and Winforms app. I assume this is easy and several options, including sockets/network, file i/o, maybe others.
Based on this
Content running in the AIR application sandbox does not need the
permission of the user to access the microphone
I don't think security warnings will be an issue? I'm not sure what a sandbox is yet, but as long as my AIR app can run in this and still talk with my winforms app, then shouldn't be an issue.
I assume the voice capture including enhancements (AEC, NS, Speex, etc) are supported in AIR?
Are there any samples I can run that use voice capture in AIR?
I am developing a silverlight video conference application which will support multicast. I want to know which technology is best, socket coding or IIS live smooth streaming. The performance is the big issue, Thanks T.
Protocol decision depends on many parameters. For example what are the expectations for latency? Are you looking at true conference experience with <500ms latency or is several seconds latency is fine? How many clients are going to be connected at the same time? Is it internet or intranet?
I can recommend you Ozeki Voip SIP SDK and its webphone solutions. After testing it in Visual Studio 2010 I went on using it. It sounds a bit like sticking to this sdk, but I have experienced that the support team is really good: they have helped me significantly in my work. I found **How to implement web to web video calls using Silverlight camera access? to be a good sample program on their website and think it would be instructive enough for you to start a business application with webphone.
Hopefully I could help you.
I have only very basic experience with HTML/CSS and have quite a bit of experience with testing software and web apps from a consumer perspective. I'd love to launch a web application that plays nicely with Google services, similar to some of the apps you'd find on the Google Apps Marketplace, such as ManyMoon, time to note, Socialwok, etc. I'm a huge Google fan and would like to build something that's well integrated with other Google services.
If you were a total beginner and wanted to build a complex app like one of examples above (project management, CRM, etc), where would you start?
If you worked your ass off 18 hours a day, 24/7, how fast could you do it?
I've dabbled into various languages and development frameworks, and read about which apps are using what languages but it's hard to figure out what would be most beneficial to jump into. Ruby on Rails, PHP, Google Web Toolkit, AppEngine. The list goes on and on. I want to be able to build and launch my own scalable web app.
Thanks.
One bit of advice: There is no shortcut for proper experience. It took me 4 years to come to a point where I can build enterprise level web apps - even though I had the dream of building one immediately, right from the beginning. Start small and build your way up.
Even though I did hate this advice when I was receiving it... Don't try to build the next Facebook platform right now.
Now, to answer your question:
Skills:
You must be absolutely clear about server-client interaction with respect to HTTP. You will never understand AJAX fully without understanding HTTP and behind the scenes of browsers. Note: being clear and knowing everything are two different things. Be clear about HTTP.
Learn about HTML/CSS and JavaScript standards to some extent to know that they bahave differently in different browsers. In the grand scheme of things, they are not that important if you are okay with some framework that handles these for you (I recommend JQuery and JQuery UI).
Learn a little about Linux, Apache, PHP.
How to go about it:
To develop web-apps, you could start with the LAMP stack - Linux + Apache + MySQL + PHP.
First build a small web app that does something trivial - like saving and retrieving user's stuff using AJAX and a nice UI or something. I'd recommend jQuery and jQueryUI for JavaScript and UI frameworks.
Then, build a small web app that just gets data from some Google service, given a user's credentials.. I am not Google expert but I guess Google provides APIs for some services(?).
Then build an app where two people can share their data coming from a Google's service or something to that effect.
Then add your own fancy stuff.
It goes on like that.
If you are a .Net person, you could go with.. Windows + IIS + MS SQL Server + ASP.Net3.5/VB/C#. Guess what? StackOverflow is build on that stack :)
Learning about and using an MVC framework is also a good idea - ASP.Net MVC or something similar for PHP.
Minor clarification - By Google-friendly did you mean SEO-friendly? If so, Google-friendly and web-app don't go well together.
It makes sense to build a Google-friendly website not a web-app.
I would start by
brainstorming a hands-on project
identify the skills you will need to achieve it
learn them as you work through the project
set progress goals and celebrate small victories
For most people 18 hrs/day 24/7 sounds a little overly optimistic. A reasonable goal would be to form an interesting project idea and research the needed skills the first week, work through a few tutorials and maybe apply your own functionality the second week, build something 'complete' the third week, then take a step back and take another look at your original goal.
As far as choosing a project, I find a notepad helps. I'll be somewhere and think, 'wouldn't it be nice if...' and I'll go look for a solution that provides that 'what if' and find it doesn't exist. So there you go.
I would also have a look to one of the top voted questions here on Stack Overflow:
What should a developer know before building a public web site.