Differences between Property Classes and Visual Attributes

Hi folks
Can anybody know the exact difference between a property class and a visual attribute?
I'm substantially good at Forms but doesn't know the exact difference.
Any reply will be deeply appreciated.
Cheers,
PCZ

Visual Attributes are only for the visual representation of your items, buttons, blocks, canvas, ...
Property Classes are for inheriting all objects including visual attributes.
If you create a style guide for your company, then first define the visual attributes for the look and feel. After that create property classes for all of the other objects in your application. On top of that create object groups, where you centralize your property classes and visual attributes.
If you have created such a form, then call this form reference-template. Now you inherit the object-groups to a second form and call this form "template".
If you create new forms, copy the template and rename it. Then you have in all your forms inherited visual attributes, property classes, etc. and all this stuff is in one "reference-template"
try it
Gerd

Similar Messages

What is the difference between document class and normal class

Hi,
Please let me know what is the difference between document class and normal class.
And I have no idea which class should call as document class or call as an object.
Thanks
-Actionscript Developer

the document class is invoked immediately when your swf opens. the document class must subclass the sprite or movieclip class.
all other classes are invoked explicitly with code and need not subclass any other class.

What is the difference between Abstract class and Interface ?

Hi,
Could u plz tell me the difference between Abstract class and Interface?
Thanks in advance.
Gopi

Lots.
An abstract class can contain some method implementations, or indeed all the method implementations. It may contain methods with all the various access modifiers. It cannot be instantiated. A class may inherit from only a single abstract class.
An interface contains only public method stubs and constants. A class may implement multiple interfaces. An interface cannot (obviously) be instantiated.
Abstract classes are particularly useful when you need to provide a semi-complete implementation for reuse. Interfaces are used more like types.
Look at java.util.* for some good examples of the use of both.

Difference between Abstarct Class and Interface

HI,
Here is a simple one for the gurus but quite important for me.
What is the difference b/w an Interface and an abstract class?
Why do we need each one of them?
I would appreciate if you people can give examples of each so that I amy understand fully
Thanks in advance...

A normal class (not abstract) has a special behaviour, like java.awt.Frame. A Frame is a frame no matter how you subclass it. If you create a subclass it will still be able to be displayed by calling it's show method. So by using a normal class you can create a type of class.
An abstract class does the same, but it leaves some of the code unwritten. For instance java.lang.Number. This class is abstract becuase it has no knowledge of how to store the number in memory. But it knows that it is a number, and any subclass will still be a number. You could create a subclass of Number that can hold the time in milliseconds and checks your system clock to see what the time is, it could also have methods that return the time in another country, but it would still be just a Number.
An interface is a way to describe what an object can do, not what it is. So with java.lang.Comparable as an example you can make any class comparable. This means that no matter what type of object you have, it can be compared with other objects. So you can have a subclass of Frame that can be compared with other windows. Or a subclass of Number that can be compared with other Numbers. You can even compare those two different types if you like. So you could compare a window with a number.
That is the difference between abstract classes and interfaces.
I hope you could follow my arguments, it isn't an easy subject,
Daniel

Difference between Data Class and Delivery Class

What is the Difference between Data Class and Delivery Class , what happens Phisically to the Data .
Moderator message: what is the difference between your question and a question that we'd welcome here in the forums?
[Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
Edited by: Thomas Zloch on Nov 22, 2010 1:17 PM

What is the Difference between Data Class and Delivery Class , what happens Phisically to the Data .
Moderator message: what is the difference between your question and a question that we'd welcome here in the forums?
[Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
Edited by: Thomas Zloch on Nov 22, 2010 1:17 PM

Difference between abstract classes and interfaces

I actually wonder about what are the differences between abstract classes and interfaces may somebody give an example code about it?
and i have one more question how can i use interfaces like multiple inheritance ? i mean when i implement an interface like
class a extends b implements c,di have to use all c and d methods but what that methods means?
I mean as i know we cannot make implementations of methods in interfaces
but for example in runnable interface there is a method like run() and it has been defined somewhere because it knows what to do(i mean when it will run), i just write my code into that method .

Once you get past the starting point (I am referring to the OP here), there are a few salient differences:
You can only extend (or generalize) a single superclass; however, you can implement (or realize) multiple interfaces. As such, all things being equal, using an interface in lieu of an abstract class 'frees' your design. Later, if you want the implementor of an interface to inherit from another class, there is not issue.
Any abstract method specifies a contract. However, abstract classes allow you to also add common behavior to subclasses. This is an overused justification for abstract classes, IMO. You can achieve the same effect using delegation and still having interfaces.
Always program to interfaces wherever possible. This means that you define an interface and have an implementing class (usually at a minimum). Do not do this for all your classes, but rather the ones that make your system unique (the domain model or M in MVC architecture). This allows you to later change implementation with a minimal amount of refactoring. This is a core precept from the Group of Four and any number of decent programming books.Best of luck.
- Saish

Difference between config toll and visual admin

HI all,
Please let me know all Difference between config toll and visual admin.
and Purpose and how to start.
Thanks & Regards,
satish k

Hi Satish,
SAP J2EE Engine 6.20 provides three basic tools for administration u2013
Visual Administrator,
Console Administrator, and
Config Tool (both Visual and Console).
There are some other tools namely DBTool, Library Tool, RMIC Tool, Shutdown Tool, and User Tool also used.
First part
Difference between config toll and visual admin:-Visual Administrator is a graphical user interface (GUI) that enables administration of the whole cluster, of the cluster nodes, and all modules running on them.On the other hand with the help of Config Tool you are able to add and configure SAP J2EE Engine 6.20 cluster elements.Again Config Tool can be used without a running SAP J2EE Engine 6.20. The only requirement is to have the server installed on the local machine.
Visual Administrator is written in the Java programming language and can be run in any environment where a Java Virtual Machine is available.On the other hand Config Tool is XML-based, which enables third-party visualizations to be developed or integrated as part of a more complicated configuration system.
Visual Administrator enables remote monitoring and management of the cluster, and for each cluster element, and enables the system administrator to monitor all managers and services working on each node in a single GUI & its online.cofig tool on the otherhand offline.
Second part Purpose
"Visual Administrator":-with the help of this tool you can able to login & logout from the server.It gives you all the details regarding different services running in your SAP server.As already mentioned that with the help of VA we enables administration of the whole cluster, of the cluster nodes, and all modules running on them.
"Config Tool":-Config Tool enables you to run the server in remote debug mode.
Again Config Tool enables you to add dispatcher and server nodes to the SAP J2EE Engine 6.20 Cluster.With the help of config tool we are enable to modification of service or manager module properties.
Third part Start procedure
"Visual Administrator" check the below link
http://help.sap.com/saphelp_nw70/helpdata/EN/23/fa1f1e5f6841cf92c64dc19d79f290/content.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm
For more Info
http://docs.sun.com/app/docs/doc/819-0698/installconfig-53?a=view
http://help.sap.com/saphelp_nwce10/helpdata/en/6f/258b2ef17d45a4afa45a00309a6a33/content.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm

Difference between Material Class and Batch Class

Hi!
What is the difference between Material Class and Batch Class?
and how can we use these classes?
Rgds,
Ajit

Iam not sure but i think
1) Material class for sorting purpose
2) Batch Class for Batch Management
thanks
K.Prabakaran

Difference between static class and singleton?

Hi I wonder what could be the difference between static methods and singleton?
In singleton at any point of time there will be only one object existing in the JVM. We create singleton to avoid multiple object creation for that class.
If I make all the methods in the class as static also it does the same job. The memory will be allocated once. Even there wont be any object in this case, so time required for object creation also can be saved. looks like more efficient but still why need singleton?
This question is also posted in java programming forum. The thread is as follows:-
[Click on this to visit that thread |http://forum.java.sun.com/thread.jspa?threadID=5278517&tstart=0]
Edited by: murrayb9654 on Mar 25, 2008 8:20 AM

yawmark wrote:
Static class is a realization of singleton pattern.Not in any conventional sense.
~Especially since a static class is completely different from a class with all static methods.

Difference between Java class and JavaBean?

What is the difference between a Java class and a JavaBean?
A class has variables which hold state.
A class has methods which can do things (like change state).
And if I understand a JavaBean it is rather like a BIG class...
i.e.
A JavaBean has variables which hold state.
A JavaBean has methods which can do things (like change state).
So, what's the difference between the two?
And in case it helps...What is the crossover point between the two? Is there a minimalist type JavaBean which is the same as a class? What is the difference between Java beans and Enterprise Java Beans?
Thanks.

Introspection, as I understand it is a bunch of
methods which allows me to ask what a class can do
etc. right? So, if I implement a bunch of
introspection methods for my class then my class
becomes a JavaBean?Introspection allows a builder tool to discover a Bean's properties, methods, and events, either by:
Following design patterns when naming Bean features which the Introspector class examines for these design patterns to discover Bean features.
By explicitly providing the information with a related Bean Information class (which implements the BeanInfo interface).
I understand now they are completely different.
Thanks. Very clear.
I do not understand how they are completely different.
In fact I don't have a clue what the differences are
other than to quote what you have written. In your
own words, what is the difference? This is the "New
to Java Technology" forum ;-) and I'm new to these
things.In that case ejbs are way too advanced for you, so don't worry about it.

Difference between using Binding and Value Attribute

what is the deference between using binding and value attribute, when I use binding attribute at the time of Value change listener is behaving like action listener,
Ex:
If I use value attribute, at the time of value change listener the component is not showing the result in the component but when I use Binding attribute it is happening automatically. So I want to know how the binding attribute is working.
I know, at the time of binding attribute the component is creating an instance at the bean side, So even also how it is following the life cycle of the JSF Frame work, and also Please suggest me weather which one is better to use either Binding or Value?

JNaveen wrote:
If I use value attribute, at the time of value change listener the component is not showing the result in the component but when I use Binding attribute it is happening automatically. So I want to know how the binding attribute is working.You need to learn about the JSF lifecycle. The ValueChangeEvent is invoked after conversion and validation in the 3rd phase, while the model values are updated in the 4th phase. In the valueChangeListener method you normally use ValueChangeEvent#getNewValue() to get the new value after the change.
I know, at the time of binding attribute the component is creating an instance at the bean side, So even also how it is following the life cycle of the JSF Frame work, and also Please suggest me weather which one is better to use either Binding or Value?Use the 'value' attribute to bind the value to the bean. Use the 'binding' attribute to bind the component to the bean. If you don't need to precreate the component or do other things than getting/setting its value, then there is no need for the 'binding' attribute.
Read on those links if you want to know something more about the JSF lifecycle:
[http://balusc.blogspot.com/2006/09/debug-jsf-lifecycle.html].
[http://jcp.org/aboutJava/communityprocess/final/jsr252/index.html] (pick 1st download).

Difference between ArrayList class and LinkedList class

I would like to ask what is the difference between the ArrayList class and the LinkedList class? If I use ArrayList class can I have a fixed size?
Thank you for your answers.

I often use LinkedList when I need a FIFO. When all you're doing is adding to the end of a list and removing the first element, it is definitely faster. Here's a quick SSCCE I wrote up to demonstrate:import java.util.*;
public class ListTest {
   public static void main(String[] args) {
      LinkedList<Integer> linked = new LinkedList<Integer>();
      ArrayList<Integer> array = new ArrayList<Integer>();
      Integer[] values = new Integer[2500000];
      for (int i = 0; i < values.length; i++) {
         values[i] = new Integer(i);
      Random rand = new Random();
      boolean[] randDir = new boolean[values.length];
      for (int i = 0; i < randDir.length; i++) {
         randDir[i] = rand.nextBoolean();
      long startTime, endTime;
      startTime = System.currentTimeMillis();
      for (int i = 0; i < values.length; i++) {
         if (linked.size() > 0 && randDir) {
linked.removeFirst();
else {
linked.addLast(values[i]);
endTime = System.currentTimeMillis();
linked.clear();
System.out.println("linked:"+(endTime-startTime));
startTime = System.currentTimeMillis();
for (int i = 0; i < values.length; i++) {
if (array.size() > 0 && randDir[i]) {
array.remove(0);
else {
array.add(values[i]);
endTime = System.currentTimeMillis();
System.out.println("array:"+(endTime-startTime));
array.clear();

Definition on and difference between a Characteristic and an Attribute

Hi all
In our Reporting group we have been asked for a one-pager, which explains the difference between attributes and characteristics and how these work in BW. We have, in our words explained to them what the difference is, but in the process of doing so, we realize that we have not seen any document or explanation, which states the u201Ctruthu201D. I am sure that such document(s) already exists. I just dont know where.
I hope someone can help!
Kind regards,
Rasmus

Hi Rasmus,
Characteristics: Characteristics are sorting keys, such as company code, product, customer group, fiscal year, period, or region. They specify classification options for the dataset
Attribute : An attribute is a characteristic that is logically assigned, and subordinated, to another characteristic.
Please check the below links, hope it will help you
http://help.sap.com/saphelp_nw04/helpdata/en/23/054e3ce0f9fe3fe10000000a114084/frameset.htm
http://help.sap.com/saphelp_apo/helpdata/en/58/2b8e39e1ba3541e10000000a11402f/content.htm
Regards
Sai

JSP - difference between extending class and importing class

In the following scenario
class A
private static String con;
Case 1
==========
class B extends A
Case 2
===========
import A;
class C
A objA = new A;
What will be the difference in Case 1 and Case 2 on accessing the variable con.
thanx
Venki

>
If i am not wrong, the above line should be private
static variables are not inherited.
NO, AFAIK, static variables, private or otherwise arent inherited. Please note that doesnt mean, its not available in the sub-class. Infact it is. However you cannot override or hide them ie polymorphism isnt applicable to static members which is what , IMO, inheritance is all about. Its logical, when you think about it, polymorphism is applicable for objects and static is a class thinggy, has nothing to do with objects.
cheers,
ram.

Difference between abstract class and the normal class

Hi...........
can anyone tell me use of abstract class instead of normal class
The main doubt for me is...
1.why we are defining the abstract method in a abstract class and then implementing that in to the normal class.instead of that we can straight way create and implement the method in normal class right...../

Class vs. interface
Some say you should define all classes in terms of interfaces, but I think recommendation seems a bit extreme. I use interfaces when I see that something in my design will change frequently.
For example, the Strategy pattern lets you swap new algorithms and processes into your program without altering the objects that use them. A media player might know how to play CDs, MP3s, and wav files. Of course, you don't want to hardcode those playback algorithms into the player; that will make it difficult to add a new format like AVI. Furthermore, your code will be littered with useless case statements. And to add insult to injury, you will need to update those case statements each time you add a new algorithm. All in all, this is not a very object-oriented way to program.
With the Strategy pattern, you can simply encapsulate the algorithm behind an object. If you do that, you can provide new media plug-ins at any time. Let's call the plug-in class MediaStrategy. That object would have one method: playStream(Stream s). So to add a new algorithm, we simply extend our algorithm class. Now, when the program encounters the new media type, it simply delegates the playing of the stream to our media strategy. Of course, you'll need some plumbing to properly instantiate the algorithm strategies you will need.
This is an excellent place to use an interface. We've used the Strategy pattern, which clearly indicates a place in the design that will change. Thus, you should define the strategy as an interface. You should generally favor interfaces over inheritance when you want an object to have a certain type; in this case, MediaStrategy. Relying on inheritance for type identity is dangerous; it locks you into a particular inheritance hierarchy. Java doesn't allow multiple inheritance, so you can't extend something that gives you a useful implementation or more type identity.
Interface vs. abstract class
Choosing interfaces and abstract classes is not an either/or proposition. If you need to change your design, make it an interface. However, you may have abstract classes that provide some default behavior. Abstract classes are excellent candidates inside of application frameworks.
Abstract classes let you define some behaviors; they force your subclasses to provide others. For example, if you have an application framework, an abstract class may provide default services such as event and message handling. Those services allow your application to plug in to your application framework. However, there is some application-specific functionality that only your application can perform. Such functionality might include startup and shutdown tasks, which are often application-dependent. So instead of trying to define that behavior itself, the abstract base class can declare abstract shutdown and startup methods. The base class knows that it needs those methods, but an abstract class lets your class admit that it doesn't know how to perform those actions; it only knows that it must initiate the actions. When it is time to start up, the abstract class can call the startup method. When the base class calls this method, Java calls the method defined by the child class.

Differences between Property Classes and Visual Attributes

Similar Messages

Maybe you are looking for