Open RobinFischer opened 6 years ago
frostyandy2k
commented
6 years ago Would be great if you made a pull request with this. The app skeletons use Ionic due to various reasons (ease of use, UI toolkit etc.). If you do the pull request, please create the pages with the Ionic style.
The Ionic style closely resembles Googles Material Design. You should look into it, if you haven't until now.
RobinFischer
commented
6 years ago Alright it took me a while, but I worked out an interface similar to the one used in the PHP app. After talking with Dr Menschig we actually do NOT want an overview page like is shown in the picture above. Instead every site should be accessible through a popup menu in the side. Therefore I added an additional Menu button on the top bar, which toggles an overlay menu with all the buttons.
The individual sites are working well, but there are actually some problems with the linking-system of different buttons. Andy, I used your ionicpage-branch as a reference on how to link different sites. However using the [navPush]="admin" seems to create some issues, or maybe I just haven't fully understand Ionics nav-system... Using href="/#/admin" seems more reliable, as it actually opens the link instead of going through the Ionic system. Which system do we want to use in the end?
As I'm not allowed create a branch in this repo, I had to copy this project to my github: https://github.com/RobinFischer/nodejs-app-skeleton Please tell me if I'm on the right track.
frostyandy2k
commented
6 years ago Here is how you can create a pull request (i.e. add to this project): https://yangsu.github.io/pull-request-tutorial/
And yes, the navPush is broken in the branch (that's the reason it was not commited to master). We are still working on a fix.
Alright it took me a while, but I worked out an interface similar to the one used in the PHP app.
-> my docker is broken right now, did you change the UI? the screenshots are still the sameMaybe you should use the alpine version, and not node:boron. It saves you a lot of space and I heard you want to make it run on a RPi.
we actually do NOT want an overwiew page like is shown in the picture above.
-> that's ok, you can modify the code as you wish and pull changes we make from upstream. If it's a useful change we'll ask you for a pull request!Thanks for the info. I figured out that my project wasn't properly forked, but now I would be able to do a pull request. However I'll wait until you fix the navPush feature, as it seems that’s what should be used in the end.
The UI currently looks like this:
You can see the menu only includes the 4 main user-roles. Inside the user-role website I'm still using the old PHP system (buttons for navigation), which isn't ideal. The goal is to move the navigation interface out of the way, so the sites are only filled with the actual content. For the role system we could either use a sub-menu in the side, or a tab system (which I think would fit better).
Regarding the RPi: that would be a nice to have, but we also have a backup system without an ARM processor. I'll try to stay close to the master branch, so it makes the merging easier.
frostyandy2k
commented
6 years ago We made an update to the app skeleton. Check it out at https://github.com/ScaleIT-Org/ionic-app-skeleton
This project will not be maintained anymore.
You should fork the new one and make a pull request. I like your menu a lot
It would be helpful for developers using this template, to be able to build upon predefined pages for different App users. As a reference you could take the interface of the PHP-app-skeleton developed by Ondics:
In case of this PHP app there are placeholder pages for Users, Developers, Admins, and a Rest-interface. There can also be more placeholders (e.g. for Documentation), but in my opinion those 4 should be enough in most cases.