Re: portal code changes

On Thursday 21 October 2004 09:12, Alexey Borzov wrote:
> Robert Treat wrote:
> >>>I mean listing "regular" events seperate from "training" events, sort of
> >>>like we have news seperate from events now.
> >>
> >>OK, I could understand *that*. ;)
> >>
> >>But *how* do you think they should be split: in display, in submit form,
> >> in admin interface, etc.?
> >
> > Well, I guess the first step is allowing people to designate things
> > differently in the submit form, and then showing that difference in the
> > admin screen. After that we can haggle over how to split the display :-)
>
> OK, so you would like to add a flag to database showing whether the
> event is "training" or "generic", all other fields would be the same.
> You'd like to add a switch to submit form and event editing form in
> admin interface.

yep.

> You don't yet know how it'll look like on website and
> don't volunteer to update the design for this.
>

Well, the easiest thing to do is to just create three separate sections on the
main page... one for news, then one for the "general" events, then one for
the training courses. Each could then carry it's own rss feed too. The idea
is that sometimes our community events get lost in the sea of training
courses, so separating the two should help to distinguish them.

Of course I am open to suggestions if people have an alternative idea they'd
like to implement, but barring a radical change the bits for the database
will need to be done regardless. As I see it we can leave a TODO item for
implementing the interface changes, if you or no one else picks it up I'll
get to it eventually.

--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL