Re: PGDN test demo

Josh,

Thank you for your functional requirements.
I have added a topic for this.

The experimentation continues as I hack more
into Druple core.

Almost all of the requirements that
you have mentioned are possible. The ones that are not can be developed
because of the great extensibility Drupal provides.

Regards,
Gevik.

> -----Original Message-----
> From: pgsql-www-owner(at)postgresql(dot)org [mailto:pgsql-www-
> owner(at)postgresql(dot)org] On Behalf Of Josh Berkus
> Sent: Thursday, June 23, 2005 8:18 PM
> To: Gevik babakhani
> Cc: 'Magnus Hagander'; 'Dave Page'; 'Rod Taylor'; 'Robert Treat'; 'Marc G.
> Fournier'; 'Devrim GUNDUZ'; pgsql-www(at)postgresql(dot)org
> Subject: Re: [pgsql-www] PGDN test demo
>
> Gevik,
>
> OK, I poked around a bit. However, here's what I'd see as "requirements".
> These things don't need to be implemented immediately, but they need to be
> *possible* on the chosen platform.
>
> In other words, Drupal is fine with me. The project which gets done is
> 100%
> better than the project which doesn't get done.
>
> Also, not everyone will agree with me, so there will be discussion.
>
> Viewing:
> a) all pages need to be bookmarkable
> b) you'll need to work on the formatting, but I'm sure you knew that
> c) each article needs to support multiple categories -- for example, Joy
> of
> Index should appear under:
> Performance
> Indexing
> Joy of Index
> and:
> Database Objects
> Tables
> Views
> Indexes
> Joy of Index
> (although really Joy needs to be overhauled and revised)
> d) You'll need to support articles which are links to articles on external
> sites. For example, I'd love to index GeneralBits using PGDN, but Elein
> is
> unlikely to permit copying.
> e) We need to make sure that this gets included in the various text search
> engines.
> f) Stories need to have their submission dates, authors, and last revision
> dates prominently displayed. Stories over 2 years old should
> automatically
> get flagged as "Old" so that users don't accidentally take advice
> appropriate
> to PostgreSQL 7.1 but not currently.
>
> Editing:
>
> g) needs to support uploading of files
>
> h) I couldn't figure out how to edit an existing story.
>
> i) needs to support specific permissions: writer, editor, admin
>
> j) should be possible to set a story to be either editable by all writers
> and
> editors, or by the author and admin only (this is needed for licensed
> content).
>
> k) can you plug in one of the many WYSWYG editors available? As an option
> for
> people who don't want to mark things up? A gui editor will also be *very*
> useful for re-formatting the existing body of articles.
>
> l) see note about multiple categories above.
>
> m) the main edit view (http://pgdn.truesoftware.net/?q=) needs to have
> some
> filterablity, and not display all stories by default.
>
>
>
> --
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match