-
Notifications
You must be signed in to change notification settings - Fork 46
/
Copy pathREADME.txt
48 lines (35 loc) · 1.59 KB
/
README.txt
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
********************* ORM PLUGIN *********************
This plugin is the generic CRUD frontend for the ORM
API used to access the non-genomic datadase in
ensembl.
------------------------------------------------------
In order to create a CRUD interface for a database
table (or set of linked tables), you will need the
following (inserting the appropriate names into the
placeholders)
* EnsEMBL::Web::Object::[Table]
a Web::Object::DbFrontend drived class acting as
a wrapper for the ORM object. Override some of
configuration methods to customise the frontend
DbFrontend's Web::Component files are already there
in this plugin, but can be inherited to modify the
frontend. Changes to the Web::Configuration drived
class will be required accordingly.
At the moment, only one table (along with its
relationships) can be mapped to a frontend. Feature
to enable multiple domain editing is still under
development.
------------------------------------------------------
GETTING AJAXY DBFRONTEND PAGES WORKING
If there is no customisation in the pages, Ajaxy
dbfrontent interface should work without any trouble
as long as Web::Object drived object for the plugin
page has sub use_ajax return true value, and value of
OBJECT_TO_SCRIPT for the given page type is configured
as 'Modal'.
But if pages are customised, JavaScript may also need
to be customised.
Any method inside DbFrontendRow.js/DbFrontendList.js
can be overridden/modified easily by using 'prototype'
or 'extend' methods provided in Base.js to customise
the page.