[TIMOB-20417] Hyperloop: Expose builtin utilities
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Done |
| Resolution Date | 2016-08-04T02:44:52.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 5.4.0 |
| Components | Hyperloop |
| Labels | hyperloop, metabase |
| Reporter | Hans Knöchel |
| Assignee | Hans Knöchel |
| Created | 2016-02-17T12:43:36.000+0000 |
| Updated | 2016-08-04T02:44:53.000+0000 |
Description
To support Hyperloop modules, developers need to access common Ti-utilities like we already do with
TiApp. Common used classes:
- TiUtils
- WebColor
- WebFont
Problem to discuss is also: What do we do for existing modules that want to be migrated to Hyperloop? They often rely on existing proxies (although not recommended).
From yesterday's discussion with [~penrique]: Because we want to replace the Ti-core with Hyperloop sooner than later, we should rewrite the common built-in classes needed for modules using Hyperloop instead of exposing proxies to Hyperloop. So renaming this ticket to "Hyperloop: Expose built-in classes and utilities". /cc [~ingo]
Update here: Got some important builtins in place (utils, webcolor, webfont). We need to find a good place for those to be accessible without copying them over everytime. I think of [this directory](https://github.com/appcelerator/hyperloop.next/tree/master/metabase/ios/templates/builtins) but without further metabase-processing, just make it possible to use it with
require("builtins/utils")etc.Pushed the current utilities to https://github.com/appcelerator/hyperloop-utilities, where we plan to manage all (both open-source and company-provided) utilities. We may think of packaging some of them into the hyperloop-module-template as well, but for now, developers are able to grab the utilities they need and thats cool!
Changing issue-type to
Story, since there is not much to test, yet.