Commit 98b1bf0d authored by Danny SMc's avatar Danny SMc

Merge branch 'master' of

parents 04c58692 fc5ff553
Discover App Documentation:
-> Multitasking,
-> Multitasking history,
-> Foreground/Background processes,
-> Touch screen,
-> Auto-updating,
-> Uses DiscoverAPI, and Base API,
-> Tablet, Turtle and Computer Support,
-> Full app meta data,
-> Can be used to manage app versions,
-> App icon support,
-> Command line interface,
-> Modular when building,
-> Cloud storage management (per-user),
-> Apps listing, with filters,
-> Snippets / Gist storage,
-> Discover Notifications/Alerts management,
-> Account management,
-> News Feed for general chat,
-> Chat rooms,
-> Mail system, for cross server mail,
-> Clean/Sleek design,
-> Fully featured API for plugins and extensions,
-> Multi-file uploader as one app,
-> New storage method in the backend,
-> Support for krist app selling (not recommended yet though),
-> Commenting system for apps,
-> Issues manager,
-> Multiple versions,
-> Upload app from pastebin,
-> User profiles for every user,
-> Embeddable API for OS's,
-> Package manager (dpm),
-> Krist support for requesting apps, donations and selling apps (maybe),
-> Embeddable API OS:
So a new feature is a lot of people are making app stores or struggle to use someone else's with this, you are actually able to call apps from the system, by choosing a list of functions to expose to your OS, like Mail, and Apps, and then you can call the function, either by adding to a coroutine, or just just a simple view.
-> Registering Plugins / Extensions
To register a plugin it's as easy as using the API code. This is an internal registering system that shall register event listeners, commands and other for your plugin, most of the time we aim to say try not to use too many otherwise you will make the App unstable due to it's internal clock. Anyway, when creating a new plugin you will need a basic plugin.ini file which should be in it's own folder inside .DA_PLUGINS folder. Here the App will parse and read your details, then install them to the program at runtime. Then it will look for a main or main.lua file. This should have your main code in, of course you can use other files, but that name is the entry point. When that program is called it shall pass over it's API environment, so you can then work with the environment.
-> Adding a menu item
This is relatively straight forward, you will need an icon which is 14 x 4 chars in size, which should use the custom image format. Once you have this image, it needs to be in the DiscoverApp icon manager as a table so then we can pass it to the menu manager. So to do this, you need to use the following:
- DiscoverApp.Register.MenuIcon(icon_name, icon_data);
- Icon name is the name of the icon in the icon database.
- Icon data is of course the table of the icon format.
Now you have registered your new image you will need to register the actual menu entry, this is done like so:
- DiscoverApp.Register.MenuEntry(icon_name, api_name, func_name, thread_name, requires login)
- Icon name is what you set when you registered the icon.
- api_name should be the middle part of the function it will run.
- func name, this is the function name that it will invoke, so the name of the function you created for it, this is the entry point into your own code.
- thread_name, this is the text that will come up in the task switcher.
- requires login is a true or false, and this will check if the user requires to be logged in to use the system, if they are not loggedin, there is no exposed user data.
Now that will register your menu entry.
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment