NetBeans Platform - Revision history

JaroslavTulach at 13:56, 24 October 2017

JaroslavTulach — Tue, 24 Oct 2017 13:56:17 GMT

←Older revision		Revision as of 13:56, 24 October 2017
Line 1:		Line 1:
-	The heart of any [[NetBeans]] based application. The only [[Swing]] based modular application [[framework]]. More info at http://platform.netbeans.org	+	The heart of any [[Apache]] [[NetBeans]] based application. The only [[Swing]] based modular application [[framework]]. More info at http://platform.netbeans.org
		+
		+	[[Image:Jested.jpg]]

	== For Beginners ==		== For Beginners ==

JaroslavTulach at 12:00, 23 July 2014

JaroslavTulach — Wed, 23 Jul 2014 12:00:05 GMT

←Older revision		Revision as of 12:00, 23 July 2014
Line 9:		Line 9:
	The '''[[NetBeans Platform]] for Beginners''' book has exactly this structure. Each chapter is focused on one of such [[usecase]], describes what problem it helps to solve, and only then the book shows the actual [[Java]] code on a cute ''car related'' sample. The high-level concepts and their usefulness is described first, the actual usage later. Gory [[API]] details (like description of {{NB\|org-openide-dialogs\|org/openide\|WizardDescriptor}} class) is left for the last chapter. I love the approach: This is the book that should replace our standard documentation!		The '''[[NetBeans Platform]] for Beginners''' book has exactly this structure. Each chapter is focused on one of such [[usecase]], describes what problem it helps to solve, and only then the book shows the actual [[Java]] code on a cute ''car related'' sample. The high-level concepts and their usefulness is described first, the actual usage later. Gory [[API]] details (like description of {{NB\|org-openide-dialogs\|org/openide\|WizardDescriptor}} class) is left for the last chapter. I love the approach: This is the book that should replace our standard documentation!

