Inside Javaos Tm Operating System

Look For Inside Javaos Tm Operating System at Amazon

Today, the utility of a car configurator is well-known: the configurator is an effective tool used in the sales procedure and helps the client in more immediate choosing his preferent configuration, leading him to the proper dealers. It has an primary contribution to the merchandising policies of manufacturers and dealers world-wide. 3D car configurators are new, and ought to be built according to numerous quality rules.

This article discloses the goals pursued by the software engineering science routine of 3DCar(TM), one of the initial (probably the very first) to the full or entire extent interactional 3D car configurators, a project started in 2005, at a time when even 2D car configurators were a rarity. 3DCar (TM) was disclosed to public only a few days ago on YouTube!

The software scheme engineering goals:

  1. easy and fast usage
  2. (fast application loading, destination based ergonomics criteria, colour changes and 3D choices are displayed very fast)

  3. stability
  4. (the chosen technology is authenti for all the purposed platforms)

  5. maximize the interactivity of users with the car
  6. (the client establishes a strong bound with the vehicle by directly exploring respective features and acting on it is interactional parts)

  7. make itself available on assorted means of presentation
  8. (Internet, CDs/DVDs, local PC application, touch-screens, showroom plasma screens etc)

  9. expandability, flexibility
  10. (easily add new software modules packed with new features, easy replacing of current modules with bettered ones, adding new 3D models as easy (and hence cheap) as possible)

  11. maximize exposure by providing higher performance (for high polygon count) with lower system requirements
  12. (the application runs well even on older schemes – this is achieved by: 1) optimization of 3D models and code 2) automatic adaptation by dropping of features with high system requirements to keep it running on older systems)

  13. interfacing with the existent sales system and also including merchandising tools
  14. (ability to order, store client preferences, track the sales process, direct advertising areas, “tell a friend” tool etc)

At the time the project was started, technology for browser embedding was gorgeous unstable, caused significant performance losses and could not sustain the high interactivity of such a complex application.

Other solutions that appeared in the meantime and used respective technologies for browser embedding, used to show a lot of blue-screens and crash the browsers or the whole operating system. 3DCar uses a web-start capacity (like a heap of of the Java apps use) for usage with browser. This assures very good performance and allows it to display models consisting of over 1 million triangles even on 5-6 year old PCs.

However, new technologies were perpetually monitored and finally, a robust and suitable solution seems to have appeared (more on this in a future article).


Inside Javaos Tm Operating System

Inside Javaos Tm Operating System Photo

Inside Javaos Tm Operating System

Inside Javaos Tm Operating System Photo

Inside Javaos Tm Operating System

Inside Javaos Tm Operating System Picture

Inside Javaos Tm Operating System

Inside Javaos Tm Operating System Photo

Inside Javaos Tm Operating System

Inside Javaos Tm Operating System Picture

Inside Javaos Tm Operating System

Inside Javaos Tm Operating System Picture

This entry was posted in Operating Systems and tagged , , , , . Bookmark the permalink.

Leave a Reply