chategory-devl Mailing List for Chategory

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

http://ajax.phpmagazine.net/2006/02/ajax_powered_chat_applications.html

All right, well, Jona is back online and ready to roll, so it's time
2.0picked up some steam.

The 2.0 version, which so far has a bunch of major changes and may have
more, is in the CVS. While the 1.x chategory used the module 'chategory',
guess what v2.0 will use? OH MY GOD YOU GOT IT RIGHT! We're using the modul=
e
'chategory2'. So check it out (literally) and get going if you can!

I've gotten the PHP mashed together. Chategory 2 uses a simple templating
system and has archiving (A much MUCH needed feature). If you grab it now,
you'll probably notice there are no admin CP controls for either of these.
That's coming. In addition, I've also restructured the files a bit,
borrowing from Zach's idea but not leaving it at a happy medium for now.

Jona has some stuff up his sleeve in terms of Javascript. New libraries,
mixing libraries, nixing libraries, visiting libraries, and all that fun
stuff.

So, grab the latest version, and if there are bugs, you have one of two
options:

1) Whine about it (If you do this, I will personally beat you! *fear me*)
2) Fix it and commit it to CVS

If you have a feature request, besides this here mailing list, there's also
the feature request tracker (
http://sourceforge.net/tracker/?atid=3D745215&group_id=3D139994&func=3Dbrow=
se). So
I think that sums it up for now. If you all don't get working, I'm gonna
send my cousin Paulie over to break your fingers! =3DP

--
- Da Bob

That's okay man, I understand.

And don't sweat it about the PSATS. They were pretty easy, just know your
rules of grammar and Math A, and you're fine. Algebra, geometry, and
probability I think were on it when I took it. Good luck mate!

On 10/9/05, Jonathan Fenocchi <jo...@sl...> wrote:
>
> Sorry, Bob, I don't have time to really think about it right now. I'm
> studying for a PSAT test that I didn't know I was supposed to take, and
> it's in less than a week!
>
> When I get a chance, I will definitely have a butt load of feedback for
> you, and once I square away some extra work, I'll spend more time
> working on Chategory (and less on other projects, like some Greasemonkey
> scripts that have been floating around).
>
> Bob F wrote:
> > 1) Yes, that makes sense. I can easily implement an error handling
> function.
> >
> > 2) Aye, yes, easily done.
> >
> > 3) Hmm. Well, with the new templating system, a user could do any of
> > those three. We can ship with a system similar to (c), but a user could
> > easily do (a) or (b) even. That was, at least it was my impression that
> > that was, the purpose of implementing a templating system. Because...
> >
> > a) It's not really that easy to just "include" something without
> > already having a UI of somesort, no matter how barebones, in place. The
> > templating system that I've prototyped allows a great, great deal of
> > configurability so that you could have the system any way you like it!
> >
> > b) A shoutbox type plugin would be capable just as easily, simply in th=
e
> > template files make the chatbox smaller with css!
> >
> > c) A full fledged system, IM-like could be our default template. Or,
> > hey, we could ship with mutliple templates! I've set it up so that
> > there's a config variable that points to the template folder.
> >
> > It might be more apparent once I implement a control panel for editing
> > the templates, but this should all be possible, methinks. Unless this
> > wasn't the intent. Then I just spent a lot of thinking for nothing, eh?
> > Ah well. Speak up Jona! Whats what?
> >
> > On 10/7/05, *Mike at GBHXonline.com* <mik...@gb...
> > <mailto:mik...@gb...>> wrote:
> >
> > Hello gang,
> >
> > Thank you, Bob. I downloaded it and started file peeping. I ran
> > across something and the next thing ya know I sort of formulated an
> > idea. Some stuff to focus on maybe.
> >
> > 1) First there needs to be consistency in things like errors. I
> > noted the varied headings mostly.
> >
> > 2) I think it's essential every bit of HTML be identified or
> > classified as styling or integrating Chategory must not conflict
> > with an existing CSS. We could ensure that everything is dished
> > out in divs, but individual element classing will almost guarantee a
> > leaner CSS. For integration, if one wants to ADD something to their
> > CSS -- let's say h3.ourclass which may or may not match
> > h3.theirclass -- it becomes their choice and either way is easy to
> > do. Construction is easy, deconstruction is difficult. Classes and
> > IDs give the "builders" more construction tools.
> > a. The classes need to be identified uniquely to avoid
> > conflicts. In other words we cannot have "#wrapper". We would need
> > "#ch2_wrapper" or something along those lines.
> >
> > 3) Chategory should be supplied in three stages of completion so to
> > speak for the three stages of use. (All with a stand-alone back-end
> > admin/mod/user, etc.)
> > a. Integration: Complete site integration (your barebones mode
> > plus). But I don't think of it as a mode, rather I think of it as a
> > bunch of module includes I can "place here" and "place there." As a
> > web developer I would need a handful of includes and a list of
> > styles (defined of course so I know what is what).
> > b. Plug-in (think Shout box): Include placed. This is a stand
> > alone unit without style choices outside of basic colors for
> > "customization." Perhaps allow width and height "choices." Maybe a
> > small set-up script or editable config to send style definitions to
> > the site-displayed module as inline styles. (Get fancy and offer
> > multiple choices and allow users to set their prefs... later lol.)
> > c. Ready-to-use, stand alone. I am thinking of something
> > entirely different employing just a wee bit of JavaScript to get it
> > done. Think instant messenger-ish versus what I have at
> > http://greenmethods.com/gm_live/. I'm thinking of something fairly
> > lightweight and portable. Not a pop-up, though (which would be great
> > actually), but a full function browser window.
> >
> > 4) This idea as a whole will be quite easy to do using nothing more
> > than CSS really. The key will be to have a CSS for each mode
> > (except "Integration" which will have no CSS, just a class and ID
> > list). Note: This does not include a global CSS for stand-alone
> > back-end admin/mod/user, etc.
> >
> > Anyway, that's about enough for one email. It's late and it was a
> > rough night. Daughter's open house at school... whole night was
> > shot, long story. But hopefully I'm lucid enough at the moment to
> > present this all in a somewhat intelligible manner.
> >
> > Mike
> >
> >
> > ----- Original Message -----
> > *From:* Bob F <mailto:mon...@gm...>
> > *To:* Chategory Mailing List
> > <mailto:cha...@li...>
> > *Sent:* Thursday, October 06, 2005 10:33 PM
> > *Subject:* Re: [Chategory-devl] FINALLY!!! =3D> Plus my own update.
> >
> > Apparently I'm productive today. Okay, I've got a zip you can
> > get here:
> >
> >
> http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1259952&grou=
p_id=3D139994&atid=3D745215
> > <
> http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1259952&grou=
p_id=3D139994&atid=3D745215
> >
> >
> >
> > Just unzip it and go. But now, first there's somethings to know.
> > This is archiving and templating, and a little file
> > restructuring. This is NOT ajax friendly. And I haven't added in
> > a control panel for editing the template files, but they can be
> > found in data/templates/default. There are 5 files:
> >
> > header.php
> > footer.php
> > post.php
> > nav.php
> > styles.css
> >
> > These contain most of the UI of Chategory. By editing these
> > files, one could completely integrate the system into their
> > site. There are API changes as well, functs.php is gone,
> > replaced by a Templater class. Forgive the bugs, I know of a
> > few, and I by no means have tested this beyond basic "It works".
> > I've got this pushed out because I felt I was slowing down the
> > project by holding up something that would have such a large
> > impact on the project. This is also to get feedback. The
> > templating is basic and not user-friendly. So how can we make it
> > work better? Archiving works. Is it okay? How can we make IT
> > work better? Ect, ect.
> >
> > This is NOT commited to the CVS repository either. If it gets
> > okayed, then I'll create a chategory2 repository for it and we
> > can get to work.
> >
> > So... GET TESTING!!!! :-P
> >
> >
> > On 10/6/05, *Mike at GBHXonline.com* <mik...@gb...
> > <mailto:mik...@gb...>> wrote:
> >
> > Great job, Bob. Within a week's time I will be going through
> > the files that I have finding class and whatnot in hopes of
> > preparing an index template. I have one idea I've been
> > tossing around but I'll wait on the details until after my
> > foray into the files.
> >
> > Mike
> >
> > ----- Original Message -----
> > *From:* Bob F <mailto:mon...@gm...>
> > *To:* Chategory Mailing List
> > <mailto:cha...@li...>
> > *Sent:* Thursday, October 06, 2005 4:48 PM
> > *Subject:* Re: [Chategory-devl] FINALLY!!!
> >
> > Alright, I've got non-saving archiving working
> > (deleting). Sorry, this should have been done earlier,
> > but I've been busy all week. My band is trying out for a
> > local "Battle of the Bands" so we've been practicing all
> > week. But I'm free tonight so I've got archiving
> > finished. But, since I've had to change the core API to
> > get it working, I'm just going to hold off and finish
> > off the templating system I've thought up instead of
> > wasting time backporting it to fit the UI (php) we plan
> > on trashing anyway. Depending on how productive I am
> > tonight, expect me finish it off for your testing and
> > reviewing by at the most end of monday (hopefully sooner).
> >
> > On 9/29/05, *Jonathan Fenocchi*
> > <jo...@sl...
> > <mailto:jo...@sl...>> wrote:
> >
> > All right! This is very cool, Bob. Let us know when
> > you've comitted it
> > to CVS so we can test it out and so forth. Thanks a
> > heap, and don't be
> > discouraged -- I'm getting back on track to help
> > work on it soon. :)
> >
> > --
> > - Da Bob
> >
> >
> >
> >
> > --
> > - Da Bob
> >
> >
> >
> >
> > --
> > - Da Bob
>

