| Goal - Migrate web framework to ASP.NET Core (.NET 6) (EnduraCode) | - EwfPage no longer uses the Web Forms life cycle internally. It now natively produces HTML markup. This change should be transparent but represents another major step in the migration away from Web Forms.
|
Goal - Reimplement Master Pages (EnduraCode)
Replace master pages with a new solution that doesn't depend on Web Forms and is compatible with our page component model. | - The web framework no longer uses or supports ASP.NET Master Pages. This is a major step in the migration away from Web Forms. Instead, EwfPage now supports a getContent method to replace loadData. For a basic page, return BasicPageContent; for a UI page, return UiPageContent. If you have your own master pages, you can replace them with implementations of the PageContent interface. This is a breaking change.
IMPORTANT: Please ensure your ASPX files no longer contain any MasterPageFile directives. Visiting a page that contains MasterPageFile will give the user a 404 response, and you will not receive error notifications.
|
| EnduraCode support - Ad Hoc Development | - The web framework Chart component now uses the latest version of Chart.js under the hood, and is now responsive for all screen sizes. It also now supports stacked bar charts with grouping, and horizontal bar charts.
- The web framework now includes automatic page prefetching, which makes navigation feel instantaneous most of the time! Pages are prefetched when a user hovers over or, on a touch device, begins to touch a link. We only do this for intra-app links since we can't guarantee that prefetching external resources is free from bad side effects. This is implemented with https://instant.page/ (a tiny JS library) and relies on <link rel="prefetch"> elements, which are supported in Chrome, Edge, and all Chromium-based browsers, but not in Firefox. In iOS, prefetch is implemented but currently disabled with a feature flag.
|