builder

What is the best practice for using Builder pattern in "deep" object hierarchies? To elaborate, I explored the idea of applying the Builder pattern as proposed by Joshua Bloch, to my XML binding code (I am using SimpleXML but this question would apply to any case). My object hierarchy is 4 levels deep, with various degree of complexity. By that, I mean, in some levels I have just a couple of properties for my objects, whereas at some other levels I have up to 10. So consider this hypothetical example (I am leaving out the Simple XML annotations for brevity) public class Outermost { private

I would like to see how is Builder pattern used in real world applications/APIs. The examples I found are all pizzas, cakes, cars et cetera (plus the parser example from the GoF book). Could you please tell me about some usages of this patten in real-world applications/APIs, preferably from the world of C++, .NET or PHP (as those are the languages I'm familiar with). Thanks. Update: I recently came across an even better example (imo). Checkout the JobBuilder and TriggerBuilder implementations in the Quartz scheduler package: http://quartz-scheduler.org/api/2.1.5/ Also, when I have time, just

I have two fields i need to increment the character limit on. I're read through the documentation and to my surprise i found no option for it. Is it possible to do? If not, how should i go about solving this? I could drop the column and re-create it with the correct properties, but i don't want to loose any data in the database. Use Raw Queries : /** * Make changes to the database. * * @return void */ public function up() { DB::query('ALTER TABLE mytable MODIFY mycolumn VARCHAR(new-length)'); } /** * Revert the changes to the database. * * @return void */ public function down() { DB::query(

I want to convert my app to a Universal app. Can anyone recommend some good tutorials for achieving this? I need to have each View in Interface Builder as a separate, view for iPhone or iPad. Thanks in advance! I just did this mostly manually, using approximately the following steps: Load the app's main window xib in Interface Builder, use the IB menu "Create iPad Version" to convert it to an iPad version, and save it under an appropriate name (a "-iPad.xib" suffix is common.) In Xcode, add this new .xib file to your project and include it in the app's target. Modify the app's Info.plist to

I'm creating a series of builders to clean up the syntax which creates domain classes for my mocks as part of improving our overall unit tests. My builders essentially populate a domain class (such as a Schedule ) with some values determined by invoking the appropriate WithXXX and chaining them together. I've encountered some commonality amongst my builders and I want to abstract that away into a base class to increase code reuse. Unfortunately what I end up with looks like: public abstract class BaseBuilder<T,BLDR> where BLDR : BaseBuilder<T,BLDR> where T : new() { public abstract T Build();