Yes. SQLLite would be perfect. The config files and class structure allow for this implementation in the future. In fact, I may make this a higher priority to encourage support for both engines by others as well.
If you could document what you had to change, it would help in the case that someone wants to add support for other databases such as PostgreSQL.
Yep. I need to define an API. It will take some time.
> - You do not have any automated tests to confirm the installation or > the logic of your code. This concerns me and would prevent me from > going further with this codebase. I'd be willing to help you get the > Apache::Test framework working and writing some basic tests to get > you started.
I am not familiar with this framework or the benefits it would provide. I am sure that I would enjoy gaining a better understanding of what you had in mind. Examples or a further description would be a great start.
I hope to be building an availability calendar for one of my clients in the next couple of weeks. If I do so, I will send you the code so that you can see the framework I'm using which includes Apache::Test and Module::Build integration.
Great. Look forward to it.
I knew there had to be a reason for multiple sets of config files and templates. To play devil's advocate, you've made installation of a simple e-commerce site twice as difficult because now I have to scrounge around in two different sets of directories which have files that contain different settings and are sometimes in different places (e.g., fmdemo/tmpl vs. flexmart/pgman/tmpl).
Yes, perhaps they could both be in .../tmpl. You are free to use one config file, (either one will work). I would use the flexmart_sys file. You can always defined flexmart_host files later for multiple hosts. Just make sure that flexmart_host.ini exists (even if empty) as I may have put in logic that requires it at least be present. The "demo" is intended to "demonstrate" features; I regret the added inconvenience, but please keep in mind that this release was generated in response to requests. I tried to put together a workable demo.
To folks like myself wanting to quickly test the package, the extra power of being able to configure multiple sites does not overcome the hassle factor. Would it be possible for all the settings to be in one or the other config file and then add support for a master config file as an extra step? My thinking is that if someone needs that capability, they would be willing to make more effort.
Just keep in mind that the "master" config file has some definition "templates" that you probably don't want to change as future releases may assume they mean certain things. You are free to use only one config file, just make sure the other one (even if empty) exists where it is supposed to.
Bill
Regards, William
-- Knowmad Services Inc. http://www.knowmad.com
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
