manifest file should be created along with sketch

[codeanticode]

Right now, the manifest file is created only after opening the permission selector, or running the sketch on the device or in the emulator. Should be available as soon the sketch is created, so the user can set parameters without having to using the permission selector or running it first.

[benfry]

As of recently, the editor now has the concept of a template project which might be helpful for this. No template code should be included, but a set of files can be added to the sketch by default.

[codeanticode]

Oh cool, thanks for the pointer. I will look into it!

[kfrajer]

Hi @codeanticode I was testing a sketch and I noticed I am able to add permissions using the permission selector. However, if I use the permission selector and un-check any permission, the manifest is not updated. I have to remove the manifest. Then, I open the permission selector and I will need to re-check all the permissions I need. Should I create a bug report?

[codeanticode]

@kfrajer Yes, please go ahead an open a separate issue about the permissions. Thank you!

[jgmy]

Hmmm. Having a manifest file from APDE, I find that...
a) Permissions in the manifest are not read by the Android Mode permissions menu.
b) Permissions from the Android Mode permissions menu are not updated into the manifest file.
c) When exporting to gradle from Android Mode, the package name in the manifest is deleted. The gradle android/app/build.gradle applicationid is changed to "processing.test."+ ScriptName, no matter what android manifest said.
d) There is no option to change packagename in AndroidMode, indeed.
(Using Processing 3.4 android mode 4.0.4).

[codeanticode]

@jgmy thanks for bringing this up. The improvement described at the beginning of this thread (making the manifest available before running the permissions manager) would be useful, and I will tag this issue for the 4.1 milestone.

However, I'm unable to reproduce (a) and (b). Both seem to work for me. What permissions specifically set in the manifest are not read by the permissions manager, and vice versa?

I think (c) is a good improvement suggestion, and will try to include it for 4.1.

As for (d), not having a UI option to set the package name was by design: Processing explicitly leaves more advanced options/features out of the PDE to keep it simple and non-overwhelming to people new to programming. One of course could debate where to draw the line on what "more advanced" means :-) In any case, if (c) is added, then there would not be a need to set the package name from the UI right ;-)

[codeanticode]

Done with bbdc492