Curious about the future of data-driven systems? Join our Data Engineering roundtable and learn how to build scalable data platforms.
Data Engineering: The industry has come a long way from organizing unstructured data to adopting today's modern data pipelines. See how.
Senior Software Developer at LexisNexis
Muenster, DE
Joined Oct 2004
Stats
| Reputation: | 27 |
| Pageviews: | 40.2K |
| Articles: | 1 |
| Comments: | 28 |
Comments
May 01, 2008 · admin
If you want to integrate your Java app with Linux, Windows and Mac a small amount of Code is necessary to make everything look right and integrate well. E.g. on Mac it's normal for applications to use Growl, a notification system. But you can only use it if you can use a little cocoa glue code. That is not possible anymore.
And that's not the only problem. Java 6 can't be used in Safari, because of the 64bit nature. I am one of the lucky guys that own a 64bit machine. Many Mac-Users don't have a 64bit machine.
May 01, 2008 · Bodo Tasche
If you want to integrate your Java app with Linux, Windows and Mac a small amount of Code is necessary to make everything look right and integrate well. E.g. on Mac it's normal for applications to use Growl, a notification system. But you can only use it if you can use a little cocoa glue code. That is not possible anymore.
And that's not the only problem. Java 6 can't be used in Safari, because of the 64bit nature. I am one of the lucky guys that own a 64bit machine. Many Mac-Users don't have a 64bit machine.
May 01, 2008 · Rebecca
E.g. Growl is a nice feature you could use. It's an application notifier system nearly every mac user has installed. The only way to use at the moment this is the Cocoa-Binding.
TV-Browser (the application I am working on) is running under mac, linux and windows. On each platform it has a little bit code that makes the application a nice desktop application for each platform.
If you want a good app that feels "right", you simply have to do this.
Server-Applications don't need to be platform specific, a migration to 1.6 is smoth for those products.
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
May 01, 2008 · Rebecca
Apr 30, 2008 · Rebecca
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
We tried something similar to that a few years ago (we used a blackboard). It didn't work.
Please try teamcity and look for yourself. It's much easier to work with it. If you make a commit that breaks the project, you will get to notice it very soon because teamcity will tell this directly after you tried to commit it. The SVN is never broken again because your code will only be commited if the code is okay.
Jan 31, 2008 · Michael Jouravlev
That's not a very intelligent solution for huge teams.
Try Teamcity. The commit gets into the SVN only after Teamcity verified that the changes will work and all tests are ok.
Simple, easy and better that a stupid dog on your desk :)