multimedia @ VU
[] readme register participant(s) college practicum feedback resource(s) _ / .

talk show tell print

present / print

(intelligent) multimedia technology

challenge(s) / inspiration(s) / picnic(s) / resource(s) / imt 07

everything you always wanted to program but never ...


(I)MT 2010 -- course topic(s)


The course will (again) be of a practical nature, encouraging the students to produce appealing applications, such as rich-media mashups, data-driven visualisation(s) and to experiment with new (media) technologies.

contact eliens@cs.vu.nl for more information.

theme(s) -- web services, visualisation, (multimodal) interaction(s)


An ongoing theme for multimedia @ VU is (serious) games. Web services, and visualisation(s) of on going activities, may contribute to authoring such games, by allowing for live/dynamic content.

theme(s) -- web services, visualisation, (multimodal) interaction(s)


Also social network technologies are of interest, not only as a source of dynamic content, but also for aspects of (real time) communication, among others to promote a sense of being connected.

inspiration(s) -- (serious) mashups


Both the social web and the instance web, as exemplified in twitter messages, may result in intersting patterns of behavior. One of the challenge(s) here is to visualize these patterns.

inspiration(s) -- (serious) mashups


Visualizations may intent to be nothing but pleasing or artful, but may potentially also lead to a better understanding of human behavior, as advocated in a discpline known as Cultural Analytics.

assignment(s)


There is considerable freedom in the choice of your project(s), however it must comply with the theme of rich media (data-driven) mashup(s), and (in principle) make use of recommended technologies, among which the flex/as3 framework.

assignment(s)


In delivering the project result, you must strive for a professional approach, that is an end product, downloadable as zip, with all sources, working examples, documentation as well as tutorial or getting started applications, that illustrate your project.

resource(s) -- recommended technology


You are strongly encouraged to develop rich-media mashup(s) in the flex/as3 framework, with (possibly) use of PHP, for server-side extensions, needed to circumvent security restrictions, using XML and/or AMF (Actionscript Message Format) for exchange.

ximpel / server(s) / material(s)


Alternatively, however, you may focus on server-side mashups, with a suitable rich-media interface, preferably availabe as a flex component.

lookat(s) -- example application(s)


To get familiar with the various technologies, kearning by example seems by far the most efficient method. After looking at the examples, get some practical experience, and then decide on the goals and requirements of your project.

lookat(s) -- actionscript


Obvoiously, one of the major challenges here is to circumvent security restrictions of the flash player and connect to servers outside of the domain of origin. As in the last examples, you need a proxy, that you may download from media/proxy.zip. By the way, do not hesitate to look at flashplayer 10.

deliverable(s)


At the beginning of the project, you have to create a web site that gives access to all deliverables, and finally a package for download (in zip format). During the course of the project, the website must reflect goals, progess, and achievements, preferably by demonstration(s) of partial results.

deliverable(s)


  1. concept -- idea & plan of approach
  2. application(s) -- code + documentation
  3. essay -- about approach and use of technology
  4. documentation -- tutorial explanation of API/SDK with elementary examples
No need to repeat that all deliverables must be made available from your website. Finally, for documentation use PDF or HTML. In particular, .doc files will not be accepted!

scope(s) -- aspiration(s)


Although it is tempting to develop the ultimate application, that will make you rich and famous for the rest of your life, there are great risk(s), that you will not succeed, and as a consequence end up with nothing useful. Develop a prototype, is my advice, that runs on localhost and may be used later, perhaps by yourself, to realize the system that ultimately fullfills your dream(s) ... Another advice, why not do the obvious, and use map(s)?

[] readme register participant(s) college practicum feedback resource(s) _ / .