A couple of notes:
I would first try to build a bare bones project with the Zend_Tool
command line in 1.10 just to see what a project would look like, the
names that are expected by default, and where things generally go. Once
you do that, you might get a better feel for the kind of changes you'd
like to make to you older project to bring it up to current standards
and expectations.
I'd perhaps move the library folder down next to application/ (not
inside), and ensure that this path is in the include_path. This can be
added in the index.php, but a better place might be inside the
application.ini file so that your controllers & models if they are
called from outside scripts, those scripts dont have to setup the
include_path on their own, they can just use the Zend_Application to
bootstrap the environment.
1). Where i usually stored the models in /application/models, am i correct
in thinking that i now need to rewrite the class definition to include the
namespace, for eg /application/models/menu/site.php would need a class name
of MyApp_Model_Menu_Site?
By Default, you'll see names like Application_Model_Menu_Site, and for
modules ModuleName_Model_Menu_Site.
2). I have another library of code located at /application/library/myRepo.
The example class name in question #1 uses a class from this library
location, yet (the current implementation of) Menu_Site_MainMenu extends
MyRepo_Menu_Abstract is not working (fatal error - class not found). Do i
need to create a seperate namespace for each library included? If so, why is
there not one declared for the zf?
This needs to simply be added to your applicaiton.ini file, something
like this:
includePaths.library = APPLICATION_PATH "/../library"
Hope that gets you started,
Ralph
