Jim writes:
Modified NEXT-TIMESLOT so if it is called without the optional scheduler and there is no *DEFAULT-SCHEDULER*, a default scheduler is created and bound to *DEFAULT-SCHEDULER*.
Good one!
Managed to get bitter by the lack of a PROCESS method for CPU-MONITOR this morning (no, yesterday morning).
Quick cheat, until we know what to do with it: (defmethod process ((mon cpu-monitor)) nil)
I'm populating a LINUX-HOST equipment with data and will hopefully have time to get data flowing from one lisp instance to another either beginning of next week or over the weekend, depending on how much hack time there is.
Unfortunately, this means my source code is FULL of stuff that really should be submitted together, so I'll hold off checking in any changes for now.
//Ingvar
Jim writes:
Modified NEXT-TIMESLOT so if it is called without the optional scheduler and there is no *DEFAULT-SCHEDULER*, a default scheduler is created and bound to *DEFAULT-SCHEDULER*.
Good one!
Glad I didn't screw things up too bad ;P
Managed to get bitter by the lack of a PROCESS method for CPU-MONITOR this morning (no, yesterday morning).
Quick cheat, until we know what to do with it: (defmethod process ((mon cpu-monitor)) nil)
I did the same in my REPL :)
I'm populating a LINUX-HOST equipment with data and will hopefully have time to get data flowing from one lisp instance to another either beginning of next week or over the weekend, depending on how much hack time there is.
Unfortunately, this means my source code is FULL of stuff that really should be submitted together, so I'll hold off checking in any changes for now.
Big commits kinda suck, don't they? :P :)
I'm working on some web stuff which, simularly, I am planning on committing in one fell swoop.
Does anyone have an opinion on if the web UI stuff should have its own subdirectory?
Jim
Jim writes:
I'm populating a LINUX-HOST equipment with data and will hopefully have time to get data flowing from one lisp instance to another either beginning of next week or over the weekend, depending on how much hack time there is.
Unfortunately, this means my source code is FULL of stuff that really should be submitted together, so I'll hold off checking in any changes for now.
Big commits kinda suck, don't they? :P :)
Well, the bits that were, on the whole, localised to packages.lisp and network.lisp I checked in as I went. Now it's just the rest of the code... (that touches, at least, scheduler.lisp and classes.lisp).
What I have now is: head$ cvs status | grep File | grep -v Up-to-date cvs status: Examining . cvs status: Examining docs cvs status: Examining test-files File: classes.lisp Status: Needs Merge File: network-globals.lisp Status: Locally Modified File: network.lisp Status: Locally Modified File: packages.lisp Status: Locally Modified File: scheduler.lisp Status: Locally Modified
I'm working on some web stuff which, simularly, I am planning on committing in one fell swoop.
Does anyone have an opinion on if the web UI stuff should have its own subdirectory?
Unless it's going to be more than 6-10 files, I think it can live in the same directory, though it should probably have its own ASDF file. However, I will not complain if it's subdirectoried off.
//Ingvar
Unless it's going to be more than 6-10 files, I think it can live in the same directory, though it should probably have its own ASDF file. However, I will not complain if it's subdirectoried off.
I was really thinking of adding two files: web.lisp (I'll take suggestions for a better name) and style.css - I'm really not sure where to put the style sheet - really, I intend it to be modified locally so your monitor can match your corporate colors, etc. ;P
Initially, I was thinking of generating the CSS from Lisp, but then I thought better of it and decided I'd rather be able to hand the style sheet to some web monkey to make my page pretty (and web monkeys don't know Lisp ;) and I don't want the latest CVS version of the web code to kill the style sheet I worked so long and hard on ;P .
Jim
-
Ingvar -
Jim Prewett