Download JAR files tagged by custom with all dependencies

Programmatically generate, load, modify, and convert Excel .xlsx spreadsheets in your Java applications. Document Solutions for Excel (DsExcel, previously GcExcel) is a cross-platform high-speed, small-footprint spreadsheet API library that requires no dependencies on Excel. The powerful calculation engine supports 450+ Excel Functions and custom functions to perform complex calculations. DsExcel is 2x+ faster and uses less memory than Apache POI and allows you to save to XLSX, PDF, HTML, CSV, JSON and Images. Deploy your applications to the cloud, Windows, Mac, or Linux. If you'd like to remove the trial watermark and other trial limitations, please email [email protected] to request your 30-day evaluation key.

Programmatically generate, load, modify, and convert Excel .xlsx spreadsheets in your Java applications. GrapeCity Documents for Excel (GcExcel) is a cross-platform high-speed, small-footprint spreadsheet API library that requires no dependencies on Excel. The powerful calculation engine supports 450+ Excel Functions and custom functions to perform complex calculations. GcExcel is 2x+ faster and uses less memory than Apache POI and allows you to save to XLSX, PDF, HTML, CSV, JSON and Images. Deploy your applications to the cloud, Windows, Mac, or Linux. If you'd like to remove the trial watermark and other trial limitations, please email [email protected] to request your 30-day evaluation key.

The app library component of SDL is meant to run on the end user’s smart-device from within SDL enabled apps, as an embedded app, or connected to the cloud. App libraries allow the apps to connect to SDL enabled head-units and hardware through bluetooth, USB, and TCP for Android, and cloud and embedded apps can connect through web sockets, Java Beans, and other custom transports. Once the library establishes a connection between the smart device and head-unit through the preferred method of transport, the two components are able to communicate using the SDL defined protocol. The app integrating this library project is then able to expose its functionality to the head-unit through text, media, and other interactive elements.

The app library component of SDL is meant to run on the end user’s smart-device from within SDL enabled apps, as an embedded app, or connected to the cloud. App libraries allow the apps to connect to SDL enabled head-units and hardware through bluetooth, USB, and TCP for Android, and cloud and embedded apps can connect through web sockets, Java Beans, and other custom transports. Once the library establishes a connection between the smart device and head-unit through the preferred method of transport, the two components are able to communicate using the SDL defined protocol. The app integrating this library project is then able to expose its functionality to the head-unit through text, media, and other interactive elements.

The app library component of SDL is meant to run on the end user’s smart-device from within SDL enabled apps, as an embedded app, or connected to the cloud. App libraries allow the apps to connect to SDL enabled head-units and hardware through bluetooth, USB, and TCP for Android, and cloud and embedded apps can connect through web sockets, Java Beans, and other custom transports. Once the library establishes a connection between the smart device and head-unit through the preferred method of transport, the two components are able to communicate using the SDL defined protocol. The app integrating this library project is then able to expose its functionality to the head-unit through text, media, and other interactive elements.

DefaultJ is a powerful Java library that provides default values for any class, offering multiple strategies for obtaining those values. It can be used as a dependency injection utility, similar to Guice. With 14 built-in strategies, DefaultJ can obtain default values through various means such as explicit bindings, annotations, enum values, factory methods, and more. It also supports custom annotations and offers annotation processors for validation. Available on Maven Central, DefaultJ can be easily integrated into Gradle and Maven projects. Contributions and selective usage of the library are encouraged.

DefaultJ is a powerful Java library that provides default values for any class, offering multiple strategies for obtaining those values. It can be used as a dependency injection utility, similar to Guice. With 14 built-in strategies, DefaultJ can obtain default values through various means such as explicit bindings, annotations, enum values, factory methods, and more. It also supports custom annotations and offers annotation processors for validation. Available on Maven Central, DefaultJ can be easily integrated into Gradle and Maven projects. Contributions and selective usage of the library are encouraged.

The Plasma project is an SDO 2.1 implementation with associated provisioning and other tools. In its initial releases, the PlasmaSDO™ implementation seeks to address the need for automation and code generation under SDO for standard enterprise Java web applications while focusing on critical operational considerations these applications face, such as optimistic and pessimistic concurrency control. The PlasmaSDO™ implementation is not bound to any integrated development environment (IDE) and provides support for standard Java™ based build tools. Note: Such operational considerations such as optimistic and pessimistic concurrency control are seen as a feature gap within various commercial and open-source SDO offerings, and are facilitated in PlasmaSDO™ by a custom UML profile and various associated SDO API extensions.

This library is a façade for image manipulation, acting as a proxy to libraries such as Java2D, JAI, ImageJ. In its early years (after 2003) it was used for photo development, metadata management and even demonstrated distributed calculus on the Sun Grid. At the end of 2016 development stopped. It resumed at the end of 2022, dropping obsolete stuff (JAI). At the moment the portions related to image manipulation are not tested. Features about metadata manipulation are being actively developed. A few scripts for U*ix and Windows systems are provided to quickly run examples: + runViewerExample.sh + runHistogramViewerExample.sh + runViewerExample.bat + runHistogramViewerExample.bat Directory tree ============== * modules/Core sources for the core component * modules/Metadata sources for the Metadata component * modules/Processor sources for the imaging processor * modules/Renderer sources for the renderer * modules/Examples/ViewerExample example about the renderer * modules/Examples/HistogramViewerExample example about histogram computation * modules/Examples/CustomOperationExample example about custom operations * modules/Examples/Miscellaneous miscellaneous examples