 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Java Forum / General / March 2006Java 6.0
Hi everyone, Does anyone know where i can get hold of the source code for the following api JTextComponent.print(MessageFormat headerFormat,MessageFormat footerFormat) throws PrinterException This code is part of the new java second edition 6.0. I have tried searching google but could not find any of its source code. What i am trying to do is hopefully create a backport for 1.5 Does anyone know where i find the java source code to the above api Any help is greatly appreciated Yours Sincerely Richard West > Hi everyone, > > Does anyone know where i can get hold of the source code for the following > api Mustang betas are available from http://java.sun.com/javase/6/, and presumably would still include the traditional src.zip > I have tried searching google but could not find any of its source code. > What i am trying to do is hopefully create a backport for 1.5 Careful about licenses if you plan to redistribute.  Signaturewww.designacourse.com The Easiest Way To Train Anyone... Anywhere. Chris Smith - Lead Software Developer/Technical Trainer MindIQ Corporation > This code is part of the new java second edition 6.0. Just fyi, the SE in "Java SE" is for Standard Edition, not Second Edition. >> This code is part of the new java second edition 6.0. > Just fyi, the SE in "Java SE" is for Standard Edition, not Second > Edition. But there is usually a 2 after "Java" and before "Standard Edition". I.e. "J2SE 1.6" aka "J2SE 6.0" aka "Java 2 6" aka "Java 6" aka "Java 1.6" aka "Java 2 1.6" aka "Java 2" (latest version is implied). Java has one of the most confusing naming/numbering schemes I've ever seen. - Oliver >>> This code is part of the new java second edition 6.0. >> Just fyi, the SE in "Java SE" is for Standard Edition, not Second [quoted text clipped - 3 lines] > I.e. "J2SE 1.6" aka "J2SE 6.0" aka "Java 2 6" aka "Java 6" aka "Java > 1.6" aka "Java 2 1.6" aka "Java 2" (latest version is implied). No. No 2s anymore. Or .0s. Java SE 6 and Java EE 5. > Java has one of the most confusing naming/numbering schemes I've ever > seen. It's a Sun specialty. Tom Hawtin SignatureUnemployed English Java programmer http://jroller.com/page/tackline/ On Thu, 16 Mar 2006 19:53:14 +0000, Thomas Hawtin <usenet@tackline.plus.com> wrote, quoted or indirectly quoted someone who said : >> Java has one of the most confusing naming/numbering schemes I've ever >> seen. > >It's a Sun specialty. I think it is a fight between the marketing and technical people. The sales types come up with a new name. The technical guys resist since the old name is burned in 10,000 places. So life proceeds with two names, with programmers using the old name. SignatureCanadian Mind Products, Roedy Green. http://mindprod.com Java custom programming, consulting and coaching. >> Java has one of the most confusing naming/numbering schemes I've ever >> seen. > It's a Sun specialty. Indeed! Have a look at this (silly silly silly but true!): http://www.ocf.berkeley.edu/solaris/versions/ Jean-Francois Briere schrieb: >>> Java has one of the most confusing naming/numbering schemes I've ever >>> seen. [quoted text clipped - 4 lines] > > http://www.ocf.berkeley.edu/solaris/versions/ The Java naming schemes are seriously confusing, but the solaris version names are actually very clean compared to others, for example the Microsoft Windows random naming system: Windows 1.0 - 3.1 Windows 95 Windows 98 Windows 98 SE Windows ME Windows NT Windows XP Windows Vista They can't stick to a naming scheme for more than a few years. But at least it's still named "Windows". The 7 (or so) different versions of Windows Vista are terribly confusing as well. But this is quite commom. Macromedia Flash has also been rebranded several times: Flash 1 - 5 Flash MX Flash MX 2004 Flash Basic/Professional 8 Adobe does it too, and IBM is even better at generating lengthy, buzzword enriched product names. This is certainly a marketing problem. Open source projects have been save from such sillyness for a long time because they were managed by programmers. But they are catching up. Take the rebranding of the VoIP app "Gnome Meeting" to "Ekiga" for example. Timo > This is certainly a marketing problem. Open source projects have been > save from such sillyness for a long time because they were managed by > programmers. But they are catching up. Take the rebranding of the VoIP > app "Gnome Meeting" to "Ekiga" for example. Instead they indulge in the sillyness of recursive acronymns, version numbers that approach 1.0 without ever getting there even after years of stable releases, and on Linux of ensuring that every name begins with a g, k or x depending on the graphical environment. Still, the commercial world would never have given us a product named "The GIMP". Dan. SignatureDaniel Dyer http://www.dandyer.co.uk > after years of stable releases, and on Linux of ensuring that every > name begins with a g, k or x depending on the graphical > environment. Just use console apps. Problem solved! Let's see ... the apps that I have open all the time are ... mutt, slrn, irssi, and screen. None of them start with a g, k, or x! Then again, good luck guessing what they do by their names ... Signaturemonique Ask smart questions, get good answers: http://www.catb.org/~esr/faqs/smart-questions.html >Instead they indulge in the sillyness of recursive acronymns, version >numbers that approach 1.0 without ever getting there even after years of >stable releases, I once learned that 0.x are internal versions and that the first published version is 1.0. By this, a published version 0.x would be a contradiction. >>Instead they indulge in the sillyness of recursive acronymns, >>version numbers that approach 1.0 without ever getting there even [quoted text clipped - 3 lines] > published version is 1.0. By this, a published version 0.x would > be a contradiction. That might make sense in the commercial world, but for free-as-in-beer open source software, releasing makes the code available, not just the end product. It's considered bad form to release a version 1.0 that's not rock solid. Consider it a warning flag. If you see a version much below 1.0, read it as, "Here there be dragons, incomplete features, and core dumps. It's mostly out there so that other developers can contribute, but if you're brave and it does what you need, more power to you. Please file frequent bug reports." On the flip side, I assume that a commercial product at version 1.0 is utter crap. I expect an open source product at version 1.0 to be rock solid and utterly incapable of breaking. Signaturemonique Ask smart questions, get good answers: http://www.catb.org/~esr/faqs/smart-questions.html >>>Instead they indulge in the sillyness of recursive acronymns, >>>version numbers that approach 1.0 without ever getting there even [quoted text clipped - 18 lines] > utter crap. I expect an open source product at version 1.0 to be rock > solid and utterly incapable of breaking. I'll keep that in mind and start releasing with version 7.0 -- LTP :) >>>>Instead they indulge in the sillyness of recursive acronymns, >>>>version numbers that approach 1.0 without ever getting there even [quoted text clipped - 25 lines] > > :) This could account for some of Sun's version numbering oddities. ;-) > I'll keep that in mind and start releasing with version 7.0 There's seriously a sort of mythology about this stuff out there. No published statistics that I've ever seen to support it, though. Generally, I hear manager-types say that they want to plan to keep their products in the 2.x - 6.x range for as long as possible, because that's when customers have the most confidence. Starting with 7.x, the mythology goes, customers start to assume that the product is a dinosaur and look for the next New Thing that will replace it. Signaturewww.designacourse.com The Easiest Way To Train Anyone... Anywhere. Chris Smith - Lead Software Developer/Technical Trainer MindIQ Corporation > Generally, I hear manager-types say that they want to plan to keep > their products in the 2.x - 6.x range for as long as possible, > because that's when customers have the most confidence. Starting > with 7.x, the mythology goes, customers start to assume that the > product is a dinosaur and look for the next New Thing that will > replace it. I seem to remember that the initial release of Watcom C was version 6.0. /gordon Signature[ do not email me copies of your followups ] g o r d o n + n e w s @ b a l d e r 1 3 . s e > I'll keep that in mind and start releasing with version 7.0 Nah. Start with 0.5. If there are lots of bug reports, next version is 0.25, otherwise if there are few reports 0.75. Continue with binary chop until you have an honestly indicative version number. Then stick with that number for all releases unless/until you change your development patterns... -- chris > I once learned that 0.x are internal versions and that the > first published version is 1.0. By this, a published version > 0.x would be a contradiction. Release early, release often is the mantra of the free/open software community. Also, some projects like to keep the 0.x forever, as an indication that there is never ever such a thing as a complete and perfect software. /Thomas SignatureThe comp.lang.java.gui FAQ: ftp://ftp.cs.uu.nl/pub/NEWS.ANSWERS/computer-lang/java/gui/faq http://www.uni-giessen.de/faq/archiv/computer-lang.java.gui.faq/ > Jean-Francois Briere schrieb: >>>> Java has one of the most confusing naming/numbering schemes I've ever [quoted text clipped - 18 lines] > Windows XP > Windows Vista [snip] You left out 2000 and 2003, but you make a very good point. Luke >> Jean-Francois Briere schrieb: >>>>> Java has one of the most confusing naming/numbering schemes I've ever [quoted text clipped - 23 lines] > > Luke Don't forget the fact that there is still a version number (and build #) lurking behind that Windows name. I'm not supporting MS, just stating facts. > The Java naming schemes are seriously confusing, but the solaris version > names are actually very clean compared to others, Wait until you have seen Sun's numbering of the C/C++ compiler and IDE. FUBAR. Sun is really good at renumbering and renaming things to achieve maximum confusion. /Thomas SignatureThe comp.lang.java.gui FAQ: ftp://ftp.cs.uu.nl/pub/NEWS.ANSWERS/computer-lang/java/gui/faq http://www.uni-giessen.de/faq/archiv/computer-lang.java.gui.faq/ Hi everyone, The thing is my entire computer network is stil using 1.4.2. I don't know if i can download the src.zip only. If i can do you know the url i can download it from. It would take me a lot of time to simply download it uninstall the porevious version and reinstall the 6.0 only to get the source code. Are you using 6.0 by the way? Yours Sincerely Richard West On Thu, 16 Mar 2006 14:07:39 -0500, "freesoft_2000" <freesoft_2000@yahoo.com> wrote, quoted or indirectly quoted someone who said : > The thing is my entire computer network is stil using 1.4.2. >I don't know if i can download the src.zip only. If i can do you know the >url i can download it from. No. Download the JDK, install it and delete everything but src.zip If you talked someone into mailing src.zip to you it would balloon up with the mime encoding, so you woud be no further ahead. SignatureCanadian Mind Products, Roedy Green. http://mindprod.com Java custom programming, consulting and coaching. > On Thu, 16 Mar 2006 14:07:39 -0500, "freesoft_2000" > <freesoft_2000@yahoo.com> wrote, quoted or indirectly quoted someone [quoted text clipped - 5 lines] > > No. Download the JDK, install it and delete everything but src.zip Not sure if this is "safe", especially if the OP is working on Windows. I believe the installer does all sorts of voodoo magic with the registry. Perhaps the OP could install the JDK, make a backup of src.zip, then uninstall the JDK, and be left with only his/her personal backup copy. - Oliver > Not sure if this is "safe", especially if the OP is working on Windows. >I believe the installer does all sorts of voodoo magic with the registry. >Perhaps the OP could install the JDK, make a backup of src.zip, then >uninstall the JDK, and be left with only his/her personal backup copy. Yes. that would be better. SignatureCanadian Mind Products, Roedy Green. http://mindprod.com Java custom programming, consulting and coaching. Hi everyone, I don't mean to be bad but seriosly i am trying ask a question here, they can name in roman numerals for all i care. Please guys i really need help with this question mine. Please stick to the topic at hand Yours Sincerely Richard West > Hi everyone, > [quoted text clipped - 7 lines] > > Richard West LOL Oh boy - here we go again. I put in my two cents last time someone tried to tell us what to do - I think I'll refrain this time. -- LTP :) > Please guys i really need help with this question mine. > Please stick to the topic at hand We /are/ sticking to the topic, it's you who are talking about something else ;-) But try: http://java.sun.com/javase/6/download.jsp Check the licences /very/ carefully. -- chris > Hi everyone, > [quoted text clipped - 17 lines] > > Richard West How about http://download.java.net/jdk6/beta/ Not that hard to find. Again I echo the comments about licences. James Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.