Download the PHP package lucinda/framework without Composer

On this page you can find all versions of the php package lucinda/framework. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package framework

Lucinda Framework

Lucinda Framework 4.0 is an ultra high performance web application skeleton developed with simplicity and modularity at its foundation. In order to fulfil these goals, it functions as an XML-based contract of 24 completely independent APIs, each designed for a particular aspect of a web application's logic:

diagram

APIs that take part in this dance are:

API Description
Abstract MVC API handles any type of requests into responses using MVC paradigm
STDOUT MVC API handles HTTP requests into responses on top of Abstract MVC API
STDERR MVC API handles errors or uncaught exceptions into reports and responses on top of Abstract MVC API
View Language API templates HTML views using a language extending HTML standard, similar to Java's EL & JSTL
Logging API logs messages/exceptions to a storage medium
SQL Data Access API connects to SQL vendors (eg: MySQL), executes queries and parses results on top of PDO
NoSQL Data Access API connects to NoSQL key-value stores (eg: Redis), executes operations (eg: get) and retrieves results
Web Security API performs authentication and authorization on different combinations
OAuth2 Client API communicates with OAuth2 Providers (eg: Facebook) in order to retrieve remote resources owned by client
HTTP Headers API encapsulates HTTP Request/Response headers according to ISO standards and applies Cache/CORS validation when demanded
Internationalization API makes it possible for HTML views to be translated automatically to client's locale

Framework logic thus becomes strictly one of integrating all above functionalities for a common goal, that of providing an integrated platform for programmers to start developing on. To further modularity and ease of update even further, framework itself is broken into THREE APIs, each with its own repo:

API Description
Framework Skeleton API contains "mobile" part of framework logic, the project skeleton developers will start working on once framework was installed. Once installed, logic inside becomes owned by developers, so it cannot be updated.
Framework Engine API contains "fixed" part of framework logic, from binding classes required in APIs "conversation as well to general purpose classes. All logic inside is owned by framework, so open for composer update but not open for change by developers.
Framework Configurer API contains console step-by-step configurer as well as files going to be copied on developers' project once process completes. All logic inside is owned by framework, as in above, but choices of configuration are in developer's hands.

As its composing APIs, framework itself is PHP 8.1+ and PSR4 autoload compliant, using unit testing (for engine) as well as functional testing (for skeleton and configurer) to insure stability.

Thanks to its modular and harmonic design, it's both extremely easy to use (as tutorials show) and exceptionally fast (as benchmarks show: 75 times faster than Laravel using factory settings for both). To learn more, go to:

https://www.lucinda-framework.com

All versions of framework with dependencies

PHP Build Version
Package Version
Requires ext-simplexml Version *
lucinda/framework-engine Version ~1.0
lucinda/http-caching Version ~2.0
lucinda/logging Version ~2.0
lucinda/nosql-data-access Version ~2.0
lucinda/oauth2-client Version ~1.0
lucinda/security Version ~2.0
lucinda/mvc Version ~2.0
lucinda/sql-data-access Version ~2.0
lucinda/view-language Version ~2.0
lucinda/internationalization Version ~2.0
lucinda/errors-mvc Version ~1.0
lucinda/request-validator Version ~1.0
lucinda/framework-configurer Version ~1.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package lucinda/framework contains the following files

Loading the files please wait ....