> There can always be changes that break something, but it's not a good > idea to put something as complex and unfinished as this into a > component as crucial and complex as the app_server. > While trunk might be broken from time to time, and even unusable, we > should always try to not commit something as complex and unfinished > that affects just everyone. > For this patch, it's a lot of work to get it right. > > I'm not sure if Christof or Hong are reading this list - I'll write a > mail to haiku-development explaining the situation, and what has to be > done. > > Bye, > Axel. > > > I have tried the Stack and Tile patch off and on for a few months now, and after a month or so it get broken since trunk and the app server and constantly moving forward and getting changes. Hopefully having it in the tree even if just on a branch will help to keep it updated and in sync with changes make to trunk. It's unfortunate that it isn't self contained, but I don't know that with it needing to touch so many different files that it could have been done in a way to be self contained. Perhaps having it parallel to trunk now, changes can more easily be made that can help move it towards being self-contained, such as moving general parts over to trunk that aren't 100% for stack and tile, but are useful in general. I haven't studied the code, but did noticed that it touched on lots of files and seemed to be scattered a bit. Can we get a special nightly build set up that can build in the stack and tile branch so that it can still continue to get user testing to report bugs? -scottmc