How Lightning’s new Lightning Core module is the next big thing
The Lightning Core framework is a huge change from the Lightning WebKit-based codebase that powered Lightning and the Lightning Connector.
In this post, we’ll take a look at the new Lightning component library and see how it’s designed to solve some of the Lightning’s biggest problems.
Lightning Components are a new way to build Lightning apps.
Lightning is built on top of WebKit, but developers can still use WebKit components as a base for building their apps.
We’ll dive into how they work and the things that they can do.
Lightning components were first announced back in November, and we’ve already seen the first Lightning apps in use.
Lightning’s WebKit library is a lot of work.
As the Lightning Core team has written, the Lightning team is working on making Lightning components a lot more flexible, so that developers can use Webkit components as the base for Lightning components.
The lightning-core-components repo contains a number of different components that have already been written to help with these goals.
The component library includes some of these components, along with an implementation of the lightning-webkit-async-streaming API, which can be used to perform asynchronous WebKit streaming of data to and from Lightning.
One of the things this library does is provide a way to make sure that WebKit has been correctly loaded in the browser, and to ensure that Webkit can be installed on any WebKit enabled device, including the Lightning.js mobile browser.
We also see a small component library for testing WebKit usage, as well as some other common components.
We haven’t seen a lot out of the component library, so this is just the tip of the iceberg, but there’s a lot that developers are already using in their Lightning apps and projects.
The Lightning Webkit Component library is also the source of a number useful tools for testing Lightning’s webkit-like implementation.
These tools include a lightning-test-webpack plugin, a lightning test-webkit-asynchrony-streamer plugin, and a lightning.webkit.test plugin.
These are all very useful tools that can help ensure that Lightning is as fast as possible, even for older browsers.
We’ve written about the Lightning webkit plugin before, so we’ll briefly describe it.
The webkit.tests plugin allows you to run WebKit tests on a Lightning app, including for debugging purposes.
WebKit is the most popular WebKit browser for Lightning.
The most important part of the webkit tests is the WebKitTest API, and the WebkitTest API can be found in the web-tests-webgl-api directory.
WebView uses a small subset of Webkit tests, which you can use to test WebKit behavior and the user interface.
The WebKit test framework provides a way for the browser to run these tests.
Webkit’s webview-asynchronous-streamed test framework is used in many of the tests we’ve written for the web server.
You can also use WebView tests to write WebKit WebView testing.
WebPack testing is useful for testing the Lightning browser.
Webpack test frameworks can run tests on WebKit browsers that support WebKit.
For example, the webpack test framework can run Webkit WebView test scripts against WebKit web browsers that don’t support WebView.
This can help test whether a particular webkit version is being used.
There are a few different types of webpack tests, and they are all fairly straightforward.
The first is WebPack test-webmock-test, which is a WebPack mock test for WebKit testing.
The second is WebMock test-test.webmocks, which allows you test a particular version of WebMocks web framework.
This test is designed to test whether WebMovies browser is being built with the latest version of the WebMScript spec, so it can be run against the latest WebM.
We don’t recommend WebMocking tests, but we think that they are useful for checking whether WebKit version is supported by the browser.
The third is WebKit unit-tests.
Webmocks unit-test framework is designed for testing how the web browser works with WebKit and other web technologies.
Webmocks WebM tests are written in the WebStorm language.
WebM is an experimental technology, and WebStorm developers don’t use it to test the WebBrowser itself.
WebStorm is designed with WebM in mind.
There is no WebM testing in WebStorm, but WebStorm unit-testing is still useful.
Web mocks are used in the Lightning test suite.
They can be a good way to test how the Lightning app responds to a particular WebM test, and can help identify problems that may arise from using WebM as part of a WebKit app.