Organization: One vs Multiple Projects For a Single Client

[Felipe_CRM]

Continuing the discussion from Connect Sessions through iframe:

I could have sworn there was a thread that discussed this but couldn't locate it, maybe I wasn't hitting it with the right keywords.

What's the main concern for 1 vs multiple projects? I can think of a few to start:

• more work on the developer to keep things organized and reduce unnecessary repetition
• more overhead
• more loading screens as the end user jumps between projects.

The only potential issue I saw with one big project was with a certain large and poorly designed Vision project (dozens and dozens of nearly-identical windows) and the poor designer would always freeze up for a few seconds just opening up the Project Tree.

[Felipe_CRM]

Stumbled on a couple of related topics while going down the link rabbit hole today:

Switching between Ignition Perspective projects

I have a question about switching between Ignition Perspective projects. Below is my example: I decided to divide the project into parts that is, into several projects. For organizational reasons it is easier for me to manage SCADA in this way to make modifications easier. Let's say I have one frontend interface on which a user logs in. I would like the interface window to show the selected production line. Similar to the principle of embedded view but from another project, let's call it embe…

Project Structure Management: Best practises

An architecture to consider: Possibly expanded as described here: The key is to push well-tested resources towards the root of the hierarchy so they can be shared. It can also be helpful to duplicate projects for development work, and then send the updated resources (via export...send to project) in a batch back to the original project. Similar to making git branches, but can be done with or without git. (Delete the duplicate project immediately after its resources are merged where intend…