Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
we have established a new documentation concept for ABAP development objects in AS ABAP 7.40 called ABAP Doc. With ABAP Doc you now document your parameters directly in the source code.
A good introduction of the topic was given by in this document :
Michael describes the option in eclipse to migrate all existing short texts of your classes and interfaces to the ABAP Doc notation. Give it a try!
we have established a new documentation concept for ABAP development objects in AS ABAP 7.40 called ABAP Doc. With ABAP Doc you now document your parameters directly in the source code.
A good introduction of the topic was given by in this document :
Michael describes the option in eclipse to migrate all existing short texts of your classes and interfaces to the ABAP Doc notation. Give it a try!
Thanks. I know ABAP Doc, as you could probably see at the subject. And I want to use it. My question is whether it's possible to handle the "old" short descriptions maintained at SE* also with ABAP Doc Comments?
As we won't have a big bang migration of our development tools, I will need to maintain comments at two places if it's not possible to create and edit short texts from ABAP Doc Comments.
Is there a @ShortText: .... ?
BTW: The "Create ABAP Doc from Short Text" isn't working at my system also.
Regards,
Franz
PS: I worked with Java and Eclipse for more than 10 years, so promoting that kind of feature to me is preaching to the choir.
yes, this synchronization of short descriptions and ABAP Doc comments will be available in future.
There will be a special tag in the ABAP Doc comment that classifies the short descriptions. Once you classified that you can maintain the short description in both places: ABAP Doc and SE... transactions.
In our lab version it is already working. Let's see when we can ship the feature.
By the way we will also support the possibility to export ABAP Docs for whole classes, interface or even packages to an offline file or zip-package. I'm sure you will like it 🙂
I would expect to import the original language, no matter whether it's DE or EN. I've never seen a system where developers have used another language as the origianl language for their comments.
another option would be to use the language with which the user is logged in to Eclipse. But I guess most of us will use the original language of all other objects, so that also new objects are created with this language as original, anyway.
we have tried to import this SAP Note to our 7.40 System, but it states, that it is obsolete. I checked the CL_OO_CLIF_UTILITY class, but it for sure needs to be changed.
is there a chance to modify this in regard to import ABAP Doc to Eclipse in login language? Maybe first trying to import in login language and than in original language if the former fails?
I'm trying to implement some coding guidelines in my company and one of those would be: All comments/in-code documentary shall be in English.
And therefore I'd like to import the English texts and not the (original) German ones.
I have to think about it whether there might be side effects when importing the texts in logon language . But why don't you change the original language of these objetcs?
This actually might be a solution. I'll have to discuss it with my colleagues, though.
Could there be problems when delivering to our (mainly German) customers? I'm not sure how the target systems will react on changed original languages of imported objects - especially in regards to displayed texts.
Bluesky
