In the past the widget HTML5 player API was not accepting sound clean friendly URLs,
only with a track ID.
But now when I try it, it seems that it does works fine, but I don't see it mentioned anywhere in the official blog or something.
So my question is: is it safe to use it please?
Using:
http://w.soundcloud.com/player/?url=http://soundcloud.com/user-name/track-name
Instead of:
http://w.soundcloud.com/player/?url=http://api.soundcloud.com/tracks/13692671
And also if you got any status of fixing the serious bug where the events are not firing, I will love to know please.
The events should be all firing properly now.
Yes, you can use friendly URLs, however, as we have to resolve them on our side, initial load of the widget will be a tad slower. So for the faster loading it is still recommended to use API URLs.
Related
I want to track the users live position using Flutter while the App is not running. I found a Tutorial on Medium explaining how to do this but I could not wrap my Head around it neither get the sample code to run. Are there any samples Apps I can use to see how it is done using Background-Process or are there any other Ressources I could use to make this happen?
I already tried to follow a Tutorial explaining how to implement this using a Background-Process but the Sample could would not run.
I would like to monitor the live location and call a callback when the position changes.
I think that this is the biggest limitation in Flutter, yet.
I've implemented a background service, but, I have to write all my way down in native code, and it's painful, I mean, it's painful if you don't have any experience in it.
The only way I managed to make a background service (to send push notification), and I believe, in your case, to track user's location, it's to find examples written in native code.
yea, the title pretty much sums it up. Is it allowed for an app to access ressources on api-v2.soundcloud.com?
Is there any documentation for it?
Relevant since I'm currently working on a soundcloud app and I just recognized that most of the calls on the websites itself are done with api-v2. The responses from the server would be extremly helpful to build some kind of infinite streaming which is the feature I like most about soundcloud.com.
I cant speak for SoundCloud, but gryzzly (a former SoundCloud engineer) stated in a previous answer:
Letting you know, that using undocumented APIs is not going in line with the our developers’ Terms of Use.
Does History.back() work in a GWTTestCase?
I have tried verifying the current token immediately after History.back() call and also after a delay using a Timer but it doesn't seem to change. The onValueChange() method doesn't seem to be called either.
I did a Google search for the issue and found a few posts that suggest others have experienced a similar problem but some are dated 2010. I did find one post where Thomas Broyer responded to one person that he observed the same but I am unable to find that post again.
Has anyone had success in testing code involving History.back() from GWTTestCase? If so, I am most likely doing something wrong. If it is a known issue or intended behavior I would appreciate knowing that so that I don't spend any more time on this.
Judging by GWT's own tests, it should work, but maybe has quirks.
I want to build simple web based app, where users, for example, could push the spacebar button, and then do something further, like answer a question, and while other users at the same time only sees that this question is not available any more for answer. When user submits answer, everyone see it.
All right, here is an example. I have seen TV shows, where four players have one button, if one or two of them know answer, they hit a button, and one lamp turns on and the first is allowed to answer, while other keeps their mouths shut. I want to build the same idea, but in the web.
But problem is that, I don't know where to start, what keywords I should search for help on google and so on. I see, that it might work on HTML5, maybe JavaScript and so on.
I have idea using Ajax, but request it every second to get latest actions made seems rubbish. Also I found one service called Pusher, but it has limited users in one time, which doesn't fit my needs.
I need just ideas. Thanks.
Before you read the rest, a disclaimer: I work for Realtime.co but I do believe I can help here so I'm not trying to "pitch a sale".
You can check out Realtime (www.realtime.co). It's basically a set of tools for developers to use real time technologies on their projects. It uses websockets but does fallback to whatever the user's browser supports (such as long polling, for example).
Behind Realtime you have a one-to-one/one-to-many/many-to-many messaging system that will transport your messages to and from your users.
There's also a plus which is the fact that the Realtime framework is actually cross-platform. This means that you can even have your web users communicate with iPhone users, Android, users, Windows Phone, desktop applications, server applications, etc..
You can learn about the JavaScript API here: http://docs.xrtml.org/getting_started/hello_message.html#javascript.
You only need to register at Realtime.co as a developer and start using the free license.
I really hope that helps.
Okey, I think I will go with node.js.
Writing all this previous post, made me think in right way :)
I'm trying to plan out an application on the iPhone/Android that could be used to track dates/locations of events and update them as necessarily but I really have no idea what kind of method I should take.
Currently, there's two ideas for methods in my head:
1) Make a mobile webpage/website that could be updated with the necessarily information, then display this particular webpage/website on the App for users to view.
2) Make an app in iOS/Android to do the above without displaying the webpage at all.
The first idea is the easiest for me to grasp, since I roughly know the procedures of setting this method up. Displaying the webpages on a iPhone/Android screen should be relatively easy and this also allows me to only update the webpage with the latest information and all without (hopefully) building some kind of update system for the app itself.
The second idea is probably the better of the two, since I can make use of all the nifty features in the iOS/Android to make some pretty cool (what are the cool things, i don't know yet) things. I'm not exactly experienced in the field of creating apps, and I really have no idea how to start some kind of self-update functionality on an app, seeing all the apps I've done thus far are offline-based apps that does not communicate with anything save for local files. Should I get the App upon startup to download a file (XML or whichever?) to "read" the contents then update as necessarily?
Or should I just go for the first method, since it can be more efficient than the second one?
I'm really lost here, can anyone offer some tips and advice?
I believe that the first approach is a good one but I would suggest the following:
1- Create the website that will do all the business in your mind then
2- Port out the application in an easy way to be a mobile application how? Please have a look into this http://www.appcelerator.com/
3- Another idea that would save you the pain of going into all the above is to create a facebook application, this way you can make use of the facebook infrastructure and you will have the viral effect as I guess thats what you are looking for.
I hope I've introduced a good tips for you.