Moved RedBrowser class from reddav.php to it's own file.

First step on cleaning up ReadDAV classes and restructuring it bit in
preparation for adding some more DAV features, photo access, CalDAV, etc.
and hopefully also some PHPunits.
Add a PHP5.3 namespace for RedDAV classes. Any objections against this or
the vendor namespace?
Add some more documentation for RedBrowser.

1 files changed, 0 insertions, 35 deletions

diff --git a/doc/to_do_code.bb b/doc/to_do_code.bb
index 89b31f46d..f4c685063 100644
--- a/doc/to_do_code.bb
+++ b/doc/to_do_code.bb
@@ -3,73 +3,38 @@
 We need much more than this, but here are areas where developers can help. Please edit this page when items are finished. Another place for developers to start is with the issues list.

 

 [li]Documentation - see Red Documentation Project To-Do List[/li]

-

 [li]Include TOS link in registration/verification email[/li]

-

 [li]Finish the anti-spam bayesian engine[/li]

-

 [li]If DAV folders exist, add an option to the Settings page to set a default folder for attachment uploads.[/li] 

-

 [li]Integrate the "open site" list with the register page[/li]

-

 [li]implement oembed provider interface[/li]

-

 [li]refactor the oembed client interface so that we can safely sandbox remote content[/li]

-

 [li]implement openid server interface[/li]

-

 [li]Write more webpage layouts[/li]

-

 [li]Write more webpage widgets[/li]

-

 [li](Advanced) create a UI for building Comanche pages[/li]

-

-[li]templatise and translate the Web interface to webDAV[/li]

-

 [li]Extend WebDAV to provide desktop access to photo albums[/li]

-

 [li]External post connectors - create standard interface[/li]

-

 [li]External post connectors, add popular services[/li]

-

 [li]service classes - provide a pluggable subscription payment gateway for premium accounts[/li]

-

 [li]service classes - account overview page showing resources consumed by channel. With special consideration this page can also be accessed at a meta level by the site admin to drill down on problematic accounts/channels.[/li]

-

 [li]Events module - fix permissions on events, and provide JS translation support for the calendar overview; integrate with calDAV[/li]

-

 [li]Events module - event followups and RSVP[/li]

-

 [li]Uploads - integrate #^[url=https://github.com/blueimp/jQuery-File-Upload]https://github.com/blueimp/jQuery-File-Upload[/url][/li]

-

 [li]Import/export - include events, things, etc.[/li]

-

 [li]Import channel from Diaspora/Friendica[/li]

-

 [li]MediaGoblin photo "crosspost" connector[/li]

-

 [li]Create management page/UI for extensible profile fields[/li]

-

 [li]Create interface to include/exclude and re-order standard profile fields[/li]

-

 [li]Provide a mechanism to share page design elements in posts (just like apps)[/li]

-

 [li]App taxonomy[/li]

-

 [li]Customisable App collection pages[/li]

-

 [li]replace the tinymce visual editor and/or make the visual editor pluggable and responsive to different output formats. We probably want library/bbedit for bbcode. This needs a fair bit of work to catch up with our "enhanced bbcode", but start with images, links, bold and highlight and work from there.[/li]

-

 [li]Photos module - turn photos into normal conversations and fix tagging[/li]

-

 [li]Provide RSS feed support which look like channels (in matrix only - copyright issues)[/li]

-

 [li]Create mobile clients for the top platforms - which involves extending the API so that we can do stuff far beyond the current crop of Twitter/Statusnet clients. Ditto for mobile themes. We can probably use something like the Friendica Android app as a base to start from.[/li]

-

 [li]Implement owned and exchangeable "things".[/li]

-

 [li]Family Account creation - using service classes (an account holder can create a certain number of sub-accounts which are all tied to their subscription - if the subscription lapses they all go away).[/li]

-

 [li]Put mod_admin under Comanche[/li]

 

 In many cases some of the work has already been started and code exists so that you needn't start from scratch. Please contact one of the developer channels like Channel One (one@zothub.com) before embarking and we can tell you what we already have and provide some insights on how we envision these features fitting together.