Next
Manage your Next app development.
Common commands:
next create <output directory>
Create a new next project in the specified directory.
next run [options]
Run your Next application.
Usage: next <command> [arguments]
Global options:
-h, --help Print this usage information.
Available commands:
add Add to property of current Next Project
build Build a project of Next
check_env check env the NextPackages
clean Clean a project of Next
create Create a new project of Next
exce Add to property of current Next Project
get Get property of current Next Project
info view info the Next
run Run a project of Next
set Set property of current Next Project
use Add new library in current project
version view version the Nex
Run "next <command> --help" for more information about a command.
Install with PyPi
pip install next-pm
Install code stable
git clone https://github.com/reitmas32/Next.git
Install code development
git clone https://github.com/reitmas32/Next.git
git checkout dev
Setup
cd $HOME # if your System is Windows use $LOCALAPPDATA
mkdir .next
cd .next/
echo 'NEXT_DIR:<DIR_OF_NEXT_INSTALATION>
NEXT_PACKAGES_DIR:<DIR_OF_NEXT_PACKAGES> > env.yaml
Contributors
Next is mainly supported by the development team of Game Engine MOON create by EGE Studios and currently managed by Next.Project
Future versions
The current version of Next is v3.4.0 but the development of Next is in constant evolution and it is planned to have for the next versions:
Commands
- next upgrade Easy update of Next
- next test Integration of Next and Unit Testing
- next doctor An easy way to view the status of C/C++ compilers
- next pbuild build custom programmer in python
- next prun run custom programmer in python
- next ptest test custom programmer in python
- next pclean clean custom programmer in python
- next install install package from next.packages.com
- next uninstall uninstall package from next.packages.com
Backend
- Dependency tree
- Separate cmake logic from next to implement more construction systems
- MacOS support
Frotend
- Create a GUI
Metadata
Release files for next-pm 3.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| next-pm-3.4.0.tar.gz | 24.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| next_pm-3.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 59.3 kB
Release files / next-pm-3.4.0.tar.gz
| Download URL | next-pm-3.4.0.tar.gz |
|---|---|
| Size | 24.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1c8cd437420418f68b94e5833657f007d0b27c52785ee056384add8ff9f3446
|
|
BLAKE2b-256 checksum How to use checksums |
a043ceb7a4ac47310917889bf1fa107cae92cfd117a761727c5dab7c1f221ed6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Release files / next_pm-3.4.0-py3-none-any.whl
| Download URL | next_pm-3.4.0-py3-none-any.whl |
|---|---|
| Size | 34.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
702ddabfc41458fd324050e034c4ce522b71535a77c359ddd796fcb406e13ccf
|
|
BLAKE2b-256 checksum How to use checksums |
10065ee8b1a5454993b759cee6afc7fa6eb9260c791a28e1ed8fcb9dc723e0c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for next-pm 3.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.