Shoot me an e-mail at trondpet[curly-thingy]hotmail.com if you’re a US based employer in need of a sr. web developer with a proven track record. I’m a US citizen with no need of sponsorship.
My strengths are web development and -programming — from architecture and back-end programming to front-end coding. Below is a list of some of my skills. More about my project experience.
- PHP4/5 (WAMP/LAMP)
- Java
- JSP
- MySQL
- MSSQL
- XSLT
- JavaScript / Ajax
- jQuery
- XHTML
- CSS
- Topic Maps
- Information Modeling / Ontology Development
- Cross-Browser Issues
- WAI
I’ve currently got a few opportunities in sight, but am still open for exciting offers and am available for hire from early April on (arrive in the US on April 5 2010). I am primarily interested in opportunities on the West Coast — Greater L.A. Area, San Francisco Bay Area, Seattle and Portland, OR.
Feel free to contact me at trondpet[curly-thingy]hotmail.com, LinkedIn or Twitter.
Edit: I am no longer seeking new opportunities 
by Trond on January 25, 2010
Happy New Year 2010
After a busy December month, the Christmas vacation finally gave me some room to concentrate on what really matters.
Here’s my third blog post on building web apps with Ontopia. A bit late – I had hoped to have it out before Christmas – but at least I made it within January 01 2010 … have a good one!
Getting to the Point
This blog post is part of a series on Web Application Development with Ontopia.
- Part 1: Installation & Requirements
- Part 2: Creating the Database
- Part 3: Creating the JSPs
In Part 2 of this series on building web applications with Ontopia we had a look at how to set up an application’s domain model using Ontopoly.
This post discusses how to go about building a custom web interface to present the data.
Read the full post »
by Trond on January 1, 2010
Intro
This blog post is part of a series on Web Application Development with Ontopia.
- Part 1: Installation & Requirements
- Part 2: Creating the Database
- Part 3: Creating the JSPs
In part 1, we looked at how to set up Ontopia. We also described the application that we intend to build (a blog) and what we need to develop in order to achieve our goal.
This time we’ll look at how to set up the “database schema” and create new blog posts by using Ontopia’s web interface. The resulting topic map can be browsed here.
Read the full post »
by Trond on December 4, 2009
Introduction
Ontopia is an Open Source application that lets you create, manipulate and navigate information represented in topic maps. It’s also a toolbox for building all sorts of applications. Among the advantages of topic maps driven applications are enhanced navigation and search capabilities.
Ever since Ontopia went Open Source earlier this year, I’ve wanted to give an example of how easy it is to build a web application on top of it.
Through the next couple of blog posts, I’ll try to show exactly how easy this is – and I promise to leave out the unnecessary talk (wont discuss Topic Maps, for instance).
First I’ll “reveal” how to set up and start Ontopia. As this requires very little typing on my part, I’ll quickly move on to discuss what our goal is. Then we’ll have a look at the required data model, before pointing out the kinds of views that our application needs to support — and how to lay this out. Afterwards, we create the limited amount of code needed to get everything up and running. Last, we deploy.
All code will be available for download
Read the full post »
by Trond on November 21, 2009
Personally I’ve never used the YUI library (yet), but the new event delegation functionality of YUI 3.0 has a very nice look to it:
// Defining simple listeners on each element:
Y.on(“click”, handleClick,
“#container ul li a.profile”);
// Defining listener on a container using the delegate() method:
Y.delegate(‘click’, handleClick,
‘#container’, ‘ul li a.profile’);
[...]
Event delegation in YUI 3 moves the overhead of walking the DOM tree from the loading process to the point of user interaction, and decreases complexity by removing the need to match target elements within the callback. Instead, delegate() tests the event target (e.target) against the selector (‘ul li a.profile’) after the event is fired but before the callback is executed…
More at the YUI Blog.
by Trond on November 16, 2009
The other day I needed to “re-invoke”/refresh the current page – i.e. the response HTML – during a <webtest />.
Since neither the manual nor a couple of quick Google searches gave me what I needed, here’s how I solved the problem using a simple <scriptStep> followed by an <invoke>:
<scriptStep description="Get the current HTTP Request URL." language="groovy">
def url = step.getContext()
.getCurrentResponse()
.getWebResponse()
.getRequestSettings()
.getUrl()
.toExternalForm();
step.setWebtestProperty('tmp.currentRequestUrl', url, step.PROPERTY_TYPE_DYNAMIC);
</scriptStep>
<!-- now you can use it like this or pass it to a definition -->
<invoke url="#{tmp.currentRequestUrl}" />
In case it might be of use to you…
by Trond on September 30, 2009
