... methinks SlashDot may be spammed by m$monkeys. Many of my Google searches on this topic ended me up at the msdev site.I resist temptation to drop US$15000 to be m$certified.
State machines, statecharts, all seems a tad modal to me. State, to me, is simply a piece of information and calling it "state" and giving it this whole modal metaphor simply confuses. I hear a FUDding sound
progging by example, examples, lots of examplesoh, and we're "modelling" here we don't actually need to do any coding
A button object definition
(aka a class) with various interface methods (messages/questions you can command/ask of this object) that I choose to dangle off of it:
Is button down Is button up
Buried underneath/within/externally/remotely of this object somewhere, that no one needs to know about, is some storage that somehow indicates whether the button is currently "up" or "down." I guess some might call this the "state" of the button.
my dream is to run lots of 10/100basedT wiring around the neighbourhood, power the hubs/switches to connect it all with solar power. Plug in regular pulse/tone dial phones into a small self-powered "telephone to ethernet" RJ11/RJ45 adaptors. The adaptor handles all the telephony/funny protocols (with the help of an embedded inux or bsd) and let's you dial out to IP addresses. And the phone rings for incoming calls to your IP address. The IP address and embedded software is configurable, of course.
I know this goes against normal geek mantra of the bigger and faster the CPU the better. And it seems to me, that you guys recommend computers based mostly on the CPU. I could careless about the CPU, to me the most important component of a computer is the monitor and the bigger the better and the easier on the eyes the better. And yes, I hope flat screens will replace cathode ray tubes altogether. rant finished.
Here is an idea to create "private" identification cards. Using our computers, we often create certificates and awards of merit for people. I propose simply creating our own id cards for ourselves. These are not forgeries and they are not in anyway fraudulent because the identification cards we create are our own totally original works.
I know of someone who is without a valid drivers license because a certain government department requires a "breeder" card to issue a new drivers license. This person applied for the breeder card in the state of their birth where there is currently a strike by the government workers. The person is stuck because the state of their birth won't issue a birth certificate unless the person succumbs to a medical emergency in a foreign country. This person has had a warning and a US$70 fine for driving without a valid driver's license because of bureaucracy in this matter.
This person has decided to leave the State of Fear and take some responsibility and use some imagination and create their own driver's license. Of course, the Dept. of Motor Vehicles of various organizations will still have to approve such a card but in the meantime the "private" drivers license will be shown to interested law enforcement officers.
I invite the "many" lawyers to offer help in this matter.
Use free (gratis) and free (open source, GPL) portable development tools. Some popular dev tools: cygwin, java, perl, php, python and others. Stop using costly, proprietary, platform-specific tools. vi$ual$tudio is not visual, it is an ugly cumbersome interface wrapping an ugly command line poor excuse for a compiler. I hear that programmers at m$ don't even use it. In learning to use m$ tools I eventually learned the wisdom in avoiding using these tools.
Historically, Win32 APIs are derived from Win16 APIs derived from Excel for DOS (a GUI spreadsheet with windows) ported from Excel for Macintosh that used the Macintosh APIs. The Win APIs still look very similar to the original Macintosh APIs. Learn to wrap(hide and bury) these ugly APIs in your own real portable functions/classes. Don't ever call someone else's functions directly. For example, create a function myRunMainEventLoop that works for Windows, Macintosh, OpenGL, KDE, Gnome, pure XWindows and whatever platform.
Slashdot Mirror
I won't use Opera for Windows because it uses Windows MDI multiple document interface. But some people like this feature of Opera.
Enjoy the opera.
Lameness filter encountered. Post aborted!
... methinks SlashDot may be spammed by m$monkeys. Many of my Google searches on this topic ended me up at the msdev site.I resist temptation to drop US$15000 to be m$certified.
State machines, statecharts, all seems a tad modal to me. State, to me, is simply a piece of information and calling it "state" and giving it this whole modal metaphor simply confuses. I hear a FUDding sound
progging by example, examples, lots of examples oh, and we're "modelling" here we don't actually need to do any coding
(aka a class) with various interface methods (messages/questions you can command/ask of this object) that I choose to dangle off of it:Buried underneath/within/externally/remotely of this object somewhere, that no one needs to know about, is some storage that somehow indicates whether the button is currently "up" or "down." I guess some might call this the "state" of the button.
clear as mud
my dream is to run lots of 10/100basedT wiring around the neighbourhood, power the hubs/switches to connect it all with solar power. Plug in regular pulse/tone dial phones into a small self-powered "telephone to ethernet" RJ11/RJ45 adaptors. The adaptor handles all the telephony/funny protocols (with the help of an embedded inux or bsd) and let's you dial out to IP addresses. And the phone rings for incoming calls to your IP address. The IP address and embedded software is configurable, of course.
I know this goes against normal geek mantra of the bigger and faster the CPU the better. And it seems to me, that you guys recommend computers based mostly on the CPU. I could careless about the CPU, to me the most important component of a computer is the monitor and the bigger the better and the easier on the eyes the better. And yes, I hope flat screens will replace cathode ray tubes altogether. rant finished.
Here is an idea to create "private" identification cards. Using our computers, we often create certificates and awards of merit for people. I propose simply creating our own id cards for ourselves. These are not forgeries and they are not in anyway fraudulent because the identification cards we create are our own totally original works.
I know of someone who is without a valid drivers license because a certain government department requires a "breeder" card to issue a new drivers license. This person applied for the breeder card in the state of their birth where there is currently a strike by the government workers. The person is stuck because the state of their birth won't issue a birth certificate unless the person succumbs to a medical emergency in a foreign country. This person has had a warning and a US$70 fine for driving without a valid driver's license because of bureaucracy in this matter.
This person has decided to leave the State of Fear and take some responsibility and use some imagination and create their own driver's license. Of course, the Dept. of Motor Vehicles of various organizations will still have to approve such a card but in the meantime the "private" drivers license will be shown to interested law enforcement officers.
I invite the "many" lawyers to offer help in this matter.
Use free (gratis) and free (open source, GPL) portable development tools. Some popular dev tools: cygwin, java, perl, php, python and others. Stop using costly, proprietary, platform-specific tools. vi$ual$tudio is not visual, it is an ugly cumbersome interface wrapping an ugly command line poor excuse for a compiler. I hear that programmers at m$ don't even use it. In learning to use m$ tools I eventually learned the wisdom in avoiding using these tools. Historically, Win32 APIs are derived from Win16 APIs derived from Excel for DOS (a GUI spreadsheet with windows) ported from Excel for Macintosh that used the Macintosh APIs. The Win APIs still look very similar to the original Macintosh APIs. Learn to wrap(hide and bury) these ugly APIs in your own real portable functions/classes. Don't ever call someone else's functions directly. For example, create a function myRunMainEventLoop that works for Windows, Macintosh, OpenGL, KDE, Gnome, pure XWindows and whatever platform.