This topic is locked
[SOLVED]

 Multiple Small Projects instead of One Large One?

6/15/2011 4:11:05 PM
PHPRunner General questions
bbarker author

A long time ago, someone mentioned that they had divided their PHPR project into two or three smaller projects. And each project only focused on a small part of the overall website.
Example: One project just delivered REPORTS.

Another one contained the Add/Edit screens.
The reasoning for this was to keep the projects smaller, so that when you make a small modification, you didn't have to rebuild the entire project (with hundreds of files) and run the risk of errors being created.
One example of this, is occasionally when I rebuild a project, one of my pages drops a </td> sign and then my tables get all messed up. Sometimes it takes me an hour or so to clean it up.
Or when I modify a Field Order, it messes up Four reports, not just the one that I was trying to fix.
So, my question is:


  1. Is anyone else building their sites as multiple projects?

    and
  2. Is this a reasonable thing to do? (assuming that you can keep the navigation straight)

Sergey Kornilov admin 6/15/2011

PHPRunner 5.3 is able to perform a partial rebuild.
I'm afraid you are dealing with something that is not related to project size. Having multiple projects will multiply the number of issues you having. Besides that having multiple projects will produce the larger number of PHP files.

bbarker author 6/16/2011



PHPRunner 5.3 is able to perform a partial rebuild.


Thanks. Maybe I'm missing the benefit of the current partial rebuild.
I have a project with approximately 450 files. If I make ONE TINY CHANGE, and then do a "partial rebuild" it rebuilds approximately 385 files.
So I don't understand the value of that.

  1. What files does it NOT rebuild? And WHEN "specifically" should I prompt for a FULL Rebuild?
  2. Isn't there an easier way to rebuild only a single file if just ONE HTML file is modified (for example)?

Sergey Kornilov admin 6/16/2011

If your change affects multiple files all of them will be rebuilt. If you need details send us your project and explain what exactly you change.
There are some common files that will be rebuilt every time (about 50 of them). If you modify one or two files in Visual Editor partial rebuild should affect 51 or 52 files.
You should do a full rebuild before uploading your application to production web server. For local testing partial rebuild is good enough.

bbarker author 6/17/2011

Thanks Sergey. I'm sure that there's good reasons for all of this.
I really don't care how many files are rebuilt as long as they don't mess up. <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=reply&id=58887&image=1&table=forumreplies' class='bbc_emoticon' alt=':lol:' />
But I'd sure like to figure out how to prevent my html files from being "modified" when I make a change to FIELD ORDER, or adding an additional FIELD. Sometimes the "collateral" damage is very frustrating (and unexpected). Maybe there's a new feature that could be added. A popup warning that describes the downstream changes that will be made.
Chow!

Sergey Kornilov admin 6/17/2011

Cannot tell much without seeing specifics. If you need help - send us your files and show what you doing and what results you getting etc.

N
nti 6/20/2011

Breaking up LARGE project with many tables into smaller projects.
Main project in main directory and additional sub-projects in sub-folders under main directory.
Is there a script or help file for login to sub-projects if currently logged into Main Project.
If we had this login solution, we can break up our LARGE projects into smaller projects.
What about it Sergy, is there a script available or method to login to sub-projects from Main Project?
Many of us are in need of script or method except those that already have the method... which I would hope would share on this post.
It would seem reasonable that if all sub-projects maintain same project name and security settings: that session cookie would work.?
Cheers,