This issue was originally filed by S.Nol...@gmail.com
It would be a great boost to productivity with the DartEditor, if it was possible to add dart scripts to be run in context from the menu.
When building a project, helper scripts that construct library stubs, generate folder structures or customized code analysis or conversion could be simply written in dart and invoked somewhere via the context menu.
Example:
I write a dart script that takes a folder as context and creates class definition stubs according to a given pattern, wiring up standard imports etc and hook it into the dart editor menu. From there on i can generate stubs, reformat code, or generate class structures from markup files:
New File...
New Folder...
New Controler... (defined in my_menu.dart)
New Model... (defined in my_menu.dart)
New View... (defined in my_menu.dart)
the helper scripts to be added to the menu could be read in based on an interface they implement and be run in context of the point from where they are invoked ideally.
Value consideration:
When talking to other dartisans, i get the notion that quite a lot feel "caged" a bit in a rather rigid structure of the Dart editor. I also realized the potential of the build script. Being able to augment customizability especially when possible in the same language i am developing in would to my mind offer a big boost to the usefulness of dart editor in aspects of productivity and individualization.
This issue was originally filed by S.Nol...@gmail.com
It would be a great boost to productivity with the DartEditor, if it was possible to add dart scripts to be run in context from the menu.
When building a project, helper scripts that construct library stubs, generate folder structures or customized code analysis or conversion could be simply written in dart and invoked somewhere via the context menu.
Example: I write a dart script that takes a folder as context and creates class definition stubs according to a given pattern, wiring up standard imports etc and hook it into the dart editor menu. From there on i can generate stubs, reformat code, or generate class structures from markup files:
New File... New Folder... New Controler... (defined in my_menu.dart) New Model... (defined in my_menu.dart) New View... (defined in my_menu.dart)
the helper scripts to be added to the menu could be read in based on an interface they implement and be run in context of the point from where they are invoked ideally.
Value consideration: When talking to other dartisans, i get the notion that quite a lot feel "caged" a bit in a rather rigid structure of the Dart editor. I also realized the potential of the build script. Being able to augment customizability especially when possible in the same language i am developing in would to my mind offer a big boost to the usefulness of dart editor in aspects of productivity and individualization.
my2 pesos, Stefan