File Header Text

[Stuart Hemming]

A small think, I know, but it would be nice if the JustCode | Options | Code Style | Common | File Header Text input area used a fixed-width font.

--
Stuart

[Svetlozar]

Hi,

Thank you for the suggestion! We changed the font of the Introduce Header Option textbox to Consolas. It will be included in the next internal build.

All the best,
Svetlozar
the Telerik team

[Stuart Hemming]

Nice 1 -- Stuart

[Ioannis]

A must have would be to include the following self-expanding predefined tags:

$SOLUTION_NAME$ --> The base name of the solution.

$SOLUTION_PATH$ --> The absolute path name of the solution (defined as drive + path + base name + file extension).

$PROJECT_PATH$ --> The absolute path name of the project (defined as drive + path + base name + file extension).

$PROJECT_VERSION$ --> would expand to the project assembly version.

$FILE_PATH$ --> The absolute path name of the file (defined as drive + path + base name + file extension).

$FILE_RELPATH$ --> would expand to the path relative to the project.
ie. if you have a class named test.cs in \Sample\Enums\ project folder structure then using $FILE_RELPATH$$FILE_NAME$ would expand to "\Sample\Enums\test.cs"

Thank you in advance,

Ioannis

[Stuart Hemming]

+1

[Ivan]

Hello,

Thank you for your feedback. This is indeed a nice suggestion and we will definitely consider implementing it.
If you have any more questions or remarks, please do not hesitate to contact us again!

Regards,
Ivan
the Telerik team

[TonyG]

I'll add a +1 to the original suggestions which haven't been implemented in almost 2 years since this post.

I'll add $TIME$ to complete the latest update timestamp.

The $AUTHOR$ tag is OK for in-house staff where there is only one user "bob". But for consultants posting code to multiple sites we need a more unique identifier, as there might be a "bob" in-house, and a consultant named "bob", coincidentally using that same name on his own PC.

So I'll recommend $DEV_INFO$ which pulls text from another JustCode Options text block. My info might be:
 Tony G, My corp, [e-mail]
That ensures that anyone can get in touch with me as the last author, and anyone searching an archive will find code that I've updated last.

All that said, I can easily understand if someone suggests that we don't need to know the last developer here because that kind of info should be tracked with inline comments, an issue tracker, etc. And we kinda don't need the file name, project, solution, etc, because if we have Visual Studio open we already know all of this - the doc and open solution are right in front of us. But not everyone uses these tools in the same way.

I think it might help if Telerik published a blog that explains the thought process behind this File Header, and how it was intended to be used. I don't think we're thinking along the same lines.

[Zdravko]

Hi Tony,

Indeed, the File header template could be improved with more commands, but currently its priority is set to low.

The lack of tags does not prevent users to input whatever information they need into the template.
I will give an example with your $DEV_INFO$ tag. Instead of getting this information from some text block you can directly input it to the template.
Thanks. 

Regards,
Zdravko
Telerik