Improve editing capabilities of Taipy tables

FlorianJacta commented 2 months ago

Description

I'm looking for a way to enable immediate editing for all editable columns or cells of a table. Instead of clicking the pencil icon for each cell I want to edit, I would like to have a single button that makes all cells in the table ready for editing.

This was asked by a user.

Requested Features

Single Button for Editing All Cells:
- A feature to enable editing mode for all editable cells in a table with a single click, rather than activating each cell individually.
Row-Wise Editing and Accept Button:
- Ability to edit multiple cells in a row simultaneously and then click an "accept" button to update an item in CosmosDB for the entire row, instead of confirming each cell's edit independently.
Master Accept Button for All Changes:
- A master "accept" button that commits all changes made across the entire table, updating the corresponding CosmosDB items for each modified row.

Current Limitation

These capabilities are not available in the existing Table element.

Environment

Taipy: develop/4.0

Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%.
[ ] Create related issue in taipy-doc for documentation and Release Notes.
[ ] Check if a new demo could be provided based on this, or if legacy demos could be benefit from it.
[ ] Ensure any change is well documented.

Code of Conduct

[X] I have checked the existing issues.
[ ] I am willing to work on this issue (optional)

Prithwi32 commented 1 month ago

@jrobinAV @FlorianJacta i would like to work on this issue under hacktoberfest and devfestAI, Please could you assign it to me?

jrobinAV commented 1 month ago

@Prithwi32 Thank you for your help

quest-bot[bot] commented 1 month ago

New Quest!

A new Quest has been launched in @Avaiga’s repo. Merge a PR that solves this issue to loot the Quest and earn your reward.

Some loot has been stashed in this issue to reward the solver!

🗡 Comment @quest-bot embark to check-in for this Quest and start solving the issue. Other solvers will be notified!

⚔️ When you submit a PR, comment @quest-bot loot #1777 to link your PR to this Quest.

Questions? Check out the docs.

Prithwi32 commented 1 month ago

@quest-bot embark

quest-bot[bot] commented 1 month ago

@Prithwi32 has embarked on their Quest. 🗡

@Prithwi32 has been on GitHub since 2022.
They have merged 104 public PRs in that time.
Their swords are blessed with JavaScript and CSS magic ✨
They haven't contributed to this repo before.

This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.

Questions? Check out the docs.

Prithwi32 commented 4 weeks ago

@jrobinAV @FlorianJacta sir please could you specify a filename, on which I should work to solve this issue, and also I tried creating a script file to work on the frontend component, but that script file is not running ..

FlorianJacta commented 3 weeks ago

I am not from R&D; maybe @FabienLelaquais or @FredLL-Avaiga could help you on this

Prithwi32 commented 3 weeks ago

@FabienLelaquais and @FredLL-Avaiga please could you help me on this

yaten2302 commented 2 weeks ago

@FlorianJacta @FredLL-Avaiga , could you please assign this issue to me?

github-actions[bot] commented 3 days ago

This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines.

Avaiga / taipy