Skip to content
This repository has been archived by the owner on Aug 4, 2021. It is now read-only.

Flatten package names #4

Open
1 of 6 tasks
KyNorthstar opened this issue Feb 2, 2019 · 1 comment
Open
1 of 6 tasks

Flatten package names #4

KyNorthstar opened this issue Feb 2, 2019 · 1 comment
Assignees
Milestone

Comments

@KyNorthstar
Copy link
Member

KyNorthstar commented Feb 2, 2019

Blue Base, Husky UI, and Husky IO (and all their platform variants) should be changed so that only one import is needed to gain all their functionality.

For instance, instead of:

import org.bh.tools.base.*
import org.bh.tools.base.abstraction.*
import org.bh.tools.base.async.*
import org.bh.tools.base.basics.*
import org.bh.tools.base.collections.*
import org.bh.tools.base.collections.extensions.*
import org.bh.tools.base.disambiguation.*
import org.bh.tools.base.errors.*
import org.bh.tools.base.func.*
import org.bh.tools.base.logging.*
import org.bh.tools.base.math.*
import org.bh.tools.base.math.geometry.*
import org.bh.tools.base.state.*
import org.bh.tools.base.strings.*
import org.bh.tools.base.struct.*
import org.bh.tools.base.util.*

The new syntax would simply be:

import BlueBase.*

The file structure should remain unchanged, to maintain the mental & internal organization of the projects, but all package declarations should be changed to simply:

package BlueBase

Analogous changes should be done in Husky UI and Husky IO


Progress

  • Blue-Base (issue #5)
  • Blue-Base-JVM
  • Blue-Base-JS
  • Husky-UI
  • Husky-UI-JVM
  • Husky-IO
@KyNorthstar KyNorthstar added this to the 2.0 milestone Feb 2, 2019
@KyNorthstar KyNorthstar self-assigned this Feb 2, 2019
@KyNorthstar
Copy link
Member Author

Progress: Blue-Base #5

@KyNorthstar KyNorthstar pinned this issue Feb 4, 2019
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