** User Story **
As a user, I want to zoom in and out, so that I can look into specific area smoothly and big picture as well.

** Acceptance Criteria **

• in big picture state, I want to see the nodes minimal without details.
• zoom in and out should be happened around mouse position
• It should feel good and smooth with appropriate speed according to current zoom level (Obsidian)
• it should work everywhere
• ability to fit all to the window
• zoom into the selected node when we edit it in big picture state
• zoom In should be done maximum to 2 and zoomOut to 0.35

** extra acceptance **

• #57
• zoom into should be animated
• Aggregate successive wheel events

When the app is in minimal state, animate the zoom In.

Cancelation of colorDialog is not working

Describe the bug
Sometimes it's not working. Test more pls

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Software Versions
Application version: (add either official git release version or git SHA)
Firmware version: (add either official git release version or git SHA)

Additional context
Add any other context about the problem here.

Steps to reproduce the issue:

1. Open the application.
2. Create a node, excluding the 'general node' type.
3. Utilize the clone feature to duplicate the node.
4. Observe that the duplicated node icon does not reflect the node's properties and remains the same as the 'general node' icon.

Instructions to reproduce the issue:

1. Launch the SituationSimulator (Or NodeLink example)
2. Create a minimum of 20 nodes (No need to establish connections between them).
3. Attempt to rapidly zoom in or out using the 'Ctrl + mouse wheel' combination.
4. You will likely encounter an unpredictable crash occurring consistently during the zooming process.

The repeater instantiates all the delegates with every change in the model data. We should customize a repeater so that only modified items will be instantiated.

Describe the bug
We need to be able to have access to equation of all link types. Currently the LType line is impossible to have access to equation type.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Software Versions
Application version: (add either official git release version or git SHA)
Firmware version: (add either official git release version or git SHA)

Additional context
Add any other context about the problem here.

Though the cloned objects are selected in code, they are not selected in run time

Describe the bug
NodeView class is very big. Some parts can be encapsulated into smaller objects.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Software Versions
Application version: (add either official git release version or git SHA)
Firmware version: (add either official git release version or git SHA)

Additional context
Add any other context about the problem here.

** User Story **
As a Developer, I want to design a icon so we can use it for branding

** Acceptance criteria **
A logo for the project is required to help its branding.

• vector graphics like svg
• multiple design for different sizes
• use 'N' and 'L' letters and have the concept of the library
• minimalistic

UserLinkView class should be cleaned and refactored.

Steps to reproduce the issue:

1. Start the NodeLink example project.
2. Perform various actions, such as creating new nodes/connections and moving them.
3. Attempt to undo some of these actions.
4. Observe that the view remained fixed on a point rather than following the modified item.

Expected behavior:
The view should maintain focus on the modified element rather than resetting to a fixed point. This ensures that users can easily identify the changes made.

As a game developer, I want to incorporate a user-friendly "Suggest Text" feature into our software, similar to what is used in NPC dialogue systems, to streamline and enhance the process of generating in-game dialogues.

Acceptance Criteria:

• When the user accesses the software, a "Suggest Text" option should be prominently displayed within the node editor. (We can add a new option to the node options)
• The "Suggest Text" option should be accessible for the Step nodes only.
• Upon clicking the "Suggest Text" option, the software should open a user-friendly prompt, asking the user what specific aspect of the dialogue they would like suggestions on.
• After selecting the option, the user should be able to interact with the integrated ChatGPT system seamlessly, just like using a ChatGPT interface.
• The software should display generated suggestions from ChatGPT in real-time as the user interacts with the system.
• For any suggestion that the user finds suitable, there should be a clear and intuitive "Insert" option that allows them to easily incorporate the suggested text into their dialogue.
• Users should have the ability to customize and edit the suggested text to match their specific narrative or stylistic requirements.

Enable right click for dragging the scene (move scene around). Keep left click for items selection only.

while resizing the nodes from the left corners, if the nodes become in minimum size, then it's impossible to resize it back

The NodeLink/Calculator documentation needs to be revised and updated to ensure accuracy, clarity, and completeness.

A.C:

• Thoroughly review the current NodeLink/Calculator documentation to identify areas that require updates or improvements.
• Ensure that all information related to NodeLink/Calculator is up to date, including features, functionalities, and usage instructions (Update the versions in the doc specially)
• Incorporate diagrams, screenshots, or illustrations where necessary to visually assist users in understanding the NodeLink/Calculator tool.
• Include practical examples and use cases to demonstrate how to use NodeLink/Calculator effectively.
• Maintain a consistent format, style, and terminology throughout the documentation to enhance readability.

Is your feature request related to a problem? Please describe.
Drawing a rubber band rectangle for enabling multiple selection. With left click. (like obsidian)
Also enable multi selection options (tools) same as obisidian

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Firmware change required?
Yes/No

Additional context
Add any other context or screenshots about the feature request here.

