[lively-kernel] Lively IDE Mockups

Philip Weaver philmaker at gmail.com
Sat Jun 26 06:51:59 CEST 2010

Hi Steve,

On Wed, Jun 23, 2010 at 1:33 PM, Steve Wart <steve at wart.ca> wrote:

> Yes I noticed that you've done a huge amount of work. I asked about the IDE
> because that is how I conceptualize the object model. Once I understand that
> hopefully all the rest of it will come together for me.
> One thing that Apple insists on when defining the user experience for a new
> application is to come up with a clear statement of purpose. Not only what
> it is its intended user base (casual, professional, etc.), but also what it
> is explicitly not intended for. What *can't* Lively do?.

I'd also consider the role of a user. Is the user primarily a consumer of
content or a producer of content? Lively allows both at the same time.
Sadly, most people in the world today are primarily consumers and not
programmers. I don't have a final answer here but read on further below.
Intended user base is indeed worthy of discussion.

> I've seen a couple of posts from Dan on his vision for Lively, but I still
> wonder, is it an educational environment, or is it something people can use
> to build commercial quality client-server applications?

I have interest in pursuing both of these but lean toward the latter,
commercial development: I want to focus on whatever goals will help sustain
and provide funding for this project. I wish and hope that Lively will
become a disruptive technology to transform web development and web
graphics creation. 1. Browser brings the history and bookmarks. 2. The
toolkit brings it's own rendering and layout: whether it be the Lively
Kernel or other. Web standards? Just say no. Use a canvas instead and your
own toolkit. Also relating to graphics development: just say no to splicing
raster images for web display: render them in Lively.

So for intended user base maybe: 1. professional "web" developers but
retrain them, 2. education

Some of the early Lively collateral discusses making web programming simpler
without HTML, CSS, DOM, etc. The problem has been that Lively has not had
enough layout support to realistically compete or replace HTML and DOM.


> Smalltalk evolved in rather unexpected ways I think. I don't think I'm
> looking for Lively on Rails, but I am interested in applications that appeal
> to mainstream development needs.
> Steve
> On Wed, Jun 23, 2010 at 10:54 AM, Philip Weaver <philmaker at gmail.com>wrote:
>> Emailing from phone. Back online in a day or so. Existing mockups
>> cover more than ide. They are maybe 10% complete and mainly for
>> inspiration. An overview at this point and existing ide mockups are
>> not necessarily accurate. Want to explore things like: zoom to morph,
>> zoom to selection, morph navigation via the main column browser,
>> multiple selection in a column stacks views in the next column,
>> contextual menu as a single column column browser maybe for zoom to
>> morph. Existing mockups need more simplification and some other
>> solutions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.hpi.uni-potsdam.de/archive/lively-kernel/attachments/20100625/839b6070/attachment.htm 

More information about the lively-kernel mailing list