Sammy.js External Navigation - sharepoint

I have built a SharePoint 2010 web part that is a single page app using knockout and Sammy to navigate between views of the SPA. Everything works fine within the SPA web part, but if I try to navigate to another page in SharePoint, the Sammy.js routing kicks in and just reloads my SPA home view. Is there a way to "override" the Sammy.js navigation when clicking a link outside the SPA web part?

Unlikely. Instead I would remove Sammy and make the navigation work using templates in knockout dependent on the current view.
Optionally wire it into Sammy so it could run stand-alone with proper URL routing, or simply nested inside the dom somewhere not using Sammy.

Related

.NET MAUI: How to have Blazor page use the layout when navigating from the Shell

I am able to navigate to a Blazor page from the shell thanks to How to navigate on a TabBar on .NET MAUI/Blazor hybrid?
However the MainLayout is not used even if I specify it in the Blazor page.
[GitHub source replicating the problem] (https://github.com/jfversluis/MauiBlazorPlatformTabs)
*edit
Goal was to navigate to a page in an existing BlazorWebView from the AppShell Flyout. This method is creating a new "website" with the one page.

I’m facing a performance issue in SharePoint online app parts

The custom app parts in SharePoint add-ins (SharePoint hosted) gives bad performance when adding them into a custom page in the hosted site.
Is there a solution for this problem?
The slow performance is most likely caused by the way the app parts are placed on the SharePoint page - each app part is contained within it's own iFrame which points to the app web. When the page loads, another full HTTP call has to be performed for the content from each app part placed on the page. Unfortunately - this behaviour is a part of the Add-in model and cannot be changed. Source: How to add SharePoint-hosted add-in as an app part
It has it's positives, as it allows to display content from provider-hosted apps in a web-part like manner. The biggest downside is - it treats SharePoint-hosted apps the same way.
To boost the performance I would suggest (if possible) switching to the SharePoint Framework, which is client-side only, doesn't use internal app webs and renders directly inside the page's DOM without being wrapped with any iFrames. Take a look here: Build your first SharePoint client-side web part

Adding pages and templates to a portlet

I am using eclipse ide and I have created a liferay project Test-portlet. I haven't written any code for this project
When I ran this project I got the usual welcome screen and I added the Test-portlet to the page and removed other stuff from the page.
I actually want to create a website using liferay. The website already exists which should be rewritten in liferay.
So when I load the project I get this welcome screen and the Test-portlet. At the top of this page I get the the menu-Admin,Sites,.... and LIferay logo on LHS.
I wish to remove all of these and displa only the web page data of the website. I know I can use themes and layouts for such purpose.
If I should use portlet to create this website , how should I keep adding pages and designs?
Also how should I add pages,themes,templates to this portlet?
Before creating this Test-portlet project, I had created pages using control panel.
How should I create this website? Using portlet by creating project?
EDIT:
Also this Test-portlet is displayed as a small portlet on the entire page. WHen click on the gear symbol and click on maximise, it only maximises during that time and when project is run again, it comes back to its original size.
Should I create this websiste using portlets?
Data for website comes from database. Few pages have static data.
Subsequent pages may be added in future.
HOw should the pages be added if I use portlet to create the website?
Please go through liferay themes and liferay layouts

How to add an application page to a site in SharePoint?

I am an experienced .NET Developer acting as interim SharePoint Developer, and am new to SharePoint. After determining that I need to go with an application page instead of a site page for a new project due to it's complexity and need of custom code behind. Before developing the entire solution, I wanted to tie up the loose ends of my understanding of application page deployments. I need to add this page as a URL on the left side of a Site Collection page (kind of like what happens when adding a subsite to a site page.) I have read about the modules, which seems extremely hacky to me. There must be a better way to develkop a custom page on top of SharePoint without the page being accessible to anyone on the entire site.
EDIT
The application I am wanting to develop on top of SharePoint exists purely for data entry and reporting purposes.
Have you considered using a Webpart?
With a visual webpart which is essencially a usercontrol wrapped in a webpart you can add as much complexity as you want and you also have code behind to hook to events etc.
The benefit of using a webpart is that you can then drop it on a page, and use all OOB sharepoint access controls.
You mention that you want to develop a data entry reporting app. So something you can do is to create a subsite. Look all access to modify pages except to owners. Create all your screens by adding pages to the subsite and dropping webparts on it with the logic you require for each screen.
Also make sure you deploy the werbparts via a web feature that only is activated in your subsite, this way the webparts are only available in that particular subsite.

Is it possible to put a Content Editor Web Part in a sharepoint app page

Is it possible to put a Content Editor Web Part in a sharepoint app page along with the ability to edit the web parts contents from the browser? In other words have it behave as it would on a web part page.
I can get the web part to show but I have no clue if it can be setup for in browser editing on the application page ... I can't get it to show the edit button.
Jay
You can put a Content Editor WebPart on an application page because it's just a special kind of web control, but there is no web part manager on the page and even if you added one it would not have a record in a content database for the page. So it would not know where to store the information.

Resources