Set Descriptive Window Titles for Consistency

[Breakdown-Dog]

Objective

• Many of Bevy’s example applications currently run without a window title, which can lead to poor user experience.
• This PR addresses this by adding a descriptive window title to each example, making them easier to identify and manage.
• This PR only include Bevy 2D Classification Examples, Bevy 3D Classification Examples, and Bevy Animation Classification Examples.

Solution

• A Python script was developed to automate the addition of window titles to all example files in the repository.
• After running the script, all changes were manually reviewed to ensure correctness and consistency.

Testing

• Each modified example was manually compiled and launched to verify that:
  • The window title appears correctly.
  • The example still runs as expected with no regressions.

---

[alice-i-cecile]

I don't think we should do this: it's noisy and distracts from the main point of the example. If this is important, I think the better way to do this is to extract this information by default based on the binary name and use that to generate the window title.

[Breakdown-Dog]

I agree with your point. I saw some examples that included this WindowPlugin setting for the window title, so I thought to add it all. 😭I also think Bevy is quite different from most game engines in terms of usage. Before users understand Bevy's concepts, at least they can set a title to actually code something. Moreover, I wonder if this also indicates that modifying content based on DefaultPlugin in Bevy is currently too cumbersome. In other game engines, many users modify and add their own content based on default settings, so does DefaultPlugin need improvements in this aspect?

[alice-i-cecile]

I agree with your point. I saw some examples that included this WindowPlugin setting for the window title, so I thought to add it all.

Yeah, I don't think that this should be set, except in the examples where it's explicitly teaching this or maybe the full game.

Before users understand Bevy's concepts, at least they can set a title to actually code something.

I don't think this is super valuable for learners: it's just procrastination :)

Moreover, I wonder if this also indicates that modifying content based on DefaultPlugin in Bevy is currently too cumbersome. In other game engines, many users modify and add their own content based on default settings, so does DefaultPlugin need improvements in this aspect?

Maybe? I don't really mind this: it's a once-per-project pattern. You could probably just insert the resource directly, as long as it was before DefaultPlugins (see #1255).