[geeklog-devtalk] geeklog-devel digest, Vol 1 #360 - 7 msgs

geeklog-devel-request at lists.geeklog.net geeklog-devel-request at lists.geeklog.net
Sat Jul 31 13:00:02 EDT 2004

Previous message: [geeklog-devtalk] geeklog-devel digest, Vol 1 #359 - 2 msgs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Send geeklog-devel mailing list submissions to
geeklog-devel at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.geeklog.net/listinfo/geeklog-devel
or, via email, send a message with subject or body 'help' to
geeklog-devel-request at lists.geeklog.net

You can reach the person managing the list at
geeklog-devel-admin at lists.geeklog.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geeklog-devel digest..."

Today's Topics:

1. Re: GL2 event model (Tony Bibbs)
2. GL2 and Unicode? (Dirk Haun)
3. Is this rocking the boat? (Tony Bibbs)
4. Re: GL2 and Unicode? (Tony Bibbs)
5. Re: GL2 and Unicode? (Dirk Haun)
6. Re: 1.3.10 to do list (Blaine Lang)
7. Re: 1.3.10 to do list (Dirk Haun)

--__--__--

Message: 1
Date: Fri, 30 Jul 2004 15:50:35 -0500
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] GL2 event model
Reply-To: geeklog-devel at lists.geeklog.net

This is a multi-part message in MIME format.
--------------080306060900030108070004
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

To fill in the blanks more I offer up the attached version. Only
difference is I show how the plugins are actually called. Also, we
might want to consider a 'priority' field for events that plugins listen
to. Using priorities would allow plugins to get called in some sort of
priorty fashion. I say that we come up with a standard set of
priorities that plugins can use. This make sense?

--Tony

Vincent Furia wrote:

>Here is what I had envisioned when I penned the Plugin API

>documentation. It is a class that would be instantiated only once by

>GL2 core and available globally. I prefer the per event registration

>as it will reduce the calls the "PluginEventHanlder" will have to make

>to listening plugins.

>

>-Vinny

>

>class PluginEventHandler {

>

> /**

> * Array containing event keys and listener (arrays as) values

> * @access private

> * @var array

> */

> private $listeners = array();

>

> /**

> * PluginEventHandler Constructor

> *

> * @access public

> *

> */

> function __construct() {

> // fetch registered listeners from database, populate $listeners

> }

>

> /**

> * Register a plugin to listen for an event

> *

> * @access public

> * @param mixed $event event(s) to listen for (string or array)

> * @param string $plugin plugin to be registered as listener

> * @return boolean true on success

> *

> */

> function registerListener($event, $plugin) {

> // add the listener to the $listeners variable and the database

> }

>

> /**

> * Unregister a plugin from listening for an event

> *

> * @access public

> * @param mixed $event event(s) to unregister (string or array)

> * @param string $plugin plugin to be unregistered as listener

> * @return boolean true on success

> *

> */

> function unregisterListener($event, $plugin) {

> // remove the listener for the specified events from $listeners

> // and the database.

> }

>

> /**

> * Get all the listeners for a specific event

> *

> * @access public

> * @param string $event event to get listeners of

> * @return array array of listeners to event $event

> *

> */

> function getListeners($event) {

> // remove the listener for the specified events from $listeners

> // and the database.

> }

>

> /**

> * Notify all listeners that an event has occurred

> *

> * @access public

> * @param mixed $event event requiring notification

> * @param mixed $vars event specific variables

> * @param mixed $plugin NOTIFY_ALL, specific plugin, or array of plugins

> * @return mixed event specific return values (or array of)

> *

> */

> function notify($event, $vars, $plugin = NOTIFY_ALL) {

>

> }

>

>}

>

>

>

>On Wed, 21 Jul 2004 22:10:55 +0000, Tom Willett <tomw at pigstye.net> wrote:

>

>

>>Let me get this straight.

>>

>>GL2 Core would make the MySubjectObserverClass

>>

>>$obs = new MySubjectObserverClass;

>>

>>then the plugin would register by somehow getting the reference to the

>>MySubjectOvserverClass and register itself as a listener

>>

>>$obs->addListner($MyPlugin);

>>or

>>$obs->addListener($MyPlugin, $events);

>>etc

>>

>>Then when a event happened GL2 Core or a plugin could notify the plugins

>>

>>$obs->notifyAll($event)

>>

>>Do I have this about right?

>>

>>--

>>Tom Willett

>>tomw at pigstye.net

>>

>>

>>

>>---------- Original Message -----------

>>From: Tony Bibbs <tony at tonybibbs.com>

>>To: geeklog-devel at lists.geeklog.net

>>Sent: Wed, 21 Jul 2004 16:31:57 -0500

>>Subject: [geeklog-devel] GL2 event model

>>

>>

>>

>>>The plugin API for GL2 that Vinny has drafted if surprisingly small

>>>because we are introducing an event based model. Essentially, the GL2

>>>and all plugins have the option to register events that others can

>>>listen to. To implement this I recommend an observer/observable design

>>>pattern similar to the example below. A few things that need

>>>discussion. First, the example below allows listening only at the

>>>object level. The alternative is the force listening at the event level

>>>(in otherwords, addListener would take as a second arg an array of

>>>events the object listens to). Any preference? General questions?:

>>>

>>>class MySubjectObserverClass {

>>> private $listeners = array();

>>> private $listernerNextID = 0;

>>>

>>> // Alternative names: register, subscribe...

>>> public function addListerner(&$obj)

>>> {

>>> $this->_listerners[] =& $obj;

>>> return $this->listernerNextID++;

>>> }

>>>

>>> // Alternative name: unregister, unsubscribe...

>>> public function removeListerner($id,'even't)

>>> {

>>> unset($this->listerners[$id]);

>>> }

>>>

>>> // Alternative name: broadcast...

>>> public function notifyAll($event)

>>> {

>>> foreach ($this->listerners as $id => $obj)

>>> {

>>> $this->listerners[$id]->notify($event, $this);

>>> }

>>> }

>>>

>>> // Alternative name: listen...

>>> function notify($event, &$obj)

>>> {

>>> switch (get_class($obj)) {

>>> case 'blah':

>>> ...

>>> }

>>> }

>>>}

>>>

>>>_______________________________________________

>>>geeklog-devel mailing list

>>>geeklog-devel at lists.geeklog.net

>>>http://lists.geeklog.net/listinfo/geeklog-devel

>>>

>>>

>>------- End of Original Message -------

>>

>>

>>

>>_______________________________________________

>>geeklog-devel mailing list

>>geeklog-devel at lists.geeklog.net

>>http://lists.geeklog.net/listinfo/geeklog-devel

>>

>>

>>

>_______________________________________________

>geeklog-devel mailing list

>geeklog-devel at lists.geeklog.net

>http://lists.geeklog.net/listinfo/geeklog-devel

>

>

--------------080306060900030108070004
Content-Type: application/x-php;
name="aptenoPluginFactory.class.php"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="aptenoPluginFactory.class.php"

PD9QSFAKCmNsYXNzIGFwdGVub0V2ZW50TWFuYWdlciB7CiAgICAvKioKICAgICogQXJyYXkg
Y29udGFpbmluZyBldmVudCBrZXlzIGFuZCBsaXN0ZW5lciAoYXJyYXlzIGFzKSB2YWx1ZXMK
ICAgICogCiAgICAqIFRoaXMgdGFrZXMgdGhlIGZvcm0gb2YgJGxpc3RlbmVyc1s8ZXZlbnRO
YW1lPl0gPSBhcnJheSg8cGx1Z2luTmFtZTE+LCA8cGx1Z2luTmFtZTI+LCBldGMpOwogICAg
KgogICAgKiBAYXV0aG9yIFZpbmNlbnQgRnVyaWEgPHZmdXJpYUBnbWFpbC5jb20+CiAgICAq
IEBhY2Nlc3MgcHJpdmF0ZQogICAgKiBAdmFyIGFycmF5CiAgICAqLwogICAgcHJpdmF0ZSAk
bGlzdGVuZXJzID0gYXJyYXkoKTsKCiAgICAvKioKICAgICogUGx1Z2luRXZlbnRIYW5kbGVy
IENvbnN0cnVjdG9yCiAgICAqCiAgICAqIEBhdXRob3IgVmluY2VudCBGdXJpYSA8dmZ1cmlh
QGdtYWlsLmNvbT4KICAgICogQGFjY2VzcyBwdWJsaWMKICAgICoKICAgICovCiAgICBwdWJs
aWMgZnVuY3Rpb24gX19jb25zdHJ1Y3QoKSAKICAgIHsKICAgICAgICAvLyBmZXRjaCByZWdp
c3RlcmVkIGxpc3RlbmVycyBmcm9tIGRhdGFiYXNlLCBwb3B1bGF0ZSAkbGlzdGVuZXJzCiAg
ICB9CgogICAgLyoqCiAgICAqIFJlZ2lzdGVyIGEgcGx1Z2luIHRvIGxpc3RlbiBmb3IgYW4g
ZXZlbnQKICAgICoKICAgICogQGF1dGhvciBWaW5jZW50IEZ1cmlhIDx2ZnVyaWFAZ21haWwu
Y29tPgogICAgKiBAYWNjZXNzIHB1YmxpYwogICAgKiBAcGFyYW0gIG1peGVkICAgJGV2ZW50
ICBldmVudChzKSB0byBsaXN0ZW4gZm9yIChzdHJpbmcgb3IgYXJyYXkpCiAgICAqIEBwYXJh
bSAgc3RyaW5nICAkcGx1Z2luIHBsdWdpbiB0byBiZSByZWdpc3RlcmVkIGFzIGxpc3RlbmVy
CiAgICAqIEByZXR1cm4gYm9vbGVhbiB0cnVlIG9uIHN1Y2Nlc3MKICAgICoKICAgICovCiAg
ICBwdWJsaWMgZnVuY3Rpb24gcmVnaXN0ZXJMaXN0ZW5lcigkZXZlbnRzLCAkcGx1Z2luKSAK
ICAgIHsKICAgICAgICAvLyBhZGQgdGhlIGxpc3RlbmVyIHRvIHRoZSAkbGlzdGVuZXJzIHZh
cmlhYmxlIGFuZCB0aGUgZGF0YWJhc2UKICAgIH0KCiAgICAvKioKICAgICogVW5yZWdpc3Rl
ciBhIHBsdWdpbiBmcm9tIGxpc3RlbmluZyBmb3IgYW4gZXZlbnQKICAgICoKICAgICogQGF1
dGhvciBWaW5jZW50IEZ1cmlhIDx2ZnVyaWFAZ21haWwuY29tPgogICAgKiBAYWNjZXNzIHB1
YmxpYwogICAgKiBAcGFyYW0gIG1peGVkICAgJGV2ZW50ICBldmVudChzKSB0byB1bnJlZ2lz
dGVyIChzdHJpbmcgb3IgYXJyYXkpCiAgICAqIEBwYXJhbSAgc3RyaW5nICAkcGx1Z2luIHBs
dWdpbiB0byBiZSB1bnJlZ2lzdGVyZWQgYXMgbGlzdGVuZXIKICAgICogQHJldHVybiBib29s
ZWFuIHRydWUgb24gc3VjY2VzcwogICAgKgogICAgKi8KICAgIHB1YmxpYyBmdW5jdGlvbiB1
bnJlZ2lzdGVyTGlzdGVuZXIoJHBsdWdpbiwgJGV2ZW50cyA9ICcnKSAKICAgIHsKICAgICAg
IC8vIHJlbW92ZSB0aGUgbGlzdGVuZXIgZm9yIHRoZSBzcGVjaWZpZWQgZXZlbnRzIGZyb20g
JGxpc3RlbmVycwogICAgICAgLy8gYW5kIHRoZSBkYXRhYmFzZS4gIElmIGV2ZW50cyBpcyBl
bXB0eSB0aGVuIHVucmVnaXN0ZXIgdGhlIHBsdWdpbiAKICAgICAgIC8vIGZvciBhbGwgZXZl
bnRzCiAgICB9CgogICAgLyoqCiAgICAqIEdldCBhbGwgdGhlIGxpc3RlbmVycyBmb3IgYSBz
cGVjaWZpYyBldmVudAogICAgKgogICAgKiBAYXV0aG9yIFZpbmNlbnQgRnVyaWEgPHZmdXJp
YUBnbWFpbC5jb20+CiAgICAqIEBhY2Nlc3MgcHVibGljCiAgICAqIEBwYXJhbSAgc3RyaW5n
ICRldmVudCAgZXZlbnQgdG8gZ2V0IGxpc3RlbmVycyBvZgogICAgKiBAcmV0dXJuIGFycmF5
ICBhcnJheSBvZiBsaXN0ZW5lcnMgdG8gZXZlbnQgJGV2ZW50CiAgICAqCiAgICAqLwogICAg
cHVibGljIGZ1bmN0aW9uIGdldExpc3RlbmVycygkZXZlbnQpIAogICAgewogICAgICAgLy8g
cmVtb3ZlIHRoZSBsaXN0ZW5lciBmb3IgdGhlIHNwZWNpZmllZCBldmVudHMgZnJvbSAkbGlz
dGVuZXJzCiAgICAgICAvLyAgIGFuZCB0aGUgZGF0YWJhc2UuCiAgICB9CgogICAgLyoqCiAg
ICAqIE5vdGlmeSBhbGwgbGlzdGVuZXJzIHRoYXQgYW4gZXZlbnQgaGFzIG9jY3VycmVkCiAg
ICAqCiAgICAqIEBhdXRob3IgVmluY2VudCBGdXJpYSA8dmZ1cmlhQGdtYWlsLmNvbT4KICAg
ICogQGFjY2VzcyBwdWJsaWMKICAgICogQHBhcmFtICBtaXhlZCAkZXZlbnQgIGV2ZW50IHJl
cXVpcmluZyBub3RpZmljYXRpb24KICAgICogQHBhcmFtICBtaXhlZCAkdmFycyAgIGV2ZW50
IHNwZWNpZmljIHZhcmlhYmxlcwogICAgKiBAcGFyYW0gIG1peGVkICRwbHVnaW4gTk9USUZZ
X0FMTCwgc3BlY2lmaWMgcGx1Z2luLCBvciBhcnJheSBvZiBwbHVnaW5zCiAgICAqIEByZXR1
cm4gbWl4ZWQgZXZlbnQgc3BlY2lmaWMgcmV0dXJuIHZhbHVlcyAob3IgYXJyYXkgb2YpCiAg
ICAqCiAgICAqLwogICAgcHVibGljIGZ1bmN0aW9uIG5vdGlmeSgkZXZlbnQsICR2YXJzLCAk
cGx1Z2luID0gTk9USUZZX0FMTCkgCiAgICB7CiAgICAJJHBsdWdpbkFycmF5ID0gJHRoaXMt
Pmxpc3RlbmVyc1skZXZlbnRdOwogICAgCWZvcmVhY2ggKCRwbHVnaW5BcmF5IGFzICRjdXJM
aXN0ZW5lcikgewogICAgCQkkdG1wUGx1Z2luID0gJHRoaXMtPnBsdWdpbkZhY3RvcnkoJGN1
ckxpc3RlbmVyKTsKICAgIAkJJHRtcFBsdWdpbi0+bm90aWZ5KCRldmVudCwgJHZhcnMpOwog
ICAgCX0KICAgIH0KICAgIAogICAgLyoqCiAgICAqIENyZWF0ZXMgYSBwbHVnaW4gYW5kIHJl
dHVybnMgaXQKICAgICogCiAgICAqIEBhdXRob3IgVG9ueSBCaWJicyA8dG9ueUBnZWVrbG9n
Lm5ldD4KICAgICogQGFjY2VzcyBwdWJsaWMKICAgICogQHBhcmFtIHN0cmluZyAkcGx1Z2lu
TmFtZSBOYW1lIG9mIHRoZSBwbHVnaW4gdG8gY3JlYXRlCiAgICAqIEByZXR1cm4gb2JqZWN0
IEFuIGluc3RhbmNlIG9mIHRoZSBnaXZlbiBwbHVnaW4gbmFtZQogICAgKgogICAgKi8KICAg
IHByaXZhdGUgZnVuY3Rpb24gJnBsdWdpbkZhY3RvcnkoJHBsdWdpbk5hbWUpCiAgICB7CiAg
ICAJZ2xvYmFsICRnQ29uZjsKICAgIAkKICAgIAkkZmlsZVRvSW5jbHVkZSA9ICRnQ29uZlsn
cGF0aF9wbHVnaW5zJ10gLiAkcGx1Z2luTmFtZTsKICAgIAkKICAgIAlpZiAoZmlsZV9leGlz
dHMoJGZpbGVUb0luY2x1ZGUpKSB7CiAgICAJCXJlcXVpcmVfb25jZSAkZmlsZVRvSW5jbHVk
ZTsKICAgIAkJdHJ5IHsKICAgIAkJCSRuZXdQbHVnaW4gPSBuZXcgJHBsdWdpbk5hbWUoKTsK
ICAgIAkJCXJldHVybiAkbmV3UGx1Z2luOwogICAgCQl9IGNhdGNoIChHTEJhc2VFeGNlcHRp
b24gJGUpIHsKICAgIAkJCWVjaG8gJGUtPmdldE1lc3NhZ2UoKTsKICAgIAkJCWV4aXQ7CiAg
ICAJCX0KICAgIAl9IGVsc2UgewogICAgCQl0aHJvdyBuZXcgR0xCYWRGaWxlRXhjZXB0aW9u
KCJUaGUgZmlsZSwgJHBsdWdpbk5hbWUsIGRvZXMgbm90IGV4aXN0Iik7CiAgICAJfQogICAg
fQp9Cgo/Pg==
--------------080306060900030108070004--

--__--__--

Message: 2
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Date: Fri, 30 Jul 2004 23:14:23 +0200
Organization: Terra Software Systems
Subject: [geeklog-devel] GL2 and Unicode?
Reply-To: geeklog-devel at lists.geeklog.net

Looking through the existing bugreports for 1.3, I see a few dealing with
problems when using unicode and/or multi-byte character sets. Has any
thought been given to these things for GL2?

bye, Dirk

--
http://www.haun-online.de/
http://mypod.de/

--__--__--

Message: 3
Date: Fri, 30 Jul 2004 16:38:26 -0500
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: [geeklog-devel] Is this rocking the boat?
Reply-To: geeklog-devel at lists.geeklog.net

Ok, I think I sent this link here, but the more I read what I see, the
more I like it. Please take some time to read about Propel:

http://propel.phpdb.org

And read the user guide:

http://propel.phpdb.org/docs/user_guide/

The long and short of it is this. We could implement Data Acces Objects
that our code uses to interact with the database. DAO is a good idea no
matter what DB abstraction layer we use and regardless if we use a tool
like Propel. Essentially it hides the data access specifics from the
developers. Instead developers will call simple methods on the data
access objects and let the DAO layer do the grunt work.

We could essentially use DAO to wrap the use of Propel for data acess.

That said there are some pros and cons:

Pros:
1) Clean API, developers no longer have to write SQL except in really
rare instances.
2) Object oriented...right in line with GL2
3) Database changes are easier, now developers don't have to find all
SQL effected by a database change. We simply change things at the
Propel level (wrapped by DAO), modify our HTML templates and we are off
to the race.

Cons:
1) It is conceptionally more complicated. Requires some ramp up.
2) Uses it's own DB abstraction layer (i.e. you can't use PEAR::DB even
if you wanted to).
3) It's in Beta.

I think this tool could really save a ton of time. Please give this a
gander and try using it against a very simply table and let me know your
thoughts.

--Tony

--__--__--

Message: 4
Date: Fri, 30 Jul 2004 16:42:26 -0500
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] GL2 and Unicode?
Reply-To: geeklog-devel at lists.geeklog.net

None, and I am ignorant on the subject. What are the key issues? I
assume this is related to internationalization, right?

--Tony

Dirk Haun wrote:

>Looking through the existing bugreports for 1.3, I see a few dealing with

>problems when using unicode and/or multi-byte character sets. Has any

>thought been given to these things for GL2?

>

>bye, Dirk

>

>

>

>

--__--__--

Message: 5
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] GL2 and Unicode?
Date: Fri, 30 Jul 2004 23:50:37 +0200
Organization: Terra Software Systems
Reply-To: geeklog-devel at lists.geeklog.net

Tony,

>None, and I am ignorant on the subject.

I'm not exactly an expert either :-/

>What are the key issues? I

>assume this is related to internationalization, right?

The problem is that you need to be careful when doing string manipulation
on multi-byte strings. To quote from <http://www.php.net/mbstring>:

"When you manipulate (trim, split, splice, etc.) strings encoded in a
multibyte encoding, you need to use special functions since two or more
consecutive bytes may represent a single character in such encoding
schemes. Otherwise, if you apply a non-multibyte-aware string function to
the string, it probably fails to detect the beginning or ending of the
multibyte character and ends up with a corrupted garbage string that most
likely loses its original meaning."

bye, Dirk

--
http://www.haun-online.de/
http://geeklog.info/

--__--__--

Message: 6
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] 1.3.10 to do list
Date: Fri, 30 Jul 2004 23:34:13 -0400
Reply-To: geeklog-devel at lists.geeklog.net

I have just submitted to CVS the changes to support the Story Archive
Feature.
I updated the themes, mysql update script and associated docs.

Dirk, I need to add one fix. I have used Javascript to disable the extra
fields in the story editor "Edit" screen if this option is disabled. The
default is for this option to be disabled unless toggled on per story. It's
a nice touch but I may have to disable it or find a quick way to leave these
new fields enabled if JS is disabled in the browser. Just about everyone has
JS enabled don't they :)

This is a topic for another day but maybe we assume JS is enabled for
Admin's and start to use JS to improve the UI.
I'd love to see a nice Tab'ed interface for some of these large admin pages.

If the user has not set the new $_CONF parm - then even if the arvhive
feature is enabled for a story and the expiry time is reached, the story
will not be effected.
$_CONF['archivetopic'] = 'archive'; // Topic ID to Auto-Archived
topics after expire date

Blaine
----- Original Message -----
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Sent: Monday, July 26, 2004 12:57 PM
Subject: Re: [geeklog-devel] 1.3.10 to do list

I would like to add the Story Archive and can do so this week.
- Option to set a date where the story will be moved to a "defined" archive
topic or delete automatically.
- It's also possible to use a new set of template files for the archive
topic

I also have a similar feature for Blocks - where you can set the show until
time then it gets disabled.

Another item I have is a change to the advanced search results. I just need
to complete a bit more testing on that one.
I will aim for this week as well to get that in.

Blaine
----- Original Message -----
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Sent: Monday, July 26, 2004 11:58 AM
Subject: [geeklog-devel] 1.3.10 to do list

Okay, I think I have pretty much implemented everything that I wanted to
go into 1.3.10. Now it's on to the usual stuff (bug fixes, documentation
and language file updates, testing, ...).

Not sure if I'll have a go at the Admin Toolbox we've talked about or
leave it for the next version. I may give it a try if I have a mood swing
or something ...

Then there are a few other open issues:

Inclusion of the SpamX plugin - what's the status here? We probably need
a new plugin API function so that plugins can filter or reject comments
before they will be saved. Also, a method to make it easier to package
plugins with Geeklog would be nice, e.g. by making the install script
read the SQL for the plugin from some predefined directory (if we do
that, it also needs to be able to handle plugin updates).

Vinny, you wanted to do some work on the comment bar. What's the status /
plan here?

PDF: Currently, the PDF-related files all produce XHTML, which is
inconsistent with the rest of Geeklog which produces plain ol' HTML. From
the documentation, the PDF add-on doesn't understand XHTML either (but
only HTML 3.2), so I don't see the need for this. Tony? Anything else
that needs to be done on the PDF support?

A few features have been mentioned in the past as being possibly ready to
go into the next release. Most notably spell checking and archiving of
old stories. Tony, Blaine - any updates?

Anything else?

bye, Dirk

--
http://www.haun-online.de/
http://www.tinyweb.de/

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel

--__--__--

Message: 7
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] 1.3.10 to do list
Date: Sat, 31 Jul 2004 10:57:27 +0200
Organization: Terra Software Systems
Reply-To: geeklog-devel at lists.geeklog.net

Blaine,

>I have just submitted to CVS the changes to support the Story Archive

>Feature.

Nice work. A couple of comments:

I'm not happy with the $_CONF['archivetopic'] variable. Topic IDs should
be kept out of the config.php, IMO. I can think of 2 better ways to do this:

1) Add an "Archive" flag to the topics table, similar to the default
topic flag.

2) Even more flexible: Add the archive topic id to the story table, so
that stories can be archived in different topics.

I'm open to other ideas, but please keep the topic ID out of config.php.

The user interface for that option is a bit clumsy. First you have to
enable archiving and then you have to select whether you want Auto
Archive or Auto Delete. I would assume that Auto Archive is the option
you'll want in most cases, so could you make that one selected
automatically when enabling the option?

>I have used Javascript to disable the extra

>fields in the story editor "Edit" screen if this option is disabled. The

>default is for this option to be disabled unless toggled on per story. It's

>a nice touch but I may have to disable it or find a quick way to leave these

>new fields enabled if JS is disabled in the browser. Just about everyone has

>JS enabled don't they :)

Thanks to Mozilla's fine-grained Javascript options, I do have Javascript
enabled most of the time. But I do use Lynx on occasion ...

>This is a topic for another day but maybe we assume JS is enabled for

>Admin's and start to use JS to improve the UI.

>I'd love to see a nice Tab'ed interface for some of these large admin pages.

I not opposed to using Javascript to make things easier / more
comfortable, but every option should also be available without Javascript.

bye, Dirk

--
http://www.haun-online.de/
http://geeklog.info/

--__--__--

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel

End of geeklog-devel Digest

Previous message: [geeklog-devtalk] geeklog-devel digest, Vol 1 #359 - 2 msgs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the geeklog-devtalk mailing list