I everybody, i’m not sure to be on a developper channel, i just wanted to share my idea.
I created last week a POC of a new functionality : make PP expose an API of its internal data (firstly statistics, also a way to launch quote updates remotely).
I use this API directly via a React app that is reachable through a browser or a native app that is packaged using capacitor.
This endpoint is designed with GraphQL (queries, mutations and also a subscription that allow to follow quotes updates with a progress bar ;)).
As you know, the Portfolio Performances App is not available in France, and this way to do is a kind of way to “cloudify” Portfolio Performances for a single user use.
I finaly packaged the app in a docker image, with xRDP for remote access and deployed it in a kubernetes cluster.
I know that i’m very far from PP original technologies. But this application is so good and so smart for me, that i found it useful to make this POC.
My question is : is anybody already try this way of development around PP ? I’m interested with experiences.
Thanks,
Vincent
Have you seen this branch: GitHub - portfolio-performance/portfolio at feature_REST_API
Quite a wile ago @AndreasB started to evaluate possibilities to make use of PP data for external tool support.
Thanks for this branch. I found here a framework to implement services, but no services, I miss something ?
The framework I made is similar but GraphQL.
@AndreasB stopped the development since other stuff became more important lately. So this is at a walking sceleton phase ever since.
Discussion is here: [new] REST API for Portfolio Performance · Issue #2085 · portfolio-performance/portfolio · GitHub
Hello, maybe this discussion is related too ?
ouvert 10:05PM - 30 Dec 20 UTC
question
I asked in issue https://github.com/buchen/portfolio/issues/1858 that I like to … make a suggestion for a new UI design. As @buchen said it might be not that easy to actually implement a more modern look because of Eclipse SWT. But I wanted to give it a shot anyway.
There are some other closed source / commercial tools with similar functionality but would be cool if an open source tool would also step up the design game a little bit :).
**New UI / Example for portfolio**
<img width="1440" alt="Portfolio Performance New Design" src="https://user-images.githubusercontent.com/7000970/103381892-69f06980-4aed-11eb-806c-2e3e11f19ac2.png">
[Figma link to the project (read only mode)](https://www.figma.com/file/wqVCPuiwykiTGKsqd27sOe/Portfolio-Performance-(Public)?node-id=0%3A1)
### So what are the ideas behind this?
Generally speaking I concentrated mostly on the UI and _not_ the UX part. And it's also not complete (like showing the opened *.xml file). Things I addressed:
**1. New navigation menu**
The current one is already really nice but I wanted to bring in the macOS style to feel more at home like the other apps. Also it gives more focus to the actual entries and not the headlines.
**2. Add new portfolio button placed differently**
When I first used the application I was confused to have so many actions behind the plus icon on the right. I think it's better to see clearly how to add a new portfolio separated from the other actions.
**3. More spacing in table rows**
It's easier to read the table entries with a little more space added. On the contra side you have less rows on one screen but improved readability was more important to me that a little bit more scrolling.
**4. Added color scheme**
I don't know if you have a primary brand color (the buttons on the website are orange) so I used the blue tone from the logo because it's more subtile than the orange or green for this purpose.
**5. Actions menu**
Depending on the screen you're at you could show the mostly used actions directly (like buy and sell) and have the three dots for more actions (same as right click on the row). The advantage for the three dots is that you know without guessing that you can do some actions on the row.
**6. Show sub headline from selected row**
Depending on the screen it helps to have context by adding a sub headline (e.g. Comdirect). So when you look at the data from the selected entry you easily can make sure it's the right one.
**7. Show important information on top**
Like profit and loss in this example. That depends of course on the screen. There might be screens where you don't need highlighted information. In this example it's nice to have some overall information.
**8. Tab navigation**
Just different style and matches more the macOS style.
**9. Vertical line on the left**
Just a visual clue to signal that all the content belongs to the selected entry above and hold it more in place.
**10. Get rid of table rows without content**
When rows are not filled with entries don't show them. This will let the design more breath because of the white / negative space.
But you may be more advanced now that what was tried previously.