CodeIgnite

[arunkumarchithanar]

There is a folder 'CodeIgnite', an application framework for PHP. I am not sure if it would be required. If it is going to be used, it must be installed on the server. Should all of the code, including the code of CodeIgnite itself, be in the repo?

[ghost]

That's how PHP stuff seems to work from my googling - you "install" the libraries by sticking them in the folder your webserver looks at.

http://codeigniter.com/user_guide/installation/index.html

Some of the code for AGORA appears to be in CodeIgnite\system\application\controllers; for instance, testcontroller.php.

It's clear that the code as written depends on both AMFPHP and CodeIgnite.

[karthikrangarajan]

I am not sure if you're still using the CodeIgniter framework at all. If you are, then you need CodeIgnite. The simplest way to know is if you're changing PHP files inside CodeIgnite/system/application/libraries/amfphp.

[ghost]

Yeah, there's argumentschememodelservice, reasonmodelservice, and the like in there. They're all empty classes, but the files require_once() the corresponding models in CodeIgnite\system\application\models and those do real work- they provide functions which query the SQL database.

[monachitnis]

We can either use all that, or setup something on our own by giving it a try

http://livedocs.adobe.com/flex/3/html/help.html?content=createevents_3.html

This seemed simple enough. Probably invest a day at max in it and if it doesnt work out, revert back to using/understanding codeignite

[karthikrangarajan]

But isn't the custom event creation? It doesn't have much to do with CodeIgniter. If you want, I can explain what happens in the CodeIgniter if we set up a meeting: its really simple, it shouldn't take longer than 30 minutes to understand.

[ghost]

Since we're probably going to end up writing new PHP code to fit with the new database layout and resulting XML schema, there's no real need to keep this "issue" around as we'll be selecting our own framework, if any.