This video was just shot at the Pub at Crestview Hills.
Thank you,
Mark McFadden
www.markmcfadden.tel
This video was just shot at the Pub at Crestview Hills.
Thank you,
Mark McFadden
www.markmcfadden.tel





A problem with a checkbox is that the browser will only include it in the request when it is checked. If it is not checked, the HTML specification suggests that it not be sent (i.e. omitted from the request). If the value of the checkbox is being persisted, either in a session bean or in the model, a checked box can never unchecked by a HTML form — because the form can never send a signal to uncheck the box. The application must somehow ascertain that since the element was not sent that the corresponding value is unchecked.
The recommended approach for Struts applications is to use the reset method in the ActionForm? to set all properties represented by checkboxes to null or false. The checked boxes submitted by the form will then set those properties to true. The omitted properties will remain false. Another solution is to use radio buttons instead, which always submit a value.
It is important to note that the HTML specification recommends this same behavior whenever a control is not "successful". Any blank element in a HTML form is not guaranteed to submitted. It is therefor very important to set the default values for an ActionForm? correctly, and to implement the reset method when the ActionForm? might kept in session scope.
public class DynamicStringArray {
public static void main(String[] args){
String[] originalArray = {"a","b","d"};
System.out.println("----- Original String Array ----");
for(int i = 0; originalArray.length > i; i++){
System.out.println(originalArray[i]);
}
//create a fixed-size ArrayList from the String array.
ArrayList oldList = new ArrayList(Arrays.asList(originalArray));
//create an ArrayList to hold the inserted items.
ArrayList newList = new ArrayList();
//assume no "b" in the array
boolean hasB = false;
//check if the array has a "b"
for(int i = 0; originalArray.length > i; i++){
if(originalArray[i].equalsIgnoreCase("b")){
hasB = true;//we have a "b" Houston
}
}
if(hasB){//the array has a "b"
for(int i = 0; oldList.size() > i; i++){
if(oldList.get(i) == "b"){//found "b"
newList.add(i,"newB");//replace "b" with "NewB"
newList.add(i + 1,"c");//add "c"
}else{//not "b"
newList.add(oldList.get(i));
}
}
}
//create new String array
String[] newArray = new String[newList.size()];
newList.toArray(newArray);
//pass new String array to old String array
originalArray = newArray;
System.out.println("----- Updated String Array -----");
for(int i = 0; originalArray.length > i; i++){
System.out.println(originalArray[i]);
}
}
}
It is that magical moment we live for: an unwieldy, unyielding data set is transformed into an image on the screen, and suddenly the user can perceive an unexpected pattern. As visualization designers we have witnessed and experienced many of those wondrous sparks. But in recent years, we have become acutely aware that the visualizations and the sparks they generate, take on new value in a social setting. Visualization is a catalyst for discussion and collective insight about data.Check it out
Given the rapidly "evolving" role of the Chief Marketing Officer (CMO), one paradigm to consider when surveying the swiftly changing CMO phenomenon is to look at natural ecosystems and how ever changing environment pressures facilitate the change or evolution of the organisms in those ecosystems. In this paper, we examine the characteristics of the "primitive" CMO, the new environmental pressures challenging the CMO, and finally the fitness factors that are involved in the survival of the fittest CMOs.Here is Survival of the Fittest CMOs.
Given the need for understanding the trends and patterns exhibited in data, utilizing the data in a way that can provide a competitive edge is vital. Three particular products or opportunities for this need are systems to store the data, systems to warehouse the data, and systems to mine the data for analysis and decision making. Data storage is a well understood concept of the use of computer systems to store customer information and transactions as well as other business related data. However, data in a data warehouse is different that the data stored by point-of-sale systems.Here is Business Intelligence from Social Media.

