Smalltalk › Smalltalk Related › Lively Kernel

How to Understand Exisiting Components

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Sean P. DeNigris

How to Understand Exisiting Components

Administrator

I share the following as a contribution, fwiw…

Where should I be looking for answers? Is there a tutorial for exploring the system? I've seen videos of how to plug together existing components, but I'm interested in digging into them to learn to build my own...

Lively Engine Experience:
- Investigating Buttons
- Let's say I want to see what the "2 cylinders" button does. I bring up the halo, but the button also fires. When I select "M", the menu briefly flashes, then disappears. I finally [1] figure out I have to hold the mouse down to keep the menu open (awkward).
- the start and ignition buttons will not bring up halos at all
- Okay, I have an inspector and object editor open for the button, but they show no scripts, and the menu shows no connections
- The inspector
- To look at the text in the ignitionMenu, I have to discover: ignitionMenu->itemMorphs->0->textChunks->0->chunkNode->childNodes->0->data

Questions:
- How to find out what a button does?
- How to bring up an inspector on a sub-item? The standard cmd+shift+i doesn't do anything

[1] I say finally because the fact that the button was firing made me think that the menu was closing because the cylinder chooser appeared. I wasn't until I got the menu open on the step button and experienced the same thing that I understood that to be the "normal" menu behavior for buttons. Moral: multiple confusing things are more confusing that the sum of their parts

Cheers,
Sean

Sean P. DeNigris

Re: How to Understand Exisiting Components

Administrator

A few of my own answers...

Sean P. DeNigris wrote

Where should I be looking for answers?

I found http://lively-kernel.org/repository/webwerkstatt/documentation/livedoc very helpful

Sean P. DeNigris wrote

Okay, I have an inspector and object editor open for the button, but they show no scripts
…
- How to find out what a button does?

Okay, figured that one out. The cylinder button has:
this.addScript(function onMouseUp(evt) {
lively.morphic.Menu.openAt(evt.getPosition(), 'Number of cylinders', this.menuItems); }).tag([]);
Maybe the editor showing no scripts was on the button label…

Sean P. DeNigris wrote

- the start and ignition buttons will not bring up halos at all

LivelyEngine was deleting and rebuilding all the buttons on every click to update the button labels (e.g. in setRunning)

Cheers,
Sean

Lincke, Jens

Quick Browsing Webwerkstatt

Hi, all

since not everybody likes to use apaches index to navigate you may also have more fun

using index pages such as http://lively-kernel.org/repository/webwerkstatt/index.xhtml for navigation.

They will load a world at a time directly into the container world (without booting a complete lively again).

You even can modify the contents of the world directly in the browser, but the user experience may vary since

we did not build lively world to edit them this way (think of global offsets or the fact that there is a world inside a world).

Module dependencies are loaded on demand (but not unloaded) so some worlds may break the browsing experience of other worlds

if they require modules that don't play nicely. But since this is practically not the case, this is not really an issue.

Sometimes you get errors when loading a world, this indicates that either the world has a problem anyway which needs fixing or

the world does not like the way it was loaded.

Some worlds, such as http://lively-kernel.org/repository/webwerkstatt/documentation/index.xhtml, even contain buttons to created new worlds based on a template. I use this feature for creating a new world every day in my journal, but it also comes in handy for quickly creating documentation page.

Using such quick browsing will let you explore much more content in the lively Wiki. This will also show you a lot of outdated worlds or plain garbage.

Feel free to use the "delete" button, or rename button (works only when not changing levels in a wiki), or the "saveAs" button and delete the old world.

This destroys the svn history, but it works across directory levels.

The changes to the wiki can be observed here: http://lively-kernel.org/repository/webwerkstatt/ChangeLog.xhtml

Have fun browsing,

Jens

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

Steve Thomas

Re: Quick Browsing Webwerkstatt

The video tutorials are great and I love the subtitling feature to make creating tutorials simpler and faster.

FYI the link for Lively2 Overview is broken.

Cheers,

Stephen

On Thu, Feb 6, 2014 at 11:23 AM, Lincke, Jens <[hidden email]> wrote:

Hi, all

since not everybody likes to use apaches index to navigate you may also have more fun

using index pages such as http://lively-kernel.org/repository/webwerkstatt/index.xhtml for navigation.

They will load a world at a time directly into the container world (without booting a complete lively again).

You even can modify the contents of the world directly in the browser, but the user experience may vary since

we did not build lively world to edit them this way (think of global offsets or the fact that there is a world inside a world).

Module dependencies are loaded on demand (but not unloaded) so some worlds may break the browsing experience of other worlds

if they require modules that don't play nicely. But since this is practically not the case, this is not really an issue.

Sometimes you get errors when loading a world, this indicates that either the world has a problem anyway which needs fixing or

the world does not like the way it was loaded.

Some worlds, such as http://lively-kernel.org/repository/webwerkstatt/documentation/index.xhtml, even contain buttons to created new worlds based on a template. I use this feature for creating a new world every day in my journal, but it also comes in handy for quickly creating documentation page.

Using such quick browsing will let you explore much more content in the lively Wiki. This will also show you a lot of outdated worlds or plain garbage.

Feel free to use the "delete" button, or rename button (works only when not changing levels in a wiki), or the "saveAs" button and delete the old world.

This destroys the svn history, but it works across directory levels.

The changes to the wiki can be observed here: http://lively-kernel.org/repository/webwerkstatt/ChangeLog.xhtml

Have fun browsing,

Jens

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

To some of us, writing computer programs is a fascinating game. A program is a building of thought. It is costless to build, weightless, growing easily under our typing hands. If we get carried away, its size and complexity will grow out of control, confusing even the one who created it. This is the main problem of programming. It is why so much of today's software tends to crash, fail, screw up.

When a program works, it is beautiful. The art of programming is the skill of controlling complexity. The great program is subdued, made simple in its complexity.

- Martin Harverbeke (from Eloquent JavaScript)

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

Lincke, Jens

Re: Quick Browsing Webwerkstatt

oh, thanks, I moved it to documentation (and did not think about the link).

btw: these hyperlinks can be edited by marking the text and pressing CMD+K or (CTRL+K) respectively... and not forget to save the world. ;-)

Am 07.02.2014 um 13:17 schrieb Steve Thomas <[hidden email]>:

The video tutorials are great and I love the subtitling feature to make creating tutorials simpler and faster.

FYI the link for Lively2 Overview is broken.

Cheers,

Stephen

On Thu, Feb 6, 2014 at 11:23 AM, Lincke, Jens <[hidden email]> wrote:

Hi, all

since not everybody likes to use apaches index to navigate you may also have more fun

using index pages such as http://lively-kernel.org/repository/webwerkstatt/index.xhtml for navigation.

They will load a world at a time directly into the container world (without booting a complete lively again).

You even can modify the contents of the world directly in the browser, but the user experience may vary since

we did not build lively world to edit them this way (think of global offsets or the fact that there is a world inside a world).

Module dependencies are loaded on demand (but not unloaded) so some worlds may break the browsing experience of other worlds

if they require modules that don't play nicely. But since this is practically not the case, this is not really an issue.

Sometimes you get errors when loading a world, this indicates that either the world has a problem anyway which needs fixing or

the world does not like the way it was loaded.

Some worlds, such as http://lively-kernel.org/repository/webwerkstatt/documentation/index.xhtml, even contain buttons to created new worlds based on a template. I use this feature for creating a new world every day in my journal, but it also comes in handy for quickly creating documentation page.

Using such quick browsing will let you explore much more content in the lively Wiki. This will also show you a lot of outdated worlds or plain garbage.

Feel free to use the "delete" button, or rename button (works only when not changing levels in a wiki), or the "saveAs" button and delete the old world.

This destroys the svn history, but it works across directory levels.

The changes to the wiki can be observed here: http://lively-kernel.org/repository/webwerkstatt/ChangeLog.xhtml

Have fun browsing,

Jens

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

--

To some of us, writing computer programs is a fascinating game. A program is a building of thought. It is costless to build, weightless, growing easily under our typing hands. If we get carried away, its size and complexity will grow out of control, confusing even the one who created it. This is the main problem of programming. It is why so much of today's software tends to crash, fail, screw up.

When a program works, it is beautiful. The art of programming is the skill of controlling complexity. The great program is subdued, made simple in its complexity.

- Martin Harverbeke (from Eloquent JavaScript)

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

Steve Thomas

Re: Quick Browsing Webwerkstatt

Got it. So when I tried CMD+K after highlighting the hyperlink I got a workspace open up with the word "nothing". It was hard to just highlight the hyperlink as when I tried to highlight it opened the link in a new tab (using Chrome Version 31.0.1650.63)

Also when I tried CMD+L I got a different looking TextAttributePanel than the one in the video (probably, the challenges of keeping video documentation up to date)

FYI: CMD+U does underline, but when I try again it does not underline.

I know this is a work in progress but I am very anxious to go Back to the Future (HyperCard as the model for the Web instead of HTML/DOM). Anyway, given that this is a work in progress, I am not sure how much I should be testing and mentioning bugs as I find them or what it the best forum for doing so.

Cheers,

Stephen

On Fri, Feb 7, 2014 at 8:10 AM, Lincke, Jens <[hidden email]> wrote:

oh, thanks, I moved it to documentation (and did not think about the link).

btw: these hyperlinks can be edited by marking the text and pressing CMD+K or (CTRL+K) respectively... and not forget to save the world. ;-)

Am 07.02.2014 um 13:17 schrieb Steve Thomas <[hidden email]>:

The video tutorials are great and I love the subtitling feature to make creating tutorials simpler and faster.

FYI the link for Lively2 Overview is broken.

Cheers,

Stephen

On Thu, Feb 6, 2014 at 11:23 AM, Lincke, Jens <[hidden email]> wrote:

Hi, all

since not everybody likes to use apaches index to navigate you may also have more fun

using index pages such as http://lively-kernel.org/repository/webwerkstatt/index.xhtml for navigation.

They will load a world at a time directly into the container world (without booting a complete lively again).

You even can modify the contents of the world directly in the browser, but the user experience may vary since

we did not build lively world to edit them this way (think of global offsets or the fact that there is a world inside a world).

Module dependencies are loaded on demand (but not unloaded) so some worlds may break the browsing experience of other worlds

if they require modules that don't play nicely. But since this is practically not the case, this is not really an issue.

Sometimes you get errors when loading a world, this indicates that either the world has a problem anyway which needs fixing or

the world does not like the way it was loaded.

Some worlds, such as http://lively-kernel.org/repository/webwerkstatt/documentation/index.xhtml, even contain buttons to created new worlds based on a template. I use this feature for creating a new world every day in my journal, but it also comes in handy for quickly creating documentation page.

Using such quick browsing will let you explore much more content in the lively Wiki. This will also show you a lot of outdated worlds or plain garbage.

Feel free to use the "delete" button, or rename button (works only when not changing levels in a wiki), or the "saveAs" button and delete the old world.

This destroys the svn history, but it works across directory levels.

The changes to the wiki can be observed here: http://lively-kernel.org/repository/webwerkstatt/ChangeLog.xhtml

Have fun browsing,

Jens

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

--

To some of us, writing computer programs is a fascinating game. A program is a building of thought. It is costless to build, weightless, growing easily under our typing hands. If we get carried away, its size and complexity will grow out of control, confusing even the one who created it. This is the main problem of programming. It is why so much of today's software tends to crash, fail, screw up.

When a program works, it is beautiful. The art of programming is the skill of controlling complexity. The great program is subdued, made simple in its complexity.

- Martin Harverbeke (from Eloquent JavaScript)

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

When a program works, it is beautiful. The art of programming is the skill of controlling complexity. The great program is subdued, made simple in its complexity.

- Martin Harverbeke (from Eloquent JavaScript)

_______________________________________________
lively-kernel mailing list
[hidden email]
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel