jolikit | Java APIs to abstract away time

by jeffhain Java Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | jolikit Summary

jolikit is a Java library. jolikit has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However jolikit build file is not available. You can download it from GitHub.

Jolikit is a Java library which APIs only depend on the most basic JDK classes and Java language features, for easier translations into other languages, and which aims to abstract away things not abstracted away by the JDK, to serve as a low lock-in decoupling basis. There is no top-level class or package dependency cycle in the code, which should simplify a lot porting into languages such as Go. See README-BWD.md for more info about the 2D UIs API.

Support

Quality

Security

License

Reuse

Support

jolikit has a low active ecosystem.

It has 3 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

jolikit has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of jolikit is current.

Quality

jolikit has no bugs reported.

Security

jolikit has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

jolikit is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jolikit releases are not available. You will need to build from source code and install.

jolikit has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi has reviewed jolikit and discovered the below as its top functions. This is intended to give you an instant insight into jolikit implemented functionality, and help decide if they suit your requirements.

Sends a backing event
Return window bounds
Invoked when the backing window is resized
Invoked when a popup window is being clicked
Override handleEvent
Deactivate the backing window
Check if a backing window maximized state is being shown
Properly paint the event
Reads the required names records
Updates the state of this event
Creates a new key list
Reads the required font data from the given stream
Returns the data accessor for the specified text rectangle
Returns a converter for the specified format
Returns the string representation of specified range of bits
Returns true if the backing window is maximized
Sets the callbacks
Update the state of the backing event
Read the required data from the given stream
Override this method to update the context
Load the backing font data at the specified font file
Load the font at the specified path
Load the system and system fonts
Add events to the stage
Load all the backing fonts at the specified path
Called when mouse is dragged

Get all kandi verified functions for this library.

jolikit Key Features

No Key Features are available at this moment for jolikit.

jolikit Examples and Code Snippets

No Code Snippets are available at this moment for jolikit.

Community Discussions

No Community Discussions are available at this moment for jolikit.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jolikit

Jars content and inter-dependencies, with compilation target version in parentheses:.
jolikit.jar (1.6): Everything except BWD bindings implementations (even those based on AWT/Swing).
jolikit-bwd-impl-utils.jar (1.6): Utilities for BWD bindings implementations. Depends on: jolikit.jar
jolikit-bwd-impl-awt.jar (1.6): A BWD binding based on AWT. Depends on: jolikit.jar jolikit-bwd-impl-utils.jar
jolikit-bwd-impl-swing.jar (1.6): A BWD binding based on Swing. Depends on: jolikit.jar jolikit-bwd-impl-utils.jar jolikit-bwd-impl-awt.jar
jolikit-bwd-impl-jfx.jar (1.6): A BWD binding based on JavaFX. Depends on: jolikit.jar jolikit-bwd-impl-utils.jar
jolikit-bwd-impl-swt.jar (1.6): A BWD binding based on SWT. Depends on: jolikit.jar jolikit-bwd-impl-utils.jar
jolikit-bwd-impl-lwjgl3.jar (1.8, due to a lambda in LWJGL3): A BWD binding based on LWJGL3. Depends on: jolikit.jar jolikit-bwd-impl-utils.jar jolikit-bwd-impl-awt.jar (for fonts)
jolikit-bwd-impl-jogl.jar (1.6): A BWD binding based on JOGL/NEWT. Depends on: jolikit.jar jolikit-bwd-impl-utils.jar jolikit-bwd-impl-awt.jar (for fonts and images)
jolikit-bwd-impl-qtj4.jar (1.6): A BWD binding based on QtJambi4. Depends on: jolikit.jar jolikit-bwd-impl-utils.jar
jolikit-bwd-impl-algr5.jar (1.6): A BWD binding based on Allegro5. Depends on: jolikit.jar jolikit-bwd-impl-utils.jar
jolikit-bwd-impl-sdl2.jar (1.6): A BWD binding based on SDL2. Depends on: jolikit.jar jolikit-bwd-impl-utils.jar
Launch JlkBuildMain: it will build the jars it can (it's fine to fail on bindings requiring unavailable libraries if you don't care about them).

Support

"Why abstracting things away, why simplicity and decoupling?" Not easy for me to explain something I feel is so obvious. A few idea that point more or less into the same direction:. "Why Java?" For its portability, its backward compatibility (i.e. portability in time), its simplicity, its basic multi-threading features, and now its openness. "Why stick to Java 6?" I don't see any new feature from Java 7+ which value for this library would compensate the fact of not be usable by all the people still using Java 6, by far. Main reasons why I didn't stick to Java 5 instead: AWT/Swing API a bit behind, no AtomicXxx.lazySet(...), no JavaCompiler class, and easy to make code Java 5 compliant if needed by removing the few Java 6 specific code. "Why not use a build tool?" Jolikit build is trivial, so it doesn't require a powerful build tool: we can just use JavaCompiler and JarOutputStream more or less directly for it.

Find more information at: