View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 217 | Composr | General / Uncategorised | public | 2010-11-22 00:26 | 2015-12-15 02:05 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | closed | Resolution | won't fix | ||
| Summary | 217: Major jump in the number of addons, split things up | ||||
| Description | Quicktime video playing should be separated into non-core addon Flash video playing should be separated into non-core addon Object-tag video playing should be separated into non-core addon ; new incompatible HTML5-jwplayer addon should be made available as an alternative Flash Comcode tag should be separated into non-core addon Realplayer video playing should be separated into non-core addon Move default catalogues into separate addons that just consist of install/uninstall code ; then remove special options from setup wizard Move default banners into separate addons that just consist of install/uninstall code and the linked pages ; then remove special options from setup wizard member merging should should be moved into a non-core addon members-online should should be moved into a non-core addon forum rules/passwords should be moved into a non-core addon birthdays should be moved into a non-core addon virtual forums should be moved into a non-core addon forum groupings should be moved into a non-core addon topic polls should be moved into a non-core addon rank images should be moved into a non-core addon topic emoticons should be moved into a non-core addon editarea should be moved into a non-core addon The default favicon should be moved into a non-core addon The default apple-icon should be moved into a non-core addon The email queue should be moved into a non-core addon main_db_notes should be moved into a non-core addon main_notes should be moved into a non-core addon main_only_if_match should be moved into a non-core addon main_comcode_page_children should be moved into a non-core addon main_include_module should be moved into a non-core addon The filetype CSS icons should be moved into a non-core addon Autosaving should be moved into a non-core addon Stack traces should be moved into a non-core addon main_emoticon_codes should be moved into a non-core addon main_sitemap and the sitemap page should be moved into a non-core addon side_personal_stats should be moved into a non-core addon Move Comcode help into separate addon All products in the pointstore addon should be separated out into separate addons; some are bundled in other addons (e.g. community billboard) and these should be separated out too core_adminzone_frontpage should have all the blocks separated out into separate addons Emoticons should should be moved into a non-core addon should be moved into a non-core addon Move rules page into separate addon All the individual payment gateways should be separate addons All the individual importers should be separate addons persistent-cache eaccelerator support should be moved into a non-core addon persistent-cache filesystem support should be moved into a non-core addon The special view modes should be moved into non-core addons The flash sound player should be moved into a non-core addon, or maybe just put into the chat addon XML sitemaps should be moved into a non-core addon quick reply should be moved into a non-core addon Split out permission tree editor as new non-core addon core_feedback features should be split into a number of non-core addons: trackbacks, ratings, comments, feedback page, guestbook page adding a member manually should be moved into a non-core addon Pluggable Conversr authentication schemes should each be a separate non-core addon Split out some addons from core_cleanup_tools The ability to close the site should be stripped out of core addons and made a non core addon core_menus should have all menu types moved out into separate addons (only tree and dropdown should be core), and actual editing interface moved out into separate non-core addon Move privacy pages into separate addons: one for Comcode page, one for Conversr module ; make Composr smart enough to make footer link go to what is installed with precedences Split core_forum_drivers into a lot of non-core addons - but don't allow uninstalling what is being used Split core_database_drivers into a lot of non-core addons - but don't allow uninstalling what is being used Move the WYSIWYG out of core_form_interfaces into a non-core addon Move the preview functionality out of core_form_interfaces into a non-core addon; and make the validation, SEO, and spelling options 3 separate addons too Ability to remove zone editor, panels, Comcode (core_rich_media addon), attachments, to have a much simpler CMS that just works on filtered WYSIWYG'd HTML for content and Tempcode layout ; Comcode pages would become just "Pages" Ability to have Comcode, but not attachments (i.e. remove attachments out of core_rich_media) Move the Comcode and block stuff out of core_form_interfaces and into core_rich_media blocks.ini and menus.ini contain some stuff for addons that might be removed. This is because not all addons have their own ini files, even if there are a few strings that come with them. | ||||
| Tags | Risk: Core rearchitecting | ||||
| Attach Tags | |||||
| Time estimation (hours) | 20 | ||||
| Sponsorship open | |||||
| parent of | 223 | Closed | Chris Graham | Rationalise language files down |
|
|
To give some context to this... Nothing here is 'important'. However if it is all done, then something happens -- Composr becomes a very light CMS. That would open up a lot of opportunities for implement lightweight custom projects using Composr as a base framework. |
|
|
I like the idea of a lightweight base framework on which to build. I was just startled at the number of addons I would need to employ to get back to what I currently use. But then, the greater granularity will allow people to build sites as they wish with much less bloat. |
|
|
Note that there are still cases in the code that are non modular. For example, in the block wizard, the special support for fancy definition of certain blocks is hard-coded (e.g. how the banner blocks allow selecting a banner type from a dropdown). In the ideal world all this would be achieved via hooks - i.e. block GUI hooks could be written. It's irrelevant for practical purposes, but I suppose if someone wanted to make an Composr distribution with addons not normally bundled, and want perfect interfaces for block adding, it could be an issue. That could be sorted at an opportune point. |
|
|
At this point the stuff remaining above is very minor, and trying to force that kind of stuff out of the core would make for a lot of extra plumbing code - effectively defeating the core aims. The sites Composr is targeted for aren't getting simpler, and inevitably I think we need to accept Composr is going to have quite a lot in the core just to do core web activities - and the best approach is to allow config options to turn things on/off or the addon split we currently have. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-06-08 00:15 | Chris Graham | Tag Renamed | Core rearchitecting => Risk: Core rearchitecting |
| 2023-02-26 18:29 | Chris Graham | Category | General => General / Uncategorised |
