Re: [Chategory-devl] FINALLY!!! => Plus my own update.

[Bob F <mon...@gm...>]

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