I’m just looking for a sanity check before I go down this road with my Windows Store App.
In the app, I am looking to have a navigation model which involves the following:
All users shown the initial page, and are asked to make a section of Items from a list before tapping continue.
Each Item has a group of pages associated with it – could be 2,3, whatever.
The user is then presented the pages in the order that they are associated with for each Item and in the order by which they selected the Items.
For example, say the user selects Items 2 & 3.
Item 2 has PageA, PageB, PageC associated with it
Item 3 has PageB, PageD, PageA associated with it.
The user journey for the App would be
Selection -> PageA -> PageB -> PageC -> PageB -> PageD -> PageA -> End
The approach I am thinking of going with involves a “UserService” which is persistent throughout the app and stores a list of the Items the user has selected (in order)
I would then have a “PagePlayer” page which would act as a container for the pages to be displayed and this would be loaded after the user is finished with the Selection.
The player would then display all the pages in order based on the Items that were saved in the UserService.
I personally don’t want to go down this road because I know that having Frames displaying Pages etc is generally a bad idea, it could ruin the navigation history etc.
Which pages are associated with each item I would have saved to a local file of some sort and have this loaded when a new Item is set to be displayed.
The number of items are “hard coded” and have IDs associated with them.
I am familiar with Prism for WPF but unfortunately the recently released Prism for Windows Runtime does not support modularity for using a composite approach.
Apologies for general-ness of this question, I couldn’t think of another way of asking it.
Any help would be greatly appreciated!
Related
I’d like to integrate vue into a existing webproject. In detail I want to use vue to integrate data from www.autoscout24.de into a website which basically uses Modx-cms, which means that the routing generally takes place inside Modx. With vue I want to realize a search form which I can integrate anywhere inside the existing website. The results should display under something like domain.tld/cars and a single car should be displayed at something like domain.tld/cars/cardetails#8574746
So regarding the routing I guess /cars and /cars/cardetails will be regular sites of the cms (vue only shows the data) but the Hashtag-routing for cardetails will be handled by vue, right?
As the App (should I call it three different apps?) will not be a SAP how can I pass data between the search form, /cars and /cars/cardetails#xyz? Is local storage the way to go?
Is that the right approach. Maybe my approach is even completely wrong, as I am new to vue?
Some further details regarding the app:
The searchform will react to every user input with a request to the Graph QL-Api in order to show the user live how many results he will get. Above the form there will be a teaser with around 10 random cars. After submitting the form the user is directed to /cars where he receives his resultslist (photos of the cars + some quick information). Above the list I want to show the filters so the user can adjust the resultslist. When the user clicks on the car he will get directed to /cars/cardetails#xyz where xyz is the id of the car in order to fetch the cardetails from the api via js/graphql.
Kind regards
Here are some screens to illustrate it. The parts which should be realized with vue are marked red.
I have created a custom fiori application and deployed it to abap repository.Now I have to create two tiles.
1.one for displaying the record.
2.other for creating the new record.
Both the pages(display and new) are created in different views in same application.
can I set the first page in first tile and second page in second tile as home page while launching,without creating the same copy of project again.
Another option is to have 2 differents target mapping parameters on the tiles and use this.getOwnerComponent().getComponentData().startupParameters to retrieve them.
This way you can read the parameter and choose what to do.
However as suggested by user6177399 the guidelines for edit and display view would not suggest that.
Lets imagine, that we have some catalog, let it be the goods catalog.
You have top level categories and many subcategories for them and so on deeper. The whole menu can be of any deep.
Of course I don't want to hardcode this catalog, I want to load its structure from a remote server (REST API for instance), so that I could change it any time wothout posting changes to apps (App Store and Play Market). I am using React-navigation (if it makes any sense). How it is usually done?
(1) Should I somehow create one page and pass there some parameters, or (2) should I create many distinct pages.
In the first case (1) I can't even imagine, how can I pass new
parameters to the same page again and again in such a way that each time
there would be a new title in header of this page and a new submenu
structure to be displayed.
The second way (2) seems rather complex to me and is not the best
idea... I suppose.
What are best practices?
The custom list app is a nice app, to show a list of items that are currently in Rally.
What I would like to get out of this list as well, is UserStories and Defects from previous Iterations.
A page can be easily setup where you have an iteration filter on top, then a list app underneath. When the page is set to show closed / past iterations it should show the user stories and defects that have been previously assigned to the applied iteration (even if they have another iteration set currently).
Is such an app available? Searching a bit did provide any usefull apps,
Blocking history seems to do a little in that area, but looks only at things that had a blocker flag set:
https://github.com/RallyApps/app-catalog/blob/master/src/legacy/BlockingHistoryApp.html
The List from this app on the other hand cannot be modified, therefor I want to combine history with the Custom Grid app as provided by Rally.
Regards
What about the Iteration Scope Change app?
Source here:
https://github.com/RallyApps/app-catalog/blob/master/src/legacy/IterationScopeChangeApp.html
It's available directly in the app catalog in the product as well.
In Sencha, how to create a DataView or List component which renders only 1 item at a time and contains prev/next buttons to navigate data?
Store has pagination enabled to pull only 5 records at a time. Out of these 5 records I want to display only 1 record at a time on the view and with navigation buttons to move forward/backwards. Is there a built-in component for this requirement?
I see few SO posts (Sencha Touch limit number of items in list) suggesting to use 2 stores (DisplayStore to slice the actual data). This didn't work for me. I tested this with static data in the actual store. It still renders all the data in the list. Moreover I am looking for forward/backward navigation buttons too.
If there is no such built-in component (at least close enough), I want to create one for my needs. Please suggest.
You should go with a filter, and two buttons.
The handler for the next button could be alike
var number= list.getStore().first().getId()
list.filter('id', number+1)
If there is anyway to increase a number for the next valid item. Otherwise you need a counter of your current selected item and increase that.