-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
Improve the default templates (at least the cpp template) #1494
Conversation
@halx99 , |
To me this PR make sense, but the name Other problem is that changing only this package/bundle dont work, because Between Other thing is that you need follow the cases where it is lowecase and uppercase. |
Why is 'hellocpp' better? |
@aismann As @paulocoutinhox mentioned in his post, the "HelloCpp" and "hellocpp" are placeholders that are replaced when a new Axmol project is created. If you're going to update the name of the project to "CPPTemplate", then you must also change this file to make sure it can look up the correct strings for replacement: |
And if you want to change HelloCpp, I suggest you use a better and more definitive name then, like "AxmolCpp". Something that doesn't look like a hello world or template. I think it's strange to have something written "template" in my project right away. |
Please avoid using the word "Axmol" in the project name, or anything that needs to be replaced, as it makes it more difficult to search for that string, since so much has "Axmol" in it already. In fact, there is nothing wrong with HelloCpp at all. It's a placeholder, and as such, it is always going to be replaced by the developer, so all it needs to be is unique enough to notice, and easy enough to search for. Also, has anyone ever actually logged an issue related to "HelloCpp", and I don't mean an issue related to personal preference, but a specific concern or technical issue about its usage? If not, then perhaps putting much focus on changing it is of no real benefit to developers using Axmol. |
Cannot be "CppProject", "MyProject", "MyApp", "CppApp", something more beautiful? |
No. Its only for: |
The problem is that you are changing everything for CPP, you need do like me on latests PR, that is change for BOTH templates. You changing all for this, but lua template follow the same pattern, ex: HelloLua, org.axmol.hellolua. The more you keep messing with it, the harder it is to maintain two templates. I've already spent a lot of time adjusting both projects and now you're going to make them different again. |
Sorry. you should not using axmol which is continues improving ;) |
Improvements to Axmol are great, but, in order for developers to use Axmol, it needs to be relatively stable, in terms of frequency of changes, and the impact that the changes have. Stating that a developer should not be using Axmol because it's continuously improving is actually a negative, not a positive, and perhaps a little inappropriate too, don't you think? |
No I think not. Everybody can use own projects which was created before whithout an effect there.
Was also mean as a funny sentence of course (look on the smiley) |
@halx99 |
Ok. I see neverone understand what 'HelloCpp' realy is: |
I perfer HelloCpp, a real project name can be build & test
…________________________________
From: aismann ***@***.***>
Sent: Sunday, December 10, 2023 9:19:22 PM
To: axmolengine/axmol ***@***.***>
Cc: Deal ***@***.***>; Mention ***@***.***>
Subject: Re: [axmolengine/axmol] Improve the default templates (at least the cpp template) (PR #1494)
@halx99<https://github.com/halx99>
Im finished, Can be merged.
—
Reply to this email directly, view it on GitHub<#1494 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABVHOJ2UKBRXQX4IK2AHXW3YIWZFVAVCNFSM6AAAAABAOGDWZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYHE3DGNRYGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
HelloCpp lets developer meaning thats an own project and not the template itself. HelloCpp should never used as a full project.
|
@aismann I'm sure everyone understands that it is just a temporary project name for the template and nothing more. There is no need to force the issue. There are a number of items in this PR that are actual good to change, such as the The project name change can be given more consideration, and can always be changed in a future PR if the need arises. |
Should be ready for merge now |
Which branch your pull-request should merge into?
dev
: Current 2.x BugFixs or FeaturesDescribe your changes
see #1493 and diff
Issue ticket number and link
#1493
Checklist before requesting a review