File: ExtendingTheIDE.txt

package info (click to toggle)
lazarus 0.9.28.2-12
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 93,096 kB
  • ctags: 89,312
  • sloc: pascal: 820,189; xml: 202,194; makefile: 110,323; sh: 2,460; perl: 395; sql: 174; ansic: 133
file content (120 lines) | stat: -rw-r--r-- 3,185 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
Extending the IDE (Overview)
============================

The IDE supports several types of plugins:

Components
  These are the items in the component palette. For a example TButton can be
  used to create Buttons.
    
Component Editors
  Component editors are used when you double click on a component in the
  designer or to add some extra items to the popup menu of the designer, when
  you right click on a component.

Property Editors
  These are used by the rows in the object inspector.

Experts
  These are all other types.


-------------------------------------------------------------------------------
There are two possibilities to add your own plugins to Lazarus:

1. Write a package, install it and register your plugins in the 'Register'
   procedure of a unit.
2. Extend the lazarus code, and send your cvs diff to the lazarus mailing list.


-------------------------------------------------------------------------------
Writing components:

ToDo
Hint: Create a new component via the package editor.



-------------------------------------------------------------------------------
Writing component editors:

ToDo
Hint: see componenteditors.pas for examples


-------------------------------------------------------------------------------
Writing property editors

ToDo
Hint: see propedits.pp for examples


-------------------------------------------------------------------------------
Register event handlers

There are several events in the IDE, for which plugins can add their own
handlers.
In propedits.pp there is a GlobalDesignHook object, which maintains several
events for designing. Each event calls a list of handlers. The default handlers
are added by the IDE. You can add your own handlers with the AddHandlerXXX and
RemoveHandlerXXX methods. They will be called before the default handlers.
Examples:

  Adding your handler (this is normally done in the constructor of your object):
    GlobalDesignHook.AddHandlerComponentAdded(@YourOnComponentAdded);
    
  Removing your handler:
    GlobalDesignHook.RemoveHandlerComponentAdded(@YourOnComponentAdded);

  You can remove all handlers at once. For example, it is a good idea to add
  this line in the destructor of object:
    GlobalDesignHook.RemoveAllHandlersForObject(Self);


The handlers of GlobalDesignHook:

  // lookup root
  ChangeLookupRoot
    Called when the LookupRoot changed.
    The LookupRoot is the owner object of the currently selected components.
    Normally this is a TForm.

  // methods
  CreateMethod
  GetMethodName
  GetMethods
  MethodExists
  RenameMethod
  ShowMethod
    Called
  MethodFromAncestor
  ChainCall

  // components
  GetComponent
  GetComponentName
  GetComponentNames
  GetRootClassName
  ComponentRenamed
    Called when a component was renamed
  ComponentAdded
    Called when a new component was added to the LookupRoot
  ComponentDeleting
    Called before a component is freed.
  DeleteComponent
    Called by the IDE to delete a component.
  GetSelectedComponents
    Get the current selection of components.

  // persistent objects
  GetObject
  GetObjectName
  GetObjectNames

  // modifing
  Modified
  Revert
  RefreshPropertyValues