Hi Lauritz -

I am a bit indecisive when it comes to adding UI elements vs. having more code 
in the code pane. So here are my thoughts on that:

On the one hand you could argue that keeping the UI of the script editor clean 
and easy is a good idea looking at how browser (e.g. the SCB) do look like. But 
I think that you should also hide as many "implementation details" of how 
scripts are added and categorized/tagged, meaning that even this.addScript(...) 
(and therefore .categorize(...) too) is some kind of information a 
beginner/user should not need to see. So an additional one-line text morph for 
"tagging" would be a simple and nice solution.
On the other hand even the "implementation details" might be interesting for 
people who e.g. want to add scripts programmatically (you could argue) but this 
is not majority of users. So in my opinion it really only adds clutter to what 
you really want to see/do.
Also moving towards a system without files (and therefore no textual JS 
representation of scripts), this feels wrong to me.

So what do you think? Comments, thoughts? ;-)

Best,

- Marko


PS: I also have to add that I never really saw the need for method categories 
and the only systems/languages (I know) that do have this are Lively and 
Squeak... :-/


On Nov 28, 2011, at 20:51 , Lauritz Thamsen wrote:

Hi.

We added script tagging to our Object 
Editor<http://www.lively-kernel.org/repository/webwerkstatt/documentation/livedoc/Tools/ObjectEditor.xhtml>
 (Script Editor).

A script might be in several categories at the same time, so we allow multiple 
tags. Further, we don't want the editor to have as many UI elements as our 
System Code 
Browser<http://www.lively-kernel.org/repository/webwerkstatt/documentation/livedoc/Tools/SCB.xhtml>.
 Therefore, we tag scripts like they are added. Programmatically in the 
editor's script pane:

this.addScript(function example() {
alertOK('hello');
}).categorize(['example', 'public']);

Any feedback or comments? :-)

Best,
Lauritz
_______________________________________________
lively-kernel mailing list
[email protected]<mailto:[email protected]>
http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel

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

Reply via email to