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

Paintroid 451 : Flutter: advanced Options #54

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

vishad-tyagi
Copy link
Contributor

@vishad-tyagi vishad-tyagi commented Mar 4, 2024

Ticket
https://catrobat.atlassian.net/browse/PAINTROID-451
Paintroid-451 : Flutter: advanced Options

Description
Add the functionality for the advanced options in the overflow menu.

New Features and Enhancements

  • New Features and Enhancements

Refactorings and Bug Fixes

  • Refactorings and Bug Fixes

Checklist

Your checklist for this pull request

Please review the contributing guidelines and wiki pages of this repository.

  • Include the name of the Jira ticket in the PR’s title
  • Include a summary of the changes plus the relevant context
  • Choose the proper base branch (develop)
  • Confirm that the changes follow the project’s coding guidelines
  • Verify that the changes generate no compiler or linter warnings
  • Perform a self-review of the changes
  • Verify to commit no other files than the intentionally changed ones
  • Include reasonable and readable tests verifying the added or changed behavior
  • Confirm that new and existing unit tests pass locally
  • Check that the commits’ message style matches the project’s guideline
  • Stick to the project’s gitflow workflow
  • Verify that your changes do not have any conflicts with the base branch
  • After the PR, verify that all CI checks have passed
  • Post a message in the #paintroid Slack channel and ask for a code reviewer

@vishad-tyagi vishad-tyagi changed the title Paintroid 451 Paintroid 451 : Flutter: advanced Options Mar 4, 2024
Copy link
Contributor

@msesko msesko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @vishad-tyagi. Good job on the UI. Check comments for changes.

Is this ticket UI only? @juliajulie95 Or do you also have ti implement the antialiasing and soothing? Would make sense to me.

  • tests are needed for UI
  • tests for functionality in case it has to be implemented

@msesko
Copy link
Contributor

msesko commented Mar 6, 2024

Also state is not saved. If I close the UI and reopen the switches states are not saved.

@vishad-tyagi
Copy link
Contributor Author

@msesko I worked on the Information provided in the ticket. I commented for more information too. After that, I took as much as I could from the Android version of the app on the Play Store. (I know Catrobat is open source and run by many students, I just don't want you to think, that I did the minimum 🙂). Just let me know what other functionality are to be added. I will commit to all the changes ASAP. Regarding the state save functionality, the specifications for the two options were not clearly defined in the ticket. Consequently, I refrained from incorporating the state change variable, anticipating that this aspect might be addressed in a future ticket.
Sorry for the late response, my mid-sem exams are going on.

@Lenkomotive
Copy link
Contributor

Lenkomotive commented Mar 9, 2024

Hi @vishad-tyagi. Good job on the UI. Check comments for changes.

Is this ticket UI only? @juliajulie95 Or do you also have ti implement the antialiasing and soothing? Would make sense to me.

  • tests are needed for UI
  • tests for functionality in case it has to be implemented

The ticket-description does not clearly state the scope of the ticket. Imo the actual implementation of the algorithms would exceed the scope of the ticket. Id say we treat it as UI only for now and create new tasks for each algorithm to be implemented later.

@juliajulie95
Copy link
Contributor

Indeed, I would not want to add UI without working functionality behind it.
We could maybe define the ticket more clearly and implement one of the two options to keep the ticket smaller?

@msesko
Copy link
Contributor

msesko commented Mar 9, 2024

Indeed, I would not want to add UI without working functionality behind it. We could maybe define the ticket more clearly and implement one of the two options to keep the ticket smaller?

It would be nice to specify if it is UI only ticket or functionality as well for this type of features.

But even if it is a UI feature it should be prepared in a way that the backend functionality can just be plugged into it (no hardcoded vals where we should have vars, correct passing in of vars, correctly managing states etc.)

Such ticket would also be 454 - Layers, where the UI in itself is quite a lot to code and would be easier to review if separated.

@vishad-tyagi
Copy link
Contributor Author

@msesko I have implemented the changes, if any more changes are required let me know (like _showAdvancedOptionsDialog() should be in io_handler instead of overflown_menu, etc)

@juliajulie95
Copy link
Contributor

Please resolve conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants