StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POBuilder pattern. Expansion interface
primarykey
Id
11385298
data
AcceptedAnswerId
11390012
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-08T17:49:53.927
FavoriteCount
0
LastActivityDate
2012-07-09T07:50:59.127
LastEditDate
2012-07-09T05:49:16.093
LastEditorUserId
1509255
OwnerUserId
1509255
ParentId
0
PostTypeId
1
Score
0
ViewCount
274
LastEditorDisplayName
text
Body
I have builder: <pre><code>public abstract class ScriptBuilder { public void buildScript() { this.commandList = Lists.newArrayList(); } public abstract void buildSleepCommand(long time); public abstract void buildSynchronizationCommand(); public abstract void buildTouchDownCommand(TouchPoint touchPoint); public abstract void buildTouchUpCommand(); public List<String> getScript() { return commandList; } } </code></pre> Implementation: <pre><code>public class StandardScriptBuilder extends ScriptBuilder{ … } </code></pre> I need to construct a new builder, which implements the new interface. This new interface is based on the interface ScriptBuilder: <pre><code>class NewScriptBuilder extends StandardScriptBuilder{ public void buildNewCommand(TouchPoint startTouchPoint, TouchPoint endTouchPoint) { buildTouchDownCommand(startTouchPoint); buildSynchronizationCommand(); buildTouchDownCommand(endTouchPoint); } … } </code></pre> Is there any pattern that will extend the existing builder interface and keep builder advantage? I mean, if we extend the interface, we can not do: <pre><code>ScriptBuilder builder = new NewScriptBuilder(); … builder.buildNewCommand; </code></pre> If there is no solution, it is normal to use?: <pre><code>((NewScriptBuilder)builder).buildNewCommand; </code></pre> Thx. <hr> I mean: For example, we can use Decorator pattern: <pre><code>public abstract class Decorator extends ScriptBuilder {...} ... public class OahDecorator extends Decorator { ... public void buildNewCommand() { ... } } </code></pre> it is a normal organization of code, or choose a different pattern is? task - adding new methods in builder.
Tags
<java><design-patterns><builder>
Title
Builder pattern. Expansion interface
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAleksandr
UserOwnerUserId
1. USAleksandr
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.