I think java swing is a very good way to handle this. PHP is very powerful and probably could handle everything you need it to do. Fox Toolkit or QT would work well if you don't mind C++. Not sure about licensing issues mixing QT with an open source project, I haven't had need to research that before.
We took measurements of everything and put it in visio to scale. An overhead view and at least a front view of each rack works well. That's for the visual part. For the connections, use a database so it can be easily queried and traced. Full dependency reports may take some SQL wizardry, but can be accomplished if the DB is carefully designed.
I've been using various versions of MySQL for about 7 years now and have had no issues at all. I don't use InnoDB, stored procedures, or subqueries, so I can't speak to those features. I have used replication, extremely long queries, complex joins and unions, and all other common features with no problem. I took many precautions like daily backups, log storage, etc. and never needed them except for restoration of lost data due to user error (user sent query that deleted all entries, or updated all entries, etc.) I have a couple programs I haven't touched in 3 years except for minor cleanup that are still running with no problems. If you're running into issues with MySQL, you must be using new features or versions that just aren't as rock-solid as core MySQL is. I must admit that by design my programs don't run into many concurent update collisions and if they did, it would only be a minor annoyance.
Yes, you would look at your UTC-SLS watch. All schedules would be tracked in UTC-SLS so this isn't the system they had in the 1800's. I wasn't refering to actually changing local time based on sun location. Just work hours could be adjusted. With today's technology, it is easy to broadcast/post start/end times. Companies could go ahead and round off to nearest hour or quarter hour if they prefer. Just indicating local scheduling can vary from place to place or company to company without changing the UTC-SLS time.
The "Everyone starts at the same time" model doesn't work anymore. Groups are spread across time zones and countries. It's nearly as likely for someone working in Chicago to work with someone in Minneapolis, New York City, Denver, or even Bangalore. Computers can adjust fragments just as easily as whole hours. People would be able to adjust as well over time.
You're correct. I meant UTC the way my computer understands it. This would not stay in sync with true UTC time though. After reading more it seems that UTC-SLS is the best idea which allows for slight adjustments at the last 1000 UTC seconds days containing leap-seconds so there are always 86400 seconds in the day.
I still like adjusting work hours to start/end based on noon +/- a number of hours (or fractions of hours).
All time can be universal (UTC). Noon can be "When the sun is directly overhead." which will locally be different. Start time for work can be Noon-3 Hours (3 hours before noon) to Noon+5 Hours (5 Hours after noon). No DST necessary and no leap-seconds necessary. Why do they want to overcomplicate things here?
Reminds me of the Outer Limits show where the clocks were all adjusted to stretch the workday to be longer and longer while shortening off-work hours.
Yes, many old systems have these limitations. The Tandem isn't one of them. It has some more obscure limitations, but you learn to work around them. Take a look sometime at what one of these can do and you'll see many more limitations in most alternatives including systems much newer than this work of genius.
If you can get past its name, try PureBasic. It is compiled and can include inline assembly or direct memory read/write using peek/poke. You can even tell it to generate the assembly code to insure it's doing what you want.
It can be targeted easily for multiple platforms as well as it has assemblers for Linux, Mac, OSX, and Windows.
http://www.purebasic.com/
Sorry for the duplicate, didn't login the first time.
Take the smaller LA program. You'll have a wider education base and enjoy the company of a wider variation of people. The fact that the program is small is a bonus as you'll have more opportunity to make important connections and get more personal attention from the professors, especially in the last two years. It will be easier to switch to something else if you decide to change direction at some point.
Even if you're an ubber-geek, you won't be taken seriously in the tech school until you start a grad school path. You can always switch to the tech school for a Master's program if you're interested at that point.
Another great reason for an Access replacement is to be able to improve on it. Access is very good for quickly making front-ends, but it has many areas that could be improved on. This is an excellent opportunity for a killer app. to step in and fill the gaps.
Slashdot Mirror
"Override all security" - Must be Forth!
I think java swing is a very good way to handle this. PHP is very powerful and probably could handle everything you need it to do. Fox Toolkit or QT would work well if you don't mind C++. Not sure about licensing issues mixing QT with an open source project, I haven't had need to research that before.
We took measurements of everything and put it in visio to scale. An overhead view and at least a front view of each rack works well. That's for the visual part. For the connections, use a database so it can be easily queried and traced. Full dependency reports may take some SQL wizardry, but can be accomplished if the DB is carefully designed.
I've been using various versions of MySQL for about 7 years now and have had no issues at all. I don't use InnoDB, stored procedures, or subqueries, so I can't speak to those features.
I have used replication, extremely long queries, complex joins and unions, and all other common features with no problem.
I took many precautions like daily backups, log storage, etc. and never needed them except for restoration of lost data due to user error (user sent query that deleted all entries, or updated all entries, etc.)
I have a couple programs I haven't touched in 3 years except for minor cleanup that are still running with no problems.
If you're running into issues with MySQL, you must be using new features or versions that just aren't as rock-solid as core MySQL is.
I must admit that by design my programs don't run into many concurent update collisions and if they did, it would only be a minor annoyance.
Yes, you would look at your UTC-SLS watch. All schedules would be tracked in UTC-SLS so this isn't the system they had in the 1800's. I wasn't refering to actually changing local time based on sun location. Just work hours could be adjusted. With today's technology, it is easy to broadcast/post start/end times. Companies could go ahead and round off to nearest hour or quarter hour if they prefer. Just indicating local scheduling can vary from place to place or company to company without changing the UTC-SLS time.
The "Everyone starts at the same time" model doesn't work anymore. Groups are spread across time zones and countries. It's nearly as likely for someone working in Chicago to work with someone in Minneapolis, New York City, Denver, or even Bangalore. Computers can adjust fragments just as easily as whole hours. People would be able to adjust as well over time.
You're correct. I meant UTC the way my computer understands it. This would not stay in sync with true UTC time though. After reading more it seems that UTC-SLS is the best idea which allows for slight adjustments at the last 1000 UTC seconds days containing leap-seconds so there are always 86400 seconds in the day.
I still like adjusting work hours to start/end based on noon +/- a number of hours (or fractions of hours).
All time can be universal (UTC). Noon can be "When the sun is directly overhead." which will locally be different. Start time for work can be Noon-3 Hours (3 hours before noon) to Noon+5 Hours (5 Hours after noon). No DST necessary and no leap-seconds necessary. Why do they want to overcomplicate things here?
Reminds me of the Outer Limits show where the clocks were all adjusted to stretch the workday to be longer and longer while shortening off-work hours.
Yes, many old systems have these limitations. The Tandem isn't one of them. It has some more obscure limitations, but you learn to work around them. Take a look sometime at what one of these can do and you'll see many more limitations in most alternatives including systems much newer than this work of genius.
If you can get past its name, try PureBasic. It is compiled and can include inline assembly or direct memory read/write using peek/poke. You can even tell it to generate the assembly code to insure it's doing what you want. It can be targeted easily for multiple platforms as well as it has assemblers for Linux, Mac, OSX, and Windows. http://www.purebasic.com/ Sorry for the duplicate, didn't login the first time.
Take the smaller LA program. You'll have a wider education base and enjoy the company of a wider variation of people. The fact that the program is small is a bonus as you'll have more opportunity to make important connections and get more personal attention from the professors, especially in the last two years. It will be easier to switch to something else if you decide to change direction at some point.
Even if you're an ubber-geek, you won't be taken seriously in the tech school until you start a grad school path. You can always switch to the tech school for a Master's program if you're interested at that point.
Another great reason for an Access replacement is to be able to improve on it. Access is very good for quickly making front-ends, but it has many areas that could be improved on. This is an excellent opportunity for a killer app. to step in and fill the gaps.