4 |
|
|
5 |
=head1 DESCRIPTION |
=head1 DESCRIPTION |
6 |
|
|
7 |
This page describes general idea about A3C application and current status of implementation |
This page describes general idea about A3C application and current status of implementation. |
8 |
|
|
9 |
|
Oppinions should be attributed to Dobrica Pavlinusic, and not other developers :-) |
10 |
|
It's surposed to convey a story which is coherent enough for new developer |
11 |
|
to join into project. Most of other documentation is more useful when |
12 |
|
developing and looking into code usage (if it's not documented and tested, |
13 |
|
it doesn't exist) but this part is delivered as pure POD for reading pleasure. |
14 |
|
|
15 |
=head1 LDAP |
=head1 LDAP |
16 |
|
|
80 |
have to take a look in C<lib/Strix.pm>) implements pure DBI code (ported |
have to take a look in C<lib/Strix.pm>) implements pure DBI code (ported |
81 |
from php) to access data directly. Keep in mind that this data have to be |
from php) to access data directly. Keep in mind that this data have to be |
82 |
cached for any resonable performance. On the other hand, data can be |
cached for any resonable performance. On the other hand, data can be |
83 |
structured usefully, for example trees are structured in useful way for JSON |
structured usefully, for example trees are structured in useful way for |
84 |
direct JSON output. |
direct output to JSON. |
85 |
|
|
86 |
If tree has C<class> key, it can be set to C<error> so that we can mark |
If tree has C<class> key, it can be set to C<error> so that we can mark |
87 |
errors in data using same CSS class in views. This might be useful convention. |
errors in data using same CSS class in views. This might be useful convention. |
88 |
|
|
89 |
|
I prefer to keep this file documented up to level that make it's usage from Jifty and |
90 |
|
C<t/50-strix.t> makes sanse, but not more than that. |
91 |
|
|
92 |
=head1 HTML |
=head1 HTML |
93 |
|
|
94 |
We don't generate HTML using templates. In fact, all HTML is encoded in perl |
We don't generate HTML using templates. In fact, all HTML is encoded in perl |
100 |
for us anyway) for easier maintenance, probably by same logic as view names |
for us anyway) for easier maintenance, probably by same logic as view names |
101 |
to skip additional step of mapping when human are watching into code. |
to skip additional step of mapping when human are watching into code. |
102 |
|
|
103 |
|
In long run, this should allow us to refactor templates at code level and |
104 |
|
create different re-usable widgets which brings us to following topic... |
105 |
|
|
106 |
|
=head1 AJAX |
107 |
|
|
108 |
|
Jifty's way of AJAX are L<Jifty::Manual::PageRegions>. |
109 |
|
|
110 |
|
=head2 Strix navigation |
111 |
|
|
112 |
|
L<http://a3c.skole.hr/strix/navigation> |
113 |
|
|
114 |
|
For now, we have implementation of two-level select which is in sync with |
115 |
|
instance clipboard (implemented by L<A3C::Model::StrixInstanceSelection> and |
116 |
|
L<A3C::View::Strix> and L<A3C::Action::StrixSelectSite>. This is |
117 |
|
good candidate to refactor into reusable widget on it's own. |
118 |
|
|
119 |
=head1 BUGS |
=head1 BUGS |
120 |
|
|
121 |
Many probably, documented in C<TODO> which is also useful for quick overview |
Many probably, documented in C<TODO> which is also useful for quick overview |