Again, supporting real- time collaboration in a project of this size is a demanding endeavor since the same implementation steps are required as for the conversion of the CKEditor. Like CKEditor, SVG-edit is also implemented in JavaScript accounting for approximately 30 000 lines of code. The tool palette as well as the canvas of the SVG-edit is shown in Figure 2. SVG-edit provides common graphics tools to accomplish typical drawing operations such as create lines, ellipses, rectangles, text, fill shapes or modify stroke styles. SVG-edit has more than 18 000 downloads of its current release version 2.51 and a development team of 17 committers and contributors). The single-user editor called SVG-edit is another widespread open source project supported by a very active community (i.e. Therefore, we selected a graphics editor capable of producing scalable vector graphics (SVG). Besides shared editing, shared drawing represents a second important collaboration domain. usability, efficiency) and collaboration characteristics (e.g.
#Svg web editor software#
Additionally, we show in Section 5 that the transformed CKEditor meets user requirements with respect to accepted software qualities (e.g. In Section 4 we demonstrate how the proposed generic collaboration approach can transform CKEditor into a collaborative multi-user editor. Amongst other things, the traditional development approach comprises the following tasks: (1) implementing a state-of-the-art conflict resolution scheme, (2) setting up a communication infrastructure to distribute synchronization messages and (3) intercepting as well as serializing user input in a dedicated messaging format.
#Svg web editor code#
However, introducing shared editing facilities in an established open source project with a JavaScript code base of more than 110 000 lines of code is not a trivial task. The large CKEditor customer base consisting of enterprises, nonprofit organizations and individual users is also confronted with joint tasks where shared editing capabilities could speed up the task execution. Since its first release in 2003, CKEditor has been widely adopted resulting in 3.5 million downloads. Google Docs), CKEditor is primarily meant to be embedded in web pages. In contrast to standalone office suites (e.g. CKEditor is a word processor offering common features such as text formatting, im- age insertion or text alignment. One prominent single-user editor is the open source project CKEditor depicted in Figure 1. Hence, multiple users may work simultaneously leveraging converted editors. Transforming these editors into collaborative multi-user editors could sig- nificantly broaden the application scope since converted editors enrich existing capabilities with shared editing support. Adobe Photoshop Express, SVG-edit) featuring only single-user support. Cloud9 IDE, Eclipse Orion) and graphics editors (e.g. Adobe Buzzword, CKEditor), integrated development environments (e.g. For instance, there are word processors (e.g. However, numerous web-based editors provide solely single-user support without shared editing capabilities. For example, teammates can jointly create documents, spreadsheets or presentations leveraging web-based office suites such as Google Docs or Microsoft Office Web Apps. Web-based groupware systems have proven to support ge- ographically dispersed teams in a variety of tasks. Section 7 compares our work to the state-of-the-art and Section 8 exhibits conclusions as well as future work.
Section 6 dis- cusses the limitations of the generic transformation approach and derives requirements for convertible web applications. Section 5 shows the results of the conducted user study evaluating the collaboration qualities of two converted editors. Section 4 illustrates an architecture and an implementation realizing the generic transformation approach and the process of converting existing single-user editors into multi-user editors. Section 3 elab- orates on the challenges designing a generic transformation approach for web editors. rest of this paper is organized as follows: Section 2 provides motivating examples introducing two single-user editors suitable for shared editing scenarios.
0 kommentar(er)
