Add development build profile

[bhall2001]

The baseline files do not allow "development" as a valid build profile. The documentation implies development is one of the baseline profiles. Without development in the app.yml file, an error is encountered when packaging an app in the development build profile.

[trevordevore]

@bhall2001 Thanks or the PR. development is the build profile that is returned when running in the IDE or using the test version of the app. You don't package an app using the development profile. If you can point me to the section in the docs where we need to clarify this point then we can update the docs.

[bhall2001]

Being able to build "development" versions of an app before going to beta is a useful feature. I find that I often need to share a WIP with someone before I call it "beta".

The documentation for packager implies to me that this is an intended capability and indeed a feature of the build profiles. I'll +1 the need to be able to have a level before beta called "development" as is suggested at the below link.

https://github.com/trevordevore/levure/wiki/packager#development

Note: If you do decide to remove the development build profile from the documentation, there is a reference in the section above the link provided as well as the screen shot.

[trevordevore]

The good news is that you can add any build profile name you would like. You are in no way limited to the ones included in the default app.yml file.

I have levureBuildProfile() return "development" in the IDE because the LiveCode environment() function returns "development" when running in the IDE. When you build a test build of your app "development" is returned as well since the app is running in the same unpackaged state.

Now that I've written the above paragraph I wonder if it would be better for levureBuildProfile() to return "unpackaged" in the IDE and when running the "test" executable Thoughts?

[macMikey]

Why not have it return "test"?

[trevordevore]

"test" could work as well.

I think I prefer "unpackaged" to "test" though. I think it is more descriptive of the application state. In the IDE and in the "test" standalone the app has not been packaged up. No passwords have been applied and files from the copy files section haven't been moved into a single packaged app.

[bhall2001]

I'm so new to Levure and in reading the docs, I was thinking there should be a default development build profile just by the example being used. It's great that any build profile name can be used.

I'm too new to Levure I honestly don't think I could make a suggestion either way except to say that I don't like test. To me test is more of a state that is almost final and as opposed. At that point the project is more of an "in the oven" still getting baked. I'd say stick with development as that is what the IDE calls it. My next vote would be unpackaged...

[macMikey]

The reason I suggest "test" is because it reflects the build terminology back.