Now that W3C have officially deprecated the GeoLocation API
How long do we have before our existing navigator.geolocation code stops working?
Is there some feature/API retirement that we can refer to as an example?
Most importantly who approved this? #GeoLocationIsNotaSensor! Sorry I take that back, MOST importantly who ask for a GeoLocation Sensor?
There is no mention of deprecation whatsoever in the page you linked to.
What this warning box says is that the specification of this API has been moved to an other working group, Geolocation Sensor.
So given they even created an entire working group for this API, I'd bet it's not going to get away of browsers' implementations any time soon, but future can prove me wrong...
Related
I'm trying to lift all the User IDs that match a segment in Adobe Analytics and store them somewhere (anywhere really), so I can then feed them into an action system for targeting.
Documentation seems hard to find - anyone have ideas on how I could achieve this?
Not sure if there's APIs or SDKs that let me pull this data, or pre-built connectors into something like Google Sheets, but again documentation seems light at best.
The simplest tool to use would likely be the Report Builder. It's an Excel extension by Adobe to export the data. It's pretty powerful. Can do pretty much everything AA can.
You could also generate data feeds and ETL the data from there to wherever you need it. It's a bit more advanced though.
Finally, you have the customer journey API, which would now be an even more advanced level of ETL.
Otherwise, yes, Adobe is notorious for how bad their documentation is and how hard it is to find it. It's almost like they don't want the good documentation to be there in order to sell more of their certification courses.
Note that sometimes when you google something and get to their forum to see the answer, Adobe will attempt to hide the answer behind the authentication wall. Just open that link in incognito and you'll be good. Adobe is pretty weird.
I'm learning ReasonReact and I would like to fetch data from a API, that I'm going to use on my component. However, on the official website about Reason or ReasonReact there's nothing about this, neither I found something searching on Google. How can I do it?
You can use the existing bindings to HTTP client libraries, e.g.:
https://redex.github.io/package/bs-fetch
https://redex.github.io/package/bs-axios
The former works in browser only, the latter works in both browser and Node.
In general, if you're looking for a way to do something, Redex is a great place to look.
I'm using the Facebook iOS SDK for a project and if I pop a UIViewController after doing a request but before receiving an answer I get an EXC_BAD_ACCESS when it tries to see if the delegate responds to a selector. Well, the delegate is the UIViewController already popped so it probably doesn't exist anymore.
When researching about this issue I stumbled upon this answer here on SO which tell me I shouldn't be having this problem since the delegate is retained. But the answer is a little old and they started to use arc after that. So I checked the SDK and noticed their not retaining it anymore.
Is this a known issue? Am I missing something here?
I tried modifying the SDK and retaining the delegate and the problem disappears. Nevertheless I don't like modifying third-party libraries as I don't have that much expertise and I'm not sure if arc is really a problem in this situation (I thought we didn't need to use retaing/release/autorelease anymore). Also, I thought this being Facebook SDK, if it were a bug someone should already stumbled upon the same problem and solved it.
EDIT: I realize now that at least the version I'm using of the Facebook SDK is not using arc (I don't know if they already support it) and the problem may be this:
#property(nonatomic,assign) id<FBRequestDelegate> delegate;
Shouldn't it be retain?
EDIT2: I'm sorry, I skipped through another answer in the same post linked earlier.
It seems what I pointed out is now obsolete in newer versions of the SDK. The best approach seems to be to cancel the request.
Shouldn't it be retain?
Absolutely not. If you did that then you'd very likely have a retain cycle (VC owning the FBRequest which owns the VC).
You're 100% correct that the right thing to do is cancel the request when the view controller is deallocated, or probably even better is to set the delegate of the request to nil and then cancel it.
I’m wondering why no web browser supports the XInclude standard for XHTML.
This standard exists for almost five years, and I think it would be very useful for the web.
For example, you could XInclude the static parts of your web site, such that the browser will only need to download the part which have changed when the user is browsing the site. Moreover (but I may be wrong) this does not seem to be very difficult to support, in comparison to standards like SVG or MathML.
(sorry for this question without real answer, I will not mind if it is closed)
There is an old open bug on the Mozilla bug tracker asking for XInclude support with a patch in which some problems are discussed:
a satisfactory XInclude implementation requires XPath, XPointer, xml:id and other specs to be implemented first,
most of the time XInclude can be simulated by the document() XSLT function,
loops must be detected and this is hard to do,
it is not well understood how the DOM changes made by XInclude's documents should be encapsulated into events and propagated.
Running an MVC2 site against IIS7 and would like to capture more detail of how users traverse the site - ideally to the point of being able to replay even the duration between mouse clicks - feedback of where people pause and/or backtrack.
I could do this with flash but that's no longer an option. Now it's just IIS7 via asp.net f4. IIS7 _should be able to provide this via 3rd party extensions - especially for this sort of niche need. I'm willing to consider client-side .net components but this sure seems to be the responsibility of the server.
[opps...does this belong on serverfault?]
thx
justSteve. Here is a solution that we have used:
http://www.seevolution.com/
I don't think that it gives time between clicks, but it does give very detailed tracking considering it's price (I don't know if that's an issue). We have really liked it. Fantastic detail.
You could also roll your own solution. Using jQuery and the $(document).click() function, you can log when they click, and the points on the screen. Then every couple of minutes, serialize it and fire it off to the server. You can get extremely fine-grained detail that way. The nice thing with seevolution is that they've done all of the work for you already, but it probably isn't as detailed as you would like.
JMax
Maybe not the "in-house" solution you're after but we are about to implement SessionCam at my company, which seems like a pretty good match for what you're looking for. Not having actually finished implementing it yet, I can't vouch for it in terms of quality at this point - but the description of the product certainly matches.
You aren't going to be able to capture the level of detail you need using a solely server-side solution. There needs to be a degree of client-side work - whether it's in flash or javascript - to capture things such as where the mouse is hovering (for heatmaps etc).
I personally haven't used this product, but a friend of mine spoke highly of it.
Clicktale