Re: Where is the enviroment files for JBuilder4.0?
On Thu, Feb 01, 2001 at 02:12:32PM +0800, Yang Yue Xiang wrote: > Who can tell me the location of the enviroment files of JBuilder4.0? What do you mean with "environment files" ? -- Paolo 2K1 RoadStar ISRA #: 4773 VROC #: 5264-R AMA #: 360867 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is there a linux java editing tool?
> [...] > Well, this is something I hear all the time and I'm sorry but I > disagree. Emacs is not an editor, it's more a way of life; editing > is just one of the things it does better than anything else. > > :-) > > One a more useful note, as someone else mentioned, emacs together with > Java Development Environment (JDE) is pretty good. You can get information > about jde from <http://sunsite.auc.dk/jde/> > -- > Ravi/ a very good tool, i.e. a visual builder for applets, for standalone applications and for beans is JavaWorkShop2.0 from Sun. You can download a free trial copy (1month) for Solaris ix86 from JavaSoft. There is a patch for Linux from SuSe ftp://ftp.suse.com/pub/SuSE-Linux/suse_update/JWS2.0/ On Linux it's works fine, except that the debugger wich uses a Solaris native code with jdk1.1.3 and with some problem with jdl1.1.5v7. Have yo fun ! Paolo Sommaruga Garda Access Internet Provider Garda Lake, Italy http://www.garda-access.com
Using two java linux port
I'm working on a java application based on Swing102. The app compiled with nikitin port works well but show a bug in resizing the main window horizontally. The same bug is visible in an example (Notepad) distributed with Swing102 and executed with nikitin java. Then I have tried the steve port (jdk1.1.6-v2-glibc.tar.gz): my app works well, and also the Notepad from Swing. But when I recompiled the app with the steve port the menubar behave erratically. I would like the best of the two ports: nikitin's javac (it also seems faster) and steve's java I hope this may help steve and nikitin. Thanks to all for the hard work done, and excuse my bad english. -- ===== Paolo Cacciatoriphone: +39 422 411729 fax: +39 422 543218 email: [EMAIL PROTECTED] Gajo & Associati srl Via Roggia 52 - 31100 TREVISO - ITALY =
Re: jdk1.1.6v2 comment, Swing Fix
Hendricks Family wrote: > > The problem that you have observed is a Swing 1.0.2 problem, A patch is > available if you want to create your own swing_fix.jar with 1.0.2 > src.zip that comes with Swing 1.0.2 (that is what I did and it works). I'm not sure it is a Swing 1.0.2 problem. I've observed this: code compiled with the other jdk linux port (nikitin) run under jdk112 without that problem (it has instead a problem with horizontal resizing of a JFrame) The problem may be related to javac. -- = Paolo Cacciatoriphone: +39 0422 411729 fax: +39 0422 543218 email: [EMAIL PROTECTED] Gajo & Associati srl Via Roggia 52 - 31100 TREVISO - ITALY =
Re: bison/java ?
>>>>> "AB" == Artur Biesiadowski <[EMAIL PROTECTED]> writes: AB> Is there any compiler-compiler available for java that takes AB> bison-like grammar as input ? I don't think only about same AB> type of grammar, but exactly same definitions (of course AB> without action bodies). AB> I was browsing through bison source and I was struck by some AB> idea. How much work would take to make bison to generate java AB> code ? State tables would be read from external files AB> (because of the max size of static initializer in AB> class). bison.simple would have to be rewritten in java. $1 AB> for type would change from yyvsp[-1].node to AB> (Node)yyvsp[yyvsphead-1] AB> Any comments ? Only that LALR and Bison-like grammars have been superceeded by LL(k) ones. The notation is simpler and more powerful. Instead of looking at JavaCC go to http://www.antlr.org. Antlr is the original tools that was used to "inspire" JavaCC. Key benefits: - EBNF grammar with single notation for Parser, Scanner and Tree walker (for ASTs). - Unlimited number of lookahaead symbols. - Built-in notation to automatically generate ASTs - Visual debugging support. - C++ and Java generation from the same grammar definition - Java 1.1, HTML and C++ grammars included. - Totally free. --Paolo
java-linux@java.blackdown.org
>>>>> "MD" == Moses DeJong <[EMAIL PROTECTED]> writes: MD> I agree. It is ugly. I would not want to use it myself. Still, MD> you should have the right to use it if you want to. Microsoft MD> should not be able to tell you how to run your software. Yes, it should not but their goal is exactly to have *total* control on the SW industry. When we try to promote Linux we should use this angle more than the technical merit of the OS. MS took away, well it tried to take away, our freedom of choice. Avoiding MS software it's about restoring one of our basic civil rights. A society, any form of society, without freedom of choice is in fact a dictatorship. -- Paolo
Re: JDK 1.2 TimeTable Not Possible Yet, Status Report
Kevin, thanks you all for your effort and for letting us know. --Paolo
Re: JBuilder and Linux
>>>>> "CARZ" == Carlos Alberto Roman Zamitiz <[EMAIL PROTECTED]> writes: CARZ> I wrote a project on JBuilder2.0 (windows), but my web CARZ> server is a linux box. I put my *class, *html in my web CARZ> server. I used some jbuilder's classes (GridView, CARZ> GridControl, and more) CARZ> I don't know if put jbcl2.0.jar or jbcl2.0-src.zip in my web CARZ> server. I got the following: jbcl2.0.jar is the Jar file that you have to include if your using jbcl component (it looks like that by the error message. The other archive contains the sources (.java) of JBCL so I don't think you should include it. CARZ> # Verifier error proy3/Applet1.jbInit()V: Cannot find class CARZ> borland/jbcl/view/GridView # Applet exception: class CARZ> proy3/Applet1 got a security violation: method verification CARZ> error java.lang.VerifyError: proy3/Applet1 CARZ> Thanks! Carlos Alberto Roman Zamitiz Departamento de CARZ> Ingenieria en Computacion, Facultad de Ingenieria UNAM CARZ> [EMAIL PROTECTED] -- Paolo
Re: BUG REPORT
>>>>> "AP" == Alex Pozgaj <[EMAIL PROTECTED]> writes: AP> I just tried it out on Solaris (SunOS 5.6), both with jdk1.2 AP> and with jdk1.1.5. AP> Under 1.2 it worked. Under 1.1.5, I got the same error message AP> as you did. AP> Oh, and something more: why in a wolrd would somebody want to AP> call his classes like *that*? The Java spec says that it supports I18N characters for identifiers. While you probably don't want to use a name like that, there are times when a non English specking programmer wants to assign names to identifiers that are easier to remeber using his/her native language. In Japanese, for example, you could use Hiragana characters for the class name and using the nativetoascii tool convert the source to the \u notation. --Paolo
Re: BUG REPORT
>>>>> "AG" == Aaron Gaudio <[EMAIL PROTECTED]> writes: AG> It was my understanding that Java source code is only AG> guaranteed to work if it's ASCII, but I may be wrong about AG> that. No, you're right but the example give *is* ASCII. The spec refers to the encoding of the source, not the result in the .class file. The \u notation was introduced exactly to have a way of specifying Unicode in ASCII (I called it UniASCII :) ). Now, the problem is that Java uses the file system for the class names *and* the package repository. Many file systems don't support Unicode encoding in the names and that's way is usually ok to use Unicode in identifiers except class and package names. --Paolo
Some problems with jdk1.1.6v2 and Debian 2.0 Beta
Hi, Recently I have update my Debian 1.1.3 system to Debian 2.0 Beta. In this current version Debian has migrated to libc6. Therefore I have installed jdk1.1.6v2 for glibc. Now the problem is that some package, like Sun JavaWorkShop 2.0 have a change of color. Before the system upgrade, with jdk1.1.6v2 for lib5 all worked fine Have you any idea ? Paolo Sommaruga Garda Access Internet Service Garda (Vr) Italy
(no subject)
Your link at JDK 1.1.6 Linux Port Status has some trouble. Please check. Paolo ([EMAIL PROTECTED])
Re: JDK 1.2 Snapshots???
>>>>> "SB" == Steve Byrne <[EMAIL PROTECTED]> writes: SB> I'll do something that I'm going to no doubt regret in the SB> fullness of time: disclose my plans ahead of time. That's great, thanks. --Paolo
Re: Hatred of 1.2 messages
>>>>> "GG" == Gerald Gutierrez <[EMAIL PROTECTED]> writes: GG> I'm starting to get the feeling that many in this group are GG> approaching "when will 1.2 be out" messages with a very GG> disheartening attitude that will surely turn potential users GG> off. GG> They ask because they want it. There is an official release GG> for Solaris. The Windows JVMs happen to run way faster than GG> anything else. Yet, they ask about the Linux version. I agree with you, common politeness should be reinstantiated on the Net. When I started programming PCs I remember being helped from professioanal programmers and journaists on line, esplaining, with a lot of patience how to use common programming techniques. That experienced burned a permanent impression in my mind and today, after 15 years or so, I still try to return the favor because I know how much it's important to have some help when you most need it. Sun is the real problem here, I thank the people at blackdown for their effort, we all know that porting java to Linux is not their main job. Sun should pour more resources in this project. It's a shame that we don't have a Linux JDK after months of the release of Java 2. What is Sun thinking ? This is the best chance they had since Java was released. They should have more people dedicated to this task. Let them know how lousy is this situation, let's send them few undreds of email complaining. After all they announced Java 2 for Linux at the beginning of November, this is ridicoulous, how we are supposed to do our job if we are half year behind ? --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hatred of 1.2 messages
>>>>> "GG" == Gerald Gutierrez <[EMAIL PROTECTED]> writes: GG> Then the web page is only providing most potential users with GG> a table full of colors and very little information for which GG> they then look on the mailing list. I disagree, having that page with the table that shows the progress is quite valuable for me and other people in my company (borland.com). We licenced the JDK long ago and we have knowledge of what's in it. Seeing what remains to be tested with JCK gives us an idea of the progress done. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hatred of 1.2 messages
>>>>> "GG" == Gerald Gutierrez <[EMAIL PROTECTED]> writes: GG> Unfortunately those, such as yourself, who understand and care GG> about what's involved only constitute the minority .. the GG> "java-elite". I know many programming gurus at Motorola where GG> I work that can't care less what JCK tests java-linux has GG> passed. They simply a) expect it to work when its released and GG> b) want to know when it'll be released. I find the same GG> attitude amongst all those whom I know that care about GG> java-linux. Still, seeing a change of status in the chart is an indication of things improving and I believe that everybody prefer to see that things are moving instead of waiting for the end result. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Flex/Bison and Java
>>>>> "FBB" == Frank B Brokken <[EMAIL PROTECTED]> writes: FBB> Dear Java-list members, I'm looking for parser and scanner FBB> generators that produce Java sourcefiles, comparable to bison FBB> and flex. I once had a reference for a parser generator FBB> producing java sources, but I lost the reference. I *do* have FBB> references voor lexical scanner generators, e.g., FBB> FBB> http://www.informatik.tu-muenchen.de/~kleing/jflex FBB> http://www.cs.princeton.edu/~appel/modern/java/JLex/ ANTLR is the way to go. It's a parser generator with EBNF and automatic generation oj ASTs. Javasoft copied the idea with JavaCC but their implementation is not as complete. http://www.antlr.org -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: terrible fonts in linux-jdk1.2
>>>>> "Louis-David" == Louis-David Mitterrand <[EMAIL PROTECTED]> writes: Louis-David> Has anyone else noticed the fonts (or lack thereof) Louis-David> in Linux-jdk1.2? Everything seems to be in "lucida" Louis-David> or is it just me? I've tried using the Where did you get the jdk ? All the mirror sites I tried didn't have it yet. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: JDBC for Oracle?????
You can find the oracle jdbc driver on your Oracle CD or you can downloand it from http://www.oracle.com It works wery well with java 1.x on Linux. Bye Paolo Comitini On 24-Mar-99 Chien-Lung Wu wrote: > Dear firends: > I am a newbie of the JAVA and Oracle. However I have to install the Oracle on > my Linux box. I read some information said that JAVA 1.X can support JDBC. > Now > this is my question. > 1. If I want to use JAVA to access Oracle, can I have to install JDBC for >ORACLE? > > 2. Where can I get the JDBC, which can support ORACLE, if I need to? > > 3. Any more information? > > Thanks in advance. > > Chien-Lung Wu > > -- > Chien-lung Wu > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Paolo Comitini[EMAIL PROTECTED] Glisco s.a.s http://glisco.it Java and Linux Solution via Barattia 6 10010 Parella (TO) ITALY tel +39 0125 668005 This message was sent by XFMail -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: go back to gzip!
>>>>> "TB" == Tucker Balch <[EMAIL PROTECTED]> writes: TB> Is java-linux for kernel developers (100s of people) or the TB> linux masses (millions)? I suppose Debian includes it, but TB> RedHat 5.2 does not include bzip2, nor bzip2 capable tar. Sorry to contradict you but bzip2 is an option in the RH 5.x installer together with all to other compressors and MC handles bzip2 files just like other archives. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ...
I'm personally disappointed by Sun's reaction. In November they announced support for Linux, for the following months we got nothing from them and nothing when the pre v1 has been released. Linux is not even in the list of officially supported platforms, despite what they announced, and there's no way of downloading the current version of the JDK. This is not what I call supporting a platform. The great peopla at Blackdown.org did an excellent job but, I agree, the lack of news for such a long perios is frightening. It doesn't encourage to invest time and energy in doing Java development on Linux. --Paolo >>>>> "RK" == Riyad Kalla <[EMAIL PROTECTED]> writes: RK> [1 ] My intent here is not to RK> stirr up emotions or cause an argument. But after 12 RK> unanswered emails I feel I have a right to comment. And I RK> don't have patients for flames over this, so please don't send RK> them. If you were in my shoes you'd be as frustrated. RK> Is anyone else a bit disappointed and/or concerned about RK> Blackdown's progress with JDK1.2? I find no other means of RK> seeing where the current project stands because the only RK> information posted on the website is more than a month old and RK> all my inquiries about it over the last few weeks have all RK> gone unheeded. I find their efforts worth noting, but when RK> I've asked this question in the past I get the response of "do RK> it yourself if your so anxious" which I find amazingly stupid RK> and a waste of time. What goes into porting Java to Linux? I RK> admit I am not farmiliar with the process, however I would RK> still like an up to date record of their current progress. RK> Does anyone know if there is a work on Sun's behalf to do the RK> port themselves in the future or atleast carry Blackdown along RK> a little faster? RK> I've seen this question asked before on this mailing list, but RK> do not remember a reply ever being issued. RK> -- Riyad Kalla [EMAIL PROTECTED] CS Major University of RK> Arizona RK> [2 ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun/bashing
>>>>> "BK" == Bernd Kreimeier <[EMAIL PROTECTED]> writes: BK> Paolo Ciccone writes: >> I'm personally disappointed by Sun's reaction. BK> While I enjoy Sun bashing as much as anybody (in my case, I BK> have the 7+ years of working with and maintaining of Sun BK> equipment to justify it), let's be reasonable. BK> a) Sun doesn't owe us anything b) there is limited if any BK> gain for Sun in supporting Linux c) they don't have unlimited BK> resources The foundation for my frustration is based on few facts: 1) Sun pushed Java as a multiplatform language. The reality is that they develop only two versions. That's not covering two of the most used platforms in the PC arena: Linux and Macintosh. Too little for me to be truly WORA. 2) In November Sun publicly announced support for Linux. The announcement has not been followed, for what I can see, by facts. If you don't say a word than you owe nothing but if you promised you better keep the promise. People are investing time and money based on what Sun says. 3) Sun has nothing to gain in doing any port, Win32, Solaris or Linux. The JDK is given away for free and, for what I know, is not a *direct* revenue generator. Now, if you look at the BTS on the JDC you'll see that there thousands of requests for Linux JDK. If Sun judges the need to port the JDK to platform based on the number of users that want it then the Linux community showed some real numbers. 4) Granted, Sun doesn't owe us anything but it's them that are pushing for the adoption of Java. If they want that to succed they have to support Linux. They promised support and after six month we still have to see some concrete effort. As I said, there no trace of Linux JDk on Sun's Java site. BK> Java is a good tool to have. Thanks to published JLS specs, BK> open source efforts like Japhar and Kaffe have a reasonably BK> clear target for taillight chasing, and a legally acceptable BK> environment. Thanks to JDK source availability, ports were BK> possible. Thanks to the Blackdown team, we do get a stable JDK BK> port after a while. BK> If what we have is not good enough for you, then you have to BK> pick a different OS, or you have to support projects that will BK> some day remedy the current shortcomings. I thought I gave plenty of credit to the Blackdown team, in my last message and in other occasions. I believe you're totally misreading my post if you think I said that Linux/Java is not good enough for me. Do we have to accept everything as gospel or there is still freedom of speech ? Things are in a prettu good shape but we have a lot to improve in the Linux/Java front. Denying this will not fix the problem. The current status of the JDK is good for early development but the silence and lack of support *from Sun* is seriously joepardizing any professional Java development under Linux. You cannot relase a product in the market based on a pre-release JDK. You cannot announce release dates of your products if Sun doesn't give us a deadline for the final JDK release. In general, the feeling of not knowing what's going on doesn't encourage investing time and resources. I believe that anybody that worked in this industry and *shipped* products is very well aware of these facts. I'm not bashing Sun, I'm trying to post some constructive critique. Sun is, objectively, moving too slowly on the Linux platform. The sooner they realize this the better for us and for them. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun/bashing
u spell that word anyway? Vacuum CA> Which is always a good thing... but how many Sun managers do CA> you think read this list? How don't know how many but I know there are people from Sun reading this list. Again, I have limited time, if I write here is because I hope Sun will receive the message. See, I'm investing time based on known facts ;) --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ...
They are probably talking about HotSpot. --Paolo >>>>> "Riyad" == Riyad Kalla <[EMAIL PROTECTED]> writes: Riyad> [1 ] The following is complete Riyad> here say, but none the less interesting: Riyad> A professor of a friend of mine went to a SAP Training Riyad> conference and came back with the news that Sun is Riyad> currently re-writing java so it (speed wise) will be on par Riyad> with the likes of C or even faster. Its being rewritting in Riyad> assembler or something to that effect. I, of course, don't Riyad> know the details. Again this is a message from AFOAF (a Riyad> friend of a friend) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: JDK 1.X on Rh 6
>>>>> "PC" == Piero Campanelli <[EMAIL PROTECTED]> writes: PC> ok..ok this means that it is unstable and it isn't PC> usableis it? In other words i am really astonished about PC> fact that under Redhat 6 i haven't any way to develop in Java: That shouldn't a surprise since RH 6.0 has been just released. The decision to go with the new glibc was a RH one and the JDK porting team has no control over it. BTW, the JDK is not the only thing that is going to be broken, a lot of other applications will need recompilation using glibc 2.1, this is going to be fixed in the next few weeks/months. PC> * Kaffe is beta and works only on 1.0 API * jdk1.1.6 doesn't PC> work * jdk1.1.7 is a test version * jdk1.2 doesn't work PC> problem is the same: libraries. Is there someone that has fix PC> it ? See above. PC> this is strange. According to my experience, until some days PC> ago (with redhat 5.2 and jdk117-v2) java was very slow on my PC> linux system against implementation for Windows NT. (in the PC> past jdk1.0 was faster on linux than nt). Probalby in these PC> days i make an error...and now i ask to you: what is PC> difference between green_thread and native? If you use native PC> is faster? and green is a special library? Native threads are implemented by the OS and use the OS scheduler, gree threads are "cooperative" subprocesses completely handled by the JVM. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ...
Well, look at javac, it's a so called "self-executable" and it's basically Java. You can take a look at the code downloading the Solaris JDK. It's basically a C program that parses the command-line, starts the JVM and passes to it a given class to run. --Paolo >>>>> "RK" == Riyad Kalla <[EMAIL PROTECTED]> writes: RK> Is there a way to make a java program self executable on RK> linux? I know on the window platform some programs do, or RK> atleast used to compile into native code for you if you RK> wanted. But I was just wondering if this was an option on a RK> linux box so incase I wanted to distribute the file, i could RK> distribute it as a binary as well as source (for people that RK> wouldn't know hwo to compile it, etc. etc.) RK> Thanks! RK> -- (: Riyad Kalla :) (: CS Major - U of A :) (: RK> http://www.u.arizona.edu/~rsk :) RK> -- RK> To UNSUBSCRIBE, email to [EMAIL PROTECTED] RK> with a subject of "unsubscribe". Trouble? Contact RK> [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Java binaries as self executable.
I don't think this support works for classes store in a Jar file, does it ? --Paolo >>>>> "JM" == Jani Mikkonen <[EMAIL PROTECTED]> writes: JM> Linux kernel has support of "Misc executables" and Java JM> executables. With both of these options you can execute class JM> files straingt from command line. Documents say that with this JM> kernel option you can even run html files containing applet JM> tag only, thus making applets executable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Fixing spaced out fonts in JDK 1.2 pre-v1
Thank for this fix it worked beatifully. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: announcement
I disagree, given the nature of the announcement I found thjis extremely interesting. The post was short, to the point and about a free software. Given the interest expressed in the past by several people about Java and 3D I think this was appropriate. Regards, --Paolo >>>>> "GS" == Gunnar Stahl <[EMAIL PROTECTED]> writes: GS> Laura Young wrote: >> INT just announced they have released the Beta 2 version of >> J/View3D, a Java 3D toolkit. It's easy to use and you need >> little Java programming experience to use it. Basically it >> simplifies your ability to create sophisticated interactive >> data visualizations. It has a high level API and uses the >> model-viewer-controller paradigm. Best of all, it's free to >> download. Go to j-extreme.int.com to get it. >> >> -- >> To UNSUBSCRIBE, email to [EMAIL PROTECTED] >> with a subject of "unsubscribe". Trouble? Contact >> [EMAIL PROTECTED] GS> Please stop putting commercial mail into this technical GS> orientated mail-list. I don´t like this kind of GS> business-making! GS> Gunnar GS> -- GS> To UNSUBSCRIBE, email to [EMAIL PROTECTED] GS> with a subject of "unsubscribe". Trouble? Contact GS> [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: jdk1.2pre-v2
Steve, I just wanted to say that you guys are doing and awesome work. The new JDk is visibly faster and better. Thank you a lot. --Paolo >>>>> "SB" == Steve Byrne <[EMAIL PROTECTED]> writes: SB> We're trying to get the 2.1 build done tonight. Stay tuned... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems with jdk1.2-pre v2
I have a very big Java app with extensive UI and it works fine, must be something in your configuration. --Paolo >>>>> "SM" == Samuel McClure <[EMAIL PROTECTED]> writes: SM> Just downloaded and installed pre-v2. When I recompile old SM> java code and run it, however, my menu bar is all screwy. SM> Instead of saying "File" and "Edit" where it should, there are SM> just "_"s. Is this just a bug, or am I doing something wrong? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Something Special for Linux Developers on alphaWorks
>>>>> "OPD" == Osvaldo Pinali Doederlein <[EMAIL PROTECTED]> writes: OPD> That's great! I did see the announcements but I though the OPD> code was still in the distant future, as I didn't see a OPD> public splash of it. So, is 'vi' doomed now on Linux? :) Well, we just didn't to talk about vaporware even though JB has been tested on Linux for some time. Also we were waiting for a more stable JVM, JBuilder is one heavy application. As we said we are working on a multiplatform version that will be released for Solaris *and* Linux. As many of us know Java is "write once test everywhere" and there are indeed differences in the way it works between Solaris and Linux. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Something Special for Linux Developers on alphaWorks
>>>>> "OPD" == Osvaldo Pinali Doederlein <[EMAIL PROTECTED]> writes: OPD> Wow! This rocks. And will probably force the competition to OPD> go Linux too. As a partner of Inprise, I hope they're fast OPD> :) We're faster :), after annoucing the product several weeks ago we demoed JBuilder for Linux last week at the shareholders' meeting (together with our C++ compiler for Linux). Expect to see it soon in other computer shows and conferences. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Something Special for Linux Developers on alphaWorks
>>>>> "RR" == Ron Resnick <[EMAIL PROTECTED]> writes: RR> You wouldn't happen to know if JBuilder on Linux might also RR> mean an imminent release of Oracle JDeveloper on Linux, which RR> is itself heavily based on JBuilder? Sorry, I have no idea what Oracle will do. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: a filesystem standard for the JDK
>>>>> "NM" == Nelson Minar <[EMAIL PROTECTED]> writes: NM> Has anyone worked up a filesystem standard for the JDK on NM> linux? I've seen it installed all over the place on different NM> Linux systems. Maybe we can come up with a standard place to NM> put everything and make the world safe for RPMs and .debs NM> everywhere. NM> Is there a sensible Solaris standard? Anyone want to work on NM> this with me? That's a great idea, I'd like to participate. At Borland we are working on the Solaris version of JBuilder and we could not find a defined JDK standard location. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: a filesystem standard for the JDK
>>>>> "SM" == Scott Murray <[EMAIL PROTECTED]> writes: SM> Well, if the user buys Solaris 7 or installs one of SunSoft's SM> Production VM packages on a 2.5.1 - 7 box, then /usr/java SM> contains the JDK (as a link to /usr/java1.1), and SM> /usr/bin/java is a link to the "official" java executable. SM> Unfortunately, if the user needs/wants to use a Reference JDK, SM> then you're screwed, as there is no default install location SM> for them. Yeah, also the 1.1 JDK is not going to be good for everything so we need a standard in order to do JDK switching in a easy and safe way. SM> For the application I work on, we package the JRE to avoid the SM> hassle of finding a known "good" VM to run with on a given SM> system. Yep, same here. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Java IDE for Linux?
>>>>> "GP" == Guillermo Payet <[EMAIL PROTECTED]> writes: GP> Hello, GP> Can someone recommend a Java Development environment for GP> Linux? That is: an IDE to develop Java code, not necessarily GP> written in Java. I know that this is a shameless plug but we just finished showing publicly the first beta of JBuilder on Linux, scheduled to be released just after the Solaris version. It's 100% Java and runs on JDK 1.2. See http://www.inprise.com/about/press/1999/javaone.html for the announcement. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Working with many .java files
>>>>> "AC" == Kontorotsui <[EMAIL PROTECTED]> writes: AC> Hello, so far I worked using the good old xemacs + Makefile AC> combo. As soon as my application grow and more classes are AC> created, I'm beginning to feel the weight of a full scale AC> compilation (like 20 seconds now, but it's increasing fast) AC> even after I change 1 line of code in 1 class. AC> Now, I don't think there is a way to recompile only the class AC> I changed, like we did in C, is this correct? I remember AC> someone who wrote, weeks ago, about a tool that can check the AC> classes and make the compiler work only on the sources that AC> really need to be compiled again, but maybe I'm mistaken. The JBuilder compiler does automatic dependecy detection and minimal recompilation. Although the compiler, called bmj, was distributed as a .exe it's actually written in Java and we have it working now on Solaris and Linux as well. With bmj you recompile an entire package with a command like this: bmj -sourcepath ./src/java -d ./classes -p com.mycompany.mypackage bmj will find all the package dependedncies and the set of files that need to be recompiled. If you are in the Primetime (JBuilder for Unix) beta you can look at the bcjbmj.jar file. Otherwise you can use wine to run the bmj.exe included with JBuilder. --Paolo JBuilder development team. Inprise corp. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: borland/inprise jit for blackdown 1.2pre2
On Mon, Sep 27, 1999 at 03:54:21PM -0400, Tim Reilly wrote: > I took a look at this, and am intrigued. Can anyone comment on > how stable the combination of this JIT and the 1.2 pre-release might be (I > realize it'd be unlikely that anyone's tested this combination yet, I'm > more concerned with the maturity of the 1.2 JDK)? Well, we tested it, among other things, with one very large application : JBuilder. The JIT showed a good speed increase while being very stable for the current state of the JDK. This version of the JITs not final and there is a forum to discuss bugs, so if you find any please post how to reproduce them. -- Paolo Ciccone JBuilder dev. team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: borland/inprise jit for blackdown 1.2pre2
On Tue, Sep 28, 1999 at 04:30:33PM -0500, Burkhart,Kelly wrote: > > > What performance does a JIT improve? Are you talking about the time to run > an uncompiled application with this JIT vs. another JIT (i.e. performance > improvement is in the JIT compilation not in running the application)? Or > are you saying that the compiled code from this JIT is faster than the > comiled code from javac or jikes? A JIT compiles in memory, on-the-fly, Java bytecode into machine code. The result is, for code that is executed more than once, a big improvement in execution speed of your applications. The javac compiler is itself a Java application, using a JIT will improve compilation time as well. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: required Libraries
On Wed, Oct 06, 1999 at 11:18:13AM -0400, Jacob Nikom wrote: > Hi, > > I am interested in this discussion, but I am trying to convert it > into more plain English. I always thought that the lightweight > components are peerless. Swing still needs some heaviweight componentes, namely the AWT Frame, to do basic communication with the underlying GUI. This is true for all platforms. >They don't need X libraries and work "directly" with OS and hardware. This is simply not true. Swing does not have any interface with the hardware, that would make it really heaviweight and completely platform dependent. In addition interfacing with the OS doesn't provide graphic management on Unix were the OS and GUI are two, fortunately, separate entities. On Window and MacOS the distiction is blurred, in that case the AWT basic services connects to the GUI API and Swing operates on top of this interface. > Swing was claimed as lightweight component based package, so it > should not need X or Windows. See above.Without connection with X or Windows how do you do GUI management ? > On contrary, AWT was claimed to be > heavyweight based component package, that is why it needs X - is it > true? Is it different on Solaris, Windows or Linux? AWT was attempting to create a peer class for each GUI element. This approach doesn't work on multiple platforms since diferent GUIs have different features. AWT was forced to be limited to the lowest common denominator. Swing, requiring only some basic heaviweight services, can create the same type of UI on multiple platform even providing features that are not present in the native GUI. > Also, "libXm appears to be statically linked into libawt.so" - does > it mean that X modules were compiled and placed into libawt.so > library, so in reality you call X, but you don't need to link with > it? libXm is actually part of Motif, not X. AWT uses Motif in the peer classes. Likewise the first implementation of AWT for Windows used MFC. Motif provides the Frame, cut-and-paste and other basic services for AWT and in turn Swing. You have two options with Motif: static and dynamic. With dynamic linking the user must have an installed version of Motif in order to run you application. Since Motif costs a lot of money you cannot put this constraint to you users . If you statically link the Motif library the whole issue goes away. That's what Netscape does. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Java on RedHat 6.1
On Thu, Oct 07, 1999 at 10:49:58AM -0700, Dan Iuster wrote: > RedHat has just released the 6.1 version of Linux. I am curious if > anyone has had any experience with the 1.1.7, 1.1.8 or 1.2 JDK and JRE > on RedHat 6.1. I have some rather large applications to port, and I > would like to know if there are any known pitfall introduced by the new > kernel. I believe 6.1 is based on the 2.2.12 kernel. I don't know about RH 6.1 but I'm using Mandrake 6.1 with kernel 2.2.13 and JDK 1.2 works normally. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Java on RedHat 6.1
On Thu, Oct 07, 1999 at 11:18:43PM +0100, Rachel Greenham wrote: > Paolo Ciccone wrote: > > > > On Thu, Oct 07, 1999 at 10:49:58AM -0700, Dan Iuster wrote: > > > RedHat has just released the 6.1 version of Linux. I am curious if > > > anyone has had any experience with the 1.1.7, 1.1.8 or 1.2 JDK and JRE > > > on RedHat 6.1. I have some rather large applications to port, and I > > > would like to know if there are any known pitfall introduced by the new > > > kernel. I believe 6.1 is based on the 2.2.12 kernel. > > > > I don't know about RH 6.1 but I'm using Mandrake 6.1 with kernel 2.2.13 and > > JDK 1.2 works normally. > > Um, I hadn't heard 2.2.13 was out. Are you on a pre? No, just the downloaded Mandrake 6.1 I noticed that the latest advertised kernel is 2.2.12 but uname -a on my system reports 2.2.13. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Benchmark results for Linux JVMs (formatted for 70 columns)
On Tue, Oct 12, 1999 at 08:51:29PM -0500, Chris Abbey wrote: > > >A # indicates that the run failed validity checks. > > poor bor...er...inprise You can use Borland :). Anyway, the result is not bad since the JIT has been released as a public Beta test and we'd like to know more details about icomaptibilities or bugs. After all that's the purpose of beta testing :) -- Paolo Ciccone JBuilder dev. team. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: escape character
On Fri, Oct 15, 1999 at 03:57:50PM -0600, Yohans Mendoza wrote:
> hi all, I was under the impression that the escape character in java was
> \.
> is that correct?
It depends. If your talking about string literals your correct. If you need
to escape some characters in strings used for MessageFormat than the story
is different. In that case you need to escape "{" with single quotes and use
double single quotes to escape a single quote.
--
Paolo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can we run Java app from a CD with Blackdown?
On Fri, Oct 15, 1999 at 01:37:10PM -0500, [EMAIL PROTECTED] wrote: > Hi: > > We got a few questions on deployment with Blackdown. It would be > appreciated if someone could help. > > Q1: After we finish a Java application development on Windows NT 4.0 (Intel) > with VisualCafe 3.0, is it possible to include everything** on a CD, and let > user run the Java application from the CD on Redhat 6.0 Linux (Intel) > without any installation or file copy? Sure, you have to test it carefully as you probably want to provide a way for the user to run the app without invoking the JDk manually. You'll have to write a shell script for that. > Q2: Can we use Blackdown in this way (i.e. from a CD without installation), > or we have to install it first? If you copy on the CD the installed version of the JDK/JRE and you set the PATH correctly you can run it directly. Let's say you have the jdk in a dir called lxjdk on the CD and the CD is mounted on /mnt/cdrom (default on RH). You'll need to add /mnt/cdrom/lxjdk/bin to the PATH. of course you need to find the correcte path (use pwd in the shell script) because the mount point for the CD could be different. For example I use to remap mine to /cdrom. > Q3: If we can use it without a installation, then which Blackdown files > should be included on the CD, and any special file structure? Just install it on a machine and then copy the tree in the CD. > Q4: Does Blackdown JVM generate any temporary files during running? We plan > to use a CD-ROM not CD-RW, so can't add any temp files to the CD. Under Unix temporary files are written to /tmp, usually mounted on a HD partition, not the current directory so that shouldn't be a problem anyway. I'm not aware of temp files created byt the VM. > Q5: Is there any JRE for Linux like the one for NT? Yes. Just download the JRE archive. -- Paolo Ciccone JBuilder dev. team. Borland/Inprise. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: JIT For linux??
On Mon, Oct 18, 1999 at 03:41:05AM -0600, Robert Simmons wrote: > Greetings, > > Is there a functional version of the JIT that works with the 1.2 Jdk on > linux ? I would love to install it before things get messy in my app. Ive > build most of the structure and now Im adding content like crazy and I could > easily see this think working on 20 panes in a tab pane all at once. Without > a JIT it could be SLOW. The Borland JIT is available for free at: http://www.borland.com/about/press/1999/jitlinux.html -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Visibroker for Java 3.4
On Tue, Nov 09, 1999 at 11:42:44PM -0200, Luis Claudio Santos wrote: > Hello, > > Can anybody HELP ME, PLEASE :-( ? > > I'm using Linux RH 5.2 and JDK1.1.7. > I download the Visibroker for Java 3.4 (linux version) from >http://www.inprise.com/downloads/. > After I followed all the instructions for instalation I tryed some commands and >...: > > 1) [root@lc bin]# oadj -help > ISO-8859-1: unknown locale > > 2) [root@lc bin]# java2idl > ISO-8859-1: unknown locale hard to say without knowing more details about your OS config. Are you using KDE ? Anyway, your locale seems to be set incorrectly. Check the value of the locale variables (LANG, LC_ALL,LC_TYPE,LC_COLLATE,LC_MONETARY, LC_NUMERIC, LC_TIME). You might also want to chek the correct names for the the locales on your system using "locale -a". -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A Java parser
On Wed, Nov 17, 1999 at 06:08:54PM +0100, Kontorotsui wrote: > > Suppose I want to do a tool that parses the java code and modifies it. > > What do you advice me to use? Are there java parsers for Linux? > If the answer is negative, what can I use? Perl (*groan*)? Take a look at ANTLR (http://www.antlr.org), it's a parser generator written in Java that outputs Java and has a Java grammar available in the package. ANTLR is quite different from Lex/Yacc and, among other things, uses EBNF, generates tree walkers and tree transformation. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IDE's
On Fri, Nov 19, 1999 at 07:08:13AM -0600, Glenn Holmer wrote: > The no-brainers that made the list right away are Visual Age, > JBuilder, and NetBeans, because they all run (or will soon) on > Linux. Can anybody give opinions or sources of info that will > help us with this decision? What I want to prepare is a feature- > for-feature comparison. Some of the main features of JBuilder: - 100% Java. - CodeInsight: shows dynamically the completion of the method and the arguments while your typing. - Dynamic syntax check shows error in code before you compile - Full support of JDk 1.2 - Visual Designer with two-way tool (you change the code in the editor and the designer updates the view). - Debugger with handling of deadlock in Threads. - Integrated and command-line compiler with true dependency checker and minimal compilation. - Remote debugging. - Applet,Servlet,Javabean support. - OpenTools architecture to extend the IDE with add-ins. - Extensive on-line help. - Available for Solaris now, Linux very soon. -- Paolo Ciccone JBuilder dev. team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem in running Jdk1.2.2rc2 Demo on redhat 6.1
On Tue, Nov 30, 1999 at 02:45:52PM -, John Louis wrote: > Hi, > I try to run the SimpleExample, it give me these error: > > Exception in thread "main" java.lang.InternalError: Can't connect to X11 window > server using ':0.0' as the value of the Display variable. > at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) > at sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:62) > ... If you have X running than it could be a matter of access rights. From another terminal window type "xhost +" and then run the program again. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IDE's
On Wed, Dec 01, 1999 at 04:25:47PM -0600, Greg Tomalesky wrote: > Hi: > > JBuilder3 is ok. I has some serious(IMHO) shortcomings. I will > enumerate: I'll use the Solaris edition, just released, to answer to this. The Linux version, under development and demoed at the last LWCE, uses the same code since JBuilder is now 100% Java. > 1. No GUI way to define JTable data model or other JTable helper classes > such as TableHeader or ColumnModel All these properties are accessible from the property list in the Visual Designer together with many others. > 2. No GUI way to modify tab labels in a JTabbedPane. This is available, just type the label in the related property in the designer. > 3. No GUI way to add icons to buttons etc. Again this is accessible from the designer. I hope this addresses the problems you mentioned if there is any suggestion about JBuilder or other Borland products please send us feedback, we have set up a community website just for this, see http://community.borland.com or http://www.borland.com Regards, -- Paolo Ciccone JBuilder dev. team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: R:Re: IDE's
> 1) It's a seriously heavy program; it needs around 128 - 256 MB ram for the > IDE to run smoothly. > 2) It's still quite unstable (version 2 was hopeless), unless you keep > strictly to the non-Visual parts of the IDE. When we switched to 10% Java code we actually reduced the memory footprint. The past three versions had to deal with the Delphi runtime environment and the JVM loaded plus some overhead because of the communication of things like the editor buffer between the IDE (Delphi) and the Designer (Java). The Solaris, and Linux, edition don't have this problems since we only use a JVM. It's still a big program, we address a lot of development needs, but it's much more usable and stable. > using it as a straight editing IDE, though, I've found it to be excellent. :) Thanks, I believe you'll like the new version a lot more. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IDE's
On Thu, Dec 02, 1999 at 08:56:07AM -0600, Greg Tomalesky wrote: > Hi Paolo: > > That Solaris edition must be way newer than the demo CD I have: Yes it is, we actually officially announced it few days ago. PrimeTime, the code name for the Solaris edition, is a new codebase for JBuilder. The first three versions of JB had about 30% of Delphi code. With PrimeTime we replaced all native code with Java and the result is highly multiplatform. While PrimeTime has been released for Solaris the Linux version will follow soon. > I was able to set the tab labels via the "constraint" parameter of an > embedded jPanel. I still can't see where to set the icon of the tab or of > any buttons. The model parameter for the jTable shows as when I > select it and complains when I complete the selection. So based on this > version/build of the demo my original concerns are mostly intact. Yes they are, that's why I referred to the Solaris edition. Since this forum is about Java and Linux the right reference point is PrimeTime, the version that will be available on Linux, instead of the JBuilder for Windows. In rewriting part of JBuilder we improved several things: designer, debugger, OpenTools, editor (Emacs emulation). Stay tuned, it's going to be exciting. --Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: R:Re: IDE's
On Thu, Dec 02, 1999 at 10:11:06AM -0800, Paolo Ciccone wrote: > > When we switched to 10% Java code we actually reduced the memory footprint. Of course this was "...100% java code..." :) -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IDE's
On Thu, Dec 02, 1999 at 02:09:30PM -0500, Joseph Shraibman wrote: > Paolo Ciccone wrote: > > > The main problem I had with Jbuiler (enterprise 3 demo for windows) was that it > wouldn't let me specify a classpath to use in compiling so I could not compile my > program (that used the quicktime jsdk from apple). Have you tried the "Required libraries" page in the project properties ? This is used to add the java packages that you depend to. We compile JBuilder with JBuilder and for sure it supports pointing to other packages :). -- Paolo Ciccone JBuilder dev. team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IDE's
On Fri, Dec 03, 1999 at 01:58:40PM -0500, [EMAIL PROTECTED] wrote: > > > On Thu, 2 Dec 1999, Paolo Ciccone wrote: > > > On Thu, Dec 02, 1999 at 02:09:30PM -0500, Joseph Shraibman wrote: > > > Paolo Ciccone wrote: > > > > > > > > > The main problem I had with Jbuiler (enterprise 3 demo for windows) was that it > > > wouldn't let me specify a classpath to use in compiling so I could not compile my > > > program (that used the quicktime jsdk from apple). > > > > Have you tried the "Required libraries" page in the project properties > > That is grayed out on my demo version. Ok, well, it works in the full verison. > And what's with the auto-indent not working? I don't know about that, it's the first time I here problems about it. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Tue, Dec 07, 1999 at 09:19:28AM -0500, Scott Murray wrote: > I'm praying that the Blackdown team continues it's work if this is what Sun > consider a useful release. I'm really curious as to why the hell Sun and > Inprise went off on their own when the Blackdown port is available... Besides extensive testing (full JCK) and performace tuning, this version includes JPDA and several Swing bugs that we found while developing JBuilder Solaris edition. -- Paolo Ciccone JBuilder dev. team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Tue, Dec 07, 1999 at 03:47:23PM +, [EMAIL PROTECTED] wrote: > I though the current 1.2.2 rc was 3, not 1? Have Sun picked up an older copy > to release on their site? The Sun/Inprise port is not the same of Blackdown's, that's why the release number is different. The Sun/Inprise port is actually the latest codebase from Sun and includes several fixes to Swing that were found in the stock 1.2.2 release. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Tue, Dec 07, 1999 at 06:15:14PM +0100, Robb Shecter wrote: > Paolo Ciccone wrote: > > > ... this version > > includes JPDA and several Swing bugs that we found ... > > Do you mean "bug fixes?" Yeah, I still have to get my first coffe :). -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Tue, Dec 07, 1999 at 12:31:28PM -0500, Scott Murray wrote: > Without native threads support, this release is IMO useless for running > any kind of serious Java applications on Linux. I disagree, we have a couple of very big applications running under this JDK, including JBuilder, and the performance is good. Now, I understand that some applications need native threads but a many others can run ok with green threads today. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Tue, Dec 07, 1999 at 04:39:07PM -0500, Derek Glidden wrote: > Paolo Ciccone wrote: > > > > On Tue, Dec 07, 1999 at 03:47:23PM +, [EMAIL PROTECTED] wrote: > > > I though the current 1.2.2 rc was 3, not 1? Have Sun picked up an older copy > > > to release on their site? > > > > The Sun/Inprise port is not the same of Blackdown's, that's why the release > > number is different. The Sun/Inprise port is actually the latest codebase > > from Sun and includes several fixes to Swing that were found in the stock > > 1.2.2 release. > > Not to dis you or your company's efforts, but if this is actually a > "clean" implementation of the JDK straight from Sun sources and never > having touched the Blackdown code, then I find the contents of > jdk1.2.2/jre/README.linux to be rather suspicious: > > README.linux for Java 2 SDK Version 1.2.1 for Linux, pre-release 1 > Steve Byrne > 29/8/1999 > > This is the Blackdown Java-Linux port of the Java 2 SDK Version 1.2.1. > > [etc...] > > It looks like either someone at Inprise or at Sun isn't playing fair. We actually are. We didn't say that this is a clean port, in fact we are giving credit to Blackdown for the port. This has been done with the press at the Java Expo in New York and I personally posted here and on /. about our use of the early patches from Blackdown. The story is simple, we took the patches for 1.2.1 and started working on 1.2.2. From that early effort, fundamental to start the port, we actually added a lot of other stuff. The AWT/Motif for example has been completely replaced and a lot of other fixes have been added. This is truly a collective achievement, starting froim the early effort of Blackdown and then accelerated by Sun and Inprise and brought to a level of stability and performance that we feel is acceptable before the release of 1.3/Hotspot. My previous post, that you quoted, was about the RC1/RC3 naming, the two ports are indeed different and I wanted to clarify some of the confusion. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Blackdown JDK vs Sun JDK
On Tue, Dec 07, 1999 at 10:52:02PM +0100, Juergen Kreileder wrote: > AFAIK Sun has all the right to use our code. But todays press release > is a slap in the face for us! Juergen, as I posted in other messages we are actually giving you guys credit for all the hard work you have done in the 1.2, 1.2.1 version. Unfortunately both press releases didn't have any mention but we have already released interviews with the press were we acknoledge your work. As you can immagine, if we wanted to hide anything, we could have change the files. That was not our intention at all. As I said before this is really a cooperative effort that shows what can be obtained when there's will to improve things. You guys gave us the ground to convince the right people to sponsor this project. We have, in our modest opinion, produced a production quality JDK. If the two things can be merged this will go just at benefit of all community. As you know very well porting and testing the JDK is quite a task. It has not been cheap to do it and we took the risk of doing it while another port was under way. As somebody said, competition is good, especially in a case like this where the outcome benefit only the developers of Java applications. I believe that from today it's clear to anybody that Linux is a viable platform for Java applications. On a similar like for JDK 1.3 Sun announced that they are going to do a Linux port directly. At the same time Blackdown is working on early code and we saw that some of the early patches are included in the standard 1.3 code. At the same time IBM announced their porting effort. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Tue, Dec 07, 1999 at 06:28:29PM -0500, Jacob Nikom wrote: > But it does matter how it was claimed. If the work was done by > Inprise it is one thing, if it is only relabeling of Blackdown > code, it is another. yes, that would be plain and simple theft. We didn't "relabelled" Blackdown JDK, why should we do something like that ? To piss off a lot of people ? No, we started from the Blackdown patches for JDK 1.2.1 and then, after many weeks of feverish work, produced a JDK 1.2.2+patches+JPDA that is the result of the work of Sun and Inprise programmers and testers. Not many people realize how much work is involved in this. Running the JCK alone, on fast iron, can take a whole day. The simple API testing is about 4 hours. If you mess around with this you have to restart it. Believe me, if we had the feeling that Blackdown wa going to produce a JDK 1.2.2+JPDA in time we would gladly have saved the time :) -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Wed, Dec 08, 1999 at 01:03:25AM +0100, Juergen Kreileder wrote: > > Early effort... Come on. > > Getting the VM running is the major part of the port. The step from > 1.2 to 1.2.2 is so small that it nearly doesn't effect the port at > all. Well, you're free to think in this way but we had a lot of work on this. The patched version would compile but not run. We started from the 1.2.1 patches and fixed things until we passed the JCk clean. Nobody denies the great work that you people have done, I hope you read my other posts here and also on /. > >From what I see the speed difference mainly comes from using a > different JIT compiler. No, for example, we found some problesm in Runtime().exec() with green threads that caused a dramatic slowdown in some situations, in particular trying to debug an application in JBuilder and used the editor at the same time. Other problems were addressed by Sun for the AWT/Motif side. We also did a lot of testing for International support. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Tue, Dec 07, 1999 at 08:37:11PM -0500, Scott Murray wrote: > I don't really mean to be a bastard here, but here's an excerpt from one > of your postings to this list earlier today: > > The Sun/Inprise port is not the same of Blackdown's, that's why the release > number is different. The Sun/Inprise port is actually the latest codebase > from Sun and includes several fixes to Swing that were found in the stock > 1.2.2 release. > > What were we supposed to think? My reply was to somebody that wondered why Sun was posting RC1 when Blackdown had released RC3. My answer was just to point out that the two are not the same and in fact they are not. The above statement should also read "... fixes to Swing that were not found in the stock 1.2.2 release." > As well, I've read three different press > articles on this today, and none of them contained the word "Blackdown". > If Inprise/Sun wanted to give credit to the Blackdown team for providing > a base for their further work, I would have expected something, especially > since the press releases for this were delayed several days. The credit should be clear in other articles that should appear on the press. Our folks at Java Expo have been clear about it. Give it a little more time. > It's not like > Sun doesn't know about the Blackdown team, they made them a licensee last > year with great fanfare. Yep, and I can't talk for Sun, as a matter of fact I'm not a spokesperson for Inprise either but just one of the developers. So while I don't know if Sun is going to give credit to Blackdown for the work done on the JDK, we at Inprise are doing our best to recognize the effort and time spent by these people. Actually I would love to see the effort of both groups merge to have the best of both worlds. We truly ported this JDK in parallel and the release of the Blackdown 1.2.2 was a surprise for us. It will be probably problematic to extacly figure out the exact difference but I would love, for example, to see the native threads working in the Sun/Inprise port. Also, I don't know what is the base for Blackdown port but our port is based on 1.2.2-004. The bottom line, and I didn't see a post about this, is that now Linux has a fully functional JDK/JRE that can be used to port thousands of applications. For many companies this was the key factor to adopt Linux. Another consequense of Inprise advocating for this port (yes, we had a lot of talks with Sun to convince them to be directly involved in this) is that now Sun is giving Linux equal treatment and future releases of the JDK will be ported to Linux together with the other two main versions: Windows and Solaris. This is a big improvement and is another key factor in evaluating Linux as a viable platform. The MacOS still today has no Java 2 support, for what I know. Trying to close with a positive note...this is just the beginning for Java on Linux, hold on tight ;) -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Blackdown JDK vs Sun JDK
On Wed, Dec 08, 1999 at 03:15:32AM +0100, Juergen Kreileder wrote: > I didn't say so. I don't have problems with somebody using our code. > This is about respect! What we have now is stuff like: > > 'The Sun/Inprise JDK is xx times faster than that Blackdown crap.' > > 'Finally! Those script kiddies at Blackdown didn't have a clue' > > You get the song of praise --- we did the dirty work. Well, first I didn't see anything like that and I hope it will never be posted. Second, everybody knows that you have been the first to port Java to Linux. I personally mentioned your JDK in all the demos I have done of JBuilder for Linux at our user conference (~3000 people) in Philadelphia and during the LWCE. I hope also the interviews with the credit to your work will appear soon. > Paolo> As I said before this is really a cooperative effort that > Paolo> shows what can be obtained when there's will to improve > Paolo> things. You guys gave us the ground to convince the right > Paolo> people to sponsor this project. We have, in our modest > Paolo> opinion, produced a production quality JDK. If the two > Paolo> things can be merged this will go just at benefit of all > Paolo> community. As you know very well porting and testing the > Paolo> JDK is quite a task. It has not been cheap to do it and we > > Do you think our port was cheap? We don't get paid for our efforts > and expenses. I never said so, my point is that no company will sponsor a project like this if there's a way of avoiding it. From the balance sheet there's just cost and no profit. We had to allocate additional resources and had to work on two, no, three projects: the JDK, JBuilder Solaris edition and JBuilder for Linux. In addition to this we had a deadline set. > How can there be competetion when people working on the Sun/Inprise > JDK are on our internal mailing list and have access to our CVS > archive? Ok, the fact are as follows, you can believe my words or not. We started with the patches for 1.2.1 and applied them to Solaris JDK 1.2.2. From that point on we didn't take any other snapshots and just fixed the problems as we found them. The first attempt compiled but didn't run and JPDA didn't work at all. The mailing list was actually not reporting anything about the on going 1.2.2 Blackdown port, we were surprised like anybody else when we saw your RC1. From the point of applying the patches to the final release, this has been a parallel effort. Juergen, I'm truly sorry of all these misunderstandings, I hope you'll see that we didn't mean to harm your excellent work in any respect. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A few words on SUN/Inprise and Blackdown
On Tue, Dec 07, 1999 at 10:21:26PM -0500, Will Koffel wrote: > I won't incriminate my source on this, but as I understand it, Sun > has been using an inhouse version of JDK1.2 for *many* months. > It's possible that Sun just gave that away to Inspire for the "right" > price. Why there should be money involved ? We've been licensing JDK from version 1.0. The port was done using the publicly available patches posted by Blackdown and the source of the Solaris JDK we get for being licensees. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Wed, Dec 08, 1999 at 12:07:07AM -0500, Nelson Minar wrote: > I think we can all work together on this. A lot of us in the Linux > community are annoyed and mystified by Sun's years-long snubbing of > Linux in the Java world. It honestly makes no sense. The press release > that came out today did no good, either, ignoring the Blackdown > contribution entirely. But I think we're all happy to see Inprise > devote effort to a Java/Linux port. Thank you! You're very welcome, yours is one of the few positive messages I got today :) > I think Inprise could help repair some bad feelings by making some > official statement of thanks and respect to the Blackdown community. > It never costs you to pay your props. A Slashdot story would be one > good way to do this, or a letter to Linux Weekly News (publishes > Thursdays), or even a note on your own release page. Hopefully this has already been taken care of. > It would be helpful if you made sure the Inprise team gets a summary > of the discussions here. Ok. > I have to disagree with you on the rest of this, though: > > >The bottom line, and I didn't see a post about this, is that now > >Linux has a fully functional JDK/JRE that can be used to port > >thousands of applications. > > No, Inprise is the third Linux JDK/JRE that can run thousands of > applications. Blackdown was there at the beginning, and IBM beat > Inrpise to it too. Inprise is different in starting out with JDK 1.2. > Smart move and useful, I think. But again, Blackdown was there first. > You're even using their code. Yes, I'm not denying this, my point was that today, because of both ports and the combined effort of Blackdown and Sun/Inprise the Linux community has a Java implementation that can compete with the ones of Solaris or Windows. The current IBM port,1.1.x, is of no use for us because we need full JDK 1.2.2 support Previous versions of the JDK were not mature enough to make it feasible for us to write the entire JBuilder IDE in Java. Today's version is completely native-code free and runs at the right speed. JBuilder stresses the JDK so much that even the stock 1.2.2 is not enough, in fact our Solaris release requires 1.2.2-004. It's not that we are picky, we just couldn't implements some features without some code fixes. An example. JBuilder has Emacs emulation, with the standard Swing of 1.2.2 if you press Alt-d or Ctrl-space Swing will pass also the "d" or the blank in the editor. While the event is processed correctly the extra character is unaccetable, at least for us. Probably we are not the only ones that found this bug, hopefully other developers will benefit from this fix. > Well, no, the beginning was several years ago. And we've been hanging > on tight, and advocating, and a few folks have worked their asses off > building a codebase that wasn't even acknowledged in the press > release. Can you understand why people are a bit annoyed? I can understand it and I have been in the chorus with all the others screaming and being ridiculized because of that. It's the story of my life, some of us are just born wired to swim upstream :) My comment was a hint of things to come... -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Blackdown JDK vs Sun JDK
On Tue, Dec 07, 1999 at 09:28:45PM -0800, Nathan Meyers wrote: > The drama never ceases. This is not a business for the faint of heart > :-). Not ideed :) Great post Nathan. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Questions to SUN, blackdown, inprise
On Wed, Dec 08, 1999 at 08:55:25AM +0100, Jan Buchmann wrote: > What I don't understand is: Why didn't Inprise ever contact or support (testing and >bugfixing) the > Blackdown team in their porting effort, if they just wanted to have (and this seems >to be the case) > a production quality JDK1.2.2 for running JBuilder on Linux? We did but we didn't get any answer back. > Will there ever be a bugfixed sunwjit? It's called Borland JIT :). Seriously the latest JIT is included in the Sun/Inprise JDK but you can use it with any other JDK 1.2 if you want. At present time there are no plans to port the JIT to other architectures than Intel. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sun and Inprise Java 2 announcement
On Tue, Dec 07, 1999 at 07:18:08PM +0100, Peter Schuller wrote: > > running the Linux kernel v 2.2.5 and GLibC v 2.1, 32 megabytes RAM > > Why on earth would it only support 2.2.5? Why not any 2.2.x kernel? > Is there any difference that is significant for a JDK? > > I'm downloading it anyway to see if it works on 2.2.13... It works with 2.2.x, don't worry. I tested on Mandrake 6.1. I believe the 2.2.5 is just because we didn't test it with anything older than RedHat 6.0. -- Paolo Ciccone JBuilder dev. team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Questions to SUN, blackdown, inprise
On Wed, Dec 08, 1999 at 06:54:44PM +0100, Jan Buchmann wrote: > On Wed, Dec 08, 1999 at 08:29:04AM -0800, Paolo Ciccone wrote: > > On Wed, Dec 08, 1999 at 08:55:25AM +0100, Jan Buchmann wrote: > > > > > What I don't understand is: Why didn't Inprise ever contact or support (testing >and bugfixing) the > > > Blackdown team in their porting effort, if they just wanted to have (and this >seems to be the case) > > > a production quality JDK1.2.2 for running JBuilder on Linux? > > > > We did but we didn't get any answer back. > Did you tell them that you're making a port for SUN too? No, because when we contacted them we were not doing it. > So sunwjit.so in the blackdown-port is the same as javacomp.so? No, javacomp.so is the JIT included in the Sun/Inprise JDK. Since out JIT is faster and has less bugs we thought there was no point in updating sunwjit. > Is the float-integer-comparison-bug fixed in javacomp? Never being there in first place. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Questions to SUN, blackdown, inprise
On Wed, Dec 08, 1999 at 07:52:02PM +0100, Jan Buchmann wrote: > On Wed, Dec 08, 1999 at 07:20:46PM +0100, Juergen Kreileder wrote: > > No, sunwjit and javacomp are two different products. sunwjit is what > > we get from Sun (actually they bought this JIT from another company) > > as a binary. javacomp is Borland's JIT. > > > > I'm not sure if we'll ever see a fixed version of sunwjit as Sun seems > > to have given up with this product. We can't fix the bug ourselves as > > we don't have the source code. > > Did you contact SUN about what has happened and far more important about what will >happen in the future (JDK 1.3) with the blackdown-port? > > Maybe you can get Inprise to let them distribute javacomp with RC4 (Paolo?), since >both ports are SUN-ports. Our JIT has been free for download from our website for quite a while (http://www.borland.com). The version that is included in our JDK is basically the same with some fixes we have done in the last couple of months. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Questions to SUN, blackdown, inprise
On Wed, Dec 08, 1999 at 07:14:11PM +0100, Juergen Kreileder wrote: > >>>>> Paolo Ciccone writes: > > Paolo> On Wed, Dec 08, 1999 at 08:55:25AM +0100, Jan Buchmann wrote: > >> What I don't understand is: Why didn't Inprise ever contact or > >> support (testing and bugfixing) the Blackdown team in their > >> porting effort, if they just wanted to have (and this seems to > >> be the case) a production quality JDK1.2.2 for running JBuilder > >> on Linux? > > Paolo> We did but we didn't get any answer back. > > As said before you never contacted me or Kevin. True, I believe we contacted Steve. Don't take this as a criticism, I'm just trying to provide positive feedback, but it's hard to target a group of people. We didn't get any news from this list for weeks and when we tried to contact some of you we didn't get any answer. If we look at other porjects there's usually an acknowledge contact or project leader that can channel all the requests. This is, IMHO, a more efficient way of handling communication. All this mess is, again IMHO, just a communication problem. Anyway, I reported our past email exchanges and the results should be visible soon. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Questions to SUN, blackdown, inprise
On Wed, Dec 08, 1999 at 07:44:24PM -0500, [EMAIL PROTECTED] wrote: > I had a single communication with the VP of engineering at inprise, telling > me that they were interested in dedicated some resources to assist with the > port. I provided him with Steve Byrne's contact information and that was > the last that I heard of it. If Steve wasn't answering, I would have been > more than happy to redirect the inprise contact to the primary porters. Well, I'm glad that you can confirm our version. AFAIK we never got anything back from Steve and we asked several times. I'm not blaming Steve at all with this, we know you have daily jobs and you don't have much time left. We just figured that there was nothing wrong in attempting the port by ourselves. We needed 1.2.2 to run JBuilder and at that time Blackdown didn't answer any of the questions asked by several people in this list about plans for 1.2.2 and JPDA. After not receiving replies to our offer of help we went ahead and tried the port. As todays we announced the availabily of JBuilder for Linux, free for anyone to download, you can see that our effort was clearly targeted for this deadline. I said it before in this forum, when a commercial company makes plans for future products it needs reliable schedules and plans. We knew we couldn't ask this to an organization of volunteers and so we just decided to "roll our own" JDK. I believe there's nothing wrong with this, your patches are public and we were not the only ones that tried to apply them to 1.2.2. As today apology from Sun proves this has been just a PR mistake, nobody wanted to rob you of all the work you have done. As I said before the two JDKs evolved, from the common starting point of the 1.2 patches, in parallel. Witness is the different path taken in supporting some features : we tried the native threads approach and left it behind because the need for updated version of glibc. Other decisions where made in similar fashion. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: another possibility wrt the press-release.
On Fri, Dec 10, 1999 at 02:43:47PM -0500, Mike Ajemian wrote: > to our postings" crap). The community will suffer as 2 products that > should be on the same code base are now completely separate products > (which Inprise likely wants since it doesn't dilute their product with > an Inprise-Blackdown label.) Sorry to disappoint your "conspiracy" theory, I really mean it in a good way, but we really don't care who provides the JDK. If Blackdown tomorrow shows a JDK that outperform ours we will be happy like hell, it will make JBuilder and JDataStore run faster. Great ! Same thing if it comes from Sun or IBM. As anybody can immagine having to port the JDK is a big PITA especially since we had to do that while working on other two projects (JBuilder Solaris and JBuilder Foundation). We literally spent the nights in the Borland Campus. > Bottom line is Inprise wants presence in the linux community and Sun > wants a greater Java presence. I don't think they're going after the > current linux base, they're going after the converts to linux (a large > number that's growing fast) who aren't going to be familiar with or > even care about this issue. Wrong again, we believe we have something that can improve the experience of the developers on Linux and on other platforms as well. The thing that is funny for me is that you, and other people on this list, refer to who works in Inprise or other companies like we are not part of the Linux community. I still have the Slackware 0.99 disks and the same is for many of us in the Borland campus. Linux is exciting for us and we have people that rooted for it for years, me being one of them. Sure we work for a commercial company, does it make us "bad". I don't think so, let us contribute to this community, we are doing our best and you'll judge if it's worth your attention and money or not. In the case of JBuilder Foundation, as you ca see, we are giving it away for free. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: another possibility wrt the press-release.
se or other companies like we are not > > part of the Linux community. > > Never said you weren't part of the linux community. My raising issue > with you means that you're a peer in this community. If I felt > otherwise I would let you know directly. > > Would appreciate it if you would consider addressing my main point, > which is that fracturing the development efforts is divisive and in > the long run potentially more harmful to the future of java on Linux. > You have an opinion on that, I'd like to hear it. To me, the prospect > of collaboration was worth more than a couple of phone calls. > > cheers, > Mike > > -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: another possibility wrt the press-release.
On Sat, Dec 11, 1999 at 03:07:36PM -0500, Mike Ajemian wrote: > 1. Inprise JBuilder, sitting on top of JDK that Inprise authored. > Good brand. Not involving Blackdown as the market might perceive > that as a dilution (I know finance folks who would view the > relationship as a major liability.) That's it. It's not > specifically about the JDK, that's a component in the solution. > It's about the packaging of Java tools from Inprise and selling > those tools to (especially) corporate buyers who are still twitchy > about Linux. For the corporate tools builder (IT departments are > potential customers who stand out to me), they might want Linux if > somebody supplied all the Java tools and supported them, too. So > Inprise supplies all the tools and supports all the components, > too. I know corporations that make decisions this way and it's > not a bad thing. Integrated components, one point-of-contact. > The market assigns a lot of value to that. I just want to point out that the JDK is already "branded" by Sun and that Blackdown has been officially appointed by Sun as the official porter. For a lot of companies this is more than enough. As I said many times before, we turned to the JDK to fix a specific need. We knew that JDK 1.3 was going to be ported by Sun but we needed something for the short term. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: another possibility wrt the press-release.
On Sat, Dec 11, 1999 at 02:03:16PM -0700, Jeff Galyan wrote: [deletia] > Just my two cents. Superbly exposed, Jeff. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: another possibility wrt the press-release.
On Fri, Dec 10, 1999 at 08:50:21PM -0800, Ted Neward wrote: > For my money, I'll download the Inprise product (I have a particular beef > with Borland as a company--why'd you kill OWL just before my OWL books came > out?--but that's neither here nor there) We didn't kill it, Microsoft did :) -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Slowly compiling java app.
On Thu, Dec 16, 1999 at 03:30:45PM +0700, Siriphen Wikaisuksakul wrote: > > When I compile java application, it take very long time to succeed and if I don't >type -J-mx option, it can't compile the application. Here is the error message: > > The compiler has run out of memory. Consider using the "-J-mx" command line >option to increase the maximum heap size. Are you using JDK 1.1 ? The -mx switch has been changed to -Xmx in Java 2. Anyway, it seems that your application requires more memory to be compiled than the standard heap size allocated by Java. Just write a script or makefile to call the compiler with the correct amount of memory. If you're using Java 2 you might want to take a look at JBuilder for Linux (free download at http://www.borland.com/jbuilder). It includes a compiler with automatic dependency checker and it's much faster than javac. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Blackdown JDK vs Sun/Inprise
On Fri, Dec 17, 1999 at 01:26:56PM -0200, José Romildo Malaquias wrote: > On Wed, Dec 15, 1999 at 04:40:47PM -0500, Alan Hazelton wrote: > > I've got a Redhat 6.1 system with the Blackdown JDK 1.2.2 RC3 > > installed. I installed the Borland Jbuilder 3 foundation IDE. It runs > > ok except for a few little annoyances. [...] > > Is there a downloadable version of JBuilder 3 for Linux? Can one get > it for free? The answer to both questions is : yes => http://www.borland.com/jbuilder -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Blackdown JDK vs Sun/Inprise
On Fri, Dec 17, 1999 at 04:10:05PM -0200, José Romildo Malaquias wrote: > On Fri, Dec 17, 1999 at 09:37:51AM -0800, Adam Ambrose wrote: > > Yes, you just need to fill out a million forms to get it, but you can > > get it for free from the Inprise web site: > > http://www.inprise.com/jbuilder/foundation/ > > The recommended minimum memory is 128MB! Is that really need? I have > only 64MB. Would it be worth downloading and experimenting? Is anybody > else using JBuilder under Linux with less than the recommended 128MB? I'm afraid it's what you need. The performance when using swapping might be quite bad. You can probably run the IDE in 64Mb but for heavier tasks, like running or debugging your app in the IDE you need 128. JDK 1.3 is supposed to have a sensible optimization of memory but I doubt it will make a huge difference. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Blackdown JDK vs Sun/Inprise
On Fri, Dec 17, 1999 at 01:47:18PM -0500, Alan Hazelton wrote: > > I agree with your surprise though. It seems quite outrageous to require so > much memory for an application. I think the JBuilder team should have spent > a bit more time trimming the memory requirements before rushing the product > out the door. Actually JBuilder uses a lot of on-demand/delayed loading of classes. The product is highly modular and the IDE basically runs a smal kernel that uses the OpenTools interface instantiate almost everything, from the Menu system to the virtual file system. We trimmed as much it was possible without sacrifying functionality. Java 2 1.3 is expected to sensibly reduce the memory footprint. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Blackdown JDK vs Sun/Inprise
On Fri, Dec 17, 1999 at 02:34:27PM -0800, Nathan Meyers wrote: > Java is a memory hog... it's not JBuilder, it's Java. I've found that > my system was pretty much useless for any Java work at 64M. When Linux > JDKs catch up with some of the improvements now being enjoyed in other > environments (like HotSpot), the situation should improve. Actually the memory footprint for JBuilder is pretty much the same on Windows. JDK 1.2 is bigger than 1.1, it provides more services too, and that's quite consistent across platforms. It is true that the Windows version is more optimized and Hotspot make a difference, especially for big applications. All this has been promised to change with JDK 1.3. -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Blackdown JDK vs Sun/Inprise
On Fri, Dec 17, 1999 at 09:01:17PM +, Nicholas Wright wrote: > Hi > > Re: 128MB minimum memory - JBuilder was a big application on Windows... what > makes you think it would be smaller written in Java? Actually JBuilder Foundation is more efficient than the previous versions because we had to deal with Java code (designer,palette, compiler and others) interfacing Delphi code (editor, IDE menu etc). With Foundation we don't have to have the JVM and the Delphi RTL in memory at the same time, one single heap is better. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inprise JDK, JBuilder, WindowMaker
On Fri, Dec 17, 1999 at 10:06:00PM +, Ekkehard Kraemer wrote: > Can anybody speculate on this? I would love to use JDK 1.2 finally (be it > Inprise or Blackdown, never mind), but I cannot do so since it crashes systems > when using JFrame/JDialog with certain window managers. Well, one place where we can stop the speculation is about JBuilder. The program is a Swing application and we don't do anything special, i.e. native code or JDK "under the hood stuff", to make it behave differently. We did a lot of testing and might have fixed some platform specific behaviors but we have done the same on any platform: write once, test everywhere :). That's exactly why we didn't release the Linux version at the same time of the Solaris one. Are you using the same JDK for both JBuilder and your Swing apps ? What about applications created with JBuilder's Application Wizard ? Do they show the same problem ? BTW, this kind of behavior is exactly why we suggested KDE, it seems that their WM has some ad hoc fix that makes it work with AWT. My current configuration is Enlightenment 0.16.x + KDE and I noticed the lack of titlebar and bad placement for applications written with JDK 1.1.x+JFC while apps written with 1.2.2 seem to be ok. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Blackdown JDK vs Sun/Inprise
On Mon, Dec 20, 1999 at 05:55:52PM -0800, noisebrain wrote: > > Aren't we forgetting something in this discussion? > > Average PC has 64M, you want to write an application that runs > on this PC, your dev environment (JBuilder or whatever) > has, in addition to the application, a compiler, the IDE, a debugger... > > ...your development environment is probably going to need more than 64m. > This would be as true of a C/C++ ide. True, in general a developement machine is bigger and faster than the one required for the application developed. Just ask John Carmak if he uses a 64Mb PC to write Quake III. I don't think so :) -- Paolo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
On Tue, Dec 21, 1999 at 12:31:17AM +0100, André Dahlqvist wrote: > I noted in Blackdowns README file that glibc 2.1.2 is required, and read > in Sun's README file that glic 2.1 is required for their version. Does > anyone know if they mean that any 2.1.x version works? The Sun/Inprise JKD has been tested with glibc 2.1.1. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
On Tue, Dec 21, 1999 at 11:22:03PM +0100, Juergen Kreileder wrote: > No big surprise, they've commented out the relevant entries in the > font.properties file. I'll do the same for the next Blackdown release > as people think that it is a bug, but it isn't. > > Try to display dingbats characters (0x2701 - 0x27be) on an AWT > component with the Inprise JDK, you'll get no warnings but the > component only will show question marks: ''. The warnings from > the Blackdown JDK just tell you immediately that something might not > work correctly. Does anybody know if installing the URW fonts fixes the problem ? If yes, than it could be a requirement for the JDk and it just could be mentioned in the README. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
On Wed, Dec 22, 1999 at 01:57:01AM +0100, Juergen Kreileder wrote: > Paolo> Does anybody know if installing the URW fonts fixes the > Paolo> problem ? > > Yes, but you have to restore the original '.1' entries in > font.properties too. I believe this is the best solution. Any reason for not doing it ? I mean, the URW fonts are free and come bundled with several distros, I think it would be reasonable to list it as a requirement. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: glibc requirements
On Tue, Dec 21, 1999 at 07:30:34PM -0800, Alan Westhagen wrote: > I tried to get this to work with blackdown jdk1.2.2-RC3. I already > had URW fonts. Some of the documentation seemed to point towards > installing Microsoft truetype fonts, as well. Since I am running > RH6.0, which has the xfs font server, I did that. It might be useful to know that RH 6.0 had support for TrueType fonts but it was removed from 6.1. Mandrake 6.0 and 6.1 both have FreeType. The JDK has a TrueType renderer so you can add TT fonts if you manage to update the fonts.properties file (I believe we need som esort of tool to make this task a little easier). -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Using JPDA with Blackdown JDK?
On Wed, Dec 22, 1999 at 05:49:07PM +0900, SHUDO Kazuyuki wrote: > > > Can the > > > JDPA work with Blackdown or does it require us to port it to Linux?? > > > Is the JPDA 100% java or does it require some native calls > > > that need to be rewritten for linux?? > > > > Some porting is required. The Inprise JDK (available from Sun) has JPDA, > > Blackdown (currently) does not. > > Does the Inprise JDK have all parts of JPDA? > I don't think so. I'm not an expert in JPDA but the Sun/Inprise JDK does have JPDA fully working. That is a requirement for the JBuilder debugger, local and remote, to work. > Native libraries are libjdwp.so and libdt_socket.so. > The libjdwp.so is the implementation of JDWP and the > libdt_socket.so is used by an executable javadt, I suppose. Check. > And I suppose only JDI requires an additional JAR file > named jpda.jar, which contains the following packages. Check. > Only JVM itself can provide JVMDI functions. I > understood it is the reason why Inprise guys decideed to > develop their JDK. One of them. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Using JPDA with Blackdown JDK?
On Thu, Dec 23, 1999 at 03:47:56PM +0900, SHUDO Kazuyuki wrote: > > I noticed jpda.jar which included in Inprise JDK is > different from it provided by Sun such as JPDA 1.0. The > Inprise's jpda.jar contains more classes than Sun's. > > Will the difference be contributed to developers other > than Inprise? As far as I know any changes done to the JDK sources are then given to any other licensees after Sun incorporates them in the baseline. > And I have more questions about JVMDI. Does Inprise JIT > (libjavacomp.so) support JVMDI? And how about Sun's > (libsunwjit.so)? I suppose Sun JIT does not and Inprise > JIT may possibly do. If Inprise JIT does not, JBuilder > should suffer it. Or is debugging possible as far as JIT > is disabled? I'll forward the question to the person that wrote the JIT. -- Paolo Ciccone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How do you use JDK?
On Mon, Jan 03, 2000 at 08:24:42PM -0800, [EMAIL PROTECTED] wrote:
> This might sound ignorant, but everything I've read is about
> java programming syntax and stuff like that. My question is
> how do you run a java program? Just using java ./Clock2 doesn't
> work. I either get "class not found" or "In class Clock2: void
> main(String argv[]) is not defined"
Java program are always defined in one package. Java uses the filesystem to
store tha package hierarchy creating a subdirectory for each level in the
package name. This means that a package named com.mycompany.mypackage will
generate: ./com/mycompany/mypackage on a Unix system. You compiled .class
files will be stored in the last subdirectory.
At the beginning of your program you should have a declaration like this:
package com.mycompany.mypackage;
After that there should be the code that defines a class. The class must be
public to be runnable and must have a method main() with the following
prototype:
public static void main( String[] args )
{
//The code here is usually in the form:
MyClass aClassObj = new MyClass();
aClassObj.method();
}
If you have an explicit package declaration you should be able to run the
class with:
java com.mycompany.mypackage.MyClass
or
java -cp lib1:lib2:libn:. com.mycompany.mypackage.MyClass
Where lib1..libn are either names of directories or jarfiles containing
additional packages.
This assumes that the com subdirectory corresponding to the first level of
the package name has been created under the current dir.
If you don't have an explicit package declaration then the class is defined
in the default package and you should be able to run it with something like:
java -cp . MyClass
Using "java ./MyClass" is not going to work because the JVM replaces the "."
in a classname with the directory separator of your OS and tries to locate
the .class in the subdirectory obtained from that sustitution. Of course the
addition of the "/" is making things event messier :). If you're using JDK
1.1 the CLASSPATH is handled in a more complicated way than 1.2 so you
should add the current directory to the CLASSPATH to run classes in the
default package:
java -cp .:$CLASSPATH MyClass
Hope this helps,
--Paolo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: January 2000 java-linux FAQ
Stephen, great job with the FAQ, thanks for putting this together. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Terrible native thread performance
On Wed, Jan 19, 2000 at 02:36:30PM -0500, Daniel Stux wrote: > Here is what I see with Linux. I am running on a freshly installed RedHat > 6.1 machine. With either JDK, running in native threads is absolutely > crippling. There seems to be a serparate JDK process ID for each running > thread, or otherwise something is casuing it to fork 15 times. Of these > threads four or five of them just hammer the CPU, leaving the whole > machine at a crawl. Actual performance of our Java GUI isn't too bad, but > it's no where near where it should be. The thred model of Linux is a little different than other OSs and each thread is assigned a PID. The thread itself runs in the same address space of the parent process but it's reported in the way you saw by tools like ps. > Switch to green threads. With Sun's JDK it's like lightning. Processor > utilization is practically nill, and the GUI is extremely responsive. The Sun/Inprise JDK is not cerified for native threads, the green threads implementation has been tested for performance so the result you obtain is the expected behavior. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RC4 - what it is about?
On Sun, Jan 30, 2000 at 12:05:41AM -0500, Jacob Nikom wrote: > Nathan, > > Thank you very much for your message - the information > about graphical debugger was very important for me. > I have problem with JBuilder installation - famous "No > free memory" message, so I thought I could use javadt. Hi Jacob, if you're referring to the message of the installer about no available disk space, it's caused by a bbug in InstallAnywhere with NFS or SMB mounted shares. If you temporarily unmount those shares you'll be able to install it. The next release will have the bug fix. Glad to see RC4, I'll give it a try with JBuilder tomorrow. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Insurmountable hurdles with JBuilder installation
Hi Jacob, I'll gladly try to help you with the installation but I think we should take this out of this forum. The installer bug with NFS/SMB has caused us some gripes but we have a fix ready for the next version. The installer requires a GUI so you have to run it from X. If you cannot unmount any of the shares you could try to install it on a another machine and then copy (ftp) it over. On Wed, Feb 02, 2000 at 09:42:36AM -0500, Jacob Nikom wrote: > So, I tried to install it locally. I could not unmount my server (it is > automounted), so I went into "single user" Linux mode with only local > drive available. However, it started to complain about Java virtual > machine which it could not find. I undersrand from this that you can reboot the machine. Why can't you unmount the shares ? > Next I installed JVM on the local drive. It almost started to install, > but hung after JVM was found and JVM selection was made. This can be caused by two thing: you were not running X or the X server was using an incompatible color depth (known problem with AWT). Please use "export LAX_DEBUG=true", rerun the program and send me the output prinmted on the console. > I am looking for graphical Java debugger for small project development > under Linux. I don't need GUI builder, source code control, etc, but > I would prefer simple nice stuff. I am interested in one which can > work with Blackdown JDK1.2+ but be easily switched to another JDK. > I cannot use VisualAge since they support only 1.1.8. I did not try > DDD - soes it work with GNOME? I heard that it works only with KDE. BTW, I tried JBuilder with Blackdown's RC4 and it seems to work. Congratulations to the team. It's still early to consider it completely compatible but we will start formal testing soon. -- Paolo Ciccone JBuilder dev.team -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
