Talk:Computer Science Design Patterns

I haven't found a more logical place to ask this as yet. If this remains unanswered for too long, I'll ask elsewhere because this discussion doesn't look too... active :-)

Could we consider merging the many millions of Design Pattern articles in WikiPedia/Books? Clearly we keep the different Design Patterns seperate, but I see no sense in having an entries in WikiPedia, the C -/-/- Design Pattern book, this Design Patterns book, the Java Design Patterns book, ... you get my point?

Should we not rather focus on fixing a set of design pattern articles in one place (I propose WikiPedia) and link to it from various other places? I see no sense in defining the Template Method Pattern, or more abstractly, Behavioural Patterns, four times (or however many WikiBooks there are on the topic) --The Extremist 13:36, 22 December 2005 (UTC)

Commands
What does it mean to decouple a sender and receiver? --Remi0o 22:24, 13 December 2006 (UTC)

Momento
In the original Gang of Four-Book, it is not called Momento, but Memento. As in MEMory (aka encapsulating state information to be rememberedlater). I'll change that now. -- de:Benutzer:Schmiddtchen 217.186.226.237 14:50, 2 February 2007 (UTC)

Merge request
I've acted on the pending merge request to the C++ Programming book and noticed that some of the content was duplicated, I have extracted all the C++ source examples and since there is still much useful content to RfD or complete a merge of the edit history I will re-tag it as a merge to the Java book (since most of the content may already be present or be useful there). If the request is opposed or after the Java content is removed/merged, please re-tag the remaining to be merged into the Computer Programming... --Panic (discuss • contribs) 07:56, 4 February 2011 (UTC)
 * I searched for the word "Design patterns" and found out that the subject is scattered all over the computer language books, which results in information duplication, making the access to all the knowledge about a design pattern subject at one place impossible. As a matter of fact, design patters can and should be used to implement code in specific languages, but the subject is high level compared to language details. I think that there should be a "software architecture book" with design pattern explained there. The merge place could be at Introduction to Software Engineering/Architecture/Design Patterns or here - that doesn't matter. Sae1962 (discuss • contribs) 11:30, 29 August 2012 (UTC)
 * I do not fully understand the "Wiki-speak", but merging these examples to specific language books would be incorrect. I agree with Sae1962, for this subject, the correct place for the code is under Computer_Science_Design_Patterns/whatever-pattern-name. Then have a link from each relevant language specific book to Computer_Science_Design_Patterns. I understand this would be an exception to the general rule of where examples should be collected, but this is what I would expect, and I believe my peers will expect the same.
 * A second point, when the C++ example was moved to the C++ book was a link created? I cannot find one, it may be just an oversight, but I could not navigate from Visitor pattern to the example I wanted. This is what has made me sign-up as a contributor! -- Rfrankla (discuss • contribs) 12:43, 21 April 2014 (UTC)


 * I see no point in continuing the debate about merging since the work has been reformatted a lot from the source initial proposed for merge in 2011 that it makes no sense in 2014, I would have hoped someone had closed it a long time ago (after 7 days of no opposition a proposal should be considered dead unless someone wishes to pursue the matter further). --Panic (discuss • contribs) 21:23, 16 July 2014 (UTC)

Design Patterns aren't code reuse
The opening sentence says design patterns are "convenient ways of reusing your code". Aren't design patterns design reuse rather than code reuse? Maybe it's better to say design patterns offer general solutions to reoccurring design problems. --EEB 75.87.186.225 (discuss) 19:21, 13 May 2011 (UTC)


 * Done. --Panic (discuss • contribs) 20:53, 13 May 2011 (UTC)

Section title issues on printable and PDF versions
In the print version, section/chapter 16 is titled "Print version". In the PDF version, this is also the case for sections/chapters 4, 6, 10-16, 18, 20, 21, and 23. I'm new to Wikibooks, so unfortunately I don't know how to fix this myself, otherwise I would. --Aardila (discuss • contribs) 12:50, 27 April 2016 (UTC)
 * ✅ [//en.wikibooks.org/w/index.php?title=Computer_Science_Design_Patterns%2FModel%E2%80%93view%E2%80%93controller&type=revision&diff=3075497&oldid=3074753 Fixed here], and then I've reprinted it with PDF Creator and updated [[Media:Computer Science Design Patterns.pdf]]. JackPotte (discuss • contribs) 07:04, 29 April 2016 (UTC)

Change the title
This title is weird. There is no such thing as Computer science design patterns any more than there are Computer science pointers or Computer science closures or Computer science interfaces. The term design pattern isn't a general computer science term, it is a term specific to object-oriented programming. I propose to change the title to Design patterns in object-oriented programming. Rp (discuss • contribs) 13:26, 11 November 2022 (UTC)

The text needs to provide this context, too. This article cannot be understood by a reader who isn't already familiar with design patterns. It should start out by saying which problem they are designed to solve, why they help solve it, who came up with the idea, etcetera. Rp (discuss • contribs) 13:30, 11 November 2022 (UTC)