Menu
▾
▴
[SM-CVS] CVS: sm2-planning/archive/developers/thomppj/chat api_files.txt,NONE,1.1 api_hash.txt,NONE,1.1 dir_structure.txt,NONE,1.1 dir_structure2.txt,NONE,1.1 hello_start.txt,NONE,1.1 idea_hash.txt,NONE,1.1
Update of /cvsroot/squirrelmail/sm2-planning/archive/developers/thomppj/chat
In directory usw-pr-cvs1:/tmp/cvs-serv16414/archive/developers/thomppj/chat
Added Files:
api_files.txt api_hash.txt dir_structure.txt
dir_structure2.txt hello_start.txt idea_hash.txt
Log Message:
finally
--- NEW FILE ---
Here is what needs defined before we start coding:
1. What is included in SquirrelCore
2. Interaction between SquirrelCore and SquirrelApps
3. Templating should be universal between all SquirrelApps, how will this happen?
--------------
Concept:
SquirrelCore
+-- index.php (starter *1)
+-- Libraries (*2)
| +-- Message API
| +-- Preference API
| +-- Logger API
| +-- ShutterBug API
|
+-- Modules (*2)
| +-- Message API
| +-- imap_general.php
| +-- cyrus_imap.php
| +-- nntp.php
| +-- Preference API
| +-- mysql.php
| +-- filesystem.php
| +-- oracle.php
| +-- Logger API
| +-- syslog.php
| +-- email.php
| +-- pager.php
| +-- ShutterBug API
| +-- mysql.php
| +-- filesystem.php
|
+-- Templates (*3)
| +-- Classic
| | +-- SquirrelMail
| | +-- SquirrelContacts
| | +-- SquirrelCalendar
| | +-- ShutterBug
| |
| +-- Slashdot
| | +-- SquirrelMail
| | +-- SquirrelContacts
| | +-- SquirrelCalendar
| | +-- ShutterBug
| |
| +-- Blue Steel
| +-- SquirrelMail
| +-- SquirrelContacts
| +-- SquirrelCalendar
| +-- ShutterBug
|
+-- Apps (*4)
+-- SquirrelMail
| +-- SquirrelMail Controller #1
| +-- SquirrelMail Controller #2
| +-- SquirrelMail Controller #3
+-- SquirrelContacts
| +-- SquirrelContacts Controller #1
| +-- SquirrelContacts Controller #2
| +-- SquirrelContacts Controller #3
| +-- SquirrelContacts Controller #4
+-- SquirrelCalendar
| +-- SquirrelCalendar Controller #1
| +-- SquirrelCalendar Controller #2
+-- ShutterBug
+-- ShutterBug Controller #1
+-- ShutterBug Controller #2
+-- ShutterBug Controller #3
*1: This starter will detect what apps are installed under it,
and perhaps to save from having to detect every time, it will
read which ones are configured. Then act accordingly.
*2: The libraries are used universally for all SquirrelApps.
These are the API implementations that we have been talking
so much about.
*3: Templates are defined under this directory. If for some
installed app, there isn't a theme, it will revert to the
default theme for that app. This will never happen with
themes that we support (we will create them universally)
but the case should be there for unsupported themes.
*4: The Apps will be loaded dynamically inside the *1 part
depending on how they're implemented. Probably, this will
be the wrapper around the controller which loads the libraries
and everything, and formats the data using the given template
in *3.
--- NEW FILE ---
array called contactsources:
$contactsource[0] = new LDAPContactSource(host1);
$contactsource[0] = new LDAPContactSource(host2);
$contactsource[2] = new MySQLContactSource("localhost","server");
$contactsource[3] = new PersonalContactSource("localhost","bob");
--- NEW FILE ---
squirrelapps/
|
+-- index.php
+-- lib/
| +-- api_message.inc
| +-- api_preference.inc
| +-- api_logging.inc
| +-- strings.inc
| +-- date.inc
| +-- i18n.inc
|
+-- modules/
| +-- message/
| | +-- imap_general.inc
| | +-- cyrus_imap.inc
| | +-- nntp.inc
| |
| +-- preference/
| | +-- mysql.inc
| | +-- filesystem.inc
| | +-- oracle.inc
| | +-- imap.inc
| |
| +-- logging/
| +-- syslog.inc
| +-- email.inc
|
+-- templates/
| +-- classic/
| | +-- sqmail/
| | | +-- frames/
| | | +-- no_frames/
| | |
| | +-- sqcontacts/
| | | +-- frames/
| | | +-- no_frames/
| | |
| | +-- sqcalendar/
| | +-- frames/
| | +-- no_frames/
| |
| +-- brushed_metal/
| +-- sqmail/
| | +-- frames/
| | +-- no_frames/
| |
| +-- sqcontacts/
| | +-- frames/
| | +-- no_frames/
| |
| +-- sqcalendar/
| +-- frames/
| +-- no_frames/
|
+-- apps/
+-- sqmail/
| +-- classic
| +-- frames
|
+-- sqcontacts/
| +-- classic
| +-- frames
|
+-- sqcalendar/
+-- classic
+-- frames
--- NEW FILE ---
$Id: dir_structure2.txt,v 1.1 2002/11/06 04:17:04 sizzlingmercury Exp $
$Author: sizzlingmercury $
$Date: 2002/11/06 04:17:04 $
--
Squirrel Applications Directory Structure
Authors: Luke Ehresman <lu...@sq...>
Paul Joseph Thompson <th...@sq...>
========================================================
Purpose: To describe the directory structure that the Squirrel
Applications will use.
Directory Structure
===================
The Squirrel Applications will use the following directory structure.
squirrelapps/
|
+-- doc/
| +-- {squirrelapps documentation}
|
+-- web/
| +-- index.php
|
+-- libraries/
| +-- api_preference.inc
| +-- api_logging.inc
| +-- api_message.inc
| +-- api_calender.inc
| +-- api_reqhandler.inc
| +-- api_uibuilder.inc
| +-- strings.inc
| +-- date.inc
| +-- i18n.inc
|
+-- modules/
| +-- preference/
| | +-- mysql.inc
| | +-- filesystem.inc
| | +-- oracle.inc
| | +-- imap.inc
| |
| +-- logging/
| | +-- syslog.inc
| | +-- email.inc
| |
| +-- uibuilder/
| | +-- ptemplate.inc
| | +-- xml_xsl.inc
| |
| +-- message/
| | +-- imap_general.inc
| | +-- cyrus_imap.inc
| | +-- nntp.inc
| |
| +-- calender/
| +-- sql_general.inc
| +-- mysql.inc
| +-- postgresql.inc
| +-- oracle.inc
|
+-- templates/
| +-- classic
| +-- brushed_metal
|
+-- applications/
+-- sqmail/
| +-- classic/
| | +-- reqhand.inc
| | +-- {reqhand files}
| |
| +-- frames/
| +-- reqhand.inc
| +-- {reqhand files}
|
+-- sqcontacts/
| +-- classic/
| | +-- reqhand.inc
| | +-- {reqhand files}
| |
| +-- frames/
| +-- reqhand.inc
| +-- {reqhand files}
|
+-- sqcalendar/
+-- classic/
| +-- reqhand.inc
| +-- {reqhand files}
|
+-- frames/
+-- reqhand.inc
+-- {reqhand files}
--- NEW FILE ---
Here is what needs defined before we start coding:
1. What is included in SquirrelCore
2. Interaction between SquirrelCore and SquirrelApps
3. Templating should be universal between all SquirrelApps, how will this happen?
--------------
Concept:
SquirrelCore
+-- index.php (starter *1)
+-- Libraries (*2)
| +-- Hello API
| +-- Preference API
| +-- Logger API
|
+-- Modules (*2)
| +-- Hello API
| +-- simple.php
| +-- filesystem.php
| +-- Preference API
| +-- mysql.php
| +-- filesystem.php
| +-- oracle.php
| +-- Logger API
| +-- syslog.php
| +-- email.php
| +-- pager.php
|
+-- Templates (*3)
| +-- Classic
| | +-- SquirrelHello
| |
| +-- Slashdot
| | +-- SquirrelHello
| |
| +-- Blue Steel
| +-- SquirrelHello
|
+-- Apps (*4)
+-- SquirrelHello
+-- SquirrelHello Noframes Controller
+-- SquirrelHello Frames Controller
*1: This starter will detect what apps are installed under it,
and perhaps to save from having to detect every time, it will
read which ones are configured. Then act accordingly.
*2: The libraries are used universally for all SquirrelApps.
These are the API implementations that we have been talking
so much about.
*3: Templates are defined under this directory. If for some
installed app, there isn't a theme, it will revert to the
default theme for that app. This will never happen with
themes that we support (we will create them universally)
but the case should be there for unsupported themes.
*4: The Apps will be loaded dynamically inside the *1 part
depending on how they're implemented. Probably, this will
be the wrapper around the controller which loads the libraries
and everything, and formats the data using the given template
in *3.
--- NEW FILE ---
Here is what needs defined before we start coding:
1. What is included in SquirrelCore
2. Interaction between SquirrelCore and SquirrelApps
3. Templating should be universal between all SquirrelApps, how will this happen?
--------------
Concept:
SquirrelCore
+-- index.php (starter *1)
+-- Libraries (*2)
| +-- Message API
| +-- Preference API
| +-- Logger API
| +-- ShutterBug API
|
+-- Templates (*3)
| +-- Classic
| | +-- SquirrelMail
| | +-- SquirrelContacts
| | +-- SquirrelCalendar
| | +-- ShutterBug
| |
| +-- Slashdot
| | +-- SquirrelMail
| | +-- SquirrelContacts
| | +-- SquirrelCalendar
| | +-- ShutterBug
| |
| +-- Blue Steel
| +-- SquirrelMail
| +-- SquirrelContacts
| +-- SquirrelCalendar
| +-- ShutterBug
|
+-- Apps (*4)
+-- SquirrelMail
| +-- SquirrelMail Controller #1
| +-- SquirrelMail Controller #2
| +-- SquirrelMail Controller #3
+-- SquirrelContacts
| +-- SquirrelContacts Controller #1
| +-- SquirrelContacts Controller #2
| +-- SquirrelContacts Controller #3
| +-- SquirrelContacts Controller #4
+-- SquirrelCalendar
| +-- SquirrelCalendar Controller #1
| +-- SquirrelCalendar Controller #2
+-- ShutterBug
+-- ShutterBug Controller #1
+-- ShutterBug Controller #2
+-- ShutterBug Controller #3
*1: This starter will detect what apps are installed under it,
and perhaps to save from having to detect every time, it will
read which ones are configured. Then act accordingly.
*2: The libraries are used universally for all SquirrelApps.
These are the API implementations that we have been talking
so much about.
*3: Templates are defined under this directory. If for some
installed app, there isn't a theme, it will revert to the
default theme for that app. This will never happen with
themes that we support (we will create them universally)
but the case should be there for unsupported themes.
*4: The Apps will be loaded dynamically inside the *1 part
depending on how they're implemented. Probably, this will
be the wrapper around the controller which loads the libraries
and everything, and formats the data using the given template
in *3.
|