Skip to content
This repository has been archived by the owner on Jun 11, 2023. It is now read-only.

[api] Analyse and implement new api PreferencesFactory. #36

Closed
Naoghuman opened this issue Jan 30, 2018 · 1 comment
Closed

[api] Analyse and implement new api PreferencesFactory. #36

Naoghuman opened this issue Jan 30, 2018 · 1 comment
Milestone

Comments

@Naoghuman
Copy link
Owner

Naoghuman commented Jan 30, 2018

[api] Analyse and implement new api PreferencesFactory.

  • core have only one class PreferencesFactory.
  • PrefercencesFactory is a merge between Builder and Factory Pattern.
  • internal have all other classes like Writer, Reader, SimplePreferences...
@Naoghuman Naoghuman added this to the v0.6.0 milestone Jan 30, 2018
@Naoghuman
Copy link
Owner Author

Naoghuman commented Jan 30, 2018

What is the different between Module-Context and Application-Context?

  • Shortly the prefix from the key.
  • Application scope means prefix is from Lib-Preferences internal class the packagename. Only one key with this name can exists in the hole application.
  • Module scope means prefix is from package class. Same key with different packagenames can exists.

@Naoghuman Naoghuman changed the title [api] Analyse the file FilePreferences. [api] Analyse new api PreferencesFactory. Sep 15, 2018
@Naoghuman Naoghuman changed the title [api] Analyse new api PreferencesFactory. [api] Analyse and implement new api PreferencesFactory. Sep 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant