Perkins, what I did until I got the wireless adapter was to run an extra long (phone first, then network) cord over to the TiVo and force a manual update once a day.
Buffistechnology 2: You Made Her So She Growls?
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
The Tivo usually gets guide data for up to two weeks in advance, so even if you just find a way to update it once in that span, you should be okay.
If the schedule doesn't change.
I have no idea how often that happens.
How do you force a manual update?
I have phone cord that will reach the jack if I run it across the room at knee level. I can leave that set up for the week I am gone, but I can't leave it up full time once the cats get here, since it would be right at their eye level. I could set it up once a day just for a short while though.
Working from (vague) memory:
If you go into connection settings, you can test or "connect now."
::googles::
Aha -- TiVo Central>Messages & Setup>Settings>Phone & Network>Connect to the TiVo service now
I think that it's entirely dependent on the application that's being modelled.
You're right, he's wrong. Unneeded abstraction is one of the things that kills large software projects.
What do you think of UML so far? To me, it seems like a ton of work for very little benefit. I'd rather just draw basic block diagrams for the overview and then do class definitions for the details.
I'm coming at UML from a conceptual angle.
I'm looking for a way to communicate with both the developers and the business users about the process at hand. UML looks like (if my developers understand it, which I doubt) I can use it to lay out pre-development application architecture/requirements for my myriad required documents.
So if we all agreed on it, I'd be fine using it for high level sequence diagrams, for instance. And use case diagramming.
Thing is, we're pretty much a waterfall development environment, and this teacher is tying UML pretty tightly to very iterative development. I dont think it's as causal as he says, though.
I'm not sure it'd help me write code if I were doing the analysis myself. I may try and write up the Phoenix and see what happens.
Still, it's helping regularise my self-taught OOP stuff, and can go on my resumé.
What is UML? Some type of markup language, I'm guessing.
UML is a detailed form of diagramming used mostly in software development.
See, I think UML makes more sense for waterfall. You can do the diagrams once and then execute on them. Maybe you change them a little bit as you go along, but not much.
In iterative, you'd have to change them over and over again. I doubt most people would, and you'd end up with the diagrams not matching the sytem.
Current instructor sees iterative as repeteadly modifying the diagrams to look progressively less and less like the "problem domain" and more like the solution architecture. Also, to pick the high profile use cases and start from there.