Something to think about: more thermal energy is available to chaotic earth processes like weather. More energy in a chaotic system means more energetic chaos, such as an increase in the number or size of the events.
Re:Jess in action somewhat fustrating...
on
Jess in Action
·
· Score: 1
The obvious "solution" (aka workaround) is to create your own local jess package and put your extension in that package. E.g. org.jess.rules is a local directory in your build tree and you can put your new Java rule classes in that package. When you compile your rules will be in the same package and the compilation will succeed.
I know, an ugly hack it is. But it will work until the class exposes public methods for extension.
In what appears to be another technology industry layoff, the (in)famous Cmdr Taco of Slashdot fame was fired today. According to sources within OSDN, the continuous spelling errors, Freudian slips and dyslexia-like juxtapositions of company names led to the dismissal.
Cmdr Taco was quoted as "being disappointed" with the decision, but was "looking forward" to spending more time at home with his computer.
In related news, OSDN has banned drugs, alcohol, controlled substances and Cowboy Neal from the Slashdot campus.
Intended as helpful content from a slightly annoyed reader- Could the Slashdot crew work up some solution to prevent linking to easily slash-dotted servers? A couple of ideas:
Load test the link using a little utility to generate a lot of requests on the link. Pre-slashdotting them to some extent to determine their robustness. If they are susceptible, see item #2.
Add a function to Slashdot to mirror the site about to be slashdotted while the story is active and link to the original as well as the mirror.
At least add a link to the Google/whoever cache if a site is smaller or susceptible to being crushed by slashdot traffic. Be merciful.
Since the forum usually provides the Google cache or mirroring functionality themselves, I think it would be prudent to make these improvements to Slashdot/Slashcode. Volunteers?
User friendly is an relative term. It depends on the audience of the UI. Non-computer savvy people will have a different level of training with common computer interface idioms, and require a lower-level of interface complexity. Lower complexity sometimes lowers the maximum possible UI productivity due to increased steps or elimination of full functional generality.
Computer-human interaction takes place on the basis of a language- text, graphics, gestures. Since computers do not have the capability to understand or detect human intent or feedback at a high level, it is the interface is designed to present the functionality and language features at a relatively low-level of complexity. As most programmers will tell you, a text-language based interface is the most flexible and functional, but not the easiest to master. UIs are intended to bring the computer-human interaction less learning on the part of the human. Graphical symbols and gestures attempt facilitate communication rapidly and intuitively (pic==1^3 words, etc).
If an interface is used a lot, humans are trained on the language and rapidly (sometimes) acquire proficiency with the available functionality. At this point, the UI is often a barrier if it is too simple. At least I find GUIs are a barrier (I'm a programmer).
Anyway, it is possible for a UI to be too simple if it lacks additional capabilities for proficient users to quickly get their task done, esp. if the intent of the product with the UI is to be used frequently.
Slashdot Mirror
Something to think about: more thermal energy is available to chaotic earth processes like weather. More energy in a chaotic system means more energetic chaos, such as an increase in the number or size of the events.
The obvious "solution" (aka workaround) is to create your own local jess package and put your extension in that package. E.g. org.jess.rules is a local directory in your build tree and you can put your new Java rule classes in that package. When you compile your rules will be in the same package and the compilation will succeed.
I know, an ugly hack it is. But it will work until the class exposes public methods for extension.
Cmdr Taco was quoted as "being disappointed" with the decision, but was "looking forward" to spending more time at home with his computer.
In related news, OSDN has banned drugs, alcohol, controlled substances and Cowboy Neal from the Slashdot campus.
The following sites I use daily (I'm a prof. programmer, currently in Java):
http://java.sun.com
- tutorials, reference API's and language spec.
http://www.theserverside.com
- information about server-side programming,
news, general interest
http://otn.oracle.com
- SQL & PL/SQL reference, free account
http://jakarta.apache.org
- tools, toolkits & infrastructure
http://www.w3.org
- RFC's (like HTTP), HTML specs, CSS, etc.
http://www.slashdot.org
- when running tests or building (goofing off)
Since the forum usually provides the Google cache or mirroring functionality themselves, I think it would be prudent to make these improvements to Slashdot/Slashcode. Volunteers?
the audience of the UI. Non-computer savvy people will have a different level of training with common computer interface idioms, and require a lower-level of interface complexity. Lower complexity sometimes lowers the maximum possible UI productivity due to increased steps or elimination of full functional generality.
Computer-human interaction takes place on the basis
of a language- text, graphics, gestures. Since computers do not have the capability to understand or detect human intent or feedback at a high level, it is the interface is designed to present the functionality and language features at a relatively low-level of complexity. As most programmers will tell you, a text-language based interface is the most flexible and functional, but not the easiest to master. UIs are intended to bring the computer-human interaction less learning on the part of the human. Graphical symbols and gestures attempt facilitate communication rapidly and intuitively (pic==1^3 words, etc).
If an interface is used a lot, humans are
trained on the language and rapidly (sometimes)
acquire proficiency with the available functionality. At this point, the UI is often
a barrier if it is too simple. At least I find
GUIs are a barrier (I'm a programmer).
Anyway, it is possible for a UI to be too simple
if it lacks additional capabilities for proficient
users to quickly get their task done, esp. if the intent of the product with the UI is to be used frequently.