Write code in NexSourceCode. Build applications with Nex MVC.
A desktop editor and a PHP framework, connected throughout development.
1<?php
2
3use Nex\Route;
4use App\Http\Controllers\HomeController;
5
6// Your application starts here.
7Route::get('/', [
8 HomeController::class,
9 'index'
10])->name('home');
11
12 WORKSPACE ILLUSTRATION Code, structure and application flow in one view.
NexSourceCode and Nex MVC complement each other. An editor to manage your work. A framework to run your application.
Write and organize code in sheets, connect it visually with Blueprint, and run your project from one desktop application.
A foundation for routes, controllers, models, views and data access. Give your application code a clear structure.
From an incoming request to the page your users see. Each part has a clear responsibility.
Map URLs to controllers and views using PHP code or Blueprint route cards.
Process requests and prepare data. Keep presentation separate from application behavior.
Render PHP pages and connect stylesheets and JavaScript through Blueprint.
<?php
use Nex\Route;
use App\Http\Controllers\HomeController;
Route::get('/', [HomeController::class, 'index'])
->name('home');
// Or connect the route and view
// using a visual Blueprint card.<?php
namespace App\Http\Controllers;
use Nex\Controller;
class HomeController extends Controller {
public function index(): array {
return ['title' => 'Hello from Nex.'];
}
}<!doctype html>
<html lang="en">
<head><title>My first website</title></head>
<body>
<h1><?= e($title) ?></h1>
<p>Built with Nex MVC.</p>
</body>
</html>
<!-- Connect CSS & JS through Blueprint. -->Learning example. In a Blueprint project, bind the view on the route card and avoid defining the same route twice.
Organize source, understand connections and test the result within the Nex workflow.
Group Client source in .nexcl and Server source in .nexsv. Multiple sheets stay together in one encrypted container.
Connect views to CSS and JavaScript. Arrange routes, controllers and views as parts of a connected application flow.
Manage NexSQL schemas and data in the application. MCP lets AI work within the selected workspace, subject to permissions and revision checks.
A short workflow to start building.
Select a project folder and use Install to prepare the Nex foundation.
Fill your sheets, link assets and bind routes to views through Blueprint.
Check prerequisites with nex doctor, then run nex dev in the NexSourceCode terminal.
NexSourceCode is the desktop editor and development environment. Nex MVC is the PHP framework. Both belong to the Nex ecosystem, with different roles.
No. Nex MVC has routes, controllers, models and views, but uses its own APIs and runtime. Do not assume support for Artisan, Blade, Eloquent, Composer packages or Laravel extensions.
The introduction and guide display content with browser interactions and do not require a database. Applications that store data need the appropriate NexSQL configuration.
Encrypted containers protect stored source. Visitors can still inspect HTML, CSS and JavaScript sent to their browser. Encryption does not make browser-delivered source invisible.
Open NexSourceCode, select a workspace folder, prepare the project using Install, and explore sheets and Blueprint. This guide covers the basic steps and commands. No public installer is linked here.
Start with the documentation. Continue with your first project.