[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ease-dev] Introduction
|
Hi,
you are already thinking about all those different use cases, which may
happen, good. In fact the process for changing scripts is much simpler
so far:
On 11.03.2017 20:03, Utsav Oza wrote:
Hi Christian,
If the user wants to edit the script fetched from remote repository
from the Script Explorer, how those changes should be synchronized
considering the script on the remote repository remains unchanged? I
suppose we might then need to allow users to save and commit those
changes depending on the system (eg. GitHub, Gerrit, or SVN) locally
and push it to their remote repository. Can we consider this as a way
to synchronise the edited scripts to their respective remote locations ?
Scripts - even from remote locations - can be opened in an editor. This
is simple as we always can fetch content. If the script comes from a
remote location, we do not allow to store it directly. A user has to use
'save as' and store it to the local file system. If it should still be
part of the registered scripts, the user also needs to register the
local folder where the script got stored to. Then he will see duplicate
names in the script explorer and needs to deal with that topic too. So
remote scripts are not intended to be changed by the user. At least not
with the means of EASE.
And if the local and remote scripts are changed simultaneously from
different sources, while executing should the preference be given to
the changes made to remote scripts than the those made to local
scripts, (thereby discarding the local changes made to the scripts)
because user may want to test his/her changes before he wants an
updated copy from remote ? If this is the case then a typical flow to
try out local changes made to the scripts from script explorer would be:
1. make some changes to the scripts locally
2. commit and push it to remote location
3. execute it from script explorer (that fetches fresh scripts when it
is executed if some new commit hashes are found on those scripts)
We do not fetch for changes on each script execution. For remote systems
we use an interval and a background job to check for updates. Users may
also trigger a manual refresh from the script explorer view.
This might apply even for small changes made from script explorer.
Please do correct me if I am wrong.
Basically, since we are saving the external script files on our own
(for filesystem and workspace locations), same thing should apply to
the remote locations.
EASE is not taking care about editing script files. If the IDE can do
it, fine. If not we do not provide any special means. There is some
exception to this rule as we allow users to change the keywords in the
script header. They get persisted in a local file similar to preference
settings.
Christian
