The Lively Kernel A Self-supporting System on a Web Page

Ingalls, Daniel H. H.; Palacz, Krzysztof; Uhler, Stephen A.; Taivalsaari, Antero; Mikkonen, Tommi

doi:10.1007/978-3-540-89275-5_2

Cited by 37 publications

(17 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Morphic first appeared in the SELF environment [47], then in the Squeak Smalltalk environment [48], and lastly in the Lively Kernel environment for web development [49] (see Figure 2.12).…”

Section: Morphicmentioning

confidence: 99%

See 1 more Smart Citation

Object-focused environments revisited

Olivero

Lanza

D’Ambros

2015

Science of Computer Programming

View full text Add to dashboard Cite

“…Morphic first appeared in the SELF environment [47], then in the Squeak Smalltalk environment [48], and lastly in the Lively Kernel environment for web development [49] (see Figure 2.12).…”

Section: Morphicmentioning

confidence: 99%

“…Directness and liveness are the two design principles behind Morphic, consisting in a simple architecture based on composable morphs, which define a visual appearance, a set of children in the form of sub-morphs, and an event handler for the mouse and keyboard events [49].…”

Section: Morphicmentioning

confidence: 99%

Object-focused environments revisited

Olivero

Lanza

D’Ambros

2015

Science of Computer Programming

View full text Add to dashboard Cite

“…We show the problems of insufficient separation between tools and objects and discuss two approaches that address these. Figure 1 shows a very abstract overview of self-supporting development environments [8] such as Squeak [9] and Lively Kernel [10]. The environment has to be bootstrapped at some point.…”

Section: Self-supporting Development Environmentsmentioning

confidence: 99%

“…Self-supporting development environments such as Smalltalk [6], Self [18], Emacs [17], Squeak [9], and Lively Kernel [10] are systems where developers can evolve their environment while they are using it. All of these environments keep the software development tools such as editors, debuggers, or code browser in the same environment as the objects and meta-objects they are working on.…”

Section: Introductionmentioning

confidence: 99%

Scoping changes in self-supporting development environments using context-oriented programming

Lincke

Hirschfeld

2012

Proceedings of the International Workshop on Context-Oriented Programming - COP '12

View full text Add to dashboard Cite

Interactive development in self-supporting systems like Smalltalk or the Lively Kernel allows for an explorative and direct development workflow. Because of the immediate and direct feedback loops, changes to core behavior can lead to accidentally breaking the programming tools themselves. By separating the tools from the objects they work on, this fatal self referentiality can be avoided, but at the expense of interactive development. In this paper we show how contextoriented programming (COP) can be used to separate tools from the objects under development. Instead of directly modifying meta-structures, changes should go into layers on top of these structures. Since layers can be scoped at run-time, changes do not affect the programming tools. We demonstrate this approach by showing examples of adapting core behavior in our self-supporting development environment Webwerkstatt with ContextJS, our COP extension for JavaScript.

show abstract

“…Due to the growth of demands for more comprehensive user interfaces, the size and the complexity of web applications are increasing. Moreover, JavaScript is also becoming a general-purpose computing platform [17] for office applications [14,15], browsers [9,10], program development environments [13], and even server-side applications [5,18].…”

Section: Introductionmentioning

confidence: 99%

Naming anonymous javascript functions

Mirghasemi

Barton

Petitpierre

2011

Proceedings of the ACM International Conference Companion on Object Oriented Programming Systems Languages and Applications Com

View full text Add to dashboard Cite

JavaScript developers create programs by calling functions and they use functions to construct objects. JavaScript development tools need to report to developers about those functions and constructors, for example in debugger callstacks and in object representations. However, most functions are anonymous: developers need not to specify names for functions. Based on our analysis of ten large, widely used JavaScript projects, less than 7% of JavaScript functions are named by developers. After studying examples from these JavaScript projects, we propose Static FunctionObject Consumption, a principled, automated approach based on local source code analysis for providing names to nameless JavaScript functions. We applied our approach to 90000 anonymous functions that appeared in the analyzed JavaScript projects. The approach is successful in naming more than 99% (91% are unique within their file) of anonymous functions while the average length of function names is kept less than 37 characters.

show abstract

The Lively Kernel A Self-supporting System on a Web Page

Cited by 37 publications

References 5 publications

Object-focused environments revisited

Object-focused environments revisited

Scoping changes in self-supporting development environments using context-oriented programming

Naming anonymous javascript functions

Contact Info

Product

Resources

About