Dagger
Search

fyne

This module has been generated via dagger init and serves as a reference to
basic module structure as you get started with Dagger.

Two functions have been pre-created. You can modify, delete, or add to them,
as needed. They demonstrate usage of arguments and return types using simple
echo and grep commands. The functions can be called from the dagger CLI or
from one of the SDKs.

The first line in this comment block is a short description line and the
rest is a long description with more detail on the module's purpose or usage,
if appropriate. All modules should have a short description.

Installation

dagger install github.com/dolanor/daggerverse/fyne@91f4dfa24ccc4895696fc98a6cbe71fd5d4d48aa

Entrypoint

Return Type
Fyne
Example
dagger -m github.com/dolanor/daggerverse/fyne@91f4dfa24ccc4895696fc98a6cbe71fd5d4d48aa call \
func (m *MyModule) Example() *dagger.Fyne  {
	return dag.
			Fyne()
}
@function
def example() -> dagger.Fyne:
	return (
		dag.fyne()
	)
@func()
example(): Fyne {
	return dag
		.fyne()
}

Types

Fyne 🔗

withFyne() 🔗

Return Type
Container !
Arguments
NameTypeDefault ValueDescription
ctrContainer !-No description provided
Example
dagger -m github.com/dolanor/daggerverse/fyne@91f4dfa24ccc4895696fc98a6cbe71fd5d4d48aa call \
 with-fyne --ctr IMAGE:TAG
func (m *MyModule) Example(ctr *dagger.Container) *dagger.Container  {
	return dag.
			Fyne().
			WithFyne(ctr)
}
@function
def example(ctr: dagger.Container) -> dagger.Container:
	return (
		dag.fyne()
		.with_fyne(ctr)
	)
@func()
example(ctr: Container): Container {
	return dag
		.fyne()
		.withFyne(ctr)
}

buildApk() 🔗

Return Type
File !
Arguments
NameTypeDefault ValueDescription
sourceDirectory !-source is the root of source we're using to build the app.
appIdString !-App ID is the identifier that is use for an app. In general, it is based on reverse name notation (eg. com.fynelabs.nomad).
targetPlatformString !-Target Platform represents which os/arch we are building for. (eg. android/arm64, android/arm)
appMainDirString !-app main dir is where fyne will look for the base of the app to build into an APK, relative to the source directory.
apkPathString !-APK Path represents the path where fyne has built it. normally, it should be in the source dir, but the name of the apk could vary. We need to set this so we know where we need to look to be able to export the file.
Example
dagger -m github.com/dolanor/daggerverse/fyne@91f4dfa24ccc4895696fc98a6cbe71fd5d4d48aa call \
 build-apk --source DIR_PATH --app-id string --target-platform string --app-main-dir string --apk-path string
func (m *MyModule) Example(source *dagger.Directory, appId string, targetPlatform string, appMainDir string, apkPath string) *dagger.File  {
	return dag.
			Fyne().
			BuildApk(source, appId, targetPlatform, appMainDir, apkPath)
}
@function
def example(source: dagger.Directory, app_id: str, target_platform: str, app_main_dir: str, apk_path: str) -> dagger.File:
	return (
		dag.fyne()
		.build_apk(source, app_id, target_platform, app_main_dir, apk_path)
	)
@func()
example(source: Directory, appId: string, targetPlatform: string, appMainDir: string, apkPath: string): File {
	return dag
		.fyne()
		.buildApk(source, appId, targetPlatform, appMainDir, apkPath)
}