Preliminary support for [Dart](https://dartlang.org/) has been added to address Issue #371. You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3372
-- Commit Summary --
* Add preliminary support for Dartlang syntax highlighting
-- File Changes --
A data/filedefs/filetypes.Dart.conf (45) M data/filetype_extensions.conf (3)
-- Patch Links --
https://github.com/geany/geany/pull/3372.patch https://github.com/geany/geany/pull/3372.diff
Looks ok at first glance (and without knowing Dart, so no idea if its accurate there)
Does Dart have a standard implementation that you could define build commands for? See for example `filetypes.Kotlin.conf`.
Looks ok at first glance (and without knowing Dart, so no idea if its accurate there)
Does Dart have a standard implementation that you could define build commands for? See for example `filetypes.Kotlin.conf`.
Technically the dart compiler can be called on individual source files, just like in Kotlin. But, the most popular use for dart is probably building mobile applications with Flutter. And that requires the running the build command at the project base folder and never directly at the file level.
For example, [this](https://github.com/flutter/packages/tree/main/packages/go_router/example) is the project base folder, whereas all the dart source files are under `lib`.
I know for Kotlin as well, a lot of times you don't directly invoke the build command on the individual file, but rather using a build system like maven and gradle and invoke it at the project base folder.
So I guess is there a preference to add these build commands anyway, although they aren't all that useful for the normal development workflow?
Technically the dart compiler can be called on individual source files, just like in Kotlin. But, the most popular use for dart is probably building mobile applications with Flutter. And that requires the running the build command at the project base folder and never directly at the file level.
That should be doable if a Geany project is open and is based at the right place, see [this](https://wiki.geany.org/howtos/configurebuildmenu) for gory details.
So I guess is there a preference to add these build commands anyway, although they aren't all that useful for the normal development workflow?
There is no requirement, languages are different, tools are different.
@yangsfang pushed 1 commit.
f5b51eb4b722a94cb4e96a4e7fa830781d360102 Add preliminary support for Dartlang syntax highlighting
Thanks for the pointers. I added two commands that might be useful in the default new projects. I didn't add more because for compilation it really depends on which platform the project is configured to build against (android, ios, web, windows, or macos). That should be sufficient for now.
BTW, the [wiki](https://wiki.geany.org/howtos/configurebuildmenu) is wrong about `[build_menu]`. The right settings is `[build-menu]` as documented in the [manual](https://www.geany.org/manual/current/index.html#custom-filetypes).
@yangsfang pushed 1 commit.
fb79379a1dbd138841726358d17be3740e1a410b Add preliminary support for Dartlang syntax highlighting
The right settings is [build-menu] as documented in the [manual](https://www.geany.org/manual/current/index.html#custom-filetypes).
Fixed thanks
github-comments@lists.geany.org