:o)
La verdad es que siempre me ha dado pereza el “mamotreto” en que se ha convertido Java con la excusa de la escalabilidad y la portabilidad. Lo mÃo hoy por hoy sigue siendo PHP… A ver si este año tengo vacaciones en lugar de “trabajaciones” y puedo aprender Ruby.
VÃa | flickr.
Compártelo
One of my biggest hurdles I have come across since taking on Java is really getting my head wrapped around the OOP (object oriented programming) idea. Most of my previous experience wtih visual basic and php was procedural programming. Because of this, my mind is stuck thinking in those terms.
All the e-books I have been going over describe OOP as something that “should” be easy to grasp. A class is a classification of an object. An object is a noun, like a dog, that can be described attributes or fields: four legs, two ears, two eyes, brown, tail, etc. A method is how that dog interacts with other objects: playFetch(), catchFrisbee(), peeOnLeg(), etc.
Okay, so that seems pretty simple. I get these things. However, I don’t see how the hell I can relate that methodology to creating an application for LDAP or even a simple calcualtor for Marine Corps Cutting Scores (the score that gets us promoted).
Luckily, the internet has a plethora of information and I found it on a Stanford student’s website. Jos Claerbout wrote the paper back in 1999. It isn’t on the intricacies of Java. Since OOP is a method or style or paradigm of programming, it doesn’t change as much over time so the age of the document is less relevant than its style.
Mr. Claerbout’s paper is called Don’t fear the OOP. He uses a trashy western novel as his focus to describe OOP. Each idea is presented in “pretty” colors. If in green, the idea is discussed in terms any literate human could understand. If in yellow, it is a bit more programmatical but still not full fledged “programming talk”. And, if in red, it is all about the code. I can’t say I have ever read a paper that used these styles of teaching but it works. It has been a great reference to put me over that edge so I can get beyond the rut I’ve been stuck in.
The internet really is a great place…
Uriel Katz wrote in to tell us that he’s burned his GearsORM framework to the ground to create the entirely new JStORM framework, announced in his blog. JStORM currently supports Google Gears, Aptana Jaxer, and Adobe AIR, but it’s still bleeding edge: no documentation yet, just code. But the feature-set is interesting:
* define your tables as models.
* full CRUD support.
* events on(Before/After)Delete/Save/Update.
* SQL LIMIT/OFFSET support.
* order by support.
* automatic creation of tables.
* selecting and deleting over relations.
* easy iterating with each syntax like in Ruby,support for query chaining and more.
* basic introspection support.
* transaction support.
* self relations.
* support multiple backends and multiple dialects,currently MySQL (in Jaxer only) and Sqlite (Jaxer, Gears and AIR).
Here’s an example of loading “Person” entities from a database using JStORM:
Looking forward to seeing some docs, Uriel 
The following is the presentation which I gave at BarCamp 3. You can download the pdf version here. Apache JMeter is a 100% pure Java desktop application designed to load test functional behavior and measure performance.
[slideshare 275602 jmeter-performance-testing-your-webapp-1203622239433273-3]
JavaScript snippet with similar function to PHP’s in_array function. However, PHP’s function returns a bool, true if the needle is found. My function returns the key of the item found, which I think is more useful. Both functions are below.
Returns Key
Returns Bool
Subscribe by RSS