Leturn is JS framework completely based on OOP. As we know, normally, it's unreasonable to implement a fully OOP substantially in Javascript. Especially, it's so more and more because there is no accessor for a parent class on the inheritance relationship and encapsulation and interface are also impossible in current Javascript. However Leturn is trying to access doing conceptually. In other words,it is to access and understanding of the development methodology right side not with or without the possibility according to the features and technical support. In addition, the final direction Leturn aims is to provide useful web component-sets. Through this, it's blueprint of the ideal and goal that ever will help to be possible to develop web applications faster. In addition there are many excellent and highend-grade frameworks for Javascript currently. I don't recommend using Leturn of them, If you want to use this for the easier and more convenient to handle, controll and access them of elements in a web page. In short, it may not be a proper imposition of easy-to-use. Of course, Leturn also provides the base functions as such, but it is only provided because they are basic foundation to implement a complex big thing. Therefore, naming of majority framework members of Leturn are not short because it is a natural process to avoid naming-duplication of members when proceeding the inheritance and increasing intuitive of OOP. In addition, in order to perform one of the largest it avoids thoroughly the situation provided that is integrated in one place. For example as for scrollbar, so as to provide it for a developer, it can put all the features into a one class but so in that case, it only just looks like OOP apparently shown, his role is not different from the general function library. The scrollProvider and the interface scrolling for it are separated for the effective reproduction by the related class of Leturn because a slider has a similar design with scrollbar. And required drag object is also divided. AshAPI that the initial version of the Leturn framework was begun in 2007 was developed based on the event and class modeling of AS3.0 from first development timing. Everything is thoroughly the class consists of a base, in canvas element case it can be a good example for the introduction of AS3.0 modeling in Leturn. Leturn은 OOP와, 클래스 정의 및 멤버 구성 이벤트처리 및 네이밍에서 AS3.0모델링을 기반으로 하기때문에, 웹요소에 대한 빠른핸들링과 간편한 작업에는 적합하지 않을수 있다. 간편한 작업보다, 복잡하고, 실제 구현하기 어렵거나 귀찮은 부분들, 그리고 대규모 프로젝트에서 확실하고 유용한 웹콤포넌트셋을 제공하여, 이를 체계적으로 관리하고, 좀더 나은 잇점을 제공하는것이 최고의 목적임으로, 쉽게 사용하는 간단한 네이밍보다, 직관적이고, 구분이 확실한 구조를 우선시한다. 또 재사용과 향상성을 중요시하기 때문에, 구조를 도식화하고 이를 클래스화하며, 설계할때 번잡함이 따를수 있지만, 방대한 코드들에 대한 중복을 최대한 피함이 최우선 원칙임으로, 실제 많은 Asset들에 비해 코드의 크기는 상대적으로 적을것이다. 만약, 일반적이고 일상적인 작업들을 위한 웹요소의 빠른접근과 조작이 최우선일경우 이 프레임웍은 적합한 대안이 아닐지 모른다.