[TIMOB-9938] Tooling: Remove Yahoo and Facebook modules from core
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Low |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | Release 2.1.0 |
| Fix Version/s | n/a |
| Components | Tooling |
| Labels | core |
| Reporter | Bill Dawson |
| Assignee | Unknown |
| Created | 2012-07-11T12:57:04.000+0000 |
| Updated | 2018-02-28T20:04:17.000+0000 |
@NEERAJ: Is our goal to make it such that no code changes will be required at all by a Titanium developer using these modules? I.e., should we still treat them as "internal" modules rather than external modules from the perspective of a developer using Titanium? Our cloud stuff (for example), though packaged in the SDK, is treated as _external_, meaning a developer using Titanium needs to use
require, likevar cloud = require("ti.cloud");. So using Yahoo as an example, current code (by a Titanium developer) looks like:Do we want them to continue to use it that way, or is it okay to make them switch toTi.Yahoo.yql("SELECT ___ FROM ___ WHERE __", function(e) {//callback});requiresuch as:The latter is a) easier for me; b) a cleaner separation; c) makes it clear that yahoo/facebook not part of core. The former is simply easier for our customers/users, of course.var yahoo = require("ti.yahoo"); yahoo.yql("SELECT ___ FROM ___ WHERE ___", function(e) {//callback});I think given that we are already moving facebook out of core in 3.1, this ticket may be invalid.