-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigator view for Gradle build scripts #85
Comments
Did you mean the same thing as in the project's context menu under "Tasks", only as a subnode for "build.gradle" (or whatever)? |
I mean the Navigator view displayed with Ctrl-7 shortcut. And if you can create tasks as subnodes of build.gradle it will be probably very simple to hook it into this view as well. I think that similar feature in IJ is handy. |
I see. Do you happen to know how to link something with build.gradle, so that it is displayed in the navigator? |
http://bits.netbeans.org/dev/javadoc/org-netbeans-spi-navigator/overview-summary.html |
Thanks, I'll read this. Anyway, Gradle mime type is still problematic as it is effectively the same as Groovy. I believe this is why two "Source" button is displayed for Gradle files (and Groovy) above the editor. Sadly, noone could tell me how to actually create the mime type properly (there was always some problem with it). That is, Gradle files should be treated like Groovy files in the editor but have a different icon. |
What do you think of such a solution where I replace the current "Tasks" action in the project's context menu with something like this: "Tasks in Navigator". This would activate the Navigator tab where tasks would be listed. I imagine a list where each line is a task with two buttons: "Run" and "Run with Different Arguments". Though with icons instead of a text captions. My problem with the current tasks action node always was that there could be a lot more tasks what can be displayed (this is true for some of my projects). Also, the list view can be easier to click on. |
|
Even if not the context menu, I'd prefer if there was also a more noticable way to list the tasks in the navigator. I'm not against showing the tasks for each ".gradle" file but there should be another way as well. That is, I don't always editing the build scripts right before I want to execute a task. Speaking of tasks, there should be a way to more quickly refresh the list of tasks. Although, fetching the tasks only takes considerably less effort than reloading the project, the internal structure of the code doesn't really support it. This is because it is not currently possible to change parts of the internal model, only reload the whole model as a single step. This is one thing to keep in mind for the new API. |
BTW: when this is done it will be simple to copy 'Add shortcut...' action that you can see on Ant task nodes. This lets you create toolbar/menu/shortcut running a build target. I think this can help a lot because it will simplify launching of non-standard tasks. |
Shortcuts would be nice but maybe it would be even better for custom tasks defined by the user. Anyway, I'll do this for the release after the next one (i.e., for 1.2.9) because I'll have a new release after Gradle 1.9 is out. This and the improved API for extensions is my priority. |
Maybe this issue similar to the new feature available in upcoming release of netbeans for Maven. Geertjan has been blogged about it. You can check here: https://blogs.oracle.com/geertjan/entry/early_maven_christmas_present_from. This is also nice to have :) I guess for the possible solution in the duplicate button in the editor because of conflicting MIME-Type is "shadow". NetBeans have this a long ago but I'm not sure if it can be used on MIME-Type. http://wiki.netbeans.org/DevFaqDotShadowFiles |
Shadow files could be good if I knew how to hook into file opening and open something else instead (if it is possible) but thanks for letting me know. |
Similar functionality as for Ant build.xml to show structure of build.gradle / list of targets. List of target should probably make it possible to run it immediately.
The text was updated successfully, but these errors were encountered: