tricky1975 / maan Goto Github PK

:P

This is a follow up to #15 -- To make sure things work as they should.

The idea is like this.
When you have a project with multiple forms, only one of them gets shown by default UNLESS you tell the scripts of course to do otherwise.
The new form gets loaded on the moment it’s requested to be opened for the first time.

No this doesn't make faster building times. In fact this will slow it down, but at least it can prevent a completely messed up file system on Unix based system when building while the Maan application is running. Rebuilding its JCR6 file is not harmful. It will only cause the Maan-application to crash, but no damage is caused in the process requiring an entire system reset.

I am really conflicted about this one.
Mac uses the top bar showing the pulldown menus.
Windows and Linux tie them to the window.
The latter also makes menus out of reach when the window is disabled or even not visible, the Mac variant does not.

I hope I can come up with a good solution to this one :-/

I don't trust the "public domain status" of the logo.
I like the design that's not the problem, but I don't want any copyright issues popping up here. ;)

The idea is this…
In the project file a list can be made of all files serving as dependency, these should be file JCR6 supports of course. These just contain the extra lua files and other stuff the library needs.

The dependency will need to be suffixed with .maanlib regardless of the used platform. Preferably lower cased due guarantee support on all OSes regardless of case-sensitive file systems (Maan is supposed to be “above” platforms… well sort of).

The system will look in either the folder where the main project file is located or in the maanlibs folder which will be “C:\users\\AppSupport\Roaming\MaanLibs\” in Windows “/Users//Library/Application Support/MaanLibs/” on Mac and “/home//.MaanLibs/“ on Linux if that latter version will actually see the light.

This way it can act as a “true” dependency (like Linux users love for some reason beyond me) or as a lib merged with the package, like in the app-bundle like Apple requires (and which works better for distribution anyway), or which is handier to make Windows builds more “portable”.

There is also a rule. Number the libs and increase it only when a new version is no longer backwards compatible with the older version (in case of deprecation or the use of external libs no longer being compatible or discontinued).

JCR6 is a patchable file system, so Maan will think it’s all one application and will not see the difference between files from the main project or any of its dependencies. That’s the idea.

For buttons, menu items and panels.
Although menu items are for the time being not that important until I got a good solution for #3

This can be supported, but is not one of the priority features, but I'll put it in here, so I will not forget later on. ;)

A full workout comes later. Getting the listbox itself to work is prime concern ;)

• Text (I’ll just dump that on the output screen)
• Pictures (if worst comes to worst, I can quickly code a previewer tool, no problem).
• Audio (There is already an ogg loader inside MAAN for the error signal, so this should be easy).

This does (fortunately) not affect the building process

I need to make sure an error is always noticed, and since getting all windows closed is not always working errors can sometimes go unnoticed... An signal is always heard.