On Feb 26, 2:27 pm, "David Whiterod" <[EMAIL PROTECTED]> wrote: > > Some config screens will be made redundant by the new feature set in > > 4.0 -- for example, file and image config > > I can still see a big role for configs. (esp. if plugin libraries use > them also - e.g. storing the Google Map's key in the plugin's config > file rather than storing within code).
The problem is you need to have a different API key depending on your URL. This is difficult to manage between dev, stage and production environments if there is only one entry in the database. The key is fixed for any specific URL so its not something that is going to ever change once set. So a code based config that can be versioned and served differently depending on the servername seems best to me. But heh that's just me. > I am still thinking about a better UI for configs > (i.e.http://bugs.farcrycms.org:8080/browse/FC-643). > > Can formtools offer some functionality here? Are FTs designed to > replace some of the webskin functionality? Can (or should) FTs be used > to just generate an custom form interface (not tied to a FC type)? Basically any form interface that fronts a content type should probably use formtools. So yeah, there is definitely hope for replacing config imnterfaces with form tool interfaces... just never made the cut for 4.0. Maybe 4.1. > p.s. Looking forward to WebDU! Going to be a good year i think :) -- geoff http://www.daemon.com.au/ PS. See you *all* at webDU I hope: http://www.webdu.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
