-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP Esi Rewrite #11
Open
w9jds
wants to merge
26
commits into
master
Choose a base branch
from
esi_rewrite
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
WIP Esi Rewrite #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Moved to native Java 8 - Moved to RxJava2 - Moved to dagger2
- Started moving to ESI and Kotlin
Since it has been awhile the whole build system, and all dependencies have been updated. Along with that, everything is being redone in Kotlin since I already have to rewrite all of the database systems for the upgrade of DBFlow and all of the models/network calls for ESI. - This commit contains rewritten Dagger Architecture in Kotline - Redone/Upgraded project gradle and dependencies - DBFlow with RX Model rewrites - Purge of all the Java that has already been rewritten in Kotlin
- Moved all Jackson parser objects to Kotlin data objects - Moved all database entry objects to RX Data Entries and hooked them up directly to their data counterpoint objects
- Started converting activities
- Moving database to Firebase - Entire project written in Kotlin now - Cleaned out a lot of useless and old code - Removed local database (Firebase handles offline) - Cleaned up layouts
- Moved database calls to loader - Removed updating from loader base classes - Fixed Dagger injection of database
- Layout moved to bindings - Got dagger working properly - Working on tabbed layout for type information
- Styling revamps - Layout compiles - Navigation to type screen works
- Pulling regions for dropdown - Populating item details and generating tabs for orders and history - Properly managing state and navigating activities - Cleaning up how fragment lists were handled
- Binding is all working and constraint layout was rewritten for the attributes section. - Databinding needs to be done for attribute values - BindingAdapters are now setup (starting with logo loading) - Item name and icon are centered now
- Fixed some styling colors
- Moved network calls to my personal api to condense the amount of calls for orders - Moved all layouts to databinding - Attached listeners to region spinner and moved networking to inside of each fragment it goes to - Last region you had selected is now saved for auto selection later - Fixed issue with html text descriptions showing the full html tags - Moved over to Kotlin Rx library
- Moved to Gson to properly parse orders - Moved back to esi calls due to SSL issues - Fixed layout for orders in constraint layout - Setup bindings for orders
- Added in queries to pull station and system names - Added in Unknown Stations label for when it is in a freeport
- Started adding room persistent storage - Started transition to androidx and jetpack - Cleaned up styles
- Moved all views to fragments and removed extra activities - Removed all custom loaders, and moved to LiveData architecture components (with custom loader code extensions) - Due to limitations in firebase, I started moving to store data locally, so I now use the Persistant storage architecture component room - Moved storage of groups and types to the new workmanager architecture components - Started setting up new navigation architecture component - Cleaned up file naming for layouts
HURRY UP AND RELEASE IT ALREADY! >:( :P |
HAHA, Google broke a huge amount of APIs and was waiting for them to fix them. Found out they did last night. I'll be getting back to it soon. |
A likely story... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Whole application was rewritten in Kotlin
ConstraintLayout
andCoordinatedLayout