Then my instructor said he could give us Microsoft Expression Studio free of charge. He made us install it in the computer lab. While it might not do as much as Adobe Dreamweaver, it is surprisingly easy to use.
After knocking out web pages with Express Studio, I wondered if it was worth it to learn how to hand code HTML pages. The verdict is yes. You will know how to debug any problem you encounter. You will also understand the setting much better than somebody who started by pointing and clicking.
One common feature between the two is that neither job will get you props with the ladies. That is just too bad. Personally I want to be more than just a web developer. And I also want to earn more than the average $85k. So I need to step up my game and learn databases as well.
The node.js set of APIs are similar to those for browsers. The main object in node is a process. A key tenet of the system is that your calls should never have to wait on anything such as file I/O.
Checked out some local job listings. There were indeed a number of Flash developer positions in the area. Some of them even posted their salary ranges. However the highest paying ones were $100k or maybe one $110k job. No salaries were even close to $150k.
The jobs themselves required graphic design skills. You also need to know ActionScript. Not sure what that is exactly. However I am not a Flash developer. May never become one. I am always looking for the high compensation technical areas. Flash might not be on the top. It still could be worthwhile to investigate a little further.
Some examples of block elements are p, div, h1, blockquote and ul. Examples of inline elements are span, a, strong,
, and img. Note that the image element actually behaves a little like both types of elements. Table is another element that is not strictly block or inline.
Blocks can contain other blocks and inline elements. They take up the entire width of their parent content box. They normally begin on a new line. Block element are also called block-level elements. They describe structure.
Inline elements can online contain text or other inline elements. They do not break the flow. They also do not form new blocks. Inline elements join with other inline elements horizontally, and wrap only if they reach the end of the parent content box. Inline elements are also called text-level elements. They usually describe the appearance. You cannot set the width of inline elements. Their width are controlled by their containers. Be warned that Internet Explorer does not follow this last rule.
In all of this, you should know that the type (block or inline) that an element normally is can be redefined using the display tag. Here are some more rules. Elements in the body are either block or inline. An inline element cannot be directly under the body level tags. Knowing block and inline can separate you from the rank and file HTML coders.
Normally I would not think twice about this. I would just click to go to some other site. But I just went through an upgrade to Microsoft Internet Explorer 8. The upgrade was a difficult path. My initial tries resulted in error. Had to get some help getting the thing installed and working.
I also thought that HTML5 was not even a standard yet. The current standard should be XHTML, which is HTML4 plus a little XML. What is going on here? Must be some Google ploy to battle with Microsoft. Maybe I will try going to the site with Firefox. But this better be a damn good site with all this trouble.
Next up you need to move your database to the cloud. Microsoft has SQL Azure. This is a scaled down version of SQL Server 2008. Make sure you app works with SQL Server 2008 first. Then review whether all the features you use are supported by SQL Azure. Beware that your connections to the database will be throttled. You got to dump the designs which connect to the database and hold the connection for the life of your app.
These are a few tips to get you started. Personally I have stayed away from cloud computing. The system I work on is complex enough with having to add another layer of trouble to it.
I am fine with this. Personally I like coding more than drawing pictures. That does not mean that design itself has been thrown out. Just the previous craze of using tools to draw diagrams.
Guess what? I can't remember the last time I opened up Rational Rose and did any design work with it. And I also don't recall the last time I sketched out a UML diagram for a developer to see. Oh well. Easy come easy go.
HTML 5 is new. It is based on an open standard. If you are doing mobile apps, HTML 5 might be for you. You might want to learn it if you are a developer. I hear that HTML 5 development opportunities are growing fast.
Companies do not have to choose Flash or HTML 5. You can code up your apps in both, and support multiple implementations of your app. You want to reach as many people as possible. Use the right tools and language for the job, even if you need to support multiple platforms.
Last year we started receiving some files in XML format. There was a big concern about the size of such files. The old input files were minimal. You just got the data arranged in a specified format. Many worried the overhead of XML tags would make the files too large to handle. So far we have not received too much data in these files. The technique has not been volume tested.
Now we are preparing to receive a combination of XML and ASCII text files next year. There will be format changes for both of these files. The ASCII text files just have a different record layout. The XML files will be formatted according to a new schema. I suspect in the future that we will only receive files in XML format. Then we will only have to deal with XML schema changes. The real thing to look out for is the growth of XML input file size. We do have a plan to split the XML files into small chunks that we can reasonably process.
Drupal users just had their first users conference. It was called DrupalCon. The conference was hosted by Microsoft Corporation.
Know that Drupal is an open source framework. About one percent of web sites use Drupal. The word Drupal is Dutch meaning drop.
The framework was created back in 2001. Its creator formed the company Acquia to provide support for the framework. This company does things like provide training.
The browser is becoming the default experience for users. Google wants the browser to be the next generation operating system. Some people are concerned about this new power being available in the browser.
This might be good if people write POSIX compliant code so it can run on all kinds of platforms. Google is positioning this technology for cloud computing. Knowing Google, this might be in Beta for a while.
Others wonder whether Chromium offers anything beyond what the Java Virtual Machine and applets can give you. C++ programmers might think this is just like Microsoft's ActiveX technology. Btw, I got all this info from readwriteweb. So props to them.
I just read up one guy proposing RESTful apps to use security assertion markup language (SAML). This standard is an accepted way to do authentication. It is an alternative to WS-*.
They say SAML has a rich syntax. I can't tell for sure yet. I have only just read about. However it sounds like something to look into if you are going RESTful.
Now I am hearing that SOA is being redefined to represent some best practices in software development. It describes using simplistic messaging. It also refers to open and scalable systems. That sounds like good techniques to me.
Like most developers, I was excited to hear about SOA. I recall a VIP from our company addressing huge amounts of developers in my building. When he mentioned SOA, the developers were happy and cheering.
Now unfortunately SOA is being used by everybody. It does not mean much to me any more. I hope this new best practices style of SOA takes over. We shall see.
HTML 5 supports Scalable Vector Graphics support. Some have speculated that Microsoft is concerned that SVG infringes on the Silverlight solution space. Luckily Microsoft is no longer holding out on HTML 5. They joined the SVG working group. Things are looking better for HTML 5.
Color is a key component. Don’t use funky background colors on web pages. The same applies to the font colors. Bright colors are bad.
Another major component is the text. Don’t use weird affects on the text. You should also be sure to avoid huge fonts.
Finally you got to limit or avoid the use of animation and video. Web pages should be quick to load and easy to view.