Using Curl, developers can implement a new class of complex, business-critical, Web-based applications that cannot easily be developed with Ajax or other smart client technologies.
Curl allows organizations with legacy client-server applications to move to Web-based delivery, increasing reach, improving processes, accelerating productivity and reducing cost.
From Bill Taylor's Practically Radical Blog at HarvardBusiness.org. In lean times, there's nothing more valuable than a great new product idea. Why not invite your customers to share their creativity with your company -- and turn the best ideas into actual products! That's what legendary shoe designer John Fluevog has done, with a project he calls open-source footwear.
If you take a flat map
And move wooden blocks upon it strategically,
The thing looks well, the blocks behave as they should.
The science of war is moving live men like blocks.
And getting the blocks into place at a fixed moment.
But it takes time to mold your men into blocks
And flat maps turn into country where creeks and gullies
Hamper your wooden squares. They stick in the brush,
They are tired and rest, they straggle after ripe blackberries,
And you cannot lift them up in your hand and move them.
--A string of blocks curling smoothly around the left
Of another string of blocks and crunching it up--
It is all so clear in the maps, so clear in the mind,
But the orders are slow, the men in the blocks are slow
To move, when they start they take too long on the way--
The General loses his stars and the block-men die
In unstrategic defiance of martial law
Because still used to just being men, not block-parts.
<mx:Image source="yourImgPath/imgName.jpg"You want to enlarge the image to a size of 450 by 450 pixels based on the action of a user. Instead of a link to a larger image, we will enlarge the image when the user passes their mouse over the image. To do this you can utilize the mx.effects.Resize class. Enter the following into your MXML file:
height="150"
width="150"
/>
<mx:Resize id="resizeBig"Then, within the Image instance, modify it with the following:
widthFrom="150" widthTo="450"
heightFrom="150" heightTo="450"
/>
<mx:Resize id="resizeSmall"
widthFrom="450" widthTo="150"
heightFrom="450" heightTo="150"
/>
<mx:Image source="yourImgPath/imgName.jpg"Finally, recompile and you will see that when the user passes their mouse over the image it enlarges without the use of links to the larger image.
height="150"
width="150"
rollOverEffect="{resizeBig}"
rollOutEffect="{resizeSmall}"
/>
Critics of reading on the Internet say they see no evidence that increased Web activity improves reading achievement. "What we are losing in this country and presumably around the world is the sustained, focused, linear attention developed by reading," said Mr. Gioia of the N.E.A. "I would believe people who tell me that the Internet develops reading if I did not see such a universal decline in reading ability and reading comprehension on virtually all tests."
Nicholas Carr sounded a similar note in "Is Google Making Us Stupid?" in the current issue of the Atlantic magazine. Warning that the Web was changing the way he — and others — think, he suggested that the effects of Internet reading extended beyond the falling test scores of adolescence. "What the Net seems to be doing is chipping away my capacity for concentration and contemplation," he wrote, confessing that he now found it difficult to read long books.
Joel and I both agree: one of the most effective coding practices you can adopt on your team is interactive, sit-down-with-your-coworker code review. 90% of the things you will learn have nothing to do with the code. I believe programming is a far more social activity than most realize. If you write code, and nobody but you ever sees that code — did you really extract all the benefit from writing that code?HEAR, HEAR!
function formFieldArray(){
var myArray = new Array(10);
myArray['myname'] = "Name";
myArray['myaddress'] = "Address";
myArray['mycity'] = "City";
myArray['mystate'] = "State";
myArray['myzip'] = "Zip Code";
myArray['myPhone'] = "Phone Number";
myArray['myEmail'] = "Email Address";
myArray['cardname'] = "Name as it appears on the Card";
myArray['cardNumber'] = "Card Number";
myArray['expDate'] = "Expiration Date";
myArray['cardCode'] = "Card Security Code";
return myArray;
}
function validateForm(){
var theFormFieldArray = formFieldArray();
//iterate thru array and clear values
for (key in theFormFieldArray) {
if(eval('document.myForm.' + key + '.value.length == 0')){
alert('Please enter the value for the ' + theFormFieldArray[key] + ' field.');
eval('document.myForm.' + key + '.focus()');
return false;
}
}
document.myForm.action = "yourNextPage.php";
document.myForm.submit();
}
if (customer.ID[0].Status != Customer.Validated){
throw new CustomerException(CustomerExceptionType.NotValidated, "Customer Not Validated");
}
The first layer is what I called the stable layer. It's not a very large part of the application in terms of functionality. But it's the part that everything else builds on top off, and is as such a very important part of it. This layer is the layer where static type safety will really help. Currently, Java is really the only choice for this layer.This layer corresponds to the data layer mentioned above.
This is where maybe half the application code resides. The language types here are predominantly dynamic, strongly typed languages running on the JVM, like JRuby, Rhino and Jython. This is also the layer where I have spent most of my time lately, with JRuby and so on. It's a nice and productive place to be, and obviously, with my fascination for JVM languages, I believe that it's the interplay between this layer and the stable layer that is really powerful.In my paper that I referenced above, I discussed that Groovy has great potential given it is designed for the JVM. Here I see this corresponding to the business logic layer.
The third layer is the domain layer. It should be implemented in DSL's, one or many depending on the needs of the system. In most cases it's probably enough to implement it as an internal DSL within the dynamic layer, and in those cases the second and third layer are not as easily distinguishable.Finally, in my view, this tier corresponds to the presentation layer. In a similar manner, the business logic and presentation tiers in many applications are often tightly coupled and "are not as easily distinguishable" as they should be. In any event, Bini’s post is an interesting perspective on the use and place for both dynamic and DSL languages.
Our center runs a seminar called "IT for the Non-IT Executive," and the refrain among the more than 1,000 senior managers who have taken the course runs something like this: "What can I do? I don't understand IT well enough to manage it in detail. And my IT people - although they work hard - don't seem to understand the very real business problems I face."