While creating a new connection, if the target position is hovered on a port then fix the margin so the connection gets in a better shape

As a user, I want the application to perform efficiently even when a significant number of node connections are added to the project. Currently, when a large number of connections are present, the app becomes excessively slow, impacting my productivity and user experience.

Acceptance Criteria:

• The application should handle a considerable number of node connections without experiencing significant performance degradation. Ideally, the app should remain responsive and smooth even with a substantial number of connections.

• Performance tests should be conducted to determine the maximum number of connections the application can handle without becoming slow.

• The development team should conduct a thorough investigation to identify potential bottlenecks in the code related to managing connections and optimize the relevant sections to improve performance.

• The new approach should have the current features that LinkView supports (e.g. selection/arrow/color/type(dash-dot)/shape)

• The new approach should look smooth and not pixelized.

As a user, I want access to an Overview window that provides a simplified and compact version of the scene. This Overview window should clearly distinguish the visible parts of the diagram from the non-visible areas. By having this feature, I can easily grasp the entire diagram at a glance and quickly comprehend the context of the scene without having to navigate through the entire diagram in detail. This will enhance my ability to make informed decisions and efficiently interact with the main scene.

A.C.

• The Overview window should be easily accessible from the main scene with a designated button or control (It's desired to use the current button groups on the scene).
• When the user opens the Overview window, it should display a scaled-down, simplified representation of the main scene's diagram.
• The visible parts of the main scene should be visually distinguishable from the non-visible areas in the Overview window. This can be achieved through shading, borders, or any other appropriate visual cues.
• The content within the Overview window should update in real-time to reflect any changes made in the main scene, providing an accurate representation of the latest state.
• The Overview window should be resizable, allowing users to adjust its size to their preference.
• Users should be able to interact with the Overview window by panning or clicking on specific areas, which should automatically navigate to the corresponding part of the main scene.
• The Overview window should maintain an aspect ratio that accurately represents the main scene's proportions.
• The feature should be responsive and perform efficiently, even with large and complex diagrams.
• The Overview window should not obscure or overlap with critical elements of the main scene when opened.
• The Overview window should have the option to be closed or minimized, allowing users to focus solely on the main scene when needed.
• If there are any limitations or restrictions in terms of the supported diagram types or features in the Overview window, they should be clearly communicated to users.

change the snapping method or update canLinkNodes so it will not be snapped to the existing links

related to #50

Is your feature request related to a problem? Please describe.
Enable zooming feature by ctrl+wheel

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Firmware change required?
Yes/No

Additional context
Add any other context or screenshots about the feature request here.

User Story:
As a developer I want to have an abstract class for the node view, so I can design my own view according to the data structure.

**Acceptance Criteria: **

• Ability to override the header item.
• Ability to override the content item.
• Ability to override the footer item.
• All the events should be activated by default (Drag, left click, right-click, etc).
• Ability to override the events.
• There should be a default example to show how it can be used

Deleting a node makes app to crash after moving the related code from the popUp to the NodeTools

Describe the bug
After resizing a node, it appears that the ports are still in the previous place.

To Reproduce
Steps to reproduce the behavior:

1. Create two nodes
2. Connect the first node's right port to the second node's left port
3. Resize the first node, from its rightside
4. See error

Screenshots
Before resizing:

After resizing:

Software Versions
main branch

** User Story **
As a developer, I want the NodeLink to be compatible with Qt 6+, so I can use any version for my application.

** Acceptance criteria **

• Compatible with Qt 6.5+ version
• Windos (msvc, mingw, GCC)
• Compatible with Qt 6.4+ version
• Compatible with Qt 6+ version
• Compatible with Qt 5.15.2 version
• Linux (gcc, Clang)
• MAC (Clang)

THe app is eating a lot of rams and also working with it is not that smooth. Profiling is required

Is your feature request related to a problem? Please describe.
Add animated font in zoom IN/Out process in the node view class

** User Story **
as an end user, I want to fix some link issue so I can feel exactly like the Obsidian.

Describe the bug
links have different behavior than Obsidian.

To Reproduce
1- when you press a link port a temp connection immediately created
2- temp connection is above the nodes in z value
3- temp connection is not snapped to the destination port when is near
4- when temp connection is released in empty space and the objects node is shown, mouse movement moves the connection

Acceptance criteria

• 1- the temp connection should be created only if the user moved the mouse after press
• 2- temp connection should be below the nodes in z value
• 3- temp connection should be snapped to the destination port when is near
• 4- when temp connection is released in empty space and the objects node is shown, mouse movement should not move the connection and just can affect the object menu

The scene size is intended to remain fixed.

Instructions for reproducing the issue:

1. Launch the SituationSimulator or NodeLink example.
2. Position 4 nodes at the corners of the scene and 1 in the center.
3. Experiment with zooming in and out, using the maximum level.
4. Occasionally, you may observe extra space being added to the scene, or the scene size may shrink, causing content to be cut off.

As a game developer, I want to be able to add sticky notes to the scene in the application. These sticky notes should serve as a quick and flexible way for me to jot down important information, or comments related to the diagram or project I am working on.
For a suggestion, you can check the windows sticky note.

Acceptance Criteria:

• The application should provide a designated "Sticky Note" tool or option that allows me to easily add a new sticky note to the scene.

• When adding a sticky note, I should be able to click on the canvas or a specific node to position it accurately within the scene.

• Each sticky note should have an editable text area where I can type, modify, or format the content according to my needs.

• The sticky notes should be resizable, allowing me to adjust their size to accommodate different amounts of text.

• The application should support multiple sticky notes on the scene simultaneously, and I should be able to add, remove, or manage them easily.

• Sticky notes should have a visually distinctive appearance, making them easily recognizable from other elements in the scene.

• The application should provide options to change the color and style of the sticky notes, enabling me to categorize or highlight different types of information.

• Sticky notes should support basic formatting options like bold, italic, bullet points, etc., to enhance the readability and organization of the content.

• The application should allow me to move the sticky notes freely across the canvas, ensuring flexibility in organizing and rearranging information as needed.

• The sticky notes should be saved/loaded with the project file.

• The users should be able to connect the sticky notes to the other nodes (by the connections)

As a developer, I want to have an example calculator project included in the project (as a subproject). This example project should serve as a reference and template for creating calculator functionalities using the available nodes. I should be able to add the following nodes to the example project:

Input Number Node (Source): This node will allow me to input numerical values into the calculator.

Operations Node (Additive, Multiplier, Subtraction, etc.): These nodes will perform different mathematical operations on the input numbers, such as addition, multiplication, subtraction, etc.

Display Node: This node will display the output or result of the calculations performed by the operations nodes.

Acceptance Criteria:

• The example calculator project should be accessible and readily available when cloning the project

• I should be able to choose the example calculator project as a starting point.

• The example calculator project should be well-documented, providing clear instructions on how to use and customize it.

• Each type of node (input number, operations, display) should have a distinct and visually recognizable representation in the node editor.

• The input number node should allow me to input numerical values when connected to other nodes.

• The operations nodes should correctly perform the specified mathematical operations and produce accurate results.

• The display node should receive the output from the operations nodes and display the calculated result accurately.

• The nodes should be easy to connect and configure to create different calculator functions.

• The example project should demonstrate basic calculator operations, such as addition, subtraction, multiplication, and division.

• The example calculator project should be free of any bugs or errors that could hinder its proper functioning.

• It should be possible to modify and expand the example calculator project to create more complex calculator functionalities.

• The example calculator project should be compatible with the main project and not cause any conflicts or compatibility issues.

• The example calculator project should be well-organized and follow best practices for creating node-based projects.

Move Fonts and Radiuses into NLStyle.

• Create a font property that holds all fonts (such as nodeIcon, nodeTitle, nodeDescription, and linkDescription, and can use a primary font for common fonts).
• Create a radius property that holds all Radiuses (such as node, button, and contextMenu items, and can use a primary Radius for common Radiuses ).

Crash when creating a link from the source node after a node is removed
Crash when creating a link from the source node after a node is removed.

To Reproduce
Steps to reproduce the behavior:

1. Create two nodes or more
2. Create a link (Node1 to Node2)
3. Remove a Node2
4. create a Link from the source port (Node1) to the destination port(Any)
5. See the error

The zooming feature is not smooth and becomes slower with more nodes/connections

** extra acceptance **

• make zoom to fit animated
• zoom into should be animated
• Aggregate successive wheel events

The scrollbars (flickable+textEdit currently) need to be customized and encapsulated.

Describe the bug
Once a connection is created between two ports, it should be stable. However in the current version, when a connection is made between two ports, If the user attempts to create the same connection with the same starting point and ending point, the previous connection is unlinked and starts moving with the mouse

To Reproduce
Steps to reproduce the behavior:

1. Create two nodes
2. Create a connection from port A of the first node to the port B of the second node
3. Attempt to create another connection from port A to port B
4. Previously made connection starts moving around and is unlinked

Expected behavior
Two approaches for fixing this:
1- We allow the user to make more than one connection between two ports
2- If there already is a connection between two points, then second attempted connection (temp connection) should disappear in the proximity of the output port. Either way, the previously made connection should be stable at all costs.

Describe the bug
1- When starting to drag a link, the direction is always downward, no matter which port is chosen sidewise
2- When a new node is made at the end of an arrow (link), the node should be at that exact place. in our current version, the node is made at the top left corner of the arrow position

To Reproduce
Steps to reproduce the behavior:

1. Create a node (any node)
2. start making a link by dragging the right hand port

Screenshots
actual behavior:

Obsidian (desired behavior):