Talk:Moodle App Plugins Development Guide
Mobile_support_for_plugins#Step_1._Update_the_db.2Fmobile.php_file currently reads "Plugin identifier - A unique name for the plugin, it can be anything (there’s no need to match the module name)." Why not to recommend to use the frankenstyle plugin name though? What else is a better candidate and why should developers use something else? It is confusing to say "it can be anything" if it is supposed to be unique. --David Mudrak (talk) 19:05, 4 September 2020 (UTC)
So, my understanding is that it is expected that the developer uses https://mobileapp.moodledemo.net/ and they make it connect to their own dev site where they have work in progress on the plugin exposed and available. However, it does not seem to be said anywhere. The "Getting started" does not say anything about what site the "app" should connect to, and then the "Development workflow" does neither. Also, it seems that the dev site should be accessible via a public URL, which again is not mentioned anywhere, as far as I could see. --David Mudrak (talk) 19:36, 4 September 2020 (UTC)
There is "First of all, we recommend creating a simple mobile.php for displaying a new main menu option" - but it does not say:
- is it db/mobile.php ?
- or is it classes/output/mobile.php ?
And in either case, what is the recommended contents of the file? --David Mudrak (talk) 21:14, 4 September 2020 (UTC)
There is external_format_text() used to format the module's intro. Why is there format_string() used to format the name and not external_format_string() ? --David Mudrak (talk) 09:59, 6 September 2020 (UTC)
