When we are editing web pages in our favourite IDE we expect that it will provide code completion support for all tags and their attributes we use. It is true for plain HTML pages as well as for JSPs and of course XHTMLs. How does code completion works? Very simple: we need to include tag library in page template and that’s it! IDE should analyze this tag library and use tag metadata to provide code completion for page author automatically. Of course tag library should contain all neccessary information for tags, their attributes, functions, etc.
When we create tag library for JSP everything is straightforward: tag library schema support all this information. So we simply create something like that: >> more…
This blog entry opens a series of short articles describing my studying of facelets and attempts to apply it in our platform.
Problem using JSF with JSPs.
First of all, why does our platform need facelets? Currently we are using JSPs with custom JSF tags inside so what’s the problem with combining JSF and JSP? There are lots of good articles related to this topic, so I won’t be repeating their authors. I’ll just briefly sum up main idea.
- JSP’s goal is to produce static and dynamic content based on HTML/scriptlet mixture; technically speaking JSP produces a servlet. JSP page is processed in one pass from top to bottom, with JSP action elements processed in the order in which they appear in the page.
>> more…
http://www.findjar.com
Yep, that’s it. A jar search engine. “Simply enter the name of the class or the JAR file you are looking for and start your search.”
Recently there was a public voting for Barbies next career. I didn’t grow up with that kind of toys, but obviously there are editions showing the Barbie doll in different professional roles. Today Mattel (the Barbie producer company) announced Barbies next two careers. There were four options: environmentalist, surgeon, news anchor and computer engineer. They did two surveys, one among girls and another public voting. While the girls have choosen news anchor as the preferred profession for their dolls, the public clearly voted for computer engineer. I must admit, I also did my best. Now we should be prepared for a new generation of girls, who know they can do it. I was impressed to read in the factsheet that they actually asked IT professionals what a computer engineer might wear. Although I personally disagree with the choosen colours and the pants, I think it’s a nice thing if girls around the world ask their teachers and parents about the meaning of that numbers on her shirt.
There are more pleasurable things then wading through the fitnesse documentation with its table style, so whenever I don’t remember some fitnesse key word, I’d rather hesitate and wait for an inspiration before going there. This is to memorize the key words to be used in do fixtures.
- show to print out non-boolean values
- check to verify non-boolean values
- reject to invert the logic of the test
Usage like this: >> more…
Next month, we will stop supporting IE6 in conjectPM. This means getting rid of all those “if it’s IE6 add 2 pixels to the y-position”, deleting lots of CSS hacks, throwing away all spezialized stylesheets… we’re already counting the days (great that February s such a short month) and think about having a “hooray, no more IE6!” party.
Or, to cite this month’s ThinkGeek newsletter, “Hearing the news was just like being in high school and getting a pass out of P.E.” (that was about Google stopping IE6 support for Mail and Docs)
I would love to receive on of these, some time.
http://news.ycombinator.com/item?id=1086527
In the past year we noted a heavy decrease in performance, espescially for new featueres we introduced. That’s because our standard testing and sign-off process did not include performance tests and we have not yet had any good ideas (that means, realizable with an adequate amount of time and effort) how to automate it.
In the last couple of months we spent a lot of time to get back to our old standard (which we even managed to outperform in some cases), take care of not ruining the performance again by testing it before releases and treat freshly introduced performance issues with the same priority as post release bugs (that means, fix them immediately). >> more…
