You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
Changing the slider values recomputes all data and updates the table content.
We want to see a similar behavior, when
table
is replaced byagGrid.table
, with no other change.Acceptance Criteria
The text was updated successfully, but these errors were encountered: