Hi Kenneth, Related to the Selection Bug on 1.5.0 > Yes and not sure I can fix this for the 1.5. > It will have to wait.
If you tell me where to look i can give it a try. But anyway, beside of the fact there are so many negative reactions on the 1.5.0 part, i again ask to some programmers to help me to get it stable for 1.5.0 and release a new 1.5.0 compiled version on sourceforge for the ppl that DO want to be up-to-date and use the very last JDK or JRE. I will manage this release if you want to, but i keep saying there SHOULD be a 1.5.0 compatible stable version, beside the fact you are up-to-date or not. I simply do not like to freeze because of OLD JDK or JRE (or even J2EE) versions. Or otherwise a second separate windows-version always compiled with the very last JDK should be released. In the past we already used some tricks to make the puppy compatible with the old 1.3 so why should we not be able to do the same for 1.5.0 ??? I really don't care about the linux and/or mac versions, but here at Stafa (and a lot of other companies) we DO use the very last java version (and the very last windows), so it's never wrong to have a windows-version that runs perfect on the very last JDK. Or maybe i should start a new project on java.net or even on the BerliOS website (which is almost the same as sourceforge) and start a windows version (compiled with the very last STABLE JDK) there. I was thinking about a name like JTN5250W so that it is clear that this version is java based for Windows. Let me know what you think. Oh and by the way, before you guys are staring a new windows-linux-mac flame-war... I appreciate that some ppl swear by their linux or mac-box, but for the most ppl mac or linux are not interesting, so i hope you understand why i should like to have a windows-version of this great java-project, so we can clean up a lot of old code (the 1.3 compat part and the specially for mac-and-linux-parts). It's just my opinion. I simply still don't believe in the compile once run everywhere fable. And be honest, we've seen this crap so many times... fix something for windows, and break linux, or fix something for linux and break the mac and vice versa, i simply get tired of that. We still can be one big happy family together, but have separate projects for separate os'es to keep the code cleaner and faster, and on a separate mailing-list we could discus the changes (read enhancements) and add them to every project separate with minimal changes, instead of coding a bunch of code to make it compat with them all. How about that ? Another advantage of this should be that we can write an installer in C# or VB so that new users can just run the installer instead of installing the project manually, or even a java version of an installer, but it will be a less more work to get it done, cause you do not have to worry about how mac or linux are doing it because the version is gonna to be installed on windows anyway. Or even a simple java-script should work to get tn5250j installed on a windows box, or a vbs-file (Visual Basic Script) to get it done. Well that was it for now, i'm serious how many negative reactions i will get this time, or that it will be as previous times where my arguments will simply be completely ignored, and nobody reacts. Time will tell, make my day :-) Met vriendelijke groeten, Best Regards, Patrick Bielen System-Administrator Stafa Holland BV Microsoft Certified Professional Sun Certified Java Programmer ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Tn5250j-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tn5250j-general
