-
Notifications
You must be signed in to change notification settings - Fork 21
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
Change package structure - enable plugin support #53
Comments
pylipp
added a commit
that referenced
this issue
Dec 28, 2019
- prepare for #53 - simplify return values of safely_run() - introduce Client.latest_exception attribute
pylipp
changed the title
Change package structure
Change package structure - enable plugin support
Dec 30, 2019
pylipp
added a commit
that referenced
this issue
Dec 30, 2019
Preparation of #53 for supporting client-'plugins'.
pylipp
added a commit
that referenced
this issue
Dec 30, 2019
- affects modules: httprequests, fflask, resources - probably in version v0.24.0.0 - related to #53
pylipp
added a commit
that referenced
this issue
Dec 30, 2019
- affects modules: httprequests, fflask, resources - probably in version v0.24.0.0 - related to #53
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
WIP
financeager
support Python plugins. It brings the opportunity to modularize the code base, and to enable extending the core package easilyfinanceager
version 0.23.0.0 was released, bringing plugin supportCurrent Situation
financeager
can be used to communicate with a database on the local machine, or a database on a remote machine (which has a webservice installed).Having both ways combined in a single package is powerful but has some smells. First of all it has to be reconsidered of how much value the 'remote' variant is at all.
When users want to use the 'local' variant,
When users want to use the 'remote' variant,
financeager
on the client sidewhich might be too much of a hazzle already.
Now one major feature I'd like to introduce is a
financeager
client TUI (like e.g. tig or pudb). When used with the 'remote' variant however, the client would have to hold a copy of the remote database for performance/connectivity reasons, and sync this local copy periodically. This bringsProposal
financeager
Then
financeager
can be extended by a TUI mode (see Non-CL user interface #50) which accesses the local databaseThe text was updated successfully, but these errors were encountered: