-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scott Penrose schrieb: | | On 23/06/2005, at 1:24, Tom Schindl wrote: | |> -----BEGIN PGP SIGNED MESSAGE----- |> Hash: SHA1 |> |> Scott Penrose schrieb: |> | Hey Tom |> | |> | I got TomKit going today |> | |> | http://new.linux.dd.com.au/early/index.xml |> | |> | Just starting to work through modules and what is required and how |> then |> | to help contribute to what else needs migrating to the new version |> and |> | what works as is. |> | |> |> Bugs can now be filed using the following URL: |> http://phpot.bestsolution.at/mantis/main_page.php | | | Hi Tom | | I am happy to report bugs for you if you would like, but only as a very | short term solution. I was wondering rather if this is planned to | become more public - ala AxKit2. Because then we could contribute to it | knowing it was going forward into a new version. | | To be blunt, I have lots of time to start working on this to work into | my project and a large number of providers and other modules I want to | release - but I can not afford to put any time into this if it does not | become the axkit replacement.
This can be only said by the dev-Team. I'm not the one who can grant you that this will be AxKit2. I already said that I(my company) would contribute the code to the AxKit-codebase but if none of the developers take a look and say "Yes this is the way we want to go" then I refuse to contribute the code and make my own CPAN release. When it comes to writting providers I'd say that you could write them maybe to work in TomKit and AxKit1 if you use the following pattern: MyAxKit::Provider (implements AxKit1-Provider-Interface) MyTomKit::Provider (implements TomKit-Provider-Interface) MyTomKitAxKit::Provider (the real code generating the XML passed on) What I'm trying to say is that if you don't insert you buisness logic directly into the Provider-code but instead but it in some other module you are free to use it in any provider. In TomKit a haven't even to do that (but you should because Caching is much more simple then) and your provider can also be a simple PerlResponseHandler, that's one of the great things about TomKit that you can use any PerlModule e.g. downloaded from CPAN to be you Provider without writting any wrapper for it. One more thing to add. Maybe when I have time I'll write a wrapper which can be used to directly run AxKit-Processor in TomKit but I really had no time to do so far. You could simply add a feature-request in the bugtracking system. | | I know this is a bit of a vicious circle, since to get it released you | probably need more work etc. so please tell me if there is some way I | can help in the short term get it more public and in the long term help | make it real. | | Thanks | | Scott -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCunHOkVPeOFLgZFIRArjcAJ4xEUviaPlSlIFa8hPJZEgHpBorkACglWiL RAC31UrDUv9UNbxS5Oe80V0= =zGrT -----END PGP SIGNATURE-----
