Add 'compact java file' to templates

[homberghp]

Description

From Cay Horstmanns talk I got the idea to add a compact java template file,
so that in an onramp for students you can do

new file > compact-java-file.

This would then create a file along the line of

void main(){
    IO.print("Hello world");
}

Having such a file will allow you to run it from the current version (27) of NetBeans IDE and would
nicely line up with the onramping effort in Java and keep the big 🐍 away.

See Cay Horstmanns talk at JavaOne 2205

Use case/motivation

There are several effort to make the on-ramping of Java easier.
In the language itself, with compact java files, the new IO package, with short methods for printing etc.

Having this in the IDE as well would be a nice thing.

Related issues

Compact files work well in Java 27, in particular for starting student projects.

Are you willing to submit a pull request?

No

[neilcsmith-net]

This would be good, but I think this needs more thought than just a template. Have you tried running the IDE with a clean userdir (eg. netbeans --userdir /tmp/test1) and working through the whole process of getting to a single source Java file, compact or not?

If you click New File on the background actions, potentially the most obvious entry point, there is a Java file template under Other. We might want a more obvious second Java category for source-only templates?

If you have a project open, the New File wizard needs enhancements to work well with non-project files.

Is a compact Java template useful inside a project? We might need the reverse option of https://bits.netbeans.org/27/javadoc/org-netbeans-api-templates/org/netbeans/api/templates/TemplateRegistration.html#requireProject() ??

PS. apologies for the close/reopen - accidental button press while selecting some text! 😆

[mbien]

Is a compact Java template useful inside a project?

not sure if its useful, but it makes no real difference from javac perspective. javac wraps it into a synthetic class and calls it a day.

You can put a file into the root package of a maven project and use the compact syntax and it will land in the jar and run if needed, single file run action should work too by now.

So I think its fine to have the same compact file template for project and non-project usage. Compact java files don't like packages which seems to be the only restriction which sounds sensible to avoid confusion.

This would be good, but I think this needs more thought than just a template. Have you tried running the IDE with a clean userdir (eg. netbeans --userdir /tmp/test1) and working through the whole process of getting to a single source Java file, compact or not?

it works pretty well but NB doesn't really tell users what to do. E.g you can simply drag a folder with java scripts into NB and it will show up as tab and you can work with the files as usual.

Or you create something from the favorites tab. (maybe we should open the favorites tab by default on first launch)

There are a few traps though. NB scans eagerly, the compact file launcher seems to be lazy, so if you put a file into your home folder (or root folder where you store all your projects) and force it to index its game over. (i think home folders are now excluded but the problem is still there essentially)

[neilcsmith-net]

So I think its fine to have the same compact file template for project and non-project usage. Compact java files don't like packages which seems to be the only restriction ...

This is the kind of concern I'm thinking of. If only useful at the default level, then the template for module info might be worth looking at?

it works pretty well but NB doesn't really tell users what to do.

Exactly, that is the point I'm getting at ...

Or you create something from the favorites tab. (maybe we should open the favorites tab by default on first launch)

We've not long simplified the opening screen. Let's not start complicating it again! The immediate actions on view include New File and Open File. We should ensure they work well for this use case, or rethink the available actions and workflow if need be.

There was an icon / text for dropping files in the original mockup for background actions IIRC. #5591

[mbien]

The immediate actions on view include New File and Open File. We should ensure they work well for this use case, or rethink the available actions and workflow if need be.

they do work fine. Users can create a new java file without project as first action after launch and do their homework, close NB and on next start it will be still there.

There was an icon / text for dropping files in the original mockup for background actions IIRC.

the open project action could allow to open folders as tab. The dir chooser jumps into folders atm if they are no projects (it already is a tree, so if someone wants to expand a node -> arrow keys). Favorites view could have an open-as-tab action too which could be grouped with similar actions like #7081.

We've not long simplified the opening screen. Let's not start complicating it again!

The first project will open the Projects, Files and Services tabs. The first opened file could open Favorites. Maybe via cluster load or something like that. Favorites doesn't open automatically at all atm.

[neilcsmith-net]

they do work fine. Users can create a new java file without project as first action after launch and do their homework, close NB and on next start it will be still there.

You and I have a different definition of "fine". 😄 They function, yes, just! It's confusing. Having the template(s) hidden under Other is odd. And once the user has opened any project, the New File wizard they've just struggled to understand doesn't allow them to repeat what they've just learned (UI failure 101).

The first project will open the Projects, Files and Services tabs. The first opened file could open Favorites. Maybe via cluster load or something like that. Favorites doesn't open automatically at all atm.

That could be good. In fact, I've always wondered why we open Services by default at all?! And multiple times people have registered confusion about the distinction between Files and Favorites. There is something to consider in there. The UI could even be combined if we wanted to take it that far.

The key thing is that adding a compact Java template could be good, but there is more work to do to support onramping than just that. And knowing how we might support that could change how we integrate any template(s).

[mbien]

And multiple times people have registered confusion about the distinction between Files and Favorites.

the tooltips of the tabs aren't very useful atm and would need some updates if possible.

The UI could even be combined if we wanted to take it that far.

I don't think thats a good idea since Favorites has a distinct role compared to Projects and (Project-) Files. While doing maintenance tasks it can be also useful to drag them out and render both side by side.

The quickest way to integrate into some of the existing functionality without fighting it would be to create a "generic project" type which is simply a folder which shows everything. This would make it work with project groups too etc.

And once the user has opened any project,

I think I finally understand what you mean. Using the toolbar action while having a favorites node selected doesn't offer a "current path" entry. I might have never clicked that since I use the right click menu action once the trees are filled.

In any case: we should add a template for compact java files

[mbien]

lets start with some low hanging fruits: #8786

bonus: #8793, #8908, #8798