> Perhaps a dedicated table _might_ be better for that, > especially if a > specialized interface can be provided, but for both early phases of > development of a complex plug in or simple "quick and dirty" > extensions used on a single site the config page part is a perfect > match.
Yes, but I thought we were talking about the problem that using a config page part is too complicated and error-prone for an end user. If it's meant for a developer to change, hard code it, and tell developers to change it if they need to. If it's meant for an end user to change, go the extra mile and give them a proper interface to change it. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
