Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • K KWayland Server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PlasmaPlasma
  • KWayland Server
  • Issues
  • #11
Closed
Open
Issue created Jul 28, 2020 by adrien faveraux@adrienfaverauxDeveloper

Migrate Seat Interface to the new approach

Hello,

I have problem to migrate seat into new approach. because many many class depend each other.

The most clean approach is to break template and make duplicate function, at end of migration process, we reintroduce template to reduce the amount of code.

This permit to adjust and test each class, before migrate all seat.

The second approach is to make all in one commit that contain all Seat and all her class. This is huge annd until we finish, we cannot compile to verify all is ok.

What do you think about that ? (and if you have another idea :) )

Assignee
Assign to
Time tracking