VisualNEO Web. Version 25.10.17 released (Major version) - Forum

Forum Navigation
You need to log in to create posts and topics.

VisualNEO Web. Version 25.10.17 released (Major version)

IMPORTANT: THIS IS A MAJOR VERSION UPDATE

Free update for those who bought or updated their license in the last three months:
The update is free only for users who have purchased VisualNEO Web or an update within the last three months (after 2025 August 17). If you are elegible for a free update please send us an email with your Purchase ID and System ID asking for a free upgrade. Please be patient. Meanwhile you will enjoy a full version 30 days free trial.

50% discount code for those who already have a license:
Users who purchased previously will get a 50% discount code.
If you don't get the discount code in your email within a few days just send us an email with your Purchase ID.

This is a major version update with many improvements:

Software: VisualNEO Web
Version: 25.10.17

Updated Plugins:

neoOpenRouter:
New command neoOpenRouterVision.
Now you can send images to the AI model (for those models supporting vision). More info here

FabricJS:
Expanded with many new action commands. . More info here

neoPhp:
Better PHP 8.1 support.
Fixed user session management problem. More info here.

neoAjax:
Better error management and efficiency improvements. More info here.

neoCrypto:
Updated JavaScript library. More info here.

neoPDF:
WEBP image format support. More info here.

neoCMS:
New commands to manage updating and deleting information. More info here.

neoAnimation:
Some fixed errors and improvements.

neoGSheets:
Now you can get Google Sheet metadata. More info here.

neoGpt:
New command neoGptChatWithVision. More info here.

New Plugins:

neoLogin:
A complete, lightweight and simple user authentication system for VisualNEO Web applications based on SQLite and PHP. More info here.

neoWP:
Seamlessly integrates your VisualNEO Web applications with WordPress, allowing you to access, display, and interact with WordPress users and content (posts, pages, media, and categories) directly from within your app. More info here.

neoPDF2:
A NEW powerful plugin for VisualNEO Web that enables creation, loading, editing, and rendering of PDF documents directly from your web applications. More info here.

neoJEdit:
This NEW plugin adds a powerful, lightweight, and fully customizable HTML WYSIWYG editor to your VisualNEO Web applications. More info here.

neoSheet:
This powerful plugin brings full-featured spreadsheet functionality to your VisualNEO Web applications, powered by the open-source Jspreadsheet CE library. More info here.

Image support:
AVIF image support (although it does not render in design view, only at run time).

Inline PHP support:

VisualNEO Web now supports inline PHP code within your app’s HTML pages.
You can include PHP snippets between <?php ... ?> tags to perform server-side tasks such as file handling, database queries, or generating dynamic content at load time, before the app is delivered to the browser.
⚠️ Note: VisualNEO Web apps are Single Page Applications (SPAs) — PHP code is executed only once on the server when the page is requested, not dynamically after navigation or interaction inside the app.
The final compiled file will be generated as index.php instead of index.html automaticaly.
A PHP web server, such as the included neoPhp Server, is needed.

This feature allows developers to easily integrate server-side logic where needed, while keeping the simplicity and performance of client-side SPAs.

HTML Example:

<p>The current date and time is: <?php echo date("Y-m-d H:i:s"); ?></p>

You can download the new version from the downloads section.

Please let me know if you have any issues or questions.
Thank you very much for your support!

Vadim, alangonzalez91 and 7 other users have reacted to this post.
Vadimalangonzalez91farhad2008BGUKCDY@44danitoemosmartmediaPhil78

Looks good  but information on the neoSheet plugin unavailable?

Can the trial version be run together with existing licensed Version?

@bguk Sorry I forgot the most important new plugin:

neoSheet:
This powerful plugin brings full-featured spreadsheet functionality to your VisualNEO Web applications, powered by the open-source Jspreadsheet CE library. More info here.

Can the trial version be run together with existing licensed Version?

I don't think so. Sorry!

You cant run it along side as I downloaded it and it replaced it.  But so what, we should all keep supporting Luis and his hard work.  Im going to sending the money in this week as I want to keep supporting Luis on this great program.  Im still trying to learn it and its been interesting but with the Link that you posted for ChatGPT, has made it much easier.

Luis, not sure how you do it but please upload to chatGPT the new docs so it can help us better.  Thanks so much.

@no1g8tor96 thank you for your kind words :)
I have updated VisualNEO Web GPT with the new version documentation.
In the coming days I will feed it with more sample code.

Thanks again!

Vadim and CDY@44 have reacted to this post.
VadimCDY@44

@luishp

Very often i have to manage the same problem. When a container has row class width and height are ignored. Why is this happening ? In neo-row happens the same ? Min-Max width,height are working with row. When i create a plugin, i want plugin to run in both situations, with row class or with specific dimensions. Any ideas . ?

@smartmedia

That’s an excellent and very common question — and it shows you’re running into one of the key differences between fixed layout and responsive layout in VisualNEO Web. Let’s go step-by-step in a simple way 👇

🧱 Why your container’s width and height are ignored when it has the row class

When you add the class row to a container, you are turning it into a layout element that follows Bootstrap’s grid rules (Bootstrap 3.1 in this case).

That means:

  • A row is designed to automatically adapt to the available space.

  • Its main job is to organize other elements (columns), not to have a fixed size.

So, even if you set a width like 300px, Bootstrap says:

“No, this row must stretch to the full width of its parent, because that’s how responsive grids work.”

That’s why your container’s width and height values appear to be ignored. The row always tries to fill all horizontal space and grow vertically based on its content.


🧩 What about neo-row?

In VisualNEO Web, neo-row is a built-in responsive class that works similarly — but it uses Flexbox, a more modern layout system than Bootstrap’s old grid.

It also automatically adjusts to the available screen size:

  • Child elements are arranged in flexible rows.

  • The container expands or shrinks depending on its children.

So yes — the same thing happens: width and height values are not respected because <neo-row> is designed to be fluid and responsive, not fixed in size.

However, min-width, max-width, min-height, and max-height do work — because they act like limits, not exact measurements.
They tell the layout: “you can stretch, but don’t go below or above this size.”


⚙️ How to make your plugin work in both cases

When creating a plugin, it’s smart to let it adapt depending on where it’s placed —
either inside a normal fixed container, a Bootstrap .row, or a VisualNEO <neo-row>.

Here’s the general idea:

  1. If the container is a row or <neo-row>
    → don’t force specific width/height values; instead, use flexible sizing like 100% or auto.

  2. If the container is a normal (non-row) container
    → use the specific pixel or percentage sizes defined in the VisualNEO app.

That way, your plugin won’t “fight” with the responsive layout.


🧠 Example logic (in plain English)

When your plugin starts:

  • Check if the element has the class row → this means it’s Bootstrap responsive.

  • Check if the element has the class neo-row  → this means it’s VisualNEO’s Flexbox layout.

  • If neither → it’s a normal fixed container.

Then:

  • For .row or neo-row → use flexible, percentage-based sizing.

  • For normal containers → use exact width/height from the properties.

Vadim and smartmedia have reacted to this post.
Vadimsmartmedia

@luishp

this is what exactly do right now, i am reading container class. The problem is that vnw ignores width and height, in normal world it should accept it and not collapse.

@smartmedia please open a new thread.
Width and height values are not respected because row and neo-row are designed to be fluid and responsive, not fixed in size.

smartmedia has reacted to this post.
smartmedia

@luishp
Such updates are always a joy.

Такие обновления только радуют

With neoLogin you can manage licenses for WordPress and more.
При помощи neoLogin можно управлять лицензиями для wordpress и не только

neoLogin allows you to create commercial applications much faster and with higher quality.
neoLogin позволяет создавать коммерческие приложения гораздо быстрее и качественнее.

Vadim and CDY@44 have reacted to this post.
VadimCDY@44