was alot better. Lucus should hire that guy to do his trailers.
Together Control Center and Borland JBuilder
on
Java IDEs?
·
· Score: 1
These two programs play well together. Together Control Center is a complete UML modeler with a built in color syntax highlighted editor. Comes bundled with JCVS and Tomcat. Has an integrated debugger and allows for live debugging of servlets. Models Java or C++ and also provides code auditing and metrics. Together has an open API so you can modify the tool to suit your needs.
I use Borland primarily to build the GUI and then do everything else in Together.
One of our graduates was hired as part of a team that installed several Sun labs and servers at CSU Chico's computer science department. He has had Gnome running on our Ultra Sparc 5's, 10's and Sunray's for months now. Works great and we now have that as the default desktop in three labs. Of course, he had to hack and compile it himself because the Sun Gnome patches would not work.
a pop up ad in weeks. Of course, I did install Mozilla and killed them all. I doubt that I will be installing any active x plugins, so I don't have to worry much. Freedom from those damned pop-ups is invigorating!
Re:If this can't break Microsoft's back nothing wi
on
Code Red Back For More
·
· Score: 1
My Linksys was only $99.00, and YES, it is great. From the help page:
Block WAN Request
This feature is designed to prevent users from attacking through the internet. When it is enabled, the router will drop both the unaccepted TCP request and ICMP packets from WAN site. The hacker will not find the router by pinging the WAN IP address.
is that it switches the drive's from master to slave and vise versa. Unless I am wrong (It has happened before) you have two drives, each with an MBR and an OS. When you want RedmondOS, you switch to that drive and the other drive becomes a slave, if you want RealOS, you just switch that drive to master and the Redmond drive becomes slave. Did I miss something?
--- This is my sig. There are many like it, but this one is mine. ---
Well, as an instructor at California State University, Chico, who teaches Java in the first programming course, I would imagine that I am finally qualified to weigh in on a Slashdot topic.
There are a few practical concerns about teaching that the students, and others, do not often take into account. First is the question of accreditation. Universities, in order to be taken seriously, must be accredited by a recognized accreditation organization. Otherwise, Joe's University would be handing out Master's Degrees via email. Wait, bad example, I get those emails all the time. Of course, the degrees are not worth the ink in the email. Since our accreditation requires that we teach at least two high level programming languages, we have chosen to do the first course in Java and the second course in C++.
Java - Enforces object-orrientation, simplifies the process of learning object-orriented techniques by abstracting a lot of the details. We get their feet wet with Java because with applets, the students can see dramatic results quickly. It helps also that the syntax is very similar to C++.
C++ - Now that we have taught them a strict object-orriented language, we turn them loose with a language that not only makes it easy to shoot your foot but often encourages it. At the end of both courses, students have two languages that are suited to different tasks.
Once those languages are out of the way, students move into Data Structures, Assembly and Operating Systems programming. Most of our courses after the "Big Five" programming courses, are not targeted to a specific language and the student decides the proper choice for what they are doing. In fact, even the Data Structures and OS programming courses are pretty much non language specific.
Often people try to focus on learning a specific language. In a university, we strive to not tie anyone to any specific language or architecture. Our job is to teach concepts, theory and practical applications of knowledge. We offer courses that provide tools for students to use the the quest of that goal. It is up to the student to decide what is best for them and for their particular need. If, after the first couple of courses, we only allowed people to program using Java on a Sun UltraSparc 10, we would not be serving our students well. On the other hand, the same applies if we only allowed them to use C++ on a Redmond box.
I often tell people that I cannot teach them Java or C++ or any other language. I have around 45 hours of lecture per semester and have class sizes of 80 students. I can facilitate their learning Java; however,in that time frame, actually teaching them the full capabilities and intricacies of a language is impossible. I teach loops, conditionals, classes, methods, arrays, inheritence, abstraction, events, exceptions, etc. I use Java to faciltate that teaching because it handles all of these things in an elegant and efficient manner.
Many attempt to look at the first CS course as a language course when it really is not. It is a concepts course and helps to aclimate new students to life in a university computer science department. The language is chosen to meet specific goals, one of which is to meet accreditation requirements. The other, more important, factor is to provide a language that facilitates the learning of what is needed in the first programming course.
Java matches our goal in the first course. It does not clutter things with referencing and dereferencing of pointers, it does not allow the student to break object-orrientation, which is one of the primary concepts we teach. We allow them to shoot their foot in the next course.
So, in closing, the language of the first course is important in that it is what facilitates the actual things that are taught in that course. BTW, check out This article about MIT's "Rethinking CS101" project. Very informative.
--- This is my sig. There are many like it, but this one is mine. ---
Cal State Chico uses Horizon Live and it supports IE5+. I have to say that the video is crap but the overall system is pretty good. They use it in conjunction with WebCT. You can find out more about it at online.csuchico.edu
--- This is my sig. There are many like it, but this one is mine. ---
Agreed. This is especially a problem with people new to OO design, where they haven't yet developed a good understanding of modular integrity. In practice, though, I find these kinds of errors much less frequent and much easier to find than classic memory leaks.
I know what you mean. As a Java instructor, getting people to understand that the scope of variables is very important, is a task in and of itself.
--- This is my sig. There are many like it, but this one is mine. ---
I don't see a problem with this on an OS Level. As long as the source code level remained OS independent, the JVM and class libraries could be implemented in any way on the OS. The problem comes when one sub-classes a standard or extended Java class. Remember the JVM is already OS dependent.
If the shared library were for core functionality and any sub-classes scope were confined to the instance that created them, no problem. Since it is the JVM that handles dynamic class loading, this approach is feasible and WITHOUT having to recompile the.class files, which is the ultimate goal.
The JVM would have to be rewritten to be able to recognize that the java.* and javax.* packages are all shared libraries and that all other packages and classes are dynamic. Or, make it a JVM option. This might not improve memory usage because when classes are loaded dynamically, the JVM has to dynamically instanciate the super classes as well. Each instance of a class would have its own heirachy in memory. It would improve the load process though because of the lack of disk hits needed to load up the core packages since the shared libraries only have to be loaded on the first hit. Another approach would be to have the.zip and.jar files on a RAM drive so that they would not have to endure the disk hit problem. Same effect but much less work. All of this, combined with the HotSpot comiler technology might make programming in Swing an option.
Of course, I could have completely missed the point.
--- This is my sig. There are many like it, but this one is mine. ---
Slashdot Mirror
was alot better. Lucus should hire that guy to do his trailers.
These two programs play well together. Together Control Center is a complete UML modeler with a built in color syntax highlighted editor. Comes bundled with JCVS and Tomcat. Has an integrated debugger and allows for live debugging of servlets. Models Java or C++ and also provides code auditing and metrics. Together has an open API so you can modify the tool to suit your needs.
I use Borland primarily to build the GUI and then do everything else in Together.
Come on, no one here has read The Belgariad or The Mallorean? How about The Ellenium or The Tamuli?
Eddings epoch tales are awesome.
Why is a 90 user drop significant?
Rock and Roll with 145KBps. Thanks. It sure beats the 1.6KBps I was getting on one of the official mirrors.
One of our graduates was hired as part of a team that installed several Sun labs and servers at CSU Chico's computer science department. He has had Gnome running on our Ultra Sparc 5's, 10's and Sunray's for months now. Works great and we now have that as the default desktop in three labs. Of course, he had to hack and compile it himself because the Sun Gnome patches would not work.
a pop up ad in weeks. Of course, I did install Mozilla and killed them all. I doubt that I will be installing any active x plugins, so I don't have to worry much. Freedom from those damned pop-ups is invigorating!
My Linksys was only $99.00, and YES, it is great. From the help page:
Block WAN Request
This feature is designed to prevent users from attacking through the internet. When it is enabled, the router will drop both the unaccepted TCP request and ICMP packets from WAN site. The hacker will not find the router by pinging the WAN IP address.
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
There are a few practical concerns about teaching that the students, and others, do not often take into account. First is the question of accreditation. Universities, in order to be taken seriously, must be accredited by a recognized accreditation organization. Otherwise, Joe's University would be handing out Master's Degrees via email. Wait, bad example, I get those emails all the time. Of course, the degrees are not worth the ink in the email. Since our accreditation requires that we teach at least two high level programming languages, we have chosen to do the first course in Java and the second course in C++.
Java - Enforces object-orrientation, simplifies the process of learning object-orriented techniques by abstracting a lot of the details. We get their feet wet with Java because with applets, the students can see dramatic results quickly. It helps also that the syntax is very similar to C++.
C++ - Now that we have taught them a strict object-orriented language, we turn them loose with a language that not only makes it easy to shoot your foot but often encourages it. At the end of both courses, students have two languages that are suited to different tasks.
Once those languages are out of the way, students move into Data Structures, Assembly and Operating Systems programming. Most of our courses after the "Big Five" programming courses, are not targeted to a specific language and the student decides the proper choice for what they are doing. In fact, even the Data Structures and OS programming courses are pretty much non language specific.
Often people try to focus on learning a specific language. In a university, we strive to not tie anyone to any specific language or architecture. Our job is to teach concepts, theory and practical applications of knowledge. We offer courses that provide tools for students to use the the quest of that goal. It is up to the student to decide what is best for them and for their particular need. If, after the first couple of courses, we only allowed people to program using Java on a Sun UltraSparc 10, we would not be serving our students well. On the other hand, the same applies if we only allowed them to use C++ on a Redmond box.
I often tell people that I cannot teach them Java or C++ or any other language. I have around 45 hours of lecture per semester and have class sizes of 80 students. I can facilitate their learning Java; however,in that time frame, actually teaching them the full capabilities and intricacies of a language is impossible. I teach loops, conditionals, classes, methods, arrays, inheritence, abstraction, events, exceptions, etc. I use Java to faciltate that teaching because it handles all of these things in an elegant and efficient manner.
Many attempt to look at the first CS course as a language course when it really is not. It is a concepts course and helps to aclimate new students to life in a university computer science department. The language is chosen to meet specific goals, one of which is to meet accreditation requirements. The other, more important, factor is to provide a language that facilitates the learning of what is needed in the first programming course.
Java matches our goal in the first course. It does not clutter things with referencing and dereferencing of pointers, it does not allow the student to break object-orrientation, which is one of the primary concepts we teach. We allow them to shoot their foot in the next course.
So, in closing, the language of the first course is important in that it is what facilitates the actual things that are taught in that course. BTW, check out This article about MIT's "Rethinking CS101" project. Very informative.
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
I know what you mean. As a Java instructor, getting people to understand that the scope of variables is very important, is a task in and of itself.
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
--- This is my sig. There are many like it, but this one is mine. ---
If the shared library were for core functionality and any sub-classes scope were confined to the instance that created them, no problem. Since it is the JVM that handles dynamic class loading, this approach is feasible and WITHOUT having to recompile the
The JVM would have to be rewritten to be able to recognize that the java.* and javax.* packages are all shared libraries and that all other packages and classes are dynamic. Or, make it a JVM option. This might not improve memory usage because when classes are loaded dynamically, the JVM has to dynamically instanciate the super classes as well. Each instance of a class would have its own heirachy in memory. It would improve the load process though because of the lack of disk hits needed to load up the core packages since the shared libraries only have to be loaded on the first hit. Another approach would be to have the
Of course, I could have completely missed the point.
--- This is my sig. There are many like it, but this one is mine. ---
I hate Micro$haft as much as the next guy but the did follow the standard on this one.
--- This is my sig. There are many like it, but this one is mine. ---
Oh God, it nearly missed us!.
Stealing blatently from George Carlin.
--- Never hold a dustbuster and a cat at the same time ---
--- Never hold a dustbuster and a cat at the same time ---