I have two WPF pages that are displayed in a master WPF window. One page is for uploading documents (UploadDocuments), which has two tree-view components on it; one displays the categories that a document can be uploaded against and the other displays an in-page file-explorer (which I built) so that users can select which document they would like to upload.
The second page is for downloading stored documents (DownloadDocuments), which has both a tree-view for the categories documents are and would be uploaded against and the data-grid I am having an issue with.
This data-grid displays all of the documents that have been uploaded against any of the categories (when a category is selected) in the corresponding tree-view.
When the DownloadDocuments page is first entered from the master menu, the data-grid is merely displayed as empty with only the headers displayed in the header row. The rendering of the data-grid is quite fast when coming in from the master-menu option and after any other page has been displayed that the user may have been working with.
HOWEVER, when I enter the DownloadDocuments page coming back from working with the UploadDocuments page, suddenly the rendering of the data-grid header gets increasingly slower merely to display the header row.
I have tried every suggestion I could find to rectify this issue but nothing appears to work. And this rending issue only occurs in the DownloadDocuments page only after uploading a document or documents in the UploadDocuments page.
Has anyone come across a similar issue?
Related
So I've started getting the hang on ReactJS and have built myself a basic Single Page Website (SPW?).
It currently is 1 "page" (really just an area which spans the whole screen) with the ability for the user to scroll down to the second "page" by clicking a button (or just scrolling).
Now what I need to do is give the user the ability to scroll up as well... to another "page".
Content Area 1
↑
LANDING AREA (user must be dumped here on initial load of the site)
↓
Content Area 2
I hope this makes sense?
EDIT: Apologies for the incorrect use of "SPA"... I've since learned the difference between that and a single page website.
A "single page app" doesn't mean you literally have all of the content on one page. You can have different "pages", however loading them won't cause a page refresh because they're not new html pages served up by the server. You should look into React Router if you want people to be able to navigate to different "pages" in your SPA, otherwise you can look into window scrolling so that you can move up and down.
According to my understanding you are trying to build one page website where each content section you linked with internal page linking & added button for the users to scroll top/bottom. It's not single page application. It's single page website. But, for learning curve it's good to start.
We are using angular-material's md-tabs to display information to the user.
Up until now we used an on-demand approach by adding
ng-click=vm.getForExampleDataForTab1(),
ng-click=vm.getForExampleDataForTab2()
and so on for each md-tab. But this solution has a problem that the first tab is displayed with no data because it doesn't get clicked by the user. So we switched to md-on-select instead. And that did the trick, the first tab was getting data and all was fine. Apparently. We then discovered in Chrome's Dev tools that when moving to another page in the app, all the other tabs that were not selected (the user didn't click on them to view the data) were called.
Did anyone encounter such a behaviour? It only happens when we used md-on-select, not ng-click on the tabs.
Thanks a lot,
ashilon
I'm trying to build a chrome extension using React and I could not figure out how I can get selected web content into my extension app. I am going to use it for creating annotations on the web content.
To give an example, User visits a web page, selects a text or whole paragraph and the extension will be able to get the content of selected text. I am going to highlight the text and show the user comment then. (e.g. medium.com's annotation model)
I've tried AnnotatorJS but I cannot annotate the content outside of my application context.
What can be the accurate way for implementing annotations in React?
So, today i have the same issue as described here.
It happenes under Appearance - Menus when i try to add more pages to my custom menu. Search option works but when i hit View All to browse all pages, then i am able to browse first two pages, other pages return No pages. text.
What might be wrong?
I'm working on a drupal site, and what I'm wondering is, I have a site that will have a main navigation menu-bar at the top of the page.
Then, other then the front page, each page will have it's own set of links. Now these links will be duplicated across pages that relate to each other. So, I know essentially what I need to do is to create individual blocks of navigation and then control those based on the page but I don't know how to do that.
Can anyone explain what I would need to do for this to work? Tutorials or videos would be helpful.
Why not create a taxonomy vocabulary containing all of the links.
Then add a term reference field to your page content type with checkboxes for the widget type.
Then when you edit the page you will be able to select any links that are needed for that page.
Control how these links are displayed on the page by looking at the manage display tab when editing the structure of the page content type.