Research Log of Web Science Students

Computer Science is not simply programming

Issue Number 2

leave a comment »

Though we list down what we’re supposed to do in our wiki, these are all very general only listing features that should be implemented. But every feature is built with many steps, is made up of smaller sub features (components). I think by simply saying that we’ve finished a feature doesn’t justify the many other things that we’ve done to finish that feature.

It was staring me right in the face before but I wished I could have thought of using an issue tracker. It was taught during my internship and I always saw it on my way to our repository page @ unfuddle. We also need a list to track the many issues we encounter during development from difficulties to bugs. This gives more weight than simply saying, “we finished this feature this week, demo demo demo demo”. Hopefully things will be much smoother from now on.

I’ve already listed the issues related to developing our save a project feature in our wiki and today I’ve learned a lot of things by resolving issue number 2: laying out GWT panels in CSS!

1. Class and Id are different in CSS

<div id="content" style="font-size:8px">
    <!-- GWT widget placed here-->
</div>

We wanted to typeset our GWT widgets but didn’t know so I made a test GWT module and tried to find out how. At first I did it the normal way placing a widget and a pre encoded div with an id and styled the div in the html. But that didn’t work out.
Apparently id applies to only one element in HTML and class can span many elements. What was wrong with my code was that
I was applying the style to a certain id and not to a widget with an id. So I gave the widget an id in gwt and then used css to style it:

# id-of-widget-that-i-used-for-testing 
{
font-size:8px;
}

2. There are two ways to style GWT widgets

<stylesheet src="__css-url__"/>

One is in plain old html and another using Automatic Resource Inclusion (ARI) also known as putting a reference in the gwt.xml file. What’s good about ARI is that a certain style goes where ever a widget is deployed. This is good if we want to reuse widgets which….I think we might be doing. But there’s a bit of a learning curve when using ARI. One is I don’t know how exactly I’d reference the styles in an xml file (see code above). The GWT tutorial does this like it treats the stylesheet as a java file

<inherits name='com.google.gwt.user.theme.standard.Standard'/>

So for now I hope, we’ll go for plain old html. Now at least I know I can layout GWT widgets.

Advertisements

Written by Jose Asuncion

November 27, 2009 at 10:58 am

Posted in Hardwire

Tagged with ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: