head	1.5;
access;
symbols;
locks; strict;
comment	@# @;


1.5
date	2000.08.28.02.28.21;	author chuck;	state dead;
branches;
next	1.4;

1.4
date	2000.01.17.22.11.01;	author chuck;	state Exp;
branches;
next	1.3;

1.3
date	2000.01.16.18.49.39;	author chuck;	state Exp;
branches;
next	1.2;

1.2
date	99.08.04.04.15.59;	author chuck;	state Exp;
branches;
next	1.1;

1.1
date	99.07.20.07.36.26;	author jon;	state Exp;
branches;
next	;


desc
@@


1.5
log
@starting to modernize babel - nothing autogenerated, standard
directory/library names, etc.
@
text
@function export_state (&$request_ref, &$hash_ref) {
  global $conf;
  
  if (isset($request_ref->post['subject']))
    $hash_ref['subject'] = $request_ref->post['subject'];
  else
    $hash_ref['subject'] = '';
  
  if (isset($request_ref->post['author_id']))
    $hash_ref['author_id'] = $request_ref->post['author_id'];
  else
    $hash_ref['author_id'] = '';
  
  global $auth;
  $hash_ref['author'] = $auth->auth_getusername($hash_ref['author_id']);
  
  if (isset($request_ref->post['created']))
    $hash_ref['created'] = date('D M dS h:ia Y', $request_ref->post['created']);
  else
    $hash_ref['created'] = '';
  
  if (isset($request_ref->post['modified']))
    $hash_ref['modified'] = date('D M dS h:ia Y', $request_ref->post['modified']);
  else
    $hash_ref['modified'] = '';
  
  if (isset($request_ref->post['body']))
    $hash_ref['body'] = $request_ref->post['body'];
  else
    $hash_ref['body'] = '';
  
  $hash_ref['url'] = $conf['url'];
  $hash_ref['topic'] = $request_ref->topic;
  $hash_ref['id'] = $request_ref->id;
  
  return success();
}
@


1.4
log
@Another whomping commit that really doesn't do much tangible. The conf
system is now moved over to the $conf[section][value|subsection] mode that
the other cvs horde stuff is using.

Also, I'm compacting and tightening up the code wherever possible when I go.
Lots of major changes - moving the configuration of forums into the
database, changes in the database code for faster sql access, options to put
different forums in different tables/databases, and some nifty setup ideas -
to come.

Comments on what people would like to see in a forum system - I've already
thought of being able to attach files (where should they be stored?) - would
be welcome.
@
text
@@


1.3
log
@Babel no longer keeps it's own user table; it grabs Horde (phplib)
usernames/ids and uses those. We'll need to figure out a way of storing
email and fullname prefs with Horde accounts.
@
text
@d2 2
d32 1
a32 1
  $hash_ref['url'] = $request_ref->conf['url'];
@


1.2
log
@cjh: pruning out all the code that either isn't used or is only used for
maintaining/creating users - all of which is moving to Horde proper. Also a
few more fixes for the new session/user stuff, though I haven't quite gotten
rid of the "users" table yet - that's coming, though.

babel.php3 is a nice bit shorter, now... ;)

Anyway, a bit more work, and a better Horde user framework, and babel should
be more or less ready for primetime. oh, there's that whole customization
thing, too.

Speaking of which, what do people prefer: imp-style defaults.php3, or
babel-style babel.conf. I figure we should standardize on one; they're both
easy to auto-generate; babel's is maybe a little bit more overhead to parse,
but it's a bit more user friendly as well. Thoughts?
@
text
@d12 2
a13 4
  if (isset($request_ref->post['author']))
    $hash_ref['author'] = $request_ref->post['author'];
  else
    $hash_ref['author'] = '';
@


1.1
log
@
jon: alrighty, babel.php3.in is now broken down into seperate
     function files.  they're jusy dying to be combined into
     objects and seperate source files.
@
text
@d7 5
@

