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:
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...
Hi dojoers,
There we go! A new demo page, it has realtime script execution, so you can play around with the library. Notice that, I put some predefined script already as example script... You can change it or do your own in custom script... The purpose of this demo page is to determine whether my API is good or not... Not forget to mention, I will post the class diagram for you to get an abstract idea about the API... Try your best not to see the source code... try to guess from the argument parameter name... I am sorry I cant provide full HTML documentation right now since I will do it later on this project lifetime...
Please go to this to see the demo page and this to see the class diagram...
I would really appreciate if you give some comments, suggestions, or critics... Thanks!
There was a delay in my project, I didn't do much last week - there were
final exams in the university and I had to prepare well. Now, when I finally
finished this term, I can concentrate on the project and be productive.
There were updates on the code since my last blog post.
I added a simple implementation of grouped tokens handling. It can be used
for the cases when you need to treat a set of equal tokens, which go one after
another, as a one big separate token.
So this past week I've been working on a new data flow for our d-rails helpers in rails. I've implemented most of the dojo.fx functionality with this new flow, since it's a relatively small subset of functionality that would give me a pretty good idea if this was going to work well or not.
So let's start.
I'm pretty happy with how the drag and drop is turning out. I have a demo that you can play with, dragging dijit names to create real form objects. The basic functionality is in place, and I can iterate on this for the rest of the summer to turn it into something usable.
Hi dojoers,
Last week is kind of researching week for me... since a lot of things came to me... From interview with Google Sydney (I am applying to work with Google) till "wet week" (people from NSW, AU should know this... Last week was raining all the time)... What have I been researching is what is the best data structure to support the 3d environment graphic? Especially for scene management (such as BSP, Octal, and soon) I also researching for best math calculation to boost the performance...
