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.

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

Demonstrate dynamic content in an AgGrid control #451

Open
2 tasks
FabienLelaquais opened this issue Feb 2, 2023 · 0 comments
Open
2 tasks

Demonstrate dynamic content in an AgGrid control #451

FabienLelaquais opened this issue Feb 2, 2023 · 0 comments
Labels
✨New feature 🟨 Priority: Medium Not blocking but should be addressed

Comments

@FabienLelaquais
Copy link
Member

FabienLelaquais commented Feb 2, 2023

What would that feature address

We want to expose an AgGrid component through a Taipy control.

A first step is to encapsulate the control and its core API through Taipy 's Extension API. That would include the base features such as columns and rows definition.

A second step is to demonstrate dynamic content: a little demo for the control would include a table that represents a short list of random values between 0 and an upper bound that is specified in an interactive slider. When the user changes the slider value (from 0 to 100), then we recompute the entire data set, and we expect the table to represent these new values.

Description of the ideal solution

A new public repository is accessible for the public, holding all it takes to build a specific
ElementLibrary ("AgGrid") that exposes a control ("table") that provides an access to AgGrid table
features through properties.

This would include multi-indexing and dynamic content.

Demonstrating dynamic content

Here is a short piece of code that uses the regular Taipy table:

from taipy import Gui

start = 0
step = 1

def compute_data(start, step):    
    values = [start+i*step/10 for i in range(0, 11)]
    squared = [x*x for x in values]
    third = [x*x*x for x in values]
    return {
        "Values": values,
        "Square": squared,
        "Third": third
    }
data = compute_data(start, step)


def on_change(state, var_name, var_value):
    if var_name == "start" or var_name == "step":
        state.data = compute_data(state.start, state.step)

Gui("""# Dynamic table


<|{data}|table|>

Start: <|{start}|slider|>

Step: <|{step}|slider|min=1|>

""").run()

Changing the slider values recomputes all data and updates the table content.

We want to see a similar behavior, when table is replaced by agGrid.table, with no other change.

Acceptance Criteria

  • All the code lies in a specific directory in the frontend-experiments private location, under '/extensions/aggrid'.
  • A README file indicates what to do to build and deliver the Python packages that relies on AgGrid's components.
@jrobinAV jrobinAV added 🟨 Priority: Medium Not blocking but should be addressed and removed 🟧 Priority: High Must be addressed as soon labels Jul 3, 2023
@jrobinAV jrobinAV assigned jrobinAV and unassigned drake-stamos and jrobinAV Jul 3, 2023
@jrobinAV jrobinAV transferred this issue from Avaiga/taipy-gui Nov 13, 2023
joaoandre-avaiga pushed a commit that referenced this issue Nov 23, 2023
…arams-generic-dn

feature/#451 added default value for read and write fct in generic dn config
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨New feature 🟨 Priority: Medium Not blocking but should be addressed
Projects
None yet
Development

No branches or pull requests

3 participants