My team have been battling to make react native play nicely with socket.io for 2 days now, without success. Is anyone currently using the most recent version of react native successfully with socket.io, or is the technology just not ready for commercial environments?
According to the answers to this question, there at least used to be a way to do use socket.io with RN. If that's indeed the case, I'd suggest opening an issue in the github repository, it might be a rather easy fix. I'd also making sure there are no existing issues related to what you're asking about before submitting an issue.
Good luck!
Related
The readme.md at https://github.com/NativeScript/windows-runtime says that the Windows runtime for Nativescript is in proof of concept stage, and then lists what I understand to be very deep language features that are not implemented yet.
The tone on the https://www.nativescript.org/blog/nativescript-runtime-preview-for-windows-10 announcement seems a bit more enthusiastic about the current feature set.
Being able to use Nativescript on Windows Phone (and any other platform) is incredibly appealing.
TJ, a core team member, recently posted on the forums about this:
Hey #NezzaGrey,
Thanks for reaching out, and awesome that you’re liking NativeScript :smile:. >Straight to the point though—we’re not actively working on UWP support because >1) it’s a ton of work to add a new platform and commit to supporting that >platform indefinitely, and 2) we’re not seeing nearly enough demand from our >community to justify taking on that work.
That doesn’t mean that UWP support in NativeScript will never happen, but it’s >not coming in the short term because we’re just not seeing the demand. That can >always change though. I’d encourage you to add your use case to the GitHub >issue open for adding UWP support in NativeScript: >https://github.com/NativeScript/NativeScript/issues/254. Yes, the issue is >somewhat ancient, but we really do pay attention to well-thought-out comments >during roadmap discussions.
I’ll note two other things. First, our initial work on making a Windows runtime >is completely open source and available on GitHub: >https://github.com/NativeScript/windows-runtime. We’d love to have community >?>help to make the new runtime a reality.
Second, one option you have is to build your iOS and Android apps with >NativeScript and Angular, and to use our code sharing approaches (see ?>https://www.nativescript.org/blog/code-sharing-between-web-and-mobile-with->angular-and-nativescript1) to share your Angular code with other apps. You >could take that approach to share Angular code between your NativeScript apps >and your UWP apps if you use something like Electron. This approach isn’t >ideal, as you’d probably prefer to build a completely native UWP app, but it’s >something to consider if you’re open to using Electron.
Anyways, hopefully you found some of this helpful. If you have any other >questions feel free to follow up.
Source: https://discourse.nativescript.org/t/windows-uwp-support/2659/3
I'm a new comer to socket.io over node.js
I found that the documentaion of socket.io in its website isn't good enough to start
is there a good referncies to start with socket.io in real projects
This is the tutorial I remember following. It's nicely broken down and the stages are well explained - and it leads to a working example (open lots of browser Windows to see it working).
http://code.tutsplus.com/tutorials/real-time-chat-with-nodejs-socketio-and-expressjs--net-31708
You might want to check out what codeschool has to offer... https://www.codeschool.com/courses/real-time-web-with-node-js They have great content and an easy to learn interface for newbies.
I'm thinking of developing a Windows Phone 7 application using PhoneGap and have a few questions around functionality available. I haven't developed a WP7 application before nor used PhoneGap so forgive me if some of the answers to these questions are obvious.
Does PhoneGap support the capability to update HTML/JS/CSS/Images hosted by the WP7 app? I imagine it's possible to easily download new content, but whether one can update or extend the existing files PhoneGap is using for the application is not clear. Given that the application functionality will be primarily driven by HTML/JS, I assume it's possible to download updated HTML/JS asynchronously and update the content on the device. In effect, this would be tantamount to updating the application without downloading a new version of the application through the MarketPlace. Assuming this is possible, what are the chances that an application which does this will pass the application verification process?
Are there any specific restrictions/guidelines that one should pay more attention to when developing an application using PhoneGap? I doubt there are but it would be helpful if anyone has any specific advice in this area.
Any help would be appreciated.
1) The short answer is yes.
The long answer is that you will need to do some native (in this case C#) dev to make that happen. I don't know the specifics of PhoneGap, but I know you can call C# methods from the JS. So you would call a method to download the data and store it in the IsolatedStorage, and then maybe have a callback to the JS to let it know it's done. Otherwise, there may be a way to download the image in JS and pass it to the code behind, but unless the PhoneGap guys have specifically catered for this scenario then I highly highly doubt it.
1.2) Yes, this will pass cert just fine. It is not up to MS to determine how/why/when/where you get your content. They don't make any money out of you updating an app, so they won't care whether you work out your own content delivery system.
2) Maybe not exactly the answer you are looking for - but if you make an app in PhoneGap, or any other non-native way, the app-gods will strike you down. To put it simpler, PhoneGap and everything like it is crap. Not the actual framework (I'm sure they put a lot of work into it), but the results. Seriously, the moment you run a non-native app you can tell how terrible it is. I don't know how to stress this enough. It's really worth developing it natively to every platform.
Newb here learning rails... any advice/comparison of community engine v. social stream? I'll be writing a dating site, so especially if either lends themselves to that development I'd appreciate the advice.
I have tried CommunityEngine in the old days. Currently to use it with rails3, you will have to use a specific branch mainly updated by the community to make it stable. i'm not sure if that rails3 branch is production ready yet.
I don't know community engine, but have been looking at social stream and it looks very well put together.
We upgraded social stream to a mobile platform by exposing api end points - it took a couple of months. We built separate controllers for each call rather than modifying the core classes. The platform is now flexible enough to cater for any use case and we can hook in to updates on the trunk. It's really well thought architecture and has had iterations of refactoring. (I think the webviews / javascript is a bit of a mess though)
I suggest you have a look at this - it took my tech lead a couple of weeks to be comfortable with this.
https://github.com/ging/social_stream/wiki/Social-Stream-Base-database-schema
WRT communityengine - I abandoned this over 4 years ago.
https://github.com/jdp-global/communityengine/commit/31f9b267706157a63bfc103a290bd6e3d874066a
Any platform you choose needs to have a focus on APIs / web services.
I've been reading about Node.js and doing some tutorials, and so far I'm liking it a lot, however I've been trying to find ways to implement it on an online server and so far I haven't found anything, is there any way to do this? Should it be installed the same way I installed it locally but on the online server?
Currently you need a VPS and setup Node like you would do it locally, you should also take a look at this article on how to make sure that your Node.js process runs all the time.
There are a couple of easy solutions coming up though:
Heroku, has announced a closed beta for Node.js support last April, but since then there haven't been any updates on the topic.
Joyent (which recently announced to support Node.js development) also has a closed beta at the moment, but it's full.
Last but not least, there's Nodejitsu, also in private beta at the moment, I don't have any further information on their status though.
As for when those three go public, no idea, but I guess Joyent will be the first to offer their service.
So, right now you'll have to go with the VPS solution and a hoster of your choice.