Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[NEW-FEATURE] RenderableContentControl optimalization #276

Closed
kuh0005 opened this issue Dec 20, 2023 · 2 comments · Fixed by #278
Closed

[NEW-FEATURE] RenderableContentControl optimalization #276

kuh0005 opened this issue Dec 20, 2023 · 2 comments · Fixed by #278
Assignees
@PTKu

Comments

@kuh0005
Copy link
Collaborator

kuh0005 commented Dec 20, 2023 •
edited
Loading

The main goal is to optimize the rendering of Blazor components. One way to achieve this is to prevent rendering that is triggered by a property not used in the Blazor component. It's necessary for the component to remember the last state of selected properties and allow rendering only based on their changes.

I propose to add to the compiler:

  • functions for working with POCO objects due to the comparison of base type values.
  • a function for directly filling an existing POCO object without reading/accessing the connector.

Implement filtering in ShouldRender() in RenderableContentControl for the array of changes of selected base properties.
@PTKu
Copy link
Member

PTKu commented Dec 27, 2023

/cib

@PTKu PTKu closed this as completed Dec 27, 2023
@IX-BOT
Copy link
Contributor

IX-BOT commented Dec 27, 2023

Branch 276-_NEW-FEATURE_RenderableContentControl_optimalization created!

IX-BOT added a commit that referenced this issue Dec 27, 2023
@IX-BOT
Create draft PR for #276
03fc57e
@IX-BOT IX-BOT mentioned this issue Dec 27, 2023
Merged
PTKu added a commit that referenced this issue Jan 3, 2024
@IX-BOT @PTKu
[NEW-FEATURE] RenderableContentControl optimalization (#278)
e846224 
* Create draft PR for #276

* adds methods to check whether online data changed
- comparison is made via Poco objects
- when POCO is compiler ignored limits use for members not present in POCO type

* lf fix

* adds mechanism to check whether StateChange should be called on primitive change.
- the mechanism checks that the given primitive is part of given components polling queue.

* fixing tests

* asp

* asp

---------

Co-authored-by: PTKu <61538034+PTKu@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PTKu PTKu

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[NEW-FEATURE] RenderableContentControl optimalization ix-ax/axsharp
3 participants
@kuh0005 @PTKu @IX-BOT