--
- Da Bob

1) Yes, that makes sense. I can easily implement an error handling function=
.

2) Aye, yes, easily done.

3) Hmm. Well, with the new templating system, a user could do any of those
three. We can ship with a system similar to (c), but a user could easily do
(a) or (b) even. That was, at least it was my impression that that was, the
purpose of implementing a templating system. Because...

a) It's not really that easy to just "include" something without already
having a UI of somesort, no matter how barebones, in place. The templating
system that I've prototyped allows a great, great deal of configurability s=
o
that you could have the system any way you like it!

b) A shoutbox type plugin would be capable just as easily, simply in the
template files make the chatbox smaller with css!

c) A full fledged system, IM-like could be our default template. Or, hey, w=
e
could ship with mutliple templates! I've set it up so that there's a config
variable that points to the template folder.

It might be more apparent once I implement a control panel for editing the
templates, but this should all be possible, methinks. Unless this wasn't th=
e
intent. Then I just spent a lot of thinking for nothing, eh? Ah well. Speak
up Jona! Whats what?

On 10/7/05, Mike at GBHXonline.com <mik...@gb...> wrote:
>
> Hello gang,
>  Thank you, Bob. I downloaded it and started file peeping. I ran across
> something and the next thing ya know I sort of formulated an idea. Some
> stuff to focus on maybe.
>  1) First there needs to be consistency in things like errors. I noted th=
e
> varied headings mostly.
>  2) I think it's essential every bit of HTML be identified or classified
> as styling or integrating Chategory must not conflict with an existing CS=
S.
> We could ensure that everything is dished out in divs, but individual
> element classing will almost guarantee a leaner CSS. For integration, if =
one
> wants to ADD something to their CSS -- let's say h3.ourclass which may or
> may not match h3.theirclass -- it becomes their choice and either way is
> easy to do. Construction is easy, deconstruction is difficult. Classes an=
d
> IDs give the "builders" more construction tools.
>  a. The classes need to be identified uniquely to avoid conflicts. In
> other words we cannot have "#wrapper". We would need "#ch2_wrapper" or
> something along those lines.
>  3) Chategory should be supplied in three stages of completion so to spea=
k
> for the three stages of use. (All with a stand-alone back-end
> admin/mod/user, etc.)
>  a. Integration: Complete site integration (your barebones mode plus). Bu=
t
> I don't think of it as a mode, rather I think of it as a bunch of module
> includes I can "place here" and "place there." As a web developer I would
> need a handful of includes and a list of styles (defined of course so I k=
now
> what is what).
>  b. Plug-in (think Shout box): Include placed. This is a stand alone unit
> without style choices outside of basic colors for "customization." Perhap=
s
> allow width and height "choices." Maybe a small set-up script or editable
> config to send style definitions to the site-displayed module as inline
> styles. (Get fancy and offer multiple choices and allow users to set thei=
r
> prefs... later lol.)
>  c. Ready-to-use, stand alone. I am thinking of something entirely
> different employing just a wee bit of JavaScript to get it done. Think
> instant messenger-ish versus what I have at
> http://greenmethods.com/gm_live/. I'm thinking of something fairly
> lightweight and portable. Not a pop-up, though (which would be great
> actually), but a full function browser window.
>  4) This idea as a whole will be quite easy to do using nothing more than
> CSS really. The key will be to have a CSS for each mode (except
> "Integration" which will have no CSS, just a class and ID list). Note: Th=
is
> does not include a global CSS for stand-alone back-end admin/mod/user, et=
c.
>  Anyway, that's about enough for one email. It's late and it was a rough
> night. Daughter's open house at school... whole night was shot, long stor=
y.
> But hopefully I'm lucid enough at the moment to present this all in a
> somewhat intelligible manner.
>  Mike
>
> ----- Original Message -----
> *From:* Bob F <mon...@gm...>
> *To:* Chategory Mailing List <cha...@li...>
> *Sent:* Thursday, October 06, 2005 10:33 PM
> *Subject:* Re: [Chategory-devl] FINALLY!!! =3D> Plus my own update.
>
> Apparently I'm productive today. Okay, I've got a zip you can get here:
>
>
> http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1259952&grou=
p_id=3D139994&atid=3D745215
>
> Just unzip it and go. But now, first there's somethings to know. This is
> archiving and templating, and a little file restructuring. This is NOT aj=
ax
> friendly. And I haven't added in a control panel for editing the template
> files, but they can be found in data/templates/default. There are 5 files=
:
>
> header.php
> footer.php
> post.php
> nav.php
> styles.css
>
> These contain most of the UI of Chategory. By editing these files, one
> could completely integrate the system into their site. There are API chan=
ges
> as well, functs.php is gone, replaced by a Templater class. Forgive the
> bugs, I know of a few, and I by no means have tested this beyond basic "I=
t
> works". I've got this pushed out because I felt I was slowing down the
> project by holding up something that would have such a large impact on th=
e
> project. This is also to get feedback. The templating is basic and not
> user-friendly. So how can we make it work better? Archiving works. Is it
> okay? How can we make IT work better? Ect, ect.
>
> This is NOT commited to the CVS repository either. If it gets okayed, the=
n
> I'll create a chategory2 repository for it and we can get to work.
>
> So... GET TESTING!!!! :-P
>
>
> On 10/6/05, Mike at GBHXonline.com <mik...@gb...> wrote:
> >
> >  Great job, Bob. Within a week's time I will be going through the files
> > that I have finding class and whatnot in hopes of preparing an index
> > template. I have one idea I've been tossing around but I'll wait on the
> > details until after my foray into the files.
> >  Mike
> >
> > ----- Original Message -----
> > *From:* Bob F <mon...@gm...>
> > *To:* Chategory Mailing List <cha...@li...>
> > *Sent:* Thursday, October 06, 2005 4:48 PM
> > *Subject:* Re: [Chategory-devl] FINALLY!!!
> >
> > Alright, I've got non-saving archiving working (deleting). Sorry, this
> > should have been done earlier, but I've been busy all week. My band is
> > trying out for a local "Battle of the Bands" so we've been practicing a=
ll
> > week. But I'm free tonight so I've got archiving finished. But, since I=
've
> > had to change the core API to get it working, I'm just going to hold of=
f and
> > finish off the templating system I've thought up instead of wasting tim=
e
> > backporting it to fit the UI (php) we plan on trashing anyway. Dependin=
g on
> > how productive I am tonight, expect me finish it off for your testing a=
nd
> > reviewing by at the most end of monday (hopefully sooner).
> >
> > On 9/29/05, Jonathan Fenocchi <jo...@sl...> wrote:
> > >
> > > All right! This is very cool, Bob. Let us know when you've comitted i=
t
> > > to CVS so we can test it out and so forth. Thanks a heap, and don't b=
e
> > >
> > > discouraged -- I'm getting back on track to help work on it soon. :)
> > >
> > > --
> > - Da Bob
> >
> >
>
>
> --
> - Da Bob
>
>

