Skip to content

LiveSync support #523

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
teobugslayer opened this issue Jun 4, 2015 · 5 comments
Closed
2 tasks done

LiveSync support #523

teobugslayer opened this issue Jun 4, 2015 · 5 comments
Assignees
Labels
Milestone

Comments

@teobugslayer
Copy link
Contributor

We will be enabling LiveSync support for NativeScript application and we plan to roll this out in a couple of stages.

v1.2

LiveSync commands

  • livesync - This command will update all your app files and will restart the app on the device.
  • livesync --watch - This command will watch for file system changes, sync only the changed files on the device and finally restart the app after the sync.
    In the 1.2 time frame we plan to have first-stage LiveSync implementation. To work, it will restart the application.

Technical details

  • The following location will be used for storing and updating the app files:
    • Android - /data/local/tmp/...and /data/data/....
    • iOS - ~/Library/Application Support/LiveSync.
  • We need to restart the app in order to guarantee that the application state will not be corrupted. This is highly critical on iOS because it relies on singleton instances of many application level objects.
@teobugslayer teobugslayer added this to the 1.2.0 milestone Jun 4, 2015
@ligaz ligaz changed the title LiveSync support for 1.2 LiveSync support Jun 5, 2015
@Fatme Fatme self-assigned this Jun 22, 2015
@NathanaelA

This comment was marked as abuse.

@ligaz
Copy link

ligaz commented Jul 16, 2015

Thanks for your feedback @NathanaelA. Here are my comments:

  1. Saving the current frame might work for some applications but will not work for others that depend on state. For example imagine an app that has a login screen. The ideal case will be for users to specify what kind of sync they want: restart, refresh (hard reload) or reload.
  2. That will be a good optimization we can apply in one of the next iterations. I have added it to the list.

@NathanaelA

This comment was marked as abuse.

@ligaz
Copy link

ligaz commented Jul 17, 2015

Yes this feature is already available in master and the v1.2 scope for will be publicly available when we officially release v1.2.

@nmladenov
Copy link

reopening due to these issues: #654

@ligaz ligaz modified the milestones: 1.4.0 (Under review), 1.5.0 Sep 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants