Quote from luishp on May 2, 2025, 6:09 pm

@tmcd VisualNEO Win and VisualNEO Web are Windows-only applications primarily due to their dependency on the Windows operating system's architecture and libraries. Here's a clear breakdown of why these tools aren't natively compatible with macOS:

1. Built Using Windows-Specific Technologies

Both VisualNEO Win and VisualNEO Web are developed using programming frameworks and tools (Delphi) that are tightly coupled with the Windows API. This means:

• They depend on .DLL files (Dynamic Link Libraries) and Windows-only runtime components.

• User interface elements are rendered using Windows-specific GUI frameworks like VCL or WinForms.

2. Installer and File System Assumptions

The applications assume a Windows-like environment:

• Installation paths and executable formats (.exe) are designed for Windows.

• They use Windows-style file paths and registry entries, which do not exist in macOS.

3. Lack of Cross-Platform Runtime

Unlike web technologies or Java (which run on a virtual machine), VisualNEO Win and Web do not use a cross-platform runtime. They are compiled as native Windows applications, which inherently cannot run on macOS without emulation.

4. No Native macOS Compilation Option

The internal compiler of VisualNEO Web does allow apps to be exported as web apps or compiled using NW.js for macOS, but the development environment itself (VisualNEO Web IDE) can’t be compiled to run on macOS without significant changes to its source code and dependencies.

5. Solutions for Mac Users

While there’s no official macOS version, Mac users can still run VisualNEO software using:

• Wine (though compatibility may vary)

• Virtual machines like Parallels Desktop or VMware Fusion

• Boot Camp (on older Intel Macs)

Quote from TMcD on May 2, 2025, 8:40 pm

Thanks everyone. Those answers were expected and I understand.

Main question is will the output for web applications actually work then on a Mac browser, Chrome, Safari, etc?

Now a few specific questions:

I’d like to create an interface that will then communicate with webhooks for sending and receiving data, is that possible as the software is now, or would a add-on/plugin be needed?

Same question with APIs. I’d like to be able to send and receive data to APIs in an app I create. Is that possible with the app as it is now?

I guess I’ll add this, Can both VisuaNEO and VisuaNEO Web do both of the above.

Thanks

Quote from luishp on May 3, 2025, 8:08 am

@tmcd

✅ 1. Will VisualNEO Web output work on Mac browsers like Chrome and Safari?

Yes, absolutely. VisualNEO Web generates standard web applications (HTML5, CSS, JavaScript), which means:

• Apps can be run in any modern web browser, including Chrome, Safari, Firefox, and Edge on Mac, Windows, or Linux.

• You can try any of the online samples to check it yourself.

✅ 2. Can you use Webhooks (send/receive data) in VisualNEO Web without plugins?

Yes, you can. VisualNEO Web includes built-in HTTP communication capabilities through NeoScript commands. For example:

• You can use the Send or POST actions with JavaScript or via plugins like neoAjax to communicate with webhooks.

• No external plugin is required unless you need more advanced handling or response parsing.

If needed, neoAjax plugin simplifies asynchronous HTTP requests (GET/POST), which are common in webhook use cases.

✅ 3. Can you work with APIs (send/receive data) in VisualNEO Web?

Yes. You can:

• Send and receive data to/from REST APIs using neoAjax (plugin) or JavaScript actions directly in NeoScript.

• Parse and handle JSON responses using built-in commands like ParseJSON, StringifyJSON, and variable management.

So again, you don’t necessarily need an add-on, but using the neoAjax plugin can simplify the process and improve maintainability.

✅ 4. Can both VisualNEO Win and VisualNEO Web handle webhooks and APIs?

• VisualNEO Web is fully capable of webhooks and API communication using the techniques above.

• VisualNEO Win, is not the appropiate tool for this but can also perform simple HTTP requests, though the approach uses different commands (like Download, Upload, or integrating Windows DLLs or VBScript).

Please check the online documentation for more information.