Hi,
For all the Lively users who are unhappy by current implementation for error reporting and logging, there is now an alternative that displays global error messages, "console.log" logs and other status messages like "alert" statements in a console window (similar to the "Transcript" in Squeak). The system console can be found in the World menu under "Tools". Cheers, Christopher _______________________________________________ lively-kernel mailing list [hidden email] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel |
Hi Christopher:
A question / confirmation how I can enable it : when a system console is placed on a world, all messages go there instead of the top-right corner popups? (it seems that's how it works and it is a great piece of functionality)
thanks milan
On Thu, May 24, 2012 at 1:11 PM, Christopher Schuster <[hidden email]> wrote: Hi, _______________________________________________ lively-kernel mailing list [hidden email] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel |
I see, thanks
On Thu, May 24, 2012 at 3:21 PM, Christopher Schuster <[hidden email]> wrote: The way it works is that all log messages get displayed in the _______________________________________________ lively-kernel mailing list [hidden email] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel |
Good People of Lively -
I think our default parts bin could use some cleanup and documentation. As a first step, each part should be tested (for many parts, this will be fun), and its description added or improved as appropriate. As a second step, I think it would be handy if every category included a part named, eg, AboutDatabase, AboutBejeweled, etc., which can be just a simple textMorph or something more comprehensive, summarizing what's in the category, and how they work together if they happen to be components of a larger application. The name "AboutX" is suggestive to newbies, will typically appear first, alphabetically and can be searched for in a regular manner. In the process, we may find parts that are broken or not useful, and reviewers could post their observations, and leave it up to the "owners" (I realize this is a loose concept here) to delete, fix or improve the parts in question. Or not. In order to minimize confusion as a community process, if you like this idea and want to clean up a category, then as your *first action*, publish an "About" morph for that category that states that you are in the process of cleaning it up, and leave that statement at the beginning until you are done. That way others can know not to interfere until you are done. Have fun! _______________________________________________ lively-kernel mailing list [hidden email] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel |
Free forum by Nabble | Edit this page |