When offline I'd like to have the UI5 documentation saved locally.
It appears the docs contained in the runtime simply reference the official website and the only other form of downloadable documentation I could find is a PDF from SAP which is indeed well structured and cross-referenced.
Still, I wonder: is there a packaged version of the UI5 documentation ?
Using the Node modules for OpenUI5, I expected to find a separate package for the documentation: there is none. Serving the unzipped SDK with any local webserver works just fine.
Related
TL;DR;
Where can I find a bundled SAPUI5 runtime/SDK for local development?
Long story: The project generated by easy-ui5 loads the UI5 framework from the relative URL (resources/...) which with "modern" UI5 tooling, will be dynamically generated. However, the DX is not ideal. It's pretty sluggish.
The following screenshots were taken from the exact hello-world app generated by easy-ui5's ts-app config.
With CDN https://ui5.sap.com:
With Downloaded resource folder from https://tools.hana.ondemand.com/#sapui5:
Dynamically Generated by UI5 Tooling - Browser Cache Enabled
All the above screenshots capture only JS downloads. Downloading 300+ JS files or even just 36 for local development in 2022 is quite hard to swallow. Does the UI5 team have any plan to publish the controls/libraries/SDK (bundled ofc) on NPM for developers to consume locally? Besides the performance issue, I don't want to rely on Internet connection for local development.
Is it possible to use the preview API in a offline environment? I means, something like to reference locally the library.
Thank you for your time.
Best regards
Yes, it is possible if you download the latest office.js version locally. To use preview APIs:
You must reference the beta library on the CDN (https://appsforoffice.microsoft.com/lib/beta/hosted/office.js). The type definition file for TypeScript compilation and IntelliSense is found at the CDN and DefinitelyTyped. You can install these types with npm install --save-dev #types/office-js-preview.
You may need to join the Office Insider program for access to more recent Office builds.
Read more about that in that in the Word JavaScript preview APIs article.
I integrated my first library with cocoapods recently and have a full documentation readme on my github repo.
Unlike other pods, where if you search for them on cocoapods.org there is an expand button to see more information about the pod on the site, mine does not have it.Instead my own has three buttons [ Site, Docs, Spec] to the right of it, which all link to my github page.
What should i do to make the documentation accessible on cocoapods or do I have to wait for cocoapods to gather more information before they do that? Thanks!
The link to my library is https://cocoapods.org/?q=lang%3Aswift%20on%3Aios%20DLLocal. If it helps my library is coded using Swift 3.
I looked at another library and found out that the Documentation parser cocoapods uses could not parse my information because it did not know my swift version.
The error given was:
Error Parsing Pod
Could not find Objective-C Classes.
The solution was to add a file in my github repo named ".swift-version"
With contents:
3.0
Which is the version of swift used in the program.
I just started to get my head around AEM 6.0 . Installed an app with 'mvn clean install -Pauto-dev-deploy'. I can see the app in CRXDE and the packages are visible in the packagemanager. It does not however show up in the touchUI. Is it possible to run a preview of this site and how to do it?
In Adobe Experience Manager your application (app) and your content are to different things. Your application contains templates and components with which you build your content.
Deploying your app therefore means that you don't necessarily will have content. Without having a look at your source it is hard to see how and where you can create content. Usually your apps templates and components only work in certain content paths. This is usually defined in /etc/designs/<your-project-name>
If you are running AEM 6.2 I suggest that you have a look at the new We Retail demo application and demo content. The source of which can be found on Github: https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail
Can I expect that I replace the Java .jar files and client-side .js files of version 2.4 or 2.5 of CometD in an existing software that is running fine, with the same files in 2.9.1 and it all runs the same?
1- Are the API of CometD exactly the same on all 2.x versions?
2- Is there an upgrade guide that I can use?
Also, I noticed that on the client side, CometD 2.4/2.5 is not AMD and is a single file, but on 2.9.1 it is AMD-based. Is there a single .js file that contains all client-side CometD code?
You can expect upgrades from 2.4/2.5 to 2.9.x to be either without problems, or requiring very little changes, so yes, it should be typically be a drop-in replacement.
While you're upgrading, I suggest to move to CometD 3. You can find here the migration guide from CometD 2.x.
CometD 2.9.x is AMD compliant, and the single file you should include in your HTML is typically org/cometd.js along with a binding for a toolkit (either jquery or dojo).
If you use extensions, you should add also those, see for example http://docs.cometd.org/3/reference/#_primer, or if you don't want to use Maven, this other section.
Follow also the tutorials, that should get you going.
Full documentation link.