All logs
From APIDesign
Combined display of all available logs of APIDesign. You can narrow down the view by selecting a log type, the user name, or the affected page.
View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500)
- 05:54, 14 June 2008 Apidesign (Talk | contribs) marked r878 of Types Of Modular Design patrolled (automatic)
- 05:54, 14 June 2008 Apidesign (Talk | contribs) marked r877 of Use Modular Architecture patrolled (automatic)
- 05:53, 14 June 2008 Apidesign (Talk | contribs) APIDesignPatterns:ResponseReply moved to APIDesignPatterns:RequestResponse
- 05:53, 14 June 2008 Apidesign (Talk | contribs) marked r874 of Code Against Interfaces, Not Implementations patrolled (automatic)
- 05:51, 14 June 2008 Apidesign (Talk | contribs) marked r873 of Reviewers:PartII patrolled (automatic)
- 05:51, 14 June 2008 Apidesign (Talk | contribs) deleted "Getting Ready for Growing Parameters" (Author request: content before blanking was: ''''Done: f1d73f9490a0''' The <tt>Request/Response</tt> example has a few superfluous usages of <tt>this</tt>. Or perhaps you prefer to prefix all field references with <tt>this</tt> -- that's fine, but it sho)
- 05:51, 14 June 2008 Apidesign (Talk | contribs) deleted "Are Abstract Classes Useful?" (Author request: content before blanking was: ''''Done: a578de6e7ceb''' agreed but not in such strong way Static factory methods can be put into a separate noninstantiable class: public interface Tweeter { void tweet(); } public class Tweeters { )
- 05:51, 14 June 2008 Apidesign (Talk | contribs) deleted "A Method Addition Lover's Heaven" (Author request: content before blanking was: ''''Done: 24bf47daa023''' The "public final class InstanceProvider" does not make sense as written. The whole point of InstanceProvider is that it is something that has to be implemented, as well as called. If)
- 05:51, 14 June 2008 Apidesign (Talk | contribs) deleted "Comparing Java Interfaces and Classes" (Author request: content before blanking was: ''''Done: cd866eaf3b80''' - I've explained something but not all the details. Still you need to know at least a bit of knowledge how the VM stores the objects, or you need to trust me that I know. Your compari)
- 05:51, 14 June 2008 Apidesign (Talk | contribs) deleted "Adding a Method or a Field" (Author request: content before blanking was: ''''Done: e368fc1dbe72''' The sentence "Imagine that NetBeans had used a different signature for the aforementioned method..." is a bit hard to read, mostly because of "different". Instead, consider something )
- 05:51, 14 June 2008 Apidesign (Talk | contribs) marked r872 of Talk:Code Against Interfaces, Not Implementations patrolled (automatic)
- 05:50, 14 June 2008 Apidesign (Talk | contribs) marked r871 of Getting Ready for Growing Parameters patrolled (automatic)
- 05:50, 14 June 2008 Apidesign (Talk | contribs) marked r870 of Are Abstract Classes Useful? patrolled (automatic)
- 05:50, 14 June 2008 Apidesign (Talk | contribs) marked r869 of A Method Addition Lover's Heaven patrolled (automatic)
- 05:50, 14 June 2008 Apidesign (Talk | contribs) marked r868 of Comparing Java Interfaces and Classes patrolled (automatic)
- 05:49, 14 June 2008 Apidesign (Talk | contribs) marked r867 of Adding a Method or a Field patrolled (automatic)
- 05:49, 14 June 2008 Apidesign (Talk | contribs) marked r866 of Code Against Interfaces, Not Implementations patrolled (automatic)
- 05:48, 14 June 2008 Apidesign (Talk | contribs) marked r865 of Do Not Expose More Than You Want patrolled (automatic)
- 05:47, 14 June 2008 Apidesign (Talk | contribs) marked r864 of Reviewers:PartII patrolled (automatic)
- 05:46, 14 June 2008 Apidesign (Talk | contribs) marked r863 of Talk:Do Not Expose More Than You Want patrolled (automatic)
- 05:46, 14 June 2008 Apidesign (Talk | contribs) deleted "Do Not Expose Deep Hierarchies" (Author request: content before blanking was: ' # Page 85: I really liked the examples about design flaws in Swing. I like that you're teaching people how to design APIs by pointing out both the right way and the wrong way of doing it, particularly when t)
- 05:46, 14 June 2008 Apidesign (Talk | contribs) marked r862 of Do Not Expose Deep Hierarchies patrolled (automatic)
- 05:46, 14 June 2008 Apidesign (Talk | contribs) deleted "Give the Creator of an Object More Rights" (Author request: content before blanking was: ''''Fixed a bit as 8577a4d13185''' First paragraph: SmallTalk should be Smalltalk. The <tt>Executor</tt> and <tt>Configuration</tt> example: either <tt>Configuration</tt> is a public API class (wrong since i)
- 05:46, 14 June 2008 Apidesign (Talk | contribs) marked r861 of Give the Creator of an Object More Rights patrolled (automatic)
- 05:45, 14 June 2008 Apidesign (Talk | contribs) deleted "Allow Access Only From Friend Code" (Author request: content before blanking was: ''''Fixed: fd5ed0a24e62''' Slightly bad coding style in the accessor example: public final class Item { ... public void setValue(int x) { It is customary to name setter pararameters after the name)
- 05:45, 14 June 2008 Apidesign (Talk | contribs) marked r860 of Allow Access Only From Friend Code patrolled (automatic)
- 05:45, 14 June 2008 Apidesign (Talk | contribs) deleted "Do Not Put Setters Where They Do Not Belong" (Author request: content before blanking was: ''''Fixed: 884544ab39ec''' This section communicates its point well, but given the popularity of Spring, a mention of IoC is probably warranted. Just referencing the later section on IoC is fine. --User:Rich)
- 05:45, 14 June 2008 Apidesign (Talk | contribs) marked r859 of Do Not Put Setters Where They Do Not Belong patrolled (automatic)
- 05:45, 14 June 2008 Apidesign (Talk | contribs) deleted "Make Everything Final" (Author request: content before blanking was: ''''Fixed: f8cac2a753b7''' The examples in this section are of little value -- most, if not all, readers know how to override a method. Instead, more useful would be an example of what might go wrong when a cl)
- 05:44, 14 June 2008 Apidesign (Talk | contribs) marked r858 of Make Everything Final patrolled (automatic)
- 05:44, 14 June 2008 Apidesign (Talk | contribs) deleted "A Factory Is Better Than a Constructor" (Author request: content before blanking was: ''''Fixed: 68efa8b9841a''' The sentence "you can synchronize better when invoking a factory method" needs more detail. Other reasons for factory methods are well described in Effective Java, but not this one. )
- 05:44, 14 June 2008 Apidesign (Talk | contribs) marked r857 of A Factory Is Better Than a Constructor patrolled (automatic)
- 05:44, 14 June 2008 Apidesign (Talk | contribs) deleted "A Method Is Better Than A Field" (Author request: content before blanking was: ''''Fixed: f4219513dece''' Regarding "public static final constants": # These are not constants at all if the type is neither primitive nor String. Definitely avoid nonconstant fields, even if static and final)
- 05:43, 14 June 2008 Apidesign (Talk | contribs) marked r856 of A Method Is Better Than A Field patrolled (automatic)
- 05:43, 14 June 2008 Apidesign (Talk | contribs) marked r855 of Talk:Do Not Expose More Than You Want patrolled (automatic)
- 05:43, 14 June 2008 Apidesign (Talk | contribs) marked r854 of Reviewers:PartII patrolled (automatic)
- 05:41, 14 June 2008 Apidesign (Talk | contribs) marked r853 of Talk:Yet Another Design Book? patrolled (automatic)
- 05:41, 14 June 2008 Apidesign (Talk | contribs) deleted "Practical Design" (Author request: content before blanking was: 'Most of the advice you present throughout this entire part is specific to Java. It's true that a good number of your points could be applied to other languages, but there's no way that someone who doesn't kno)
- 05:41, 14 June 2008 Apidesign (Talk | contribs) marked r852 of Practical Design patrolled (automatic)
- 05:38, 14 June 2008 Apidesign (Talk | contribs) marked r851 of Reviewers:PartI patrolled (automatic)
- 05:37, 14 June 2008 Apidesign (Talk | contribs) deleted "Functional Compatibility" (Author request: content before blanking was: '* The captions in Figure 5.1 and 5.2, "How we think our applications look like", is not grammatically correct. Use "How we think our applications look", "How it really looks". * Figure 5.3: "in Next Version" )
- 05:37, 14 June 2008 Apidesign (Talk | contribs) marked r850 of Talk:Ever Changing Targets patrolled (automatic)
- 05:37, 14 June 2008 Apidesign (Talk | contribs) deleted "Incremental Improvements" (Author request: content before blanking was: '* p 67, para 2: "How Many People Have to Die?": ha - I like this expression and may start using it myself! * p 59, para 5: "optimists" => "optimist's" * p 59, para 5: "before big bang and after big band" => ")
- 05:37, 14 June 2008 Apidesign (Talk | contribs) marked r849 of Incremental Improvements patrolled (automatic)
- 05:37, 14 June 2008 Apidesign (Talk | contribs) deleted "Life-cycle of an API" (Author request: content before blanking was: 'AndreiBadea: Using Linux kernel as an example of compatible development is a bit adventurous, as kernel developers are proud of having no compatibility. JaroslavTulach true, for their modules and APIs )
- 05:37, 14 June 2008 Apidesign (Talk | contribs) marked r848 of Life-cycle of an API patrolled (automatic)
- 05:36, 14 June 2008 Apidesign (Talk | contribs) deleted "API Reviews" (Author request: content before blanking was: '* p 54, para 3: "commitee. That it needs" => "committee, that it needs" (fix spelling, sentence fragment) * p 54, para 5: "users. Also, that" => "users, and also that" (fix sentence fragment) * p 54, para -4: )
- 05:36, 14 June 2008 Apidesign (Talk | contribs) marked r847 of API Reviews patrolled (automatic)
- 05:36, 14 June 2008 Apidesign (Talk | contribs) deleted "The Importance of Being Usecase Oriented" (Author request: content before blanking was: '* section title: "Usecase Oriented" => "Use Case Oriented" or "Use Case-Oriented" * p 51, para -2: "usecase oriented" => "use case oriented" or "use case-oriented" * p 51, para -2: "Anyway," => "In any case," )
- 05:36, 14 June 2008 Apidesign (Talk | contribs) marked r846 of The Importance of Being Usecase Oriented patrolled (automatic)