File Header Text

8 posts, 1 answers
  1. Stuart Hemming
    Stuart Hemming avatar
    1622 posts
    Member since:
    Jul 2004

    Posted 19 Jan 2012 Link to this post

    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
  2. Answer
    Svetlozar
    Admin
    Svetlozar avatar
    269 posts

    Posted 23 Jan 2012 Link to this post

    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

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

  3. DevCraft banner
  4. Stuart Hemming
    Stuart Hemming avatar
    1622 posts
    Member since:
    Jul 2004

    Posted 23 Jan 2012 Link to this post

    Nice 1 -- Stuart
  5. Ioannis
    Ioannis avatar
    3 posts
    Member since:
    Oct 2012

    Posted 20 Feb 2012 Link to this post

    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

  6. Stuart Hemming
    Stuart Hemming avatar
    1622 posts
    Member since:
    Jul 2004

    Posted 20 Feb 2012 Link to this post

    +1
  7. Ivan
    Admin
    Ivan avatar
    106 posts

    Posted 23 Feb 2012 Link to this post

    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
    Sharpen your .NET Ninja skills! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>
  8. TonyG
    TonyG avatar
    239 posts
    Member since:
    Feb 2006

    Posted 08 Dec 2013 Link to this post

    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, tg@mydomain.tld
    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.
  9. Zdravko
    Admin
    Zdravko avatar
    657 posts

    Posted 11 Dec 2013 Link to this post

    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
    Share what you think about JustCode with us, so we can help you even better! You can use the built-in feedback tool inside JustCode, our forum, or our JustCode feedback portal.
Back to Top
DevCraft banner