camac / Swiper

Swiper Metadata Filter for Domino Designer Source Control
Apache License 2.0
16 stars 5 forks source link

Files aren't filtered unless Automatic Import / Export is selected #3

Open codemasonnet opened 9 years ago

codemasonnet commented 9 years ago

I have automatic Import and Export of data to and from ODP switched off. I also have Build Automatically switched off.

I have an existing NSF/ODP that I have applied Swiper to (1.0.1). When I "Sync with ODP" via Team Development right-click menu, the code is synced but not filtered. I can get it to filter if I right-click the individual element and apply the filter, but would rather not do that. I am not sure if this is how it is designed to work.

camac commented 9 years ago

Hi Rob, Unfortunately at the moment Swiper will only work automatically when Automatic export is switched on. I didn't think about this when I recorded the video, but now I realise I should have mentioned this.

It is due to the way the standard Designer Source Control plugin works. The standard source control sync can run via 2 different mechanisms

  1. The Automatic Export / Import which is triggered during a 'Build'
  2. Deliberately 'Synced' using the 'Team Development -> Sync with On-Disk Project'

If the project is synced using 1, Swiper is able to monitor the files. If the project is synced via 2, there is no way for Swiper to get involved due to the structure of the current standard Designer Source Control plugin

There are a couple of ideas that I could do

  1. Provide a 'Swiper -> Sync With On-Disk Project' option which will do the same as 'Team -> Sync With on-disk project' but will additionally filter any files modified during the sync.
  2. Provide a 'Swiper -> Filter Project' which just does the same as 'Swiper -> Filter Selected' but for every file on the project
  3. Ask IBM to open source the standard plugin and I can fix it all there!

For the current version the only fix would be to enabled automatic export.

Just for curiosity what is the reason for disabling automatic export and Build Automatically?

Cameron

tinusriyanto commented 9 years ago

Adding my own experience here since I also get this problem. I turn off auto export because I don't want my Working Files to contain code that might have compile / run time error. I save often as I code and I only want the finished version to be exported to ODP. I turn off built automatically since I do Notes Classic development most of the time and it is annoying to have designer suddenly crawl into a halt because there is an automatic built running.

Tinus Riyanto

codemasonnet commented 8 years ago

Thanks for that Cameron. Options 1 or 2 would be superb. Will see if I can find the right person to lean on for number 3.

I use the setup described for the same reasons as Tinus.

Ta

edm00se commented 8 years ago

I generally leave Build Automatically off as well, as our largest app is so large that my DDE essentially just constantly processes.

I would love to see the ability for the option of 'Swiper -> Filter Project' and Swiper version of 'Team Development -> Sync with On-Disk Project' as @camac described.