There was previously a documentation to build a minimized.js embedding the necessary modules for a particular project with a configuration file.
The french version can still be found, although outdated at :
https://openlayers.org/workshop/fr/custom-builds/create.html
For those like me preferring to avoid developing within node, that was handy!
What would be the way to do so with Openlayers 6?
____ EDIT _____
I tried to be nore specific in the new version of this question at: Minified OpenLayers in CommonJs
Everything is on openlayers.org. It is specified in the quickstart part.
https://openlayers.org/en/latest/doc/quickstart.html
Related
I am new to lit specifically, and web components in general. I have built a web component for usage in Wix (as a custom element), just using straight vanilla js, and have found some success. See https://app.njaplatform.one/rating-element.js for a sample of what I built.
However, I have been asked to redo the work in Lit (https://lit.dev/). I like the syntax of the code better, and it feels like a smarter way to go (as a developer). However, I am really struggling with publishing it.
Whilst I have been able to rebuild my component in Lit, and it is working when I run a local "Web Dev Server", I am really uncertain as to how I publish my lit component so that it is available to other sites. I haven't found any great documentation, walkthroughs, or tutorials on this area. I am really struggling to get over this implementation hump (I am more of a front-end developer and can do some deployments, but I am often very dependent on documentation and well-established ways of doing things).
Key points:
I started with the typescript starter kit at https://lit.dev/docs/tools/starter-kits/
Running npm run serve serves the app to a 'Web Dev server' and that appears fine locally for testing.
I am not sure what I should be doing when I build/deploy the app.
I have made some attempts to publish on some services online, and I am getting a mix of failures, or partial successes which fashion some documentation on the component (generated by eleventity), but the actual javascript generated appears to break as either
1: file not founds (404), or, 2: Error resolving module specifier "Lit". Relative module specifiers must start with "./", "../", or "/"
Not sure how to proceed, would appreciate some "Lit 101" input on strategies as to what I should be doing at this point.
The starter kits are set up primarily to be a development bed for standalone components, and not exactly for web apps.
The errors you are getting about resolving module specifiers are due to lit being published to npm with bare module specifiers as lit and it's dependencies can be referenced by package name in the code, and deduplicated by npm. Running with Web Dev Server in the starter kit does not have this problem because it uses a plugin #rollup/plugin-node-resolve which resolves those bare specifiers to paths in node_modules directory.
The optimal thing to do depends on what your use case is.
If you are creating a web app/site, the common thing to do for production apps would be to create a JS bundle with your source code. Have an entrypoint file that imports all of your components. You can use something like rollup and also apply the aforementioned #rollup/plugin-node-resolve to create a single JS file. This should be added to your index.html, and have your server or static host serve them.
If you're creating reusable components, you could just leave your code as is and it would be up to the end user to take the steps above to bundle. This would be ideal since if the end user uses multiple components authored with Lit, they won't get duplicate copies of Lit.
If you want your user to be able to simply add a script tag for a js file and use your web components, you'd need to publish the bundled component, which you can also prepare with rollup. The down side of this is that each component will come with its own copy of Lit.
I am using this code: https://github.com/pradeepramakrishna/Lightning-Experience/tree/master/aura-components to compile on my org.
I have got one components as eventLib.lib and interactive.js in eventLib folder. I have put this folder in c:MyDevOrg\force-app\main\default\aura folder in the local machine and tried to deploy in the org using VSCode but it didn't work.
I tried creating folder in the Files tab and added the interactive.js in the folder but that is also not seeming to work with the Aura components.
How can I deploy this lib into the org as it is being used in some Aura components.
We don't know what you're trying to achieve. You asked a very technical question to which the answer is "you're probably doing it wrong". Instead try to write what business functionality you are trying to achieve and you might get better answers.
You shouldn't have to import ui:eventLib. It's supposed to be part of core Salesforce's Aura components framework. But.
You've referenced a repo that wasn't updated in a while, no promises this still compiles / is best way to do X.
This repo seems to rely on open source Aura framework which is well... dead in the water.
You might be able to reuse something from this repo in your app using SF's built-in tags - but whole ui: library has been deprecated. Announced in Winter'20 = almost 2 years ago, finally dead in May 2021.
I don't think eventLib was ever exposed, might be something needed just in open source version which complicates the matter more. The answer would be to not work with the really "decompiled" tags but with their higher abstracted versions like ui:inputDate.
So, back to my question. What exactly are you trying to achieve.
You want to build something on pure SF platform (use pure Aura/LWC).
Want to have an app written in Angular, React etc, pure JS, connecting to SF data via API? (build it, upload as static resourcethen import using lightning:container)
want to prettify an existing Java/PHP/.NET app, make it look more Lightning-ish and embed it as iframe? (look into https://www.lightningdesignsystem.com/ and connected apps + "canvas")
want to expose piece of SF as reusable element that can be embedded in another website but could even be an Outlook plugin? (search for "lightning out")
want to look at modern equivalent of that old open source Aura repo and decide what to do next? Check https://lwc.dev/ out.
I am working on the SAPUI5 application with normal ES5 code and using grunt-openui5 to create the Component-preload.js file to deploy to CRM system. Now I am planning to use ES6 style coding but we need to support an old browser. Therefore, I need to transpile it down to ES5 and then create the Component-preload.js file. Now my concern with this approach is when I debug the production issue, everyone gets it right, I want to debug my ES6 file, not ES5 file.
Any help or guidance is very appreciated.
One way to have a transpiled, debuggable preload file and separate ES6 based source files is probably to use the sap-ui-debug=true URL parameter option. Instead of the normal files, it will try to load -dbg.js versions of everything. This for instance is what the SAP WebIDE generates:
If you can set up your build set so that the original, untranspiled files are copied as -dbg versions, and your preload picks up the transpiled ones you might be able to make it work.
Here's the section of the SDK documentation that'll give you some more background information: https://openui5.hana.ondemand.com/#/topic/c9b0f8cca852443f9b8d3bf8ba5626ab
I am new to sakai, i want to add my own tool in sakai source code like announcement,syllabus...etc That tool having some my own functionality for this what i have to do, how can i develop my own tool in sakai.
Thanks.
Use one of the archetypes to get you started, then customise it. When you are comfortable you can change the UI layer to be whatever you like.
https://confluence.sakaiproject.org/display/BOOT/Developer+Tools
If you are looking for a solid "base" tool shell to begin with tool development my recommendation would be to start here: "Sakai Wicket Maven Archetype". There are a few other very good archetypes available but are often outdated and may cause you some problems based on my experience. This has been the one I've had the most success with.
This uses Wicket but does not mean you have to use Wicket to develop further with it. Make sure to pull the 1.2 version as last check the binaries for the others were not available yet so replace -DarchetypeVersion=1.4.1 with -DarchetypeVersion=1.2 It will compile and deploy successfully as a tool "as-is" that you can modify as needed. It also allows you to code in Java to directly access the sakai API and pull from its database or even add your own tables. I've successfully used it with NetBeans 8.0.1 and MySQL 5.6 under Windows 7 with Maven 3.2.3 and Sakai 10.1.
The code is well-documented and is no-frills but with enough varied functional use examples to allow you to do "almost" anything you want. The wicket manual is 600+ pages but in my experience you should be able to accomplish a lot just by looking at the code in the archetype.
I'm working on a semantic-web project and I'm looking for real-life ontologies to test a couple of applications an algorithms. What I'm searching for are different sizes and structures, something that will allow me to benchmark the company's solutions, preferably, not home-made mocks, but something that is actually used. Unfortunately, looking at the entire ontology using OntoGraf is a little cumbersome.
I found a Protégé plugin called NavigOwl, which seems to be perfect for the task of viewing an entire ontology at once and judging its general complication and structure. The thing is, I can't get it to work.
I download the plugin from HERE and follow the instructions.
I put the jar in the plugin directory of my Protégé install.
I open protege and load an ontology
I go to Window>Tabs and select NavigOwl
A NavigOwl tab appears but it only contains the class hierarchy view, while the rest of the window is grey. It's simply blank, as shown below:
Clicking any of the classes in the hierarchy view does not change anything.
I googled for a solution and I managed to find this thread on nabble.com. The poster says he fixed the problem but he doesn't know how. Resetting the tab to default state is among the implied solutions but it doesn't work for me. Closing and reopening the tab, as well as Protégé itself changes nothing.
Have you encountered the problem? What could be the cause?
I'm using Protégé 4.1.0 Build 239 with the bundled JRE (1.5.0) on Windows 7 home premium x64.
I've tried both the JAR available here (NavigOwl plugin for Protégé 4.1) and the one mentioned in Protégé wiki at Stanford, here (version 1.1.0) but the situation persists.
I had came across the same problem but when i upgraded the JDK it started working. though i do not propose upgrading was the solution but it is working now.