I would like to ask everyone who haven't shared their opinions on what should our chat program look like. Should it be a native-looking user-installed SWT application (my preference), or a built from framebuffer in-browser applet (daedius's way)? Please share your points, or else I and daedius are going to waste all energy arguing with each other and end up writing a Tetris game in gwbasic.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
LOL... qbasic... *reminices*. I agree with alankor, if we use abstraction, it doesn't really matter. I'm all about OOP. I think for now, all we really need is an applet. People are NOT going to download a beta software. I like being able to create something that looks cool and show dozens of people immediately by just uploading the web applet.
I think, our biggest difference is not whether our application is a windows-app or an applet, but whether we use swing or pixel graphics interface.
It sounds like people are saying no to pixel graphics engine, but I want to work hard on a pixel engine so that I might be able to convince you before we make a final no =) If I can't convince you, then I will go with swing and just work on the pixel graphics engine as a personal side project (because i enjoy that game programming stuff ;P) laters.. i'm off for lunch.
- Daedius
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am quite partial to http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-home/rcp/index.html (Eclipse Rich Client Platform). SWT + JFace + selected bits of goodness from Eclipse itself (without any IDE stuff). So, it looks like we got three devs with three completely different ideas on what should the program look like ;). Sounds fun. How about a chat about all this? irc.freenode.net #nwdo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm of the opinion that we should use Swing. Admitedly, this is because that's all I know how to use in java, and I reall don't feel like trying to learn how to use anything else, as that seems like it will be real pain in the ass.
Now, I haven't had a look at what Roman is suggesting, as I'm still DLing the new version of the JRE, to get your damn applet to work Daedius. It was working just fine a while ago. What happened?
-ipsi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I strongly suggest you to familiarize yourself with what SWT offers. I already said why is it the best thing since sliced bread in these forums for about a dozen times ;). The best way to see what is possible to do with SWT/JFace is to play around with Eclipse.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ipsi , the applet itself runs on jdk 1.4.2. Unfortunately it requires that you download a new JRE. I wonder how many of our users won't use our chat because it is jdk 1.4.2.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to ask everyone who haven't shared their opinions on what should our chat program look like. Should it be a native-looking user-installed SWT application (my preference), or a built from framebuffer in-browser applet (daedius's way)? Please share your points, or else I and daedius are going to waste all energy arguing with each other and end up writing a Tetris game in gwbasic.
I already made my point in the other post, but just wanted to leave this here too.
- We can do both (applet AND client), if we use abstraction
- The applet is better for lazy users, so it gets my vote, but I don't really think we need a full-new-from-scratch graphics engine.
My two cents, anyways.
LOL... qbasic... *reminices*. I agree with alankor, if we use abstraction, it doesn't really matter. I'm all about OOP. I think for now, all we really need is an applet. People are NOT going to download a beta software. I like being able to create something that looks cool and show dozens of people immediately by just uploading the web applet.
I think, our biggest difference is not whether our application is a windows-app or an applet, but whether we use swing or pixel graphics interface.
It sounds like people are saying no to pixel graphics engine, but I want to work hard on a pixel engine so that I might be able to convince you before we make a final no =) If I can't convince you, then I will go with swing and just work on the pixel graphics engine as a personal side project (because i enjoy that game programming stuff ;P) laters.. i'm off for lunch.
- Daedius
I am quite partial to http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-ui-home/rcp/index.html (Eclipse Rich Client Platform). SWT + JFace + selected bits of goodness from Eclipse itself (without any IDE stuff). So, it looks like we got three devs with three completely different ideas on what should the program look like ;). Sounds fun. How about a chat about all this? irc.freenode.net #nwdo
I'm of the opinion that we should use Swing. Admitedly, this is because that's all I know how to use in java, and I reall don't feel like trying to learn how to use anything else, as that seems like it will be real pain in the ass.
Now, I haven't had a look at what Roman is suggesting, as I'm still DLing the new version of the JRE, to get your damn applet to work Daedius. It was working just fine a while ago. What happened?
-ipsi
I strongly suggest you to familiarize yourself with what SWT offers. I already said why is it the best thing since sliced bread in these forums for about a dozen times ;). The best way to see what is possible to do with SWT/JFace is to play around with Eclipse.
ipsi , the applet itself runs on jdk 1.4.2. Unfortunately it requires that you download a new JRE. I wonder how many of our users won't use our chat because it is jdk 1.4.2.
//as I'm still DLing the new version of the JRE, to //get your damn applet to work Daedius. It was //working just fine a while ago. What happened?
What happened is that we decided to go to a higher version of jdk. This annoyance is going to felt be a good majority of people who visit our site.