Skip to content

Separate DLLs #5

Description

@klanderfri

This program should basically be a open-source library for identifying MtG-cards. For it to be that, the borders between the application and the library needs to be clearer, perhaps by using separate DLL-files.

It fells like OpenCV has a good structure. How are they doing it?

Suggestion for splitting up the code:

  • rmc_core.dll - A file containing the classes, containers enums and other parts used by pretty much everything and everyone.
  • rmc_library.dll - All "useful" methods of a abstract/general nature.
  • rmc_engine.dll - The applied engine that does the job of identifying the cards.

Metadata

Metadata

Assignees

No one assigned

    Labels

    LibraryReusable code for other's projectshelp wantedExtra attention is needed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions