Currently the MIME database (include/mime.xml) is a static list provided as part of JAS. It would be handy if this list could easily be updated via the backend.  The question that comes to mind however is whether upgrade should overwrite a customized version. It seems rather annoying if you spend time to add your own MIME types that are subsequently forgotten when JAS is upgraded. Maybe adding a flag "custom" to the XML file to indicate it shouldn't be touched by upgrades.

The JAS backend should have a filter section to more effectively drill down in the data. the filters should be automatically generated based on the module (similar to the CMS). Text fields should have a inline dropdown with available values (like the search box). Additionally it should remember the last set filters if the user comes back to the page later. This will require a "Reset" button to set all values to their defaults.

Float and price fields should have round/floor/ceil field mutilations Mutilate::round(number, precision=0, mode=false) mode: normal, floor, ceil  if precision > 0 and mode = floor/ceil:  floor(number * pow(10, precision))/ pow(10, precision) Data::addMutilationFormat_Template

Generally show_from+show_total are used to split data over multiple pages. As such it's seems logical to support this natively. If show_page is set it should be used to calculate show_from (show_page * show_total) prior to getting the data (and thus overwriting the set show_from). When the data is gathered and show_count is set this value should be used to calculate show_pages ( ceil ( show_count / show_total)).

IP (range) lock downbrute force protection (X attempts from same IP per Y minutes)email confirmation (should contain only the logic, requires an email field in a project module)timezone / language settingsseparators (also CSV) settingsdate/time format settingsEach feature should be configurable (config module) and should have the option to be locked down for admins (non owner). This should also be extended to changing username and password. It seems logical to add a user/settings action th...

Currently the page browser logic in the lister plugin only remembers the sorting and the filters in rewrite mode. It should use a more generic approach where it reads the relevant filters from the Data object and use that. Additionally it's probably a good idea to split off the page browser logic in the lister plugin from the output function so other plugins can easily reuse this logic.  Convert by: JAS13OCT014

Add change default timezone(timezone=false (=default in config)) and date(format, tme=false (= current time)) to DT.