GoZync5

Separation Model

GoZync5.SeparationModel History

Hide minor edits - Show changes to output

November 04, 2014, at 07:12 PM by 98.245.117.26 -
Changed line 7 from:
In your local files the work is done in GoZyncMobile so there are no layouts to add; the scripts you add are interface-type scripts (the scripts for your sync buttons, for example) and those belong in the interface file.
to:
In your mobile files the work is done in GoZyncMobile so there are no layouts to add; the scripts you add are interface-type scripts (the scripts for your sync buttons, for example) and those belong in the interface file.
June 12, 2014, at 01:44 PM by 50.132.85.96 -
Changed lines 3-5 from:
Yes. In fact it can be quite nice to Zync separated systems as you can use GoZync to deliver new builds of your interface files, clobbering the versions already on your users' devices.

Since all the work of GoZync is done in GoZyncMobile, there are no issues unique to separated systems.
to:
Yes. In fact it can be quite nice to sync separated systems as you can use GoZync to deliver new builds of your interface files, clobbering the versions already on your users' devices.

It doesn't matter where you put the scripts and layouts you'll add to your hosted file--you can add these to the data file or the interface file. You may want to put the code in your data file if you have only one data file as that would mean you could sync without opening your interface file, which is undoubtedly faster. If you have more than one data file you'll want to add these scripts and layouts to your interface file so you can access all your data files from one place.

In your local files the work is done in GoZyncMobile so there are no layouts to add; the scripts you add are interface-type scripts (the scripts for your sync buttons, for example) and those belong in the interface file.

GoZync's required fields don't need to be added to your interface tables, just to tables you want to sync
.
June 30, 2013, at 06:42 PM by 50.132.84.245 -
Changed lines 5-9 from:
!! Where do the sync layouts go?

The easiest thing to do is put them in the data file. Then GoZync even know your solution is separated and there are no issues.

But, you can put the sync layouts in your interface file if you wish. You'll just need to change two scripts, one in GoZyncMobile and another in GoZyncHosted. You'll find instructions for modifying these two scripts %newwin% [[http://www.seedcode.com/support/viewtopic.php?f=38&t=3782 | here]]
.
to:
Since all the work of GoZync is done in GoZyncMobile, there are no issues unique to separated systems.
June 30, 2013, at 06:41 PM by 50.132.84.245 -
Changed lines 3-4 from:
Yes. In fact it can be quite nice to Zync separated systems as you can use GoZync to deliver new builds of your interface files, clobbering the versions already on your user' device.
to:
Yes. In fact it can be quite nice to Zync separated systems as you can use GoZync to deliver new builds of your interface files, clobbering the versions already on your users' devices.
January 04, 2013, at 03:12 AM by 50.132.84.245 -
Changed lines 3-9 from:
Yes.
to:
Yes. In fact it can be quite nice to Zync separated systems as you can use GoZync to deliver new builds of your interface files, clobbering the versions already on your user' device.

!! Where do the sync layouts go?

The easiest thing to do is put them in the data file. Then GoZync even know your solution is separated and there are no issues.

But, you can put the sync layouts in your interface file if you wish. You'll just need to change two scripts, one in GoZyncMobile and another in GoZyncHosted. You'll find instructions for modifying these two scripts %newwin% [[http://www.seedcode.com/support/viewtopic.php?f=38&t=3782 | here]].
January 04, 2013, at 02:54 AM by 50.132.84.245 -
Added lines 1-3:
!! Does GoZync work with separated solutions?

Yes.
(855) SEEDCODE
[email protected]
Follow us: