Mahdiware™

🔨 1 new commit to saynaa-packages:main: ad53278: added memory library by Mohammed Abdifitaax (Mahdiware)

Usage -- patch no required to use hex bytes

First test, mod menu build in SaynaaIDE

🚀 Saynaa Mod Menu Development I’m currently working on a set of Mod Menu tools for Saynaa, which will be used with SaynaaIDE to build Mod Menus. If you have any useful C/C++ tools, native libraries, utilities, or ideas that could be useful for Mod Menu development with Saynaa, feel free to share them with me. I’d like to explore and integrate useful tools into the ecosystem. Saynaa can load native .so modules, so these tools can be written in C/C++, built independently, and used from Saynaa through its native API. There is currently an Android limitation I’m working on: Android doesn't allow the .so libraries to be loaded normally from external/shared storage such as /storage/emulated/0. Loading the same libraries from the app's internal storage works correctly. I’m currently working on a solution so the workflow can be more flexible. The goal is to make SaynaaIDE a practical environment for building Mod Menus, while allowing developers to extend it with their own native tools. 🔥 If you have something useful that could fit this project, share it with me! #Saynaa #SaynaaIDE #ModMenu #Android #C #Cpp #Termux #NativeDevelopment

Soon...

⚠️ Important — Existing SaynaaIDE Projects Projects created with older versions of SaynaaIDE may not work directly in SaynaaIDE 1.0.1. This release contains major internal changes, so older projects may need to be updated. For example, in init.sa:

activity.getSaynaaDir() 

should now be used instead of:

java.saynaadir 

This is especially important because SaynaaIDE now supports creating Mod Menus, where SaynaaActivity may not be available. The package name has also changed:

com.android.saynaa → com.saynaa

There are also other internal changes that may require modifications to older projects. ### 🆕 loadfile() has been updated The built-in loadfile() now supports:

loadfile([module:Module], path:String, [mode:Number=0]) -> Var 

Modes:

0: CLONE  — Create child module from parent context 1: SHARED — Execute inside parent module; changes affect parent 2: NEW    — Create empty module with no parent context 

package.loadfile has been removed because it was a duplicate of the built-in loadfile(). 🔧 If you are updating an old project, make sure to review these changes and update your code accordingly. #SaynaaIDE #Saynaa #Update #BreakingChanges #Development

⚠️ Important — Existing SaynaaIDE Projects Projects created with older versions of SaynaaIDE may not work directly in SaynaaIDE 1.0.1. This release contains major internal changes, so older projects may need to be updated. For example, in init.sa: activity.getSaynaaDir() should now be used instead of: java.saynaadir This is especially important because SaynaaIDE now supports creating Mod Menus, where SaynaaActivity may not be available. The package name has also changed: com.android.saynaa → com.saynaa There are also other internal changes that may require modifications to older projects. ### 🆕 loadfile() has been updated The built-in loadfile() now supports: loadfile([module:Module], path:String, [mode:Number=0]) -> Var Modes: 0: CLONE — Create child module from parent context 1: SHARED — Execute inside parent module; changes affect parent 2: NEW — Create empty module with no parent context package.loadfile has been removed because it was a duplicate of the built-in loadfile(). 🔧 If you are updating an old project, make sure to review these changes and update your code accordingly. #SaynaaIDE #Saynaa #Update #BreakingChanges #Development

Tasbeeh App

📢 Saynaa IDE — Project Directory Update I’ve changed the project directory structure in Saynaa IDE to make it more organized and easier to manage. Previously, projects were stored directly in: /storage/emulated/0/.SaynaaIDE/ This caused projects to not appear correctly in the app’s project list. 🔧 New project directory: /storage/emulated/0/.SaynaaIDE/project/ The main reason for this change is to keep the .SaynaaIDE directory organized and allow Saynaa IDE to have separate directories for different purposes, such as: - 📁 .SaynaaIDE/project/ — User projects - ⚙️ .SaynaaIDE/.build/ — Build-related files - 📦 .SaynaaIDE/.bin/ — Binary/tool files - 📤 .SaynaaIDE/.share/ — Files used when sharing projects This new structure will make it easier to manage projects, builds, binaries, and project-sharing data as Saynaa IDE continues to grow. 🚀 ⚠️ Important: Projects from older development builds may need to be moved to the new project/ directory. Thanks for testing Saynaa IDE and helping improve the project! ❤️ #SaynaaIDE #Android #IDE #Programming #Development #DevBuild #Update