=20
Potential improvements a=
nd bugs
We now have a basic interface but it already has some bugs and it could =
be improved in a lots of ways. Here is a list of things that are left as ex=
ercises:
- Improve the look and feel and output: it's partially of done in commit =
13d5a0b2 but can probably improved further.
- Reload only the table, not the full view when filtering.
- Sorting.
- More filters, more columns, etc.
- The server side code deserves to be refactored.
- Unit tests.
- [bug] Highlight is buggy in navigation because we have=
several routes while the navigation item added in Configure the navigation only recogniz=
es the first route we add.
- [bug] 'eng-GB' hardcoded when getting Content Type nam=
e.
Documentation pages to =
go further
This tutorial talks and uses a lots of concepts coming from Symfony, eZ =
Platform, PlatformUI itself or YUI. Here is a list of documentation pages t=
hat are worth reading to completely understand what's going on behind the s=
cenes:
Symfony-related doc=
umentation pages
eZ Platform-rela=
ted documentation pages
PlatformUI-relat=
ed documentation pages
YUI-related documentati=
on pages
The whole YUI documentation could be useful when working with PlatformUI=
, but amongst others things here is a list of the most important pages:
- For the very low level foundations, the guides about Attribute and Base (almost everything in Platform=
UI is YUI Base object with attributes), EventTarget<=
/a> (custom events) and Plugin (for tweaking almost an=
y PlatformUI components) can be very useful
- A large part of the application is about manipulating the DOM and subsc=
ribing to DOM events, this is covered in the Node and DOM Events guides.
- The PlatformUI Application is based on the YUI App Framework which itse=
lf is mainly described in the App Framework, Router and View guides.