-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update Getting Started Page with Tile Layout #56
Comments
To support the categories, I'll need some agent and database updates:
|
I have started to implement this in a separate project without including it yet in SHP. I've decided to use TileView from DevExpress as a most robust way of displaying cards. I will try to finish something on Monday and post here screenshots. |
|
@JoelProminic It would be good to have method which returns for me items for specific categories, if possible. |
- Change DataGrid to Tile view in details of each category (reference #56)
- Implement selected index on Tile (reference #56)
I have added interaction with Tile layout. I'm displaying instead of DataGrid tiles. Basic breadcrump is added, without interaction and going too deep right now. I will get more into that implementation once I get categories. |
Proposed categories from a previous meeting:
|
I pushed some updates to the Domino Visual Editor project, but these probably won't be useful for now. I'll generate the new agent tomorrow and send @piotrzarzycki21 a copy of the updated database. I sent an email so that @JustinProminic can start reviewing the categorization of the Documentation Forms |
- Fix issue where stateChangeComplete event was double dispatched by removing bead SimpleStatesImpl which is already registered in main application (reference #56)
@piotrzarzycki21, I have created the initial agents. I'll send you a copy of the database by email. To read the Categories, use: /SuperHumanPortal.nsf/CategoryRead?OpenAgent
DocumentationFormRead was updated with the Categories property, which is a list of CategoryIDs. Each DocumentationForm should be assigned to at least one property (not enforced by the agents, currently):
For agent security, I matched the DocumentationForm agents. Currently, this means that the agents are accessible to all users. They are limited on the UI side by the ui_documentation_editable properly, but the agents do not check this - I may make a quick update for this. TODO:
|
- Load Cat and Documentation at the same time - later items will be filtered on UI sight (reference #56)
@JoelProminic I thin it won't be necessary. There is not much Documents in that case, so I have pushed changes where I'm loading at the same time Categories and Documentations - I will filter results on UI sights. Remaining tasks:
I will try to finish this over weekend. You can try current changes. |
I installed a build from here. This looks like a good start. |
- Display items under each categories (reference #56)
- Move Edit/Remove to more neasted views where these buttons make more sense to show (reference #56)
@JoelProminic I think I have finished Tile interface.
We should review stuff during our call. |
Prepare list of icons for all items under categories for @JoelProminic |
Alternatively, you could prepare a short list of generic icons and then alternate between them when generating the entries for a category. I suspect some of these articles won't have obvious icons. On the agent and database side, I should just need to add an Icon field to DocumentationForm similar to what I have for Category. If this is blank or null, Super.Human.Portal should use a default entry (or an entry from a short list, as described above). |
@JoelProminic Here is list of material icons. Some of them may not be necessary suit to item and in case of other s when I didn't know what to put I stayed with default one. I think we should in long term prepare some proper images for each of these items. I would rather you to add for that purpose two fields: icon - represents some material icon I have implemented things on my sight ant it's pushed to branch. |
@piotrzarzycki21, how do you envision the
I would prefer to stick with icons unless we really can't get a satisfactory result with icons only. |
Both option for me are ok, whatever you think is better and more convenient on your sight. Third option is to have them stored somewhere on the serve disk and provide trough |
@JoelProminic We should think to move this issue to 1.0. If you add images/icons to sub categories it will be ready. |
cloud communication developer marketplace security |
I updated the DocumentationForm agents with the Icon property. I sent an updated database with the icons populated. The icon list above was very helpful, thanks. I updated a couple of the "image" icons, but I didn't have any problems with the other cases. |
I have pushed fix for icons, because after your update initially they didn't display. Unfortunately some icons displays in a weird way. You can check that in my last push. I'm going to change this set of icons to different one - also material design but not from google. I will prepare for you new set of names. They are going to be taken from here: https://pictogrammers.com/library/mdi/ We are using these icons as well in MyAccount. |
@JoelProminic here is new refreshed lists of icons. Pull my changes in repository as well. Categories: cloud communication developer marketplace portal security |
I just sent an updated copy of the database with the Pictogrammer icons. I checked the icons on domino-49, and they look good to me. |
Should we merge this to main and add issue to current milestone ? |
@JoelProminic This has been merged to main. |
I haven't noticed any problems in my tests with the release candidates. |
@JustinProminic would like to improve the appearance of the Getting Started page, since it will be the first user experience when opening the application.
His proposal was to have a tiled interface instead (example
It doesn't have to look exactly like this, but this is a starting point.
The text was updated successfully, but these errors were encountered: