Please add more TODOs if necessary. Add them also in the Issues
section of the Halalan Google Code.
--
Waldemar Amado Bautista
* Candidates Management: group by position and group by party
* Restrict admin login to "one at a time" (included in "audit trails
for admin"?)
* Hierarchical/Tree voter groups/classifications
- I have an idea now. We can call this "Voter Control Lists" (for a
lack of a better term) which is basically an ACL-like mechanism, but
for voters. The voter groups can be represented as a tree-like
structure and different "permissions" can be given for each group.
This is essentially based on access control lists (ACLs). In our case,
the Access Control Objects (ACOs) will be the Positions, and the
Access Request Objects (AROs) will be the Voters. I don't have any
solid idea on the implementation though but the general idea is there.
Do you think we can have a very simple implementation of this?
----
* Admin controller:
- Can we move the CRUD logic for the Boter, Candidate, Party, and
Position models from the Admin controller intro their own separate
controllers? This is to make the code more manageable.
My other TODOs are already in the Issues list but I may or may not
include them in 1.4.0 since they're pretty trivial enhancements.
On Mon, Jun 30, 2008 at 2:06 PM, Waldemar Bautista
<waldemar...@gmail.com> wrote:
>
> Here are the TODOs before we can release 1.4.0:
> - audit trails for admin
> - hashing of image trails
>
> Please add more TODOs if necessary. Add them also in the Issues
> section of the Halalan Google Code.
--
~dmb
I finally had the time to do this. It's already in the repository.
It broke the JS menu highlighting though.
--
Waldemar Amado Bautista