Feature request - edit/save Project Importer topics

[sdcinvan]

Hello all,

I am often finding that I need to open a second copy of Flare (the master document) in order to make small edits to its master documents. It would be nice that when I open a topic copied by Project Importer, I am offered the option to save any edits back to the source topic.

I have mocked up the option that I would like to see, here (in red):

Changing source topics.jpg

By selecting my suggested option, "Continue with edit(s) and save to source topic.", I eliminate the need to open the Flare master document, edit the topic and then synchronize the topic between the parent and child projects...thus, saving time and effort.

I submitted this as a feature request.

[Robotman]

Great suggestion. The file is already connected so it shouldn't be difficult to push it back to the original.

I wonder if it's connected to Source Control whether that would make a difference?

[sdcinvan]

Great suggestion. The file is already connected so it shouldn't be difficult to push it back to the original.

I wonder if it's connected to Source Control whether that would make a difference?

Thanks Gary,

I just thought that it made no sense that Flare could not push a changed child topic back to its parent, on demand. This is especially annoying for me because some of my parent topics require relatively frequent edits.

[wclass]

As long as it is an option. Your suggestion makes sense for solo authors, but in a team who share files, I'd rather others weren't randomly updating topics that I use in my project. We use Project linking to try to keep things more standard and avoid the ad hoc changes.

If that option were allowed, I'd need to have a flag somewhere that prevents uploading from child projects - don't know how that would work.

[Robotman]

As long as it is an option. Your suggestion makes sense for solo authors, but in a team who share files, I'd rather others weren't randomly updating topics that I use in my project. We use Project linking to try to keep things more standard and avoid the ad hoc changes.
If that option were allowed, I'd need to have a flag somewhere that prevents uploading from child projects - don't know how that would work.

Agreed, Margaret. I wonder if changes could be flagged somehow and accepted or dismissed or modified (similar to manual resolve process when using source control) by those who maintain the GPL project.

[wclass]

I like the flagging option - I am happy for people to suggest updates, and then do the work so that makes sense, but updates have to be controlled..
Therefore I think in the parent, or template project, there would need to be a setting that allows updates, prevents updates, or has a flag to monitor/accept/reject changes.
And continuing on from that, when you import one of these controlled projects, the import should let you know that "this project is controlled for updates/allows updates, whatever".

[sdcinvan]

As long as it is an option. Your suggestion makes sense for solo authors, but in a team who share files, I'd rather others weren't randomly updating topics that I use in my project. We use Project linking to try to keep things more standard and avoid the ad hoc changes.

If that option were allowed, I'd need to have a flag somewhere that prevents uploading from child projects - don't know how that would work.

Excellent point and certainly possible to implement either arithmetically in Flare or by setting Network folder permissions accordingly. That is, if the parent topics are read-only to staff, selecting my proposed update topic option would result in a read-only error. Flare would just need to be coded to gracefully handle read-only errors.