summaryrefslogtreecommitdiff
path: root/doc/reference/tmpl/seed-jsclass.sgml
blob: c0ea39b0a6dbceab8f369c0ba016e41184ad2bef (plain)
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
<!-- ##### SECTION Title ##### -->
Creating JavaScript classes

<!-- ##### SECTION Short_Description ##### -->
Dealing with Seed class definitions and constructors

<!-- ##### SECTION Long_Description ##### -->
<para>
Defining new Seed classes allows for implementing more complex
behavior than possible with the traditional JavaScript object system
and default class.

When writing Seed modules, it is often the best pattern to define many
of your types through classes and static functions/value.

Please note that inside the finalize callback of a class, it is not
legal to call any method requiring a #SeedContext (with the exception
of protect/unprotect, though it is not guaranteed this will continue
to work with future versions of JSCore).
</para>

<!-- ##### SECTION See_Also ##### -->
<para>

</para>

<!-- ##### SECTION Stability_Level ##### -->


<!-- ##### SECTION Image ##### -->


<!-- ##### ENUM SeedPropertyAttributes ##### -->
<para>

</para>

@SEED_PROPERTY_ATTRIBUTE_NONE: 
@SEED_PROPERTY_ATTRIBUTE_READ_ONLY: 
@SEED_PROPERTY_ATTRIBUTE_DONT_ENUM: 
@SEED_PROPERTY_ATTRIBUTE_DONT_DELETE: 

<!-- ##### ENUM SeedClassAttributes ##### -->
<para>

</para>

@SEED_CLASS_ATTRIBUTE_NONE: 
@SEED_CLASS_ATTRIBUTE_NO_SHARED_PROTOTYPE: 

<!-- ##### TYPEDEF SeedClass ##### -->
<para>

</para>


<!-- ##### MACRO seed_empty_class ##### -->
<para>

</para>



<!-- ##### FUNCTION seed_create_class ##### -->
<para>

</para>

@def: 
@Returns: 


<!-- ##### FUNCTION seed_make_constructor ##### -->
<para>

</para>

@ctx: 
@klass: 
@constructor: 
@Returns: