It might be a good idea to better distinguish requirements from suggestions then
I called our Website people suggesting exactly this. Glad you like it, try the debugger and CodeInsight or the BeanExpress. Without even mentioning the GUI designer (oops just did it), they are worth the wait.
The Webpage will be corrected asap. KDE is not a requirement. On our testing of the two Dektop managers available for Linux, GNOME+Enlightenment 0.15 and KDE+kwm, we found the latter more stable. Not a terrible surprise since Enlightenment is at development stage. My personal system is Mandrake 6.1 + E0.16.2 + KDE and JBuilder runs just fine. The icon on the desktop, and personal menu, is installed only optionally. We tested JBuilder on RedHat but it should run on any system that can run our JDK (kernel 2.2.x + glibc 2.1.1 or higher).
Except for the installation kit, which bombed on my machine
Kinda generic uh ? We can help if you give a little more details.
Only if you're an x86-user running RedHat (eck, yech, blechhh) and have KDE installed. If you run an Alpha, MIPS, or S/Linux box, you're S.O.L.
Have you tried ? The installer and JBuilder themselves have no native code. The JDK is a different story but then if you're writing about Java you probably already have a JDK for the platforms you mentioned.
The installer is written in Java with a loader written in Unix shell. It should run on any Unix system. KDE is not required.
The code name of this project was PrimeTime to clarify that Java is finally ready. That's why we need JDK 1.2.2 and we cannot use previous versions of it. Anybody that tried JBuilder Foundation or JBuilder Solaris will tell you that this version is significantly faster than the previous ones that were written partially in native code.
KDE is not required for JBuilder or the JDk to work. We just had tested the JDK with a limited number of WMs and found that kwm, at the date of release was one of the most stable. The installatiomn of the icon is totally optional, the installer checks if you have a ~/Desktop directory and it will just add the JBuilder.kdelnk file to it.
-- Paolo Ciccone JBuilder dev.team -- Paolo "ZioPino" Ciccone
Once again, id, and John Carmak, are showing how to play in the businnes. I didn't see many peopl epointing out that John played a key role, perhaps the most important role, in making OpenGL a viable platform for gaming. I'm not talking about the technical aspect but he's decision to not use D3D. Once again he's showing how to cast our vote for Linux (and Mac). As he said he would love to have a single SKU but this way of distributing is going to convince the box movers that Linux is a reality.
I like the idea of casting your vote with your money and now that I think about it I see that for once we can vote twice and that's exactly what I'm going to do. I'll buy a box for me and another for a friend.
You can download the Borland JIT, free, here. We measure it to be 30% faster than then JIT included in the current JDK 1.2 for Linux.
Re:What planet are they from?
on
KDE Looks Ahead
·
· Score: 1
Now KDE is already struggling because of its C++ centric nature. If they're going to cast away a standard language interaction technology like CORBA... well I'm more and more convinced that Gnome is the way to go.
Don't confuse your hopes with reality. KDE is not struggling at all. Last time I checked RH was the only distro that promoted GNOME and the level of sophistication and the number of applications available for KDE outperform GNOME by a long shot. Not to mention that their deployment model actually allows you to install the darn thing without problems and to add the updates without going insane chasing the dependencies and version numbers of each components (GNOME).
Let's take the time to review Kanossa and all its implications before criticizing. I bet the decision was not an easy one and they took it only after a year of struggling with CORBA.
I think it's about time we let Psion know that they should write the PC-connection software also for Linux. Cmon guys, let's use the/. effect and send them some quality email.
It's not a matter of importance, for us all our products are important, we are not language bigots and that's why we support Pascal, C++ and Java. The point is that the current development version of JBuilder is written 100% in Java so we can release it to Linux as soon as there is a JDK for this platform and we finished writing and testing the program. It's also important for a lot of people to have a tool that runs on the platform of choice. Being forced to use another OS than the one you are targeting is not much fun. Sure you can use today's versions of JBuilder on Windows and deploy on Linux but being able to do all your development in Linux is another story altogether.
Delphi and CBuilder are native applications and so they require more work to be ported. It's just like this.
As we all know this is exactly what MS described in the Halloween doc. As someone else said the DHCP/DDNS via WINS resolution has been around for a while and that created already enough damage. Let me explain. Since the majority of machines our there use Windows and they have name resolution working, the Linux users are seen has "trouble" by the IS people. It's just a fact. Even worse if only few people complain about lack of name resolution. It seems incredible but there are actually people working in a IS department that, when facing the problem to buy Networking solutions, buy Windows-based packages. Windows never played nicely with Unix and it never will. If youi find yourself in the situation where you are denied some network services I suggest to gather together with all the people that have the same problem and talk nicely to you IS people. They will probably buy better software than try to manage 50/100 IP addresses manually. After all they switched to dhcp exactly to avoid that kind of mess. I speak from experience, it takes some time and a lot of diplomacy but it can work.
GMC did "work", and I think it is a GOOD sign that the GNOME developers recognized that something needed to be improved. It shows that the project is still alive and growing.
Well, I'm glad it works fo you but on all machines I have installed GNOME GMC showed all kinds of crashes and usability problems. After months of use of GNOME I was still using MC.
This is a broad accusation you just made about all of GNOME, but you're basing it on one program. Don't tell me KDE never scrapped an idea.
We are comparing apples and oranges here. My "accusation", as you call it, to GNOME is based on the fact that KDE came out first. Of course you scap an idea or two in developing a new project but my question was: do we really need anothe Desktop Manager since KDE is already out ? After evaluating both programs I realized that the answer, for me, is "NO !". All the energy poured on GNOME could have been reversed to create a free themable clone of Qt and help KDE to get more features sooner.
They need to be able to change event sounds and themes in ONE place.
Agree but that doesn't require a specialized WM. If KDE and GNOME have a standard way of communicating something like: "Hey, I'm changing theme, I'll use the "XYZ" theme. Please synchronize". We, of course, need a standard (XML based ?) "Theme Description Format" but that's doable. Even in the case of synchronizing WMs people don't want to write the same theme for the Desktop Manager and the Window Manager. Still, this looks more interesting and clean to me that writing a dedicated WM. It also gives more freedom to the power user to select the WM, once all the WMs conform to the API.
I've been a strong advocate for GNOME since version 0.3. I knew about KDE but I decided to "suffer" a little in order to promote real free software. Then I talked with some of the folks of KDE at the last LWCE and decided to give KDE a try. KDE rocks. These guys not only did a GUI that works today but they spent a good deal of time and effort in making everything consistent and simply a pleasure to use. I agree, it looks a little too Windowish but this can be fixed easily with both KDE 2.0 and themes or using E for the WM (the development version has KDE support). If the widget set was the big problem that caused the creation of a new project, GNOME, I'm disappointed in that decision. It would have been much faster and simpler to write a free version of Qt, in other words help the Harmony project, instead of trying to reinvent the wheel. The current version of GNOME is far from being complete or even comparable with KDE. The file manager never worked and now the GNOME team decided to rewrite completely. Not a good sign. Excuse me but I believed that one of the strong points of of OSS was to promote code reuse, with GNOME we keep rewriting code over and over. Since KDE is an Open Source project, if you don't like something about it just grab the code and change it. Last time I checked the KDE folks where more than happy to see more people helping them and they showed good attitude and realist goals.
And I don't think they're really trying to put down gcc
That was not the intention, we are tring to add value to our products and speed, both compilation speed and speed of the executable, is generaly very important to compiler users.
Sorry to disappoint you but the Linux porting plan has been discussed in the company for quite a long time. This kind of decisions are not taken lightly or quickly. The MS announcement should be read for what it is, they paied for using our software patents ($100 million) and bought some stock. That's common practice in settlements like this. Please note that the "preferred stock" is a legal term and that MS doesn't have any representation in the board of directors. Our direction hasn't changed a bit since we closed the deal.
Instead of listening to whispers:) let me said it loud and clear: we are going to build the best, most productive development tools for Linux because the time is right and because it's very exciting for us:).
Slashdot Mirror
It might be a good idea to better distinguish requirements from suggestions then
I called our Website people suggesting exactly this. Glad you like it, try the debugger and CodeInsight or the BeanExpress. Without even mentioning the GUI designer (oops just did it), they are worth the wait.
--
Paolo Ciccone
JBuilder dev.team
--
Paolo "ZioPino" Ciccone
The Webpage will be corrected asap. KDE is not a requirement. On our testing of the two Dektop managers available for Linux, GNOME+Enlightenment 0.15 and KDE+kwm, we found the latter more stable. Not a terrible surprise since Enlightenment is at development stage. My personal system is Mandrake 6.1 + E0.16.2 + KDE and JBuilder runs just fine. The icon on the desktop, and personal menu, is installed only optionally.
We tested JBuilder on RedHat but it should run on any system that can run our JDK (kernel 2.2.x + glibc 2.1.1 or higher).
--
Paolo "ZioPino" Ciccone
JBuilder dev.team
--
Paolo "ZioPino" Ciccone
Except for the installation kit, which bombed on my machine
Kinda generic uh ? We can help if you give a little more details.
Only if you're an x86-user running RedHat (eck, yech, blechhh) and have KDE installed. If you run an Alpha, MIPS, or S/Linux box, you're S.O.L.
Have you tried ? The installer and JBuilder themselves have no native code. The JDK is a different story but then if you're writing about Java you probably already have a JDK for the platforms you mentioned.
The installer is written in Java with a loader written in Unix shell. It should run on any Unix system. KDE is not required.
--
Paolo "ZioPino" Ciccone
JBuilder dev.team
--
Paolo "ZioPino" Ciccone
The code name of this project was PrimeTime to clarify that Java is finally ready. That's why we need JDK 1.2.2 and we cannot use previous versions of it. Anybody that tried JBuilder Foundation or JBuilder Solaris will tell you that this version is significantly faster than the previous ones that were written partially in native code.
:)
Time to take a second look at Java
--
Paolo "ZioPino" Ciccone
JBuilder dev.team
--
Paolo "ZioPino" Ciccone
Just click on the dialog box.
--
Paolo "ZioPino" Ciccone
Hi,
KDE is not required for JBuilder or the JDk to work. We just had tested the JDK with a limited number of WMs and found that kwm, at the date of release was one of the most stable. The installatiomn of the icon is totally optional, the installer checks if you have a ~/Desktop directory and it will just add the JBuilder.kdelnk file to it.
--
Paolo Ciccone
JBuilder dev.team
--
Paolo "ZioPino" Ciccone
Do you have NFS mounted dirs ? Sometimes InstallAnywhere has problems with that. Try unmounting the NFS share and then install.
--
Paolo "ZioPino" Ciccone
Once again, id, and John Carmak, are showing how to play in the businnes. I didn't see many peopl epointing out that John played a key role, perhaps the most important role, in making OpenGL a viable platform for gaming. I'm not talking about the technical aspect but he's decision to not use D3D. Once again he's showing how to cast our vote for Linux (and Mac). As he said he would love to have a single SKU but this way of distributing is going to convince the box movers that Linux is a reality.
I like the idea of casting your vote with your money and now that I think about it I see that for once we can vote twice and that's exactly what I'm going to do. I'll buy a box for me and another for a friend.
I'm impressed, XMMS is a pleasure to use and the IQ plugin is so good I bought it after listening to the trial version for 5 minutes.
Great job guys, thanks so much.
--Paolo
You can download the Borland JIT, free, here. We measure it to be 30% faster than then JIT included in the current JDK 1.2 for Linux.
Now KDE is already struggling because of its C++ centric nature. If they're going to cast away a standard language interaction technology like
CORBA... well I'm more and more convinced that Gnome is the way to go.
Don't confuse your hopes with reality. KDE is not struggling at all. Last time I checked RH was the only distro that promoted GNOME and the level of sophistication and the number of applications available for KDE outperform GNOME by a long shot. Not to mention that their deployment model actually allows you to install the darn thing without problems and to add the updates without going insane chasing the dependencies and version numbers of each components (GNOME).
Let's take the time to review Kanossa and all its implications before criticizing. I bet the decision was not an easy one and they took it only after a year of struggling with CORBA.
Time to send them some email and let them know how numerous we are: Psion USA email page
Here is the link to send the email to Psion:h tml
http://www.psioninc.com/support/usasupport_frm.
I think it's about time we let Psion know that they should write the PC-connection software also for Linux. Cmon guys, let's use the /. effect and send them some quality email.
Is the recent licensing announcement with Microsoft going to affect Delphi & CB on Linux wrt MFC?
The MS Borland license issue doesn't affect the Linux projects as we said at the time of the announcement.
It's not a matter of importance, for us all our products are important, we are not language bigots and that's why we support Pascal, C++ and Java. The point is that the current development version of JBuilder is written 100% in Java so we can release it to Linux as soon as there is a JDK for this platform and we finished writing and testing the program. It's also important for a lot of people to have a tool that runs on the platform of choice. Being forced to use another OS than the one you are targeting is not much fun.
Sure you can use today's versions of JBuilder on Windows and deploy on Linux but being able to do all your development in Linux is another story altogether.
Delphi and CBuilder are native applications and so they require more work to be ported. It's just like this.
Take care,
Paolo Ciccone
JBuilder dev. team.
And you can download it for free from here
As we all know this is exactly what MS described in the Halloween doc. As someone else said the DHCP/DDNS via WINS resolution has been around for a while and that created already enough damage. Let me explain. Since the majority of machines our there use Windows and they have name resolution working, the Linux users are seen has "trouble" by the IS people. It's just a fact. Even worse if only few people complain about lack of name resolution. It seems incredible but there are actually people working in a IS department that, when facing the problem to buy Networking solutions, buy Windows-based packages. Windows never played nicely with Unix and it never will. If youi find yourself in the situation where you are denied some network services I suggest to gather together with all the people that have the same problem and talk nicely to you IS people. They will probably buy better software than try to manage 50/100 IP addresses manually. After all they switched to dhcp exactly to avoid that kind of mess. I speak from experience, it takes some time and a lot of diplomacy but it can work.
Ahem. KDE has a new file manager too. Konqueror, it's called. I just read about it on Slashdot. Admittedly, it's a newer story.
yes, but the old one used to work pretty well. GMC never reached the point of being usable.
GMC did "work", and I think it is a GOOD sign that the GNOME developers recognized that something needed to be improved. It shows that the project is still alive and growing.
Well, I'm glad it works fo you but on all machines I have installed GNOME GMC showed all kinds of crashes and usability problems. After months of use of GNOME I was still using MC.
This is a broad accusation you just made about all of GNOME, but you're basing it on one program. Don't tell me KDE never scrapped an idea.
We are comparing apples and oranges here. My "accusation", as you call it, to GNOME is based on the fact that KDE came out first. Of course you scap an idea or two in developing a new project but my question was: do we really need anothe Desktop Manager since KDE is already out ? After evaluating both programs I realized that the answer, for me, is "NO !". All the energy poured on GNOME could have been reversed to create a free themable clone of Qt and help KDE to get more features sooner.
They need to be able to change event sounds and themes in ONE place.
Agree but that doesn't require a specialized WM. If KDE and GNOME have a standard way of communicating something like: "Hey, I'm changing theme, I'll use the "XYZ" theme. Please synchronize". We, of course, need a standard (XML based ?) "Theme Description Format" but that's doable. Even in the case of synchronizing WMs people don't want to write the same theme for the Desktop Manager and the Window Manager. Still, this looks more interesting and clean to me that writing a dedicated WM. It also gives more freedom to the power user to select the WM, once all the WMs conform to the API.
--Paolo
I've been a strong advocate for GNOME since version 0.3. I knew about KDE but I decided to "suffer" a little in order to promote real free software. Then I talked with some of the folks of KDE at the last LWCE and decided to give KDE a try. KDE rocks. These guys not only did a GUI that works today but they spent a good deal of time and effort in making everything consistent and simply a pleasure to use. I agree, it looks a little too Windowish but this can be fixed easily with both KDE 2.0 and themes or using E for the WM (the development version has KDE support). If the widget set was the big problem that caused the creation of a new project, GNOME, I'm disappointed in that decision. It would have been much faster and simpler to write a free version of Qt, in other words help the Harmony project, instead of trying to reinvent the wheel. The current version of GNOME is far from being complete or even comparable with KDE. The file manager never worked and now the GNOME team decided to rewrite completely. Not a good sign. Excuse me but I believed that one of the strong points of of OSS was to promote code reuse, with GNOME we keep rewriting code over and over. Since KDE is an Open Source project, if you don't like something about it just grab the code and change it. Last time I checked the KDE folks where more than happy to see more people helping them and they showed good attitude and realist goals.
Take care,
--Paolo
And I don't think they're really trying to put down gcc
That was not the intention, we are tring to add value to our products and speed, both compilation speed and speed of the executable, is generaly very important to compiler users.
Just my, very personal, $0.2.
--Paolo
Sorry to disappoint you but the Linux porting plan has been discussed in the company for quite a long time. This kind of decisions are not taken lightly or quickly.
:) let me said it loud and clear: we are going to build the best, most productive development tools for Linux because the time is right and because it's very exciting for us :).
The MS announcement should be read for what it is, they paied for using our software patents ($100 million) and bought some stock. That's common practice in settlements like this. Please note that the "preferred stock" is a legal term and that MS doesn't have any representation in the board of directors. Our direction hasn't changed a bit since we closed the deal.
Instead of listening to whispers
Take care,
Paolo Ciccone
JBuilder R&D
That's a totally wrong interpretation