Extending phpScheduleIt (2.2.2)

[TheoretixSoftwareSolution]

Hi all,
bit of a newb here..
I have been working to do some customization to phpscheduleit for a client of mine. I am wondering how we handle changing the code w/o embedding it so deep that we cannot upgrade?

ex: I've created buttons to filter based on "offline"/"online"  for the end point http://example.com/schedule/Web/admin/manage_reservations.php

It required updates to Pages/ManageResources.php ,  lib/Database/Command/Queries.php ,  Domain/Access/ResourceRepository.php ... etc.

When it comes time to upgrade to 2.3 how will those changes be kept?

[Nick]

The short answer is that the changes won't make it through an upgrade. You'll need to reapply them manually.

I am trying to make the app as pluggable as possible, though. If you have areas where you think an extension point would be valuable I'd love to hear about it.

[TheoretixSoftwareSolution]

Has there been any thought to making it more of a library/Framework than a full on system? So one could instead use the pieces in our own pages.. Then to make our own bits we just extend the library or something like that.. Kind like how I can extend pieces of Zend Framework and still just go into the lib and do svn up and more or less end up with a functioning system.  I'll think through a way to do something in between to get extensibility into the project.

[Nick]

It's a difficult balance to achieve. What would be the top 3 components that you'd want extracted into reusable pieces?

[TheoretixSoftwareSolution]

Hey Nick,
Sorry, I got lost in the code..
I've since been going deep into phpschedule it. I've basically been adding a "Location" to all bookings. So a reservation will be made by a user of a resource and it will be utilised at a location.
Ex: John(user) will book the Garbage Cleanup Crew (resource) at the Rock Concert Site (location). I'm probably about 80% done.

As for what re-usable bits am i thinking; I'm not too sure at this point. Pieces I've modified that will be broken by upgrade include the additional translations, and a bunch of sql bits
lib/Database/Commands/Queries.php <--- get locations etc queries
lib/Database/Commands/Commands.php
lib/Database/Commands/ColumnNames.php <--- location column names
lib/Database/Commands/ParameterNames.php

also some cleaning up stuff could be done, like Namespaces, one class/interface per file...

It could be written as a ZF2 module and just use ZF's pieces like Views, Db_table adapters, ZendX_Jquery etc.

Would also love to see this hosted as a github project so others can freely contribute to it, fork etc...

Lots of thoughts, I know there isnt enough time in the day for even 1/2 of it.

Thanks for what you've written thus far.

[luciobolton]

Hello.....I am also a newbie like you and learning php for several days..Hope will get lots of help from the forum friends..