Refactoring #266

Refactor MaterialManager

Added by herck almost 8 years ago. Updated almost 7 years ago.

Status:ArchivedStart date:16 Apr 2013
Priority:HighDue date:
Assignee:pospelov% Done:

0%

Category:-
Target version:Sprint 20

Description

Should it be an application-wide registry of materials? Does it need to be Singleton?
Is its usage not too cumbersome for the user?
see also item #162

  • Simplify change of properties of existing materials, including material name, refractive index (const -> to non-const ?)
    to make life in MaterialBrowserView easier
  • Provide UnitTests for MaterialManager

History

#1 Updated by herck almost 8 years ago

  • Description updated (diff)

#2 Updated by pospelov over 7 years ago

  • Description updated (diff)

#3 Updated by pospelov over 7 years ago

  • Target version set to Sprint 14

#4 Updated by pospelov over 7 years ago

  • Description updated (diff)

#5 Updated by pospelov over 7 years ago

  • Target version deleted (Sprint 14)

#6 Updated by pospelov about 7 years ago

  • Priority changed from Normal to High
  • Found out the bug in MaterialVisitor & MaterialManager behavior:
    Attempt to create HomogeniousMaterial with the name of previously created HomogeneousMagneticMaterial will lead to appearance of MagneticMaterial in the sample instead of expected normal one.

#7 Updated by pospelov almost 7 years ago

  • Status changed from Backlog to Sprint
  • Target version set to Sprint 20

#8 Updated by pospelov almost 7 years ago

  • Status changed from Sprint to Resolved
  • Assignee set to pospelov

MaterialManager has gone completely from Core.
Now it resides in GUI waiting for refactoring of MaterialManagerWidget.

#9 Updated by pospelov almost 7 years ago

  • Status changed from Resolved to Archived

Also available in: Atom PDF