search

montegoulding / lcVCS

Stackfile export/import for VCS support in LiveCode
http://goulding.ws
GNU General Public License v3.0
13 stars 10 forks source link

Build completely new Stack on Import #2

Closed Tate83 closed 10 years ago

Tate83 commented 11 years ago

Hi Monte,

I gave it a few more tries regarding "Import a .vcs into a new stack" but I did not succeed. My idea is that you open a new empty mainstack and then drag&drop the .vcs folder onto the Import symbol and click the button. lcVCS then imports the data into a completely new stack. This makes opening the "original" stack and then clicking "import" unnecessary since I find this rather confusing because if you do this way of importing you cannot really see a difference between the original (that was closed) and the imported vcs stack.

I tried editing the Import function to find a way to do this but did not succeed yet..

Regards, Pascal

montegoulding commented 11 years ago

I gave it a few more tries regarding "Import a .vcs into a new stack" but I did not succeed. My idea is that you open a new empty mainstack and then drag&drop the .vcs folder onto the Import symbol and click the button. lcVCS then imports the data into a completely new stack. This makes opening the "original" stack and then clicking "import" unnecessary since I find this rather confusing because if you do this way of importing you cannot really see a difference between the original (that was closed) and the imported vcs stack.

I'm not sure what you are trying to do. Are you trying to import a stack and keep the original open? You can't do that because of stack name conflicts. You don't need to open an empty mainstack before the drag and drop of the vcs folder.

Tate83 commented 11 years ago

Sorry for my explanations, must be confusing.

If I just open LC 6.0.2 without any stack loaded (except lcVCS) and then drag my .vcs onto the import button and click import, it should import the vcs and build the stack, right?

Because when I do this, nothing at all happens. The only time the VCS stack is actually imported is when the original stack (that was exported using lcVCS) is already open and is then replaced by the imported version.

montegoulding commented 11 years ago

Because when I do this, nothing at all happens.

OK, there must be an issue in there somewhere.

montegoulding commented 10 years ago

I'll close this now that lcVCS 1 is in beta. The UI is completely different now and based on a lcVCSProject.json file controlling what to import.