<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Class: Interfaces - Events - Internal Types -  Aliases in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/class-interfaces-events-internal-types-aliases/m-p/3684604#M887289</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Interface&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              In its most common form, an interface is a group of related methods with empty bodies. A bicycle's behavior, if specified as an interface, might appear as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Bicycle {&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       void changeCadence(int newValue);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       void changeGear(int newValue);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       void speedUp(int increment);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       void applyBrakes(int decrement);&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To implement this interface, the name of your class would change (to ACMEBicycle, for example), and you'd use the implements keyword in the class declaration: &lt;/P&gt;&lt;P&gt;class ACMEBicycle implements Bicycle {&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   // remainder of this class implemented as before&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Implementing an interface allows a class to become more formal about the behavior it promises to provide. Interfaces form a contract between the class and the outside world, and this contract is enforced at build time by the compiler. If your class claims to implement an interface, all methods defined by that interface must appear in its source code before the class will successfully compile. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Event&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Event is a platform-independent class that encapsulates events from the platform's Graphical User Interface in the Java 1.0 event model. In Java 1.1 and later versions, the Event class is maintained only for backwards compatibilty.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They are definetely declared in classes. These concepts are related to one other for declaring methods and handling events in our program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think this will be helpful for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Swamy Kunche.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Apr 2008 19:23:08 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-04-03T19:23:08Z</dc:date>
    <item>
      <title>Class: Interfaces - Events - Internal Types -  Aliases</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/class-interfaces-events-internal-types-aliases/m-p/3684602#M887287</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can someone tell me what one of the above, or all of the above tabs are used for in Classes?&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;                Thank-You&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Tom M. on Apr 3, 2008 5:35 PM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Tom M. on Apr 3, 2008 5:36 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Apr 2008 15:31:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/class-interfaces-events-internal-types-aliases/m-p/3684602#M887287</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-03T15:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: Class: Interfaces - Events - Internal Types -  Aliases</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/class-interfaces-events-internal-types-aliases/m-p/3684603#M887288</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi tom,&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;please explain your question in detail.......&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Apr 2008 16:14:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/class-interfaces-events-internal-types-aliases/m-p/3684603#M887288</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-03T16:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: Class: Interfaces - Events - Internal Types -  Aliases</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/class-interfaces-events-internal-types-aliases/m-p/3684604#M887289</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Interface&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              In its most common form, an interface is a group of related methods with empty bodies. A bicycle's behavior, if specified as an interface, might appear as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Bicycle {&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       void changeCadence(int newValue);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       void changeGear(int newValue);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       void speedUp(int increment);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       void applyBrakes(int decrement);&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To implement this interface, the name of your class would change (to ACMEBicycle, for example), and you'd use the implements keyword in the class declaration: &lt;/P&gt;&lt;P&gt;class ACMEBicycle implements Bicycle {&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   // remainder of this class implemented as before&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Implementing an interface allows a class to become more formal about the behavior it promises to provide. Interfaces form a contract between the class and the outside world, and this contract is enforced at build time by the compiler. If your class claims to implement an interface, all methods defined by that interface must appear in its source code before the class will successfully compile. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Event&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Event is a platform-independent class that encapsulates events from the platform's Graphical User Interface in the Java 1.0 event model. In Java 1.1 and later versions, the Event class is maintained only for backwards compatibilty.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They are definetely declared in classes. These concepts are related to one other for declaring methods and handling events in our program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think this will be helpful for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Swamy Kunche.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Apr 2008 19:23:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/class-interfaces-events-internal-types-aliases/m-p/3684604#M887289</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-03T19:23:08Z</dc:date>
    </item>
    <item>
      <title>Re: Class: Interfaces - Events - Internal Types -  Aliases</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/class-interfaces-events-internal-types-aliases/m-p/3684605#M887290</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Look at [ABAP Objects Examples|https://wiki.sdn.sap.com/wiki/x/Aq] in [ABAP Objects Wiki section|https://wiki.sdn.sap.com/wiki/x/o5k], there is a lot of useful stuff !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also look at [ABAP Objects Library|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_library&amp;amp;query=abap+objects&amp;amp;adv=false&amp;amp;sortby=cm_rnd_rankvalue].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Don't forget to close this Thread when your question be answered !&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marcelo Ramos&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Apr 2008 19:55:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/class-interfaces-events-internal-types-aliases/m-p/3684605#M887290</guid>
      <dc:creator>marcelo_ramos1</dc:creator>
      <dc:date>2008-04-03T19:55:11Z</dc:date>
    </item>
  </channel>
</rss>

