smalltalk
/
osmo-st-core
Archived
1
0
Fork 0
Code Pull Requests Releases Activity

core: Add proper categories to the class, call it OsmoCore

This commit is contained in:
Holger Hans Peter Freyther 2011-09-27 16:09:34 +02:00
parent 22f6836925
commit 2390e42814
3 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Dispatcher.st
View File

@ -18,7 +18,7 @@
Object subclass: Dispatcher [
| queue dispatch quit |
<category: 'OSMO-Core'>
<category: 'OsmoCore'>
<comment: 'I run tasks from the same context.'>
Dispatcher class >> instance [

4
LogArea.st
View File

@ -19,6 +19,8 @@
PackageLoader fileInPackage: #OsmoLogging.
Osmo.LogArea subclass: LogAreaTimer [
<category: 'OsmoCore-Logging'>
LogAreaTimer class [
areaName [ ^ #timer ]
areaDescription [ ^ 'Timer related' ]
@ -32,6 +34,8 @@ Osmo.LogArea subclass: LogAreaTimer [
]
Osmo.LogArea subclass: LogAreaCore [
<category: 'OsmoCore-Logging'>
LogAreaCore class [
areaName [ ^ #core ]
areaDescription [ ^ 'Core related things' ]

4
Timer.st
View File

@ -19,7 +19,7 @@
Object subclass: Timer [
| schedule timeout block |
<category: 'OSMO-Timer'>
<category: 'OsmoCore-Timer'>
<comment: 'This is a receipt for an active timer'>
Timer class >> on: aSchedule [
@ -68,7 +68,7 @@ Object subclass: Timer [
Object subclass: TimerScheduler [
| queue sem loop quit |
<category: 'OSMO-Timer'>
<category: 'OsmoCore-Timer'>
<comment: 'I can help to fire things at the right time. Right now I
only work on seconds granularity because Time has no direct access to
milliseconds. Also I run a loop every second. I should use a Semaphore to