The Summer of Code is over; where did the time go?

Demo

The final demo is available at http://jbalogh.dojotoolkit.org/dojo-svn/release/dojo/soc/test.html

Hi dojoers,

In this opportunity, I would like to share my status update for gfx project with Dojo.

What was achieved lately?
- Revised test page.
Yes, a new cool looking page! It cut around 40% loading time from previous version (because of dijit dependancy), which from ~40 seconds become ~20 seconds.

- Camera

Hi dojoers,

I would like to introduce you a new page for GFX 2.0... Now the new page focuses on the display of the canvas (it is located in the middle of the page and it is very big). How about the other (console and help page)? Dont worry, I made such a way when you need them, all you should do just go to bottom left to click either console or help page... And a draggable panel will be shown! In terms of loading, it cuts the loading time around 50% (from 40 seconds to 20 seconds), it is due to I am using a lot of dijit component... Unfortunately, the only problem of new page is performance downgrade since the canvas size is bigger (take more time to draw)... Please go to this page to see the new look of GFX 2.0 page.

Last week before getting sick, I worked on making it possible to export the created form. I've been procrastinating on this part of the app for a while because I was stumped on how to make it easy to use, because exportable data exists on different levels: some parts are on the object I use to wrap each form element (soc.Element), and other parts are on the element being wrapped (the dijits).

This week I've been trying to integrate the GridContainer into the form creator, so users can create forms with multiple columns. Unfortunately, it hasn't been an easy drop-in replacement, and I've discovered some bugs. #7217 turned out to be a "mini flub", easily fixed once I found the faulty code.

Hi dojoers,

As mid evaluation comes, I am prepared myself with a document to give brief explanation about my implementation. It is provided class diagram, sequence diagram, some explanation for each component and screenshot about some demonstration.

You can find about:
- Design Document
- Implementation Overview Document
- Simple Class Diagram

I continue working on Markdown parser and for now it already supports:

• span elements (bold, italic, inline images links and code)
• settext and atx headers
• code blocks
• blockquotes, partly supported for now (in some cases output differs from original Markdown output)
• horizontal rules
• backslash escaping for special chars (\*, \`, etc)

I missed my update last week, so this post actually covers the past two weeks.

Hi dojoers,

I am thinking to put my analysis document for GFX 2.0 (this document has been updating from the first time discussion with my mentor Mr.Eugene Lazutkin). You can read the document to know more about abstract design of GFX 2.0... At the moment, I am writing document to explain thoroughly about GFX 2.0 implementation, it will be described about:
- Assumption implementation (for example, no color texturing, no light feature, etc)
- Implementation detail (including design diagram, improvement made to increase performance)
- Problem (algorithm, feature that hard to implement)

Link for the analysis document can be read in this link

Hi dojoers,

Finally, after bugging around with algorithm to change Quaternion to Euler rotation system... The Opera implementation for GFX 2.0 is out... It is around 90% though (I need mathematician who understand about good camera management).

Since the Firefox and Opera implementation are already out... So I already achieved the unification API feature of GFX 2.0... After mid evaluation, I want to jump into high level of GFX 2.0 to make interactive 3D module... such as loading 3d model... and easy 3d environment loader file... I also want to make a real world example...