-	[[I]] often say that [[I]] have become [[good]] [[API]] designer by making all possible mistakes when designing [[NetBeans]]. One of such mistakes was not enough stress on [[usecase]] description in our [[Javadoc]]. We improved significantly in recently designed [[API]]s, but the description of old ones is really too ''class hierarchy''-oriented. We don't have cycles to fix that, but there is one thing I am going to do: I will put reference to '''[[NetBeans Platform]] for Beginners''' into each module [[Javadoc]] entry page - because, if you are developing [[modular]] desktop application in [[Java]], this book is clearly a must read!	+	[[I]] often say that [[I]] have become [[good]] [[API]] designer by making all possible mistakes when designing [[NetBeans]]. One of such mistakes was not enough stress on [[usecase]] description in our [[Javadoc]]. We improved significantly in recently designed [[API]]s, but the description of old ones is really too ''class hierarchy''-oriented. We don't have cycles to fix that, but there is one thing I am going to do: I will put a [http://hg.netbeans.org/ergonomics/rev/07eb2231b946 reference] to '''[[NetBeans Platform]] for Beginners''' into each module [[Javadoc]] entry page - because, if you are developing [[modular]] desktop application in [[Java]], this book is clearly a must read!

	Get your copy at https://leanpub.com/nbp4beginners		Get your copy at https://leanpub.com/nbp4beginners

JaroslavTulach: /* For Beginners */

JaroslavTulach — Wed, 23 Jul 2014 10:58:47 GMT

For Beginners

←Older revision		Revision as of 10:58, 23 July 2014
Line 5:		Line 5:
	[[Image:NetBeansPlatformForBeginners.jpg\|right\|Go to https://leanpub.com/nbp4beginners]]		[[Image:NetBeansPlatformForBeginners.jpg\|right\|Go to https://leanpub.com/nbp4beginners]]

-	There is a new book about the [[NetBeans Platform]] and I am fascinated by it. ~~During~~ writing my [[TheAPIBook\|Practical API Design]] book I tried to stress as much as I could that proper [[API]] entry point should not be default [[Javadoc]] with its list of classes and methods, but a list of [[usecase]]s. Because newcomers starting to use your [[API]] are not interested in hierarchy of your classes - they have a real problem and they want to solve it - looking at flat list of all classes won't help them with that! However, if your [[API]] contains [[good]] list of [[usecase]]s, the chances are high, one of them matches user's need and it will be easy to use it as a starting point and modify it slightly to solve the actual need.	+	There is a new book about the [[NetBeans Platform]] and I am fascinated by it. While writing my [[TheAPIBook\|Practical API Design]] book I tried to stress as much as I could that proper [[API]] entry point should not be default [[Javadoc]] with its list of classes and methods, but a list of [[usecase]]s. Because newcomers starting to use your [[API]] are not interested in hierarchy of your classes - they have a real problem and they want to solve it - looking at flat list of all classes won't help them with that! However, if your [[API]] contains [[good]] list of [[usecase]]s, the chances are high, one of them matches user's need and it will be easy to use it as a starting point and modify it slightly to solve the actual need.

	The '''[[NetBeans Platform]] for Beginners''' book has exactly this structure. Each chapter is focused on one of such [[usecase]], describes what problem it helps to solve, and only then the book shows the actual [[Java]] code on a cute ''car related'' sample. The high-level concepts and their usefulness is described first, the actual usage later. Gory [[API]] details (like description of {{NB\|org-openide-dialogs\|org/openide\|WizardDescriptor}} class) is left for the last chapter. I love the approach: This is the book that should replace our standard documentation!		The '''[[NetBeans Platform]] for Beginners''' book has exactly this structure. Each chapter is focused on one of such [[usecase]], describes what problem it helps to solve, and only then the book shows the actual [[Java]] code on a cute ''car related'' sample. The high-level concepts and their usefulness is described first, the actual usage later. Gory [[API]] details (like description of {{NB\|org-openide-dialogs\|org/openide\|WizardDescriptor}} class) is left for the last chapter. I love the approach: This is the book that should replace our standard documentation!

JaroslavTulach at 10:56, 23 July 2014

JaroslavTulach — Wed, 23 Jul 2014 10:56:29 GMT

←Older revision		Revision as of 10:56, 23 July 2014
Line 3:		Line 3:
	== For Beginners ==		== For Beginners ==

-	~~There is a new book about the~~ [[~~NetBeans Platform]] and I am fascinated by it~~. ~~During writing my [[TheAPIBook~~\|~~Practical API Design]] I tried~~ to ~~stress as much as I could that proper API entry point should not be [[Javadoc]] with its list of classes and methods, but a list of [[Usecase]]s~~. ~~Because newcomers using your [[API~~]] are not interested in hierarchy of your classes - they have a problem and they want to solve it. If the [[API]] contains [[good]] list of [[usecase]s, the chances are high, one of them will match user's need and it will be easy to use it as a starting point and modify it slightly to solve the actual need.	+	[[Image:NetBeansPlatformForBeginners.jpg\|right\|Go to https://leanpub.com/nbp4beginners]]

-	~~The '''~~[[NetBeans Platform]] ~~for Beginners''' book has exactly this structure~~. ~~Each chapter is focused on one of such~~ [[~~usecase~~]]~~, describes what problem it helps to solve, and only then the~~ book ~~shows the actual~~ [[~~Java~~]] ~~code on a cute car related sample. The high-level concepts~~ and ~~their usefulness is described first~~, ~~the actual usage later~~. ~~Gory~~ [[API]] ~~details (like description~~ of ~~{{nb\|org~~-~~openide~~-~~dialogs\|org/openide/WizardDescriptor}} class) is left for the last chapter. I love the approach: This is the book~~ that ~~should replace our standard documentation~~!	+	There is a new book about the [[NetBeans Platform]] and I am fascinated by it. During writing my [[TheAPIBook\|Practical API Design]] book I tried to stress as much as I could that proper [[API]] entry point should not be default [[Javadoc]] with its list of classes and methods, but a list of [[usecase]]s. Because newcomers starting to use your [[API]] are not interested in hierarchy of your classes - they have a real problem and they want to solve it - looking at flat list of all classes won't help them with that! However, if your [[API]] contains [[good]] list of [[usecase]]s, the chances are high, one of them matches user's need and it will be easy to use it as a starting point and modify it slightly to solve the actual need.

-	~~[[I]] often say that [[I]] have become good API designer by making all possible mistakes when designing~~ [[NetBeans]]. ~~One~~ of such ~~mistakes was not enough stress on~~ [[usecase]] ~~description in our~~ [[~~Javadoc~~]]~~. We improved significantly in recently designed [[API]]s, but the old ones, are really too~~ ''~~class hierarchy~~''-~~oriented~~. ~~We don't have cycles to fix that, but there is one thing I am going to do: I will put reference to ''~~[[~~NetBeans Platform~~]] for ~~Beginners'' into each module [[Javadoc]] entry page - because, if you are developing [[modular]] desktop application in [[Java]], this~~ book ~~is clearly a must read~~!	+	The '''[[NetBeans Platform]] for Beginners''' book has exactly this structure. Each chapter is focused on one of such [[usecase]], describes what problem it helps to solve, and only then the book shows the actual [[Java]] code on a cute ''car related'' sample. The high-level concepts and their usefulness is described first, the actual usage later. Gory [[API]] details (like description of {{NB\|org-openide-dialogs\|org/openide\|WizardDescriptor}} class) is left for the last chapter. I love the approach: This is the book that should replace our standard documentation!

-	[[~~Image:NetBeansPlatformForBeginners~~.~~jpg\|right\|Go~~ to https://leanpub.com/nbp4beginners]]	+	[[I]] often say that [[I]] have become [[good]] [[API]] designer by making all possible mistakes when designing [[NetBeans]]. One of such mistakes was not enough stress on [[usecase]] description in our [[Javadoc]]. We improved significantly in recently designed [[API]]s, but the description of old ones is really too ''class hierarchy''-oriented. We don't have cycles to fix that, but there is one thing I am going to do: I will put reference to '''[[NetBeans Platform]] for Beginners''' into each module [[Javadoc]] entry page - because, if you are developing [[modular]] desktop application in [[Java]], this book is clearly a must read!
		+
		+	Get your copy at https://leanpub.com/nbp4beginners

JaroslavTulach at 10:49, 23 July 2014

JaroslavTulach — Wed, 23 Jul 2014 10:49:47 GMT

←Older revision		Revision as of 10:49, 23 July 2014
Line 1:		Line 1:
	The heart of any [[NetBeans]] based application. The only [[Swing]] based modular application [[framework]]. More info at http://platform.netbeans.org		The heart of any [[NetBeans]] based application. The only [[Swing]] based modular application [[framework]]. More info at http://platform.netbeans.org
		+
		+	== For Beginners ==
		+
		+	There is a new book about the [[NetBeans Platform]] and I am fascinated by it. During writing my [[TheAPIBook\|Practical API Design]] I tried to stress as much as I could that proper API entry point should not be [[Javadoc]] with its list of classes and methods, but a list of [[Usecase]]s. Because newcomers using your [[API]] are not interested in hierarchy of your classes - they have a problem and they want to solve it. If the [[API]] contains [[good]] list of [[usecase]s, the chances are high, one of them will match user's need and it will be easy to use it as a starting point and modify it slightly to solve the actual need.
		+
		+	The '''[[NetBeans Platform]] for Beginners''' book has exactly this structure. Each chapter is focused on one of such [[usecase]], describes what problem it helps to solve, and only then the book shows the actual [[Java]] code on a cute car related sample. The high-level concepts and their usefulness is described first, the actual usage later. Gory [[API]] details (like description of {{nb\|org-openide-dialogs\|org/openide/WizardDescriptor}} class) is left for the last chapter. I love the approach: This is the book that should replace our standard documentation!
		+
		+	[[I]] often say that [[I]] have become good API designer by making all possible mistakes when designing [[NetBeans]]. One of such mistakes was not enough stress on [[usecase]] description in our [[Javadoc]]. We improved significantly in recently designed [[API]]s, but the old ones, are really too ''class hierarchy''-oriented. We don't have cycles to fix that, but there is one thing I am going to do: I will put reference to ''[[NetBeans Platform]] for Beginners'' into each module [[Javadoc]] entry page - because, if you are developing [[modular]] desktop application in [[Java]], this book is clearly a must read!
		+
		+	[[Image:NetBeansPlatformForBeginners.jpg\|right\|Go to https://leanpub.com/nbp4beginners]]

JaroslavTulach at 14:20, 17 October 2012

JaroslavTulach — Wed, 17 Oct 2012 14:20:23 GMT

←Older revision		Revision as of 14:20, 17 October 2012
Line 1:		Line 1:
-	The heart of any [[NetBeans]] based application. The only Swing based modular application framework. More info at http://platform.netbeans.org	+	The heart of any [[NetBeans]] based application. The only [[Swing]] based modular application [[framework]]. More info at http://platform.netbeans.org

JaroslavTulach at 10:17, 20 June 2010

JaroslavTulach — Sun, 20 Jun 2010 10:17:22 GMT

←Older revision		Revision as of 10:17, 20 June 2010
Line 1:		Line 1:
-	The heart of any [[NetBeans]] based application.	+	The heart of any [[NetBeans]] based application. The only Swing based modular application framework. More info at http://platform.netbeans.org

JaroslavTulach at 19:37, 26 June 2008

JaroslavTulach — Thu, 26 Jun 2008 19:37:21 GMT

←Older revision		Revision as of 19:37, 26 June 2008
Line 1:		Line 1:
-	The heart of any [[~~wikipedia::~~NetBeans]] based application.	+	The heart of any [[NetBeans]] based application.

JaroslavTulach: New page: The heart of any wikipedia::NetBeans based application.

JaroslavTulach — Mon, 16 Jun 2008 11:57:13 GMT

New page: The heart of any wikipedia::NetBeans based application.

New page

The heart of any [[wikipedia::NetBeans]] based application.

←Older revision		Revision as of 10:58, 23 July 2014
Line 5:		Line 5:
	[[Image:NetBeansPlatformForBeginners.jpg\|right\|Go to https://leanpub.com/nbp4beginners]]		[[Image:NetBeansPlatformForBeginners.jpg\|right\|Go to https://leanpub.com/nbp4beginners]]

-	There is a new book about the [[NetBeans Platform]] and I am fascinated by it. ~~During~~ writing my [[TheAPIBook\|Practical API Design]] book I tried to stress as much as I could that proper [[API]] entry point should not be default [[Javadoc]] with its list of classes and methods, but a list of [[usecase]]s. Because newcomers starting to use your [[API]] are not interested in hierarchy of your classes - they have a real problem and they want to solve it - looking at flat list of all classes won't help them with that! However, if your [[API]] contains [[good]] list of [[usecase]]s, the chances are high, one of them matches user's need and it will be easy to use it as a starting point and modify it slightly to solve the actual need.	+	There is a new book about the [[NetBeans Platform]] and I am fascinated by it. While writing my [[TheAPIBook\|Practical API Design]] book I tried to stress as much as I could that proper [[API]] entry point should not be default [[Javadoc]] with its list of classes and methods, but a list of [[usecase]]s. Because newcomers starting to use your [[API]] are not interested in hierarchy of your classes - they have a real problem and they want to solve it - looking at flat list of all classes won't help them with that! However, if your [[API]] contains [[good]] list of [[usecase]]s, the chances are high, one of them matches user's need and it will be easy to use it as a starting point and modify it slightly to solve the actual need.

	The '''[[NetBeans Platform]] for Beginners''' book has exactly this structure. Each chapter is focused on one of such [[usecase]], describes what problem it helps to solve, and only then the book shows the actual [[Java]] code on a cute ''car related'' sample. The high-level concepts and their usefulness is described first, the actual usage later. Gory [[API]] details (like description of {{NB\|org-openide-dialogs\|org/openide\|WizardDescriptor}} class) is left for the last chapter. I love the approach: This is the book that should replace our standard documentation!		The '''[[NetBeans Platform]] for Beginners''' book has exactly this structure. Each chapter is focused on one of such [[usecase]], describes what problem it helps to solve, and only then the book shows the actual [[Java]] code on a cute ''car related'' sample. The high-level concepts and their usefulness is described first, the actual usage later. Gory [[API]] details (like description of {{NB\|org-openide-dialogs\|org/openide\|WizardDescriptor}} class) is left for the last chapter. I love the approach: This is the book that should replace our standard documentation!