Blogs:JaroslavTulach:Theory:RightDependencies - Revision history

JaroslavTulach at 08:10, 19 May 2010

2010-05-19T08:10:45Z

←Older revision		Revision as of 08:10, 19 May 2010
Line 3:		Line 3:
	Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and dedicated last nine months to [[Netigso\|interoperability with OSGi]]. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].		Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and dedicated last nine months to [[Netigso\|interoperability with OSGi]]. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].

-	I'll continue to investigate various interoperability options as part of my daily job. At the end it should not matter whether you code for [[Eclipse]] or [[NetBeans]], but whether you have the right [[dependencies]] (read: no ''SWT'', bunch of [[Swing]] and don't forget [[Lookup]] ;-). This is another sign that (when there is a common ground - a lingua franca - e.g. common module system for [[Java]]) interoperability will be easier than ever. [[The_Art_of_Building_Modern_Software\|Building applications]] will be like composing them from [[Lego]] bricks.	+	I'll continue to investigate various interoperability options as part of my daily job. At the end it should not matter whether you code for [[Eclipse]] or [[NetBeans]], but whether you have the right [[dependencies]] (read: no ''SWT'', bunch of [[Swing]] and don't forget [[Lookup]] ;-). This is another sign that (when there is a [[module system\|common ground]] - a lingua franca - e.g. common [[module system]] for [[Java]]) interoperability will be easier than ever. [[The_Art_of_Building_Modern_Software\|Building applications]] will be like composing them from [[Lego]] bricks. There is only one prerequisite:

	Choose your [[dependencies]] wisely!		Choose your [[dependencies]] wisely!

JaroslavTulach at 08:09, 19 May 2010

2010-05-19T08:09:05Z

←Older revision		Revision as of 08:09, 19 May 2010
Line 1:		Line 1:
	I've just seen following [[Blogs:JaroslavTulach:Theory:RightDependencies\|quote in my mailbox]]: 'perhaps [[NetBeans]] is easiest to build plugin for...' (read: easier than other IDEs).		I've just seen following [[Blogs:JaroslavTulach:Theory:RightDependencies\|quote in my mailbox]]: 'perhaps [[NetBeans]] is easiest to build plugin for...' (read: easier than other IDEs).

-	Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and I dedicated last nine months to [[Netigso\|interoperability with OSGi]]. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].	+	Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and dedicated last nine months to [[Netigso\|interoperability with OSGi]]. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].

	I'll continue to investigate various interoperability options as part of my daily job. At the end it should not matter whether you code for [[Eclipse]] or [[NetBeans]], but whether you have the right [[dependencies]] (read: no ''SWT'', bunch of [[Swing]] and don't forget [[Lookup]] ;-). This is another sign that (when there is a common ground - a lingua franca - e.g. common module system for [[Java]]) interoperability will be easier than ever. [[The_Art_of_Building_Modern_Software\|Building applications]] will be like composing them from [[Lego]] bricks.		I'll continue to investigate various interoperability options as part of my daily job. At the end it should not matter whether you code for [[Eclipse]] or [[NetBeans]], but whether you have the right [[dependencies]] (read: no ''SWT'', bunch of [[Swing]] and don't forget [[Lookup]] ;-). This is another sign that (when there is a common ground - a lingua franca - e.g. common module system for [[Java]]) interoperability will be easier than ever. [[The_Art_of_Building_Modern_Software\|Building applications]] will be like composing them from [[Lego]] bricks.

	Choose your [[dependencies]] wisely!		Choose your [[dependencies]] wisely!

JaroslavTulach at 08:01, 19 May 2010

2010-05-19T08:01:16Z

←Older revision		Revision as of 08:01, 19 May 2010
Line 3:		Line 3:
	Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and I dedicated last nine months to [[Netigso\|interoperability with OSGi]]. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].		Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and I dedicated last nine months to [[Netigso\|interoperability with OSGi]]. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].

-	I'll continue to investigate various interoperability options as part of my daily job. At the end it should not matter whether you code for [[Eclipse]] or [[NetBeans]], but whether you have the right [[dependencies]] (read: no ''SWT'', bunch of [[Swing]] and don't forget [[Lookup]] ;-).	+	I'll continue to investigate various interoperability options as part of my daily job. At the end it should not matter whether you code for [[Eclipse]] or [[NetBeans]], but whether you have the right [[dependencies]] (read: no ''SWT'', bunch of [[Swing]] and don't forget [[Lookup]] ;-). This is another sign that (when there is a common ground - a lingua franca - e.g. common module system for [[Java]]) interoperability will be easier than ever. [[The_Art_of_Building_Modern_Software\|Building applications]] will be like composing them from [[Lego]] bricks.

	Choose your [[dependencies]] wisely!		Choose your [[dependencies]] wisely!

JaroslavTulach at 07:58, 19 May 2010

2010-05-19T07:58:06Z

←Older revision		Revision as of 07:58, 19 May 2010
Line 1:		Line 1:
	I've just seen following [[Blogs:JaroslavTulach:Theory:RightDependencies\|quote in my mailbox]]: 'perhaps [[NetBeans]] is easiest to build plugin for...' (read: easier than other IDEs).		I've just seen following [[Blogs:JaroslavTulach:Theory:RightDependencies\|quote in my mailbox]]: 'perhaps [[NetBeans]] is easiest to build plugin for...' (read: easier than other IDEs).

-	Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and I dedicated last nine months to interoperability with OSGi. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].	+	Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and I dedicated last nine months to [[Netigso\|interoperability with OSGi]]. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].

	I'll continue to investigate various interoperability options as part of my daily job. At the end it should not matter whether you code for [[Eclipse]] or [[NetBeans]], but whether you have the right [[dependencies]] (read: no ''SWT'', bunch of [[Swing]] and don't forget [[Lookup]] ;-).		I'll continue to investigate various interoperability options as part of my daily job. At the end it should not matter whether you code for [[Eclipse]] or [[NetBeans]], but whether you have the right [[dependencies]] (read: no ''SWT'', bunch of [[Swing]] and don't forget [[Lookup]] ;-).

	Choose your [[dependencies]] wisely!		Choose your [[dependencies]] wisely!

JaroslavTulach at 07:57, 19 May 2010

2010-05-19T07:57:31Z

←Older revision		Revision as of 07:57, 19 May 2010
Line 1:		Line 1:
-	I've just seen following [[Blogs:JaroslavTulach:Theory:RightDependencies\|quote in my mailbox]]: 'perhaps [[~~Netbeans~~]] is easiest to build plugin for...' (read: easier than other IDEs).	+	I've just seen following [[Blogs:JaroslavTulach:Theory:RightDependencies\|quote in my mailbox]]: 'perhaps [[NetBeans]] is easiest to build plugin for...' (read: easier than other IDEs).

	Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and I dedicated last nine months to interoperability with OSGi. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].		Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi\|'standard' modularity]] and [[Swing\|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and I dedicated last nine months to interoperability with OSGi. Some even say it is [[Talk:NetbinoxTutorial\|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].

JaroslavTulach: New page: I've just seen following quote in my mailbox: 'perhaps Netbeans is easiest to build plugin for...' (read: easier than other IDEs). We...

2010-05-19T07:57:18Z

New page: I've just seen following quote in my mailbox: 'perhaps Netbeans is easiest to build plugin for...' (read: easier than other IDEs). We...

New page

I've just seen following [[Blogs:JaroslavTulach:Theory:RightDependencies|quote in my mailbox]]: 'perhaps [[Netbeans]] is easiest to build plugin for...' (read: easier than other IDEs).

Well, the mileage may vary. However if you want (or even have people with knowledge of) [[OSGi|'standard' modularity]] and [[Swing|standard UI toolkit]], then [[NetBeans]] Platform 6.9 is the easiest way to merge these two. We support [[Swing]] for ages and I dedicated last nine months to interoperability with OSGi. Some even say it is [[Talk:NetbinoxTutorial|easier to use Equinox with NetBeans IDE 6.9 than with Eclipse IDE]].

I'll continue to investigate various interoperability options as part of my daily job. At the end it should not matter whether you code for [[Eclipse]] or [[NetBeans]], but whether you have the right [[dependencies]] (read: no ''SWT'', bunch of [[Swing]] and don't forget [[Lookup]] ;-).

Choose your [[dependencies]] wisely!