--
- Da Bob

Hello gang,

Thank you, Bob. I downloaded it and started file peeping. I ran across =
something and the next thing ya know I sort of formulated an idea. Some =
stuff to focus on maybe.

1) First there needs to be consistency in things like errors. I noted =
the varied headings mostly.=20

2) I think it's essential every bit of HTML be identified or classified =
as styling or integrating Chategory must not conflict with an existing =
CSS. We could ensure that everything is dished out in divs, but =
individual element classing will almost guarantee a leaner CSS. For =
integration, if one wants to ADD something to their CSS -- let's say =
h3.ourclass which may or may not match h3.theirclass -- it becomes their =
choice and either way is easy to do. Construction is easy, =
deconstruction is difficult. Classes and IDs give the "builders" more =
construction tools.
    a. The classes need to be identified uniquely to avoid conflicts. In =
other words we cannot have "#wrapper". We would need "#ch2_wrapper" or =
something along those lines.=20

3) Chategory should be supplied in three stages of completion so to =
speak for the three stages of use. (All with a stand-alone back-end =
admin/mod/user, etc.)
    a. Integration: Complete site integration (your barebones mode =
plus). But I don't think of it as a mode, rather I think of it as a =
bunch of module includes I can "place here" and "place there." As a web =
developer I would need a handful of includes and a list of styles =
(defined of course so I know what is what).
    b. Plug-in (think Shout box): Include placed. This is a stand alone =
unit without style choices outside of basic colors for "customization." =
Perhaps allow width and height "choices." Maybe a small set-up script or =
editable config to send style definitions to the site-displayed module =
as inline styles. (Get fancy and offer multiple choices and allow users =
to set their prefs... later lol.)=20
    c. Ready-to-use, stand alone. I am thinking of something entirely =
different employing just a wee bit of JavaScript to get it done. Think =
instant messenger-ish versus what I have at =
http://greenmethods.com/gm_live/. I'm thinking of something fairly =
lightweight and portable. Not a pop-up, though (which would be great =
actually), but a full function browser window.

4) This idea as a whole will be quite easy to do using nothing more than =
CSS really. The key will be to have a CSS for each mode (except =
"Integration" which will have no CSS, just a class and ID list). Note: =
This does not include a global CSS for stand-alone back-end =
admin/mod/user, etc.

Anyway, that's about enough for one email. It's late and it was a rough =
night. Daughter's open house at school... whole night was shot, long =
story. But hopefully I'm lucid enough at the moment to present this all =
in a somewhat intelligible manner.

Mike

  ----- Original Message -----=20
  From: Bob F=20
  To: Chategory Mailing List=20
  Sent: Thursday, October 06, 2005 10:33 PM
  Subject: Re: [Chategory-devl] FINALLY!!! =3D> Plus my own update.

  Apparently I'm productive today. Okay, I've got a zip you can get =
here:

  =
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1259952&grou=
p_id=3D139994&atid=3D745215=20

  Just unzip it and go. But now, first there's somethings to know. This =
is archiving and templating, and a little file restructuring. This is =
NOT ajax friendly. And I haven't added in a control panel for editing =
the template files, but they can be found in data/templates/default. =
There are 5 files:

  header.php
  footer.php
  post.php
  nav.php
  styles.css

  These contain most of the UI of Chategory. By editing these files, one =
could completely integrate the system into their site. There are API =
changes as well, functs.php is gone, replaced by a Templater class. =
Forgive the bugs, I know of a few, and I by no means have tested this =
beyond basic "It works". I've got this pushed out because I felt I was =
slowing down the project by holding up something that would have such a =
large impact on the project. This is also to get feedback. The =
templating is basic and not user-friendly. So how can we make it work =
better? Archiving works. Is it okay? How can we make IT work better? =
Ect, ect.=20

  This is NOT commited to the CVS repository either. If it gets okayed, =
then I'll create a chategory2 repository for it and we can get to work.=20

  So... GET TESTING!!!! :-P

  On 10/6/05, Mike at GBHXonline.com <mik...@gb...> wrote:
    Great job, Bob. Within a week's time I will be going through the =
files that I have finding class and whatnot in hopes of preparing an =
index template. I have one idea I've been tossing around but I'll wait =
on the details until after my foray into the files.

    Mike
      ----- Original Message -----=20
      From: Bob F=20
      To: Chategory Mailing List=20
      Sent: Thursday, October 06, 2005 4:48 PM
      Subject: Re: [Chategory-devl] FINALLY!!!

      Alright, I've got non-saving archiving working (deleting). Sorry, =
this should have been done earlier, but I've been busy all week. My band =
is trying out for a local "Battle of the Bands" so we've been practicing =
all week. But I'm free tonight so I've got archiving finished. But, =
since I've had to change the core API to get it working, I'm just going =
to hold off and finish off the templating system I've thought up instead =
of wasting time backporting it to fit the UI (php) we plan on trashing =
anyway. Depending on how productive I am tonight, expect me finish it =
off for your testing and reviewing by at the most end of monday =
(hopefully sooner).

      On 9/29/05, Jonathan Fenocchi <jo...@sl...> wrote: =

        All right! This is very cool, Bob. Let us know when you've =
comitted it
        to CVS so we can test it out and so forth. Thanks a heap, and =
don't be=20
        discouraged -- I'm getting back on track to help work on it =
soon. :)

      --=20
      - Da Bob=20

  --=20
  - Da Bob 
Apparently I'm productive today. Okay, I've got a zip you can get here:

http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1259952&group_=
id=3D139994&atid=3D745215

Just unzip it and go. But now, first there's somethings to know. This is
archiving and templating, and a little file restructuring. This is NOT ajax
friendly. And I haven't added in a control panel for editing the template
files, but they can be found in data/templates/default. There are 5 files:

header.php
footer.php
post.php
nav.php
styles.css

These contain most of the UI of Chategory. By editing these files, one coul=
d
completely integrate the system into their site. There are API changes as
well, functs.php is gone, replaced by a Templater class. Forgive the bugs, =
I
know of a few, and I by no means have tested this beyond basic "It works".
I've got this pushed out because I felt I was slowing down the project by
holding up something that would have such a large impact on the project.
This is also to get feedback. The templating is basic and not user-friendly=
.
So how can we make it work better? Archiving works. Is it okay? How can we
make IT work better? Ect, ect.

This is NOT commited to the CVS repository either. If it gets okayed, then
I'll create a chategory2 repository for it and we can get to work.

So... GET TESTING!!!! :-P

On 10/6/05, Mike at GBHXonline.com <mik...@gb...> wrote:
>
>  Great job, Bob. Within a week's time I will be going through the files
> that I have finding class and whatnot in hopes of preparing an index
> template. I have one idea I've been tossing around but I'll wait on the
> details until after my foray into the files.
>  Mike
>
> ----- Original Message -----
> *From:* Bob F <mon...@gm...>
> *To:* Chategory Mailing List <cha...@li...>
> *Sent:* Thursday, October 06, 2005 4:48 PM
> *Subject:* Re: [Chategory-devl] FINALLY!!!
>
> Alright, I've got non-saving archiving working (deleting). Sorry, this
> should have been done earlier, but I've been busy all week. My band is
> trying out for a local "Battle of the Bands" so we've been practicing all
> week. But I'm free tonight so I've got archiving finished. But, since I'v=
e
> had to change the core API to get it working, I'm just going to hold off =
and
> finish off the templating system I've thought up instead of wasting time
> backporting it to fit the UI (php) we plan on trashing anyway. Depending =
on
> how productive I am tonight, expect me finish it off for your testing and
> reviewing by at the most end of monday (hopefully sooner).
>
> On 9/29/05, Jonathan Fenocchi <jo...@sl...> wrote:
> >
> > All right! This is very cool, Bob. Let us know when you've comitted it
> > to CVS so we can test it out and so forth. Thanks a heap, and don't be
> > discouraged -- I'm getting back on track to help work on it soon. :)
> >
> > --
> - Da Bob
>
>

--
- Da Bob

Great job, Bob. Within a week's time I will be going through the files =
that I have finding class and whatnot in hopes of preparing an index =
template. I have one idea I've been tossing around but I'll wait on the =
details until after my foray into the files.

Mike
  ----- Original Message -----=20
  From: Bob F=20
  To: Chategory Mailing List=20
  Sent: Thursday, October 06, 2005 4:48 PM
  Subject: Re: [Chategory-devl] FINALLY!!!

  Alright, I've got non-saving archiving working (deleting). Sorry, this =
should have been done earlier, but I've been busy all week. My band is =
trying out for a local "Battle of the Bands" so we've been practicing =
all week. But I'm free tonight so I've got archiving finished. But, =
since I've had to change the core API to get it working, I'm just going =
to hold off and finish off the templating system I've thought up instead =
of wasting time backporting it to fit the UI (php) we plan on trashing =
anyway. Depending on how productive I am tonight, expect me finish it =
off for your testing and reviewing by at the most end of monday =
(hopefully sooner).

  On 9/29/05, Jonathan Fenocchi <jo...@sl...> wrote:=20
    All right! This is very cool, Bob. Let us know when you've comitted =
it
    to CVS so we can test it out and so forth. Thanks a heap, and don't =
be=20
    discouraged -- I'm getting back on track to help work on it soon. :)

  --=20
  - Da Bob 
Alright, I've got non-saving archiving working (deleting). Sorry, this
should have been done earlier, but I've been busy all week. My band is
trying out for a local "Battle of the Bands" so we've been practicing all
week. But I'm free tonight so I've got archiving finished. But, since I've
had to change the core API to get it working, I'm just going to hold off an=
d
finish off the templating system I've thought up instead of wasting time
backporting it to fit the UI (php) we plan on trashing anyway. Depending on
how productive I am tonight, expect me finish it off for your testing and
reviewing by at the most end of monday (hopefully sooner).

On 9/29/05, Jonathan Fenocchi <jo...@sl...> wrote:
>
> All right! This is very cool, Bob. Let us know when you've comitted it
> to CVS so we can test it out and so forth. Thanks a heap, and don't be
> discouraged -- I'm getting back on track to help work on it soon. :)
>
> --
- Da Bob

All right! This is very cool, Bob. Let us know when you've comitted it 
to CVS so we can test it out and so forth. Thanks a heap, and don't be 
discouraged -- I'm getting back on track to help work on it soon. :)

Bob F wrote:
> Woot! Archiving is almost complete! It feels sort of ugly, but if I knew 
> how to improve it I would. At any rate I've got it almost completely 
> working. You can cycle through all the messages, and you can archive 
> based on whenever. All that remains is to have the option to not 
> archive, but delete based on the time preference. And of course, make 
> the time period and wether to save messages changeable from the control 
> panel. But all the hard work is done! My brain bashing paid off.
> 
> I'll try to get it completed, and see if I can't less uglify the code. 
> But I should have it finished off tomorrow (gonna sleep now) and so then 
> I can start really digging into templating.
> 
> Rawk on! \m/
> 
> -- 
> - Da Bob

Woot! Archiving is almost complete! It feels sort of ugly, but if I knew ho=
w
to improve it I would. At any rate I've got it almost completely working.
You can cycle through all the messages, and you can archive based on
whenever. All that remains is to have the option to not archive, but delete
based on the time preference. And of course, make the time period and wethe=
r
to save messages changeable from the control panel. But all the hard work i=
s
done! My brain bashing paid off.

I'll try to get it completed, and see if I can't less uglify the code. But =
I
should have it finished off tomorrow (gonna sleep now) and so then I can
start really digging into templating.

Rawk on! \m/

--
- Da Bob

I think having a built-in updates would be awesome. Like you go to the 
admin cp and it says, "New updates available! <link>See what's 
new</link> or <link>go ahead and upgrade</link!>" The second link would 
be to something like "upgrade.php" (obviously it'd be secure for admins 
only) and would overwrite the PHP of other files (and possibly even 
itself, if necessary) based on the remote PHP source code that would be 
available on SF.net.

I'm not sure if I explained that thoroughly before (my memory evades me, 
as the idea has been running around in my head for quite some time), but 
I believe that would be an extremely cool feature, and plus it would 
highly encourage upgrading. I'm running Wordpress 1.5x and Wordpress 
tells me when there are updates, but I don't feel like it's worth 
upgrading unless I need to in order to make use of a plugin of some 
sort. If there was a link that said "Click here to upgrade 
automatically," I'd upgrade each time a new version is released.

Where is Zach, by the way? Ignoring the mailing list? Tsk, tsk.

Bob F wrote:
> Templating system isn't giving me problems, it was archiving. But that's 
> mainly because of my backwards (literally) naming scheme. I confused 
> myself using a $back variable for going forward and ++ when I should -- 
> and the like. Simpler now then I originally thought it would be, 
> wonderous what looking at something afresh can do.
> 
> Mike, I think you'll be happy to here about our new templating system we 
> have planned. If you've ever used wordpress or textpattern or any number 
> of PHP apps that use these things, you'll be familiar. Basically, we're 
> going to have four template pages that users can modify to their own 
> pleasing: Header, Footer, Navigation, Posts. So admins will have almost 
> total control over the HTML used (except for things like UBB code which 
> we'll generate on our own, of course). So users can totally incorporate 
> Chategory into their website exactly as they please, even making the 
> HTML fit in. They have control of everything before, and everything 
> after Chategory, they have control over the markup for the navigation 
> (This is chategory navigation - Home, Users Online, User Control Panel, 
> ect.) and how posts are presented. So if you want the posts displayed in 
> an unordered list, you can do it. If you want them to be all one line, 
> go ahead. If you want to have the post text, followed by the poster's 
> name, followed by the date then you can do it.
> 
> This was Zach's idea I believe, and I think it offers a great degree of 
> customization. We will, however, ship with a default template so that 
> Chategory is ready to go out of the box. Also, it's a lot easier to edit 
> what's already there instead of starting from scratch so this should 
> really ease it for admins. I'm also thinking of having an update script, 
> if possible,  which will make Chategory look the exact same on upgrading 
> to save existing users from any hassles that might pop up. Just an idea 
> for now, but I think it's doable.
> 

Templating system isn't giving me problems, it was archiving. But that's
mainly because of my backwards (literally) naming scheme. I confused myself
using a $back variable for going forward and ++ when I should -- and the
like. Simpler now then I originally thought it would be, wonderous what
looking at something afresh can do.

Mike, I think you'll be happy to here about our new templating system we
have planned. If you've ever used wordpress or textpattern or any number of
PHP apps that use these things, you'll be familiar. Basically, we're going
to have four template pages that users can modify to their own pleasing:
Header, Footer, Navigation, Posts. So admins will have almost total control
over the HTML used (except for things like UBB code which we'll generate on
our own, of course). So users can totally incorporate Chategory into their
website exactly as they please, even making the HTML fit in. They have
control of everything before, and everything after Chategory, they have
control over the markup for the navigation (This is chategory navigation -
Home, Users Online, User Control Panel, ect.) and how posts are presented.
So if you want the posts displayed in an unordered list, you can do it. If
you want them to be all one line, go ahead. If you want to have the post
text, followed by the poster's name, followed by the date then you can do
it.

This was Zach's idea I believe, and I think it offers a great degree of
customization. We will, however, ship with a default template so that
Chategory is ready to go out of the box. Also, it's a lot easier to edit
what's already there instead of starting from scratch so this should really
ease it for admins. I'm also thinking of having an update script, if
possible, which will make Chategory look the exact same on upgrading to sav=
e
existing users from any hassles that might pop up. Just an idea for now, bu=
t
I think it's doable.

Hello Chatters,

Thanks for the archive link. I had missed that. I was looking at the =
referred Yahoo page and reading about that (and others). Good stuff.=20

I suppose Chategory could be delivered in parts. The drive nowadays =
being to separate style from mark-up, no reason that couldn't be the =
focus here I suppose. Two parts: The engine and the vehicle. The engine =
is what makes Chategory work, the vehicle being what makes it look =
organized on the page (the basic style sheet and set of beginning =
classes and IDs).

To aid the web developer/user, two things could be done in addition to =
offering the basic style. First there should be an inclusion of =
additional classes and IDs. Driftwood and deadweight now, but they =
afford more design flexibility later on down the road. Second, a more =
involved style configuration could be supplied as a plug-in/option. The =
second CSS would make use of the spare classes and IDs (to make sure it =
works and is complete for one thing).

This stems from a problem with the first release. It had so little =
mark-up in the stand alone, it was a challenge to add style in any deep =
and meaningful way. Having a wrapper div thrown in there would have been =
nice, even it wasn't used at the time of the release. If we supply the =
elements, divs, and spans, people can have more fun with it. But ALL =
styling must be CSS. No <small></small>, no <strong></strong>, none of =
it should go into the build unless those elements are semantic in being =
styled as such (really important content needing strong emphasis, etc.) =
included in the CSS.

I haven't checked the files to see what's there for a CSS, but has this =
been considered. Adding classes et. al.?

<div id=3D"wrapping this up">
  <div id=3D"sincerely">
    <div id=3D"Mike"><span class=3D"Cherim"> :) </span></div>
   </div>
</div>

  ----- Original Message -----=20
  From: Bob F=20
  To: Chategory Mailing List=20
  Sent: Tuesday, September 27, 2005 12:12 AM
  Subject: Re: [Chategory-devl] Versioning: Chategory 2.0, 3.0

  Aye, sorry, I feel foolished, forgot that you lived out in Texas. =
Everything alright in your neck of the woods?

  In regards to Mike, yes, I saw him added to the team and have spoken =
with him a bit prior. Personally, I think he can be a great help =
user-end, including design and accessibility. I added him to this =
development mailing list a few days ago since, well, he's part of the =
team. =20

  Mike, if you're reading this, you may find it helpful to read this =
(http://sourceforge.net/mailarchive/forum.php?forum_id=3D46241). =
Sourceforge keeps a copy of messages sent in the mailing list for =
archival purposes, so if you want to know our discussions recently there =
you go.

  I've been planning out templating/archiving in my head. Ultimately =
we'll have a much better MVC model, which means that customization and =
spinoffs like Mike's GreenMethods (http://www.greenmethods.com/gm_live/) =
which is tech support using modified Chategory. I'll try and get it =
moving along, but the archiving system is making my head hurt. Its one =
of those things that I've spent too much time looking at. So I hope to =
get it wrapped up in the next week or so, then I'll commit it to CVS, =
but maybe as a new branch.=20

  On 9/26/05, Jonathan Fenocchi <jo...@sl... > wrote:
    Sorry for no response. Had a hurricane nearby and was out for about =
a
    week. Still trying to get back into the swing of things, so I might =
not
    be of much help in the coming couple of weeks. Hope to get back on =
track
    very soon, though.

    I haven't touched templating as of yet, and as far as I know no one =
else=20
    has either.

    By the way, I just wanted to update everyone on a new team member, =
Mike
    Cherim. He's not superlative in his programming skills, but he is a
    great creative source and will no doubt help keep the project =
running=20
    (trust me, he's pretty good at that). Also I think his assistance =
will
    be invaluable in regards to the user interface design. I plan to get =
him
    into helping us out as soon as possible, so look out for messages =
from=20
    him on the mailing list and elsewhere in the coming weeks.

  --=20
  - Da Bob 
Aye, sorry, I feel foolished, forgot that you lived out in Texas. Everythin=
g
alright in your neck of the woods?

In regards to Mike, yes, I saw him added to the team and have spoken with
him a bit prior. Personally, I think he can be a great help user-end,
including design and accessibility. I added him to this development mailing
list a few days ago since, well, he's part of the team.

Mike, if you're reading this, you may find it helpful to read this (
http://sourceforge.net/mailarchive/forum.php?forum_id=3D46241). Sourceforge
keeps a copy of messages sent in the mailing list for archival purposes, so
if you want to know our discussions recently there you go.

I've been planning out templating/archiving in my head. Ultimately we'll
have a much better MVC model, which means that customization and spinoffs
like Mike's GreenMethods (http://www.greenmethods.com/gm_live/) which is
tech support using modified Chategory. I'll try and get it moving along, bu=
t
the archiving system is making my head hurt. Its one of those things that
I've spent too much time looking at. So I hope to get it wrapped up in the
next week or so, then I'll commit it to CVS, but maybe as a new branch.

On 9/26/05, Jonathan Fenocchi <jo...@sl...> wrote:
>
> Sorry for no response. Had a hurricane nearby and was out for about a
> week. Still trying to get back into the swing of things, so I might not
> be of much help in the coming couple of weeks. Hope to get back on track
> very soon, though.
>
> I haven't touched templating as of yet, and as far as I know no one else
> has either.
>
> By the way, I just wanted to update everyone on a new team member, Mike
> Cherim. He's not superlative in his programming skills, but he is a
> great creative source and will no doubt help keep the project running
> (trust me, he's pretty good at that). Also I think his assistance will
> be invaluable in regards to the user interface design. I plan to get him
> into helping us out as soon as possible, so look out for messages from
> him on the mailing list and elsewhere in the coming weeks.
>
>
--
- Da Bob

Sorry for no response. Had a hurricane nearby and was out for about a 
week. Still trying to get back into the swing of things, so I might not 
be of much help in the coming couple of weeks. Hope to get back on track 
very soon, though.

I haven't touched templating as of yet, and as far as I know no one else 
has either.

By the way, I just wanted to update everyone on a new team member, Mike 
Cherim. He's not superlative in his programming skills, but he is a 
great creative source and will no doubt help keep the project running 
(trust me, he's pretty good at that). Also I think his assistance will 
be invaluable in regards to the user interface design. I plan to get him 
into helping us out as soon as possible, so look out for messages from 
him on the mailing list and elsewhere in the coming weeks.

Bob F wrote:
> Just to give you all an update.
> 
> I've been a bit busy as of late (last week or two). I have, however, 
> redesigned how Chategory stores messages. Have a bit of a snag with 
> cycling through them, but given a bit of time I can iron that out. When 
> I finish it, I'll upload a zip of it, because it does have some major 
> changes from what we have now. Basically, what I worked up uses a 
> directory for the data, and Chategory stores the files in with numeric 
> names that increase. Eg: 0.xml, 1.xml, 2.xml, ect. I've modified the 
> next and back links (and of course the API has a big change) so you can 
> cycle through all of these seamlessly. I've got archiving/cleanout 
> checks for when you post a new message, figured that was the best way. 
> The only snag, like I said, is I'm having some logic problems with 
> cycling backwards through messages, but that's probably because I'm not 
> thinking straight as of late. Soon to be ironed out.
> 
> Also, is anyone working on templating? I've got some ideas floating 
> around for doing that all, but I don't want to launch into some major 
> work on it if somebody else is already working on it.
> 
> 
> On 9/10/05, *Jonathan Fenocchi* <jo...@sl... 
> <mailto:jo...@sl...>> wrote:
> 
>     Good thinking, Bob. I think that's the best choice. Perhaps group
>     like-options, though? That is,
> 
>       Archive [Never, Monthly, Weekly, Daily]
>       Cleanout [Never, Monthly, Weekly, Daily]
> 
>     What do you think? Overkill? I know it's not best practice to give too
>     many options (according to our good usability friends, the 37 Signals),
>     but I think that this is an important flexibility feature, so it's okay
>     to make an exception.
> 
> -- 
> - Da Bob

Just to give you all an update.

I've been a bit busy as of late (last week or two). I have, however,
redesigned how Chategory stores messages. Have a bit of a snag with cycling
through them, but given a bit of time I can iron that out. When I finish it=
,
I'll upload a zip of it, because it does have some major changes from what
we have now. Basically, what I worked up uses a directory for the data, and
Chategory stores the files in with numeric names that increase. Eg: 0.xml,
1.xml, 2.xml, ect. I've modified the next and back links (and of course the
API has a big change) so you can cycle through all of these seamlessly. I'v=
e
got archiving/cleanout checks for when you post a new message, figured that
was the best way. The only snag, like I said, is I'm having some logic
problems with cycling backwards through messages, but that's probably
because I'm not thinking straight as of late. Soon to be ironed out.

Also, is anyone working on templating? I've got some ideas floating around
for doing that all, but I don't want to launch into some major work on it i=
f
somebody else is already working on it.

On 9/10/05, Jonathan Fenocchi <jo...@sl...> wrote:
>
> Good thinking, Bob. I think that's the best choice. Perhaps group
> like-options, though? That is,
>
> Archive [Never, Monthly, Weekly, Daily]
> Cleanout [Never, Monthly, Weekly, Daily]
>
> What do you think? Overkill? I know it's not best practice to give too
> many options (according to our good usability friends, the 37 Signals),
> but I think that this is an important flexibility feature, so it's okay
> to make an exception.
>
--
- Da Bob

Hm, you mean something like Meebo? (http://www.meebo.com/)

I'm not sure, either. It seems like a cool idea, but one concern I have 
is that, due to the fact that it will require images for the interface 
style, not just anyone will be able to create their own theme anymore, 
unless they can create the images necessary... What are the thoughts on 
theme changes, if we chose to drop the web-look and go for the app-like GUI?

Bob F wrote:
> Whoah, I saw this, I was blown away.
> 
> http://patcavit.com/2005/09/14/y-mail-beta-impressions/
> 
> He posts screenshots of Yahoo's beta mail service. So why am I posting 
> this to the Chategory Mailing List? The user interface - it looks like 
> an application level user interface. What web app has that kind of look? 
> Everything seems so traditional. I think it's definately possible for us 
> to create a GUI that looks and feels like an application, don't you? So, 
> thoughts/feelings/ideas ?
> 
> -- 
> - Da Bob

Whoah, I saw this, I was blown away.=20

http://patcavit.com/2005/09/14/y-mail-beta-impressions/

He posts screenshots of Yahoo's beta mail service. So why am I posting this=
=20
to the Chategory Mailing List? The user interface - it looks like an=20
application level user interface. What web app has that kind of look?=20
Everything seems so traditional. I think it's definately possible for us to=
=20
create a GUI that looks and feels like an application, don't you? So,=20
thoughts/feelings/ideas ?

--=20
- Da Bob

Good thinking, Bob. I think that's the best choice. Perhaps group 
like-options, though? That is,

  Archive [Never, Monthly, Weekly, Daily]
  Cleanout [Never, Monthly, Weekly, Daily]

What do you think? Overkill? I know it's not best practice to give too 
many options (according to our good usability friends, the 37 Signals), 
but I think that this is an important flexibility feature, so it's okay 
to make an exception.

Bob F wrote:
> Well, I'll tell you right now that I don't like every X posts, because  
> then on each submission we'd have to count, and write and read. Lot of 
> extra processing. If we give the admin an option,  I'm in favor of also 
> having an option of cleaning things out.
> 
> Think about it, if this is say used on a heavily traffic-ed website, 
> they may not want to store megabytes of conversations. So maybe,
> 
> Archive Monthly
> Archive Weekly
> Archive Daily
> Cleanout Monthly
> Cleanout Weekly
> Cleanout Daily
> 
> All as choices.
> 
> On 9/9/05, *Jonathan Fenocchi* < jo...@sl... 
> <mailto:jo...@sl...>> wrote:
> 
>     Do we archive? Yes. Does the admin have to press a button? No. When are
>     archives created? Well, we can give the admin a few choices -- monthly,
>     weekly, daily, or we can let him say after X messages. Actually, I
>     think
>     "after X messages" wouldn't be a good idea, since you could have a lot
>     of conversation in five minutes and it may archive automatically at that
>     time. On the other hand, every month might not be a good idea, either,
>     since someone could be having a conversation at the end of the month,
>     and suddenly have no messages... Hmm... Thoughts on that?
> 
>     Still, I think the best option would be to give the admin a dropdown:
>     "Store archives every: [month, week, day]"
> 
>     Bob F wrote:
>>  Cool, we got that hashed out.
>>
>>  Now, I've got another for discussion, that we've yet to think out
>>  entirely. Archiving. There are obviously problems with working with
>>  humungous files. Jona suggests archiving, but how should this be
>     done?
>>  On a daily/weekly/monthly basis? After X amount of posts? Does it
>>  require a mod or admin to press a button? Or do we not archive?
> 
>     -------------------------------------------------------
>     SF.Net email is Sponsored by the Better Software Conference & EXPO
>     September 19-22, 2005 * San Francisco, CA * Development Lifecycle
>     Practices
>     Agile & Plan-Driven Development * Managing Projects & Teams *
>     Testing & QA
>     Security * Process Improvement & Measurement *
>     http://www.sqe.com/bsce5sf
>     _______________________________________________
>     Chategory-devl mailing list
>     Cha...@li...
>     <mailto:Cha...@li...>
>     https://lists.sourceforge.net/lists/listinfo/chategory-devl
> 
> 
> 
> 
> -- 
> - Da Bob
> 
> -- 
> - Da Bob

Well, I'll tell you right now that I don't like every X posts, because then=
=20
on each submission we'd have to count, and write and read. Lot of extra=20
processing. If we give the admin an option, I'm in favor of also having an=
=20
option of cleaning things out.=20

Think about it, if this is say used on a heavily traffic-ed website, they=
=20
may not want to store megabytes of conversations. So maybe,

Archive Monthly
Archive Weekly
Archive Daily
Cleanout Monthly
Cleanout Weekly
Cleanout Daily

All as choices.=20

On 9/9/05, Jonathan Fenocchi <jo...@sl...> wrote:
>=20
> Do we archive? Yes. Does the admin have to press a button? No. When are
> archives created? Well, we can give the admin a few choices -- monthly,
> weekly, daily, or we can let him say after X messages. Actually, I think=
=20
> "after X messages" wouldn't be a good idea, since you could have a lot
> of conversation in five minutes and it may archive automatically at that
> time. On the other hand, every month might not be a good idea, either,=20
> since someone could be having a conversation at the end of the month,
> and suddenly have no messages... Hmm... Thoughts on that?
>=20
> Still, I think the best option would be to give the admin a dropdown:
> "Store archives every: [month, week, day]"=20
>=20
> Bob F wrote:
> > Cool, we got that hashed out.
> >
> > Now, I've got another for discussion, that we've yet to think out
> > entirely. Archiving. There are obviously problems with working with
> > humungous files. Jona suggests archiving, but how should this be done?=
=20
> > On a daily/weekly/monthly basis? After X amount of posts? Does it
> > require a mod or admin to press a button? Or do we not archive?
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO=20
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle=20
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Chategory-devl mailing list
> Cha...@li...=20
> https://lists.sourceforge.net/lists/listinfo/chategory-devl
>=20

--=20
- Da Bob=20

--=20
- Da Bob

Fine by me, course I'm not one for designing any way. Content-wise, it's=20
great.

On 9/9/05, Zach Blume <zac...@gm...> wrote:
>=20
> Um, eww. I don't like that. I loved the old one.
>=20
> On 9/9/05, Jonathan Fenocchi <jo...@sl... > wrote:
> >=20
> > Hey guys, I took the time to redesign the Chategory site 'cause the old=
=20
> > design got old. Check it out: http://chategory.sourceforge.net/ and let
> > me know what you think.
> >=20
> >=20
> > -------------------------------------------------------
> > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > September 19-22, 2005 * San Francisco, CA * Development Lifecycle=20
> > Practices
> > Agile & Plan-Driven Development * Managing Projects & Teams * Testing &=
=20
> > QA=20
> > Security * Process Improvement & Measurement *=20
> > http://www.sqe.com/bsce5sf
> > _______________________________________________
> > Chategory-devl mailing list
> > Cha...@li...
> > https://lists.sourceforge.net/lists/listinfo/chategory-devl
> >=20
>=20
>=20

--=20
- Da Bob

Um, eww. I don't like that. I loved the old one.

On 9/9/05, Jonathan Fenocchi <jo...@sl...> wrote:
>=20
> Hey guys, I took the time to redesign the Chategory site 'cause the old
> design got old. Check it out: http://chategory.sourceforge.net/ and let
> me know what you think.
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle=20
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Chategory-devl mailing list
> Cha...@li...
> https://lists.sourceforge.net/lists/listinfo/chategory-devl
>

Hey guys, I took the time to redesign the Chategory site 'cause the old 
design got old. Check it out: http://chategory.sourceforge.net/ and let 
me know what you think.

Do we archive? Yes. Does the admin have to press a button? No. When are 
archives created? Well, we can give the admin a few choices -- monthly, 
weekly, daily, or we can let him say after X messages. Actually, I think 
"after X messages" wouldn't be a good idea, since you could have a lot 
of conversation in five minutes and it may archive automatically at that 
time. On the other hand, every month might not be a good idea, either, 
since someone could be having a conversation at the end of the month, 
and suddenly have no messages... Hmm... Thoughts on that?

Still, I think the best option would be to give the admin a dropdown: 
"Store archives every: [month, week, day]"

Bob F wrote:
> Cool, we got that hashed out.
> 
> Now, I've got another for discussion, that we've yet to think out 
> entirely. Archiving. There are obviously problems with working with 
> humungous files. Jona suggests archiving, but how should this be done? 
> On a daily/weekly/monthly basis? After X amount of posts? Does it 
> require a mod or admin to press a button? Or do we not archive?
> 
> 
> On 9/9/05, *Jonathan Fenocchi* <jo...@sl... 
> <mailto:jo...@sl...>> wrote:
> 
>     Sounds good to me, too, Bob.
> 
>     Zach Blume wrote:
>      > Seems good to me.
> 
> -- 
> - Da Bob

Are we the only ones on the mailing list? lol....

On 9/9/05, Jonathan Fenocchi <jo...@sl...> wrote:
>=20
> Sounds good to me, too, Bob.
>=20
> Zach Blume wrote:
> > Seems good to me.
> >
> > On 9/9/05, *Bob F* <mon...@gm...
> > <mailto:mon...@gm...>> wrote:
> >
> > Yahr, that's what I meant. My brain wasn't making much sense last
> > night. We can, it's the ultimate extensibility. And, I guess if we
> > ship with a default, what harm is there? Just two points:
> >
> > 1) We obviously need to include a error message (Friendly, of
> > course) if template files can't be found
> >
> > 2)How many template files?
> >
> > I mean, it's simple enough templating the main page. But how about
> > the Control Panels? And Users Online? Login and Logout? And the Help
> > Page?
> >
> > I propose that we have, as part of the templating, a Header and a
> > Footer. So the user can define Header, Footer, Nav, Posts, and the
> > submit form. Then, for things like Login and Logout, CP's, Users
> > Online, ect. we can just use these header and footer templates and
> > thus keep it simple.
> >
> > Your all thoughts?
> >
> > On 9/9/05, *Zach Blume* < zac...@gm...
> > <mailto:zac...@gm...>> wrote:
> >
> >
> >
> > Well, actually, I was thinking of something more traditional like:
> >
> > <?php
> > echo '<ul>';
> > $posts =3D mssgLoop(15);
> > foreach ($posts as $post)
> > {
> > echo '<li><span class=3D"mssgMeta">'.time(
> > $post['time'], '\a\t g:i a' ).$post['author'].' said:</span>
> > '.$post['text'].'</li>';
> > }
> > echo '</ul>';
> > ?>
> >
> > Seems more logical to me, at least. And extensible. I am still
> > for letting the users make their own nav. If they know enough to
> > do templating, they are going to want to fully integrate the
> > HTML into their existing site CSS (I think).
> >
> > --
> > - Da Bob
> >
> >
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle=20
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Chategory-devl mailing list
> Cha...@li...
> https://lists.sourceforge.net/lists/listinfo/chategory-devl
>

2005	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (31)	Oct (7)	Nov	Dec
2006	Jan	Feb (1)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

chategory-devl Mailing List for Chategory

chategory-devl — Mailing List for Chategory Developers, about Chategory Development