Geeklog - Geeklog 2 To-Do List

Geeklog 2 To-Do List

Wednesday, July 14 2004 @ 12:38 PM EDT
Contributed by: Tony
Views: 11,215

As promised, here is a high level to-do list for Geeklog 2

Implement Item-level Security. An 'item' is an abstract concept in GL2. Most modules will manage their own special kind of items (forum posts, pictures, etc). The security for managing access to them, however, should be the same and should not require plugin developers to do anything special. That way they can focus on innovation
Implement Plugin API. This has already be started by Vinny and we need to throw a real world example at the API to determine how effective it is.
Implement Libraries. Geeklog will come with a number of stock libraries for doing a number of things (image manipulation, HTML widgets, Web Services, etc). We need identify the the libraries to include by default and get started on them
Formulate layout game plan. A big gripe with Geeklog users is most Geeklog sites look the same. Sure, they have different colors, logos, etc but in general terms they look the same. We need to come up with a way to break the mold and allow theme developers to really get creative
Implement plugins. Geeklog must ship with, at a minimum, the plugins needed to provide the same functionality as the core Geeklog 1.3.x system.
Implement Geeklog Channel. PEAR has recently developed support for channels (in their CVS currently). This will allow plugins to be browsed, installed, removed and include dependency handling out of the box. Best part is all this can be done from within a Geeklog installation (no more needs for wandering aimlessly on www.geeklog.net looking for new features)
Formulate upgrade path from latest 1.3.x to GL2.

I'm sure I'm missing a few things but that is a lot of the big items. As you can see there is a lot of work to be done so if you want to be a part of the team and have a chance to get involved from the ground on up then now is a great time.

Geeklog 2 To-Do List | 10 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

Authored by: wooge on Thursday, July 15 2004 @ 03:08 PM EDT

if you are looking for insight comments or ideas concerning the themeing
schema - drop me a line - or i can post on the forums somewhere...

Authored by: destr0yr on Thursday, July 15 2004 @ 07:40 PM EDT

themeable to the degree and sexyness of css Zen Garden. :)

---
-- destr0yr - "People like you are the reason people like me need medication."

Authored by: Tony on Saturday, July 17 2004 @ 02:08 AM EDT

wooge, again, speak now or forever hold your peace.

---
The reason people blame things on previous generations is that there's only one other choice.

Themes and plugins

Authored by: Euan on Saturday, July 17 2004 @ 11:20 AM EDT

Wishes:

1) Obvious but, nothing hard coded. not even a single little <b>
anywhere.
2) Everything able to be disabled. This will happen anyway as everything will
be a plugin I guess.
3) Menus need to be flexible - one of the binds with theming at present is
that you have to recode your own menus and blocks if you want to get away
from the menu-bar look.
4) To get some of the freakier effects in CSSZenGarden, they have different
classes set for each paragraph/article. The ability to set different classes/
styles per article would be interesting (this should be in the article plugin list I
guess).

Cheers,

Euan.

Authored by: vinny on Sunday, July 18 2004 @ 12:05 AM EDT

Just wanted to add a few things to the TODO list. Some of these issues overlap with what Tony has already said, but hey, they're probably worth repeating anyway:

1. Create the top-level Item class (item.class.php). We should decide how many properties/functions we want to share among all items.

2. Finalize the architecture of Geeklog2 and get all the low level basics implemented. Especially important here is how the MVCnPHP will be used. With just one index page under the web-tree? Will that be where session info, A&A, translations stuff, etc is initiated. What is the layout? And please, please change the what is currently Geeklog.class.php to Logging.class.php or something else. We should try to keep class names relevant.

3. Put together a list of things that should be implemented as libraries (A&A, Sessions, Translation) and list of things that should be implemented as plugins. Decide where in the development process these should be implemented. Other things that might be better to implement as libraries than plugins: image processing, spellcheck, smilies...

-Vinny

Authored by: Remdotc on Friday, July 23 2004 @ 10:39 AM EDT

My Thoughts..

Templating Scheme

The current template scheme isnt really flexable. Example, everyone unless they edit the lib-common.php is stuck using style.css.

This is just one example of how large chunks of HTML are stuck in core files. Thats part of the problem

My suggestion is this:
For each function call. (GetNews, ReadStory) what ever, have each tag call a template
Readmore tag = Somehtmlcode

For each File section, I would add an extensive configurion that allows for custom css file per section, custom header, footer, or blocks ectra

I would also allow, Several different template models.
1. Current Style (dnymaic block assignment via array)
2. Static Code assignment
3. Mixed mode

Static mode would meen, If someone wanted to just and use one file for header, footer functions, they could.

3. Mixed mode. Really touched on more up above, You could assign page 1, template 1. page 2 template 2 so on and so forth

Finally could we have some core features added?

Banning By referer type , IP address , or user name
Automatic, or Manual Approval of New users

File Management, Gallery Block, and Memos, should be core plugins

Thanks for hearing me out.

Authored by: Dirk on Friday, July 23 2004 @ 02:43 PM EDT

The current template scheme isnt really flexable.
Agreed. And GL2 will use a different template engine.

Example, everyone unless they edit the lib-common.php is stuck using style.css. This is just one example of how large chunks of HTML are stuck in core files. Thats part of the problem
That's actually a bad example. You're free to use any CSS file name you prefer - simply don't use the {css_url} variable in header.thtml.

Also, there aren't really any large chunks of HTML left in Geeklog's core code (although I have to agree that the ones that are left can be a hinderance for creative use of templates), but it's next to impossible to get rid of them with the current design (without adding dozens of tiny template files for each of them).
GL2, as has been stated elsewhere, will provide a much better and stricter separation of layout and content anyway.

bye, Dirk

Authored by: Remdotc on Friday, July 23 2004 @ 03:08 PM EDT

Just suggestions, geeklog 1.39 was a nice improvement. While I am awareit would be sickening to try pulling every ounce of html code from functions, it would be cool if GL2 had something like template.functions.thml as part of the layout

then something like one file that contained

functionX = somehtml
functionY = someotherhtml

Simular to the current language layout. you woulc call someFunctionOutput.X and in then lay it out someplace else.

Authored by: Tony on Tuesday, August 10 2004 @ 11:29 AM EDT

Specifically we will be using PEAR::HTML_Template_Flexy or Flexy for short.

---
The reason people blame things on previous generations is that there's only one other choice.

Authored by: maximusrex on Wednesday, July 28 2004 @ 01:36 PM EDT

Well, to avoid a long repost, look in the comments for the following story:

http://www.geeklog.net/article.php/20040712142246310#comments

For the comment:

A request for theme and layout.
Authored by: maximusrex on Wednesday, July 21 2004 @ 12:39 PM EDT

Resources

Sections

User Functions

What's New

STORIES

COMMENTS last 2 days

TRACKBACKS last 2 days

NEW FILES last 14 days

LINKS last 2 weeks

Older Stories

Monday 17-Mar

Tuesday 08-Jan

Saturday 29-Dec

Tuesday 04-Dec

Sunday 04-Nov

Geeklog 2 To-Do List

What's Related

Story Options