To do a linux Keyboard Viewer, you'd have to get samples of all commercial keyboards (including some that haven't been sold yet), and figure out how to identify their layout.
*Have* you *really* been running Linux?;) Half-baked things happen here all the time, that's one of the platform's strengths.
Ah, but they *do*! Everything that they have ever written for Win32 can probably be run under Wine. (And if it can't, then MSFT could fix the broken parts of Wine.)
the post I replied to was saying that nobody needs objects 'cause files are the same.
Gotcha. Your "file" system is something like JavaBeans or OLE for processing/parsing file formats? If so, then is it required that the application programmer provide the "Print" methods for each new data format that he wants the system to handle?
PS: Phanom's native language is very C++/Java alike, of course. I don't want to create a thing which looks completely alien.:)
On an SELinux (or similarly configured) system, that file might only be available to the user who created it. It truly could be unavailable to the public.:) Anyway, I was under the impression that "Only readable by the user who created the file" was not "publicly available". So, what is the "rest of the world" in your scenario? A single process and those that it deigns to communicate with? If so, how does a process indicate that another process is permitted to have access to its data?
2. Now repeat that for unrelated processes and show me the code size.
Oh. You're moving the goalposts. Thanks. I imagine that I'd use something like DBUS to do what it seems like you are proposing.
3. Now call me that file's method.
What is a file's method? I get the feeling that we're running into a language barrier here. (Don't worry too much about it, though. Your English is far better than any non-English human language that *I* know.:) )
run = new.ru.dz.phantom.system.thread_test();// Create runnable object
boot_object.18(run);// that's lowlevel thread start call
run.store_boot_reference(boot_object);// give him something to chew
This looks like plain old C++ to me.
3. method of passed object is available to receiver, not just some bytes. 4. class of object is known to receiver and can be used to access it's structure thriugh reflections mechanism
This strongly smells of a wrapper around DBUS or something *very* similar.
As of at *least* KDE 4.2, you've been able to have zero or more "plasmoid bars". They may be on any edge of the screen. I've played with the majority of the plasmoids that ship with the default Gentoo installation. They all seem to be able to be contained within a "bar", or float freely on the workspace. I've been told that Gnome applets are kind of like OS X's widgets? (In that there's a separate dashboard that they live on?) What I've read on the internet tells me that Gnome applets are programs that have functional UI and live in a task bar. Is either (or both) of these descriptions correct?
Aye. The flashy transitions and animations are dumb. I *really* dig the various translucent window options, though... ESPECIALLY when working on a low-rez screen.
The reason I ended up disliking KDE4 was because of the lack of options in putting things neatly at the edges,
I'm not sure I follow. Are you saying that Plasmoids need to a) snap to each other, and b) snap to the edge of the screen? If not, would you please elaborate?
This is incorrect. Amarok 2 is a plasmoid container. *Any* app can contain Plasmoids, assuming that it's been modified to do so. Also, you've used KDE 4.2, right? You know that taskbar with the K menu, and the system tray, and the pager, & etc? Those were all Plasmoids contained within a single panel. (Windows would call that panel the Taskbar.)
As RoccamOccam says, the "Plasmoids on the Desktop" notion is optional. Here's how to get your traditional desktop back in KDE 4.2:
1) Right click on desktop. 2) Click on "Appearance Settings" 3) Find the "Type" pulldown in the "Desktop Activity" section of the window that has appeared. 4) Change the "Type" from "Desktop" to "Folder View". 5) Click "Ok" 6) Remove any existing Plasmoids that may be still on your desktop. [1]
HTH.
[1] See? You can have your traditional "Desktop as a Folder" metaphor, while simultaneously keeping any Plasmoids on the desktop that you may like. Or you can have no extra plasmoids at all! Moreover, try clicking on the "Cashew" in the upper right corner and zooming out. You can add NEW desktops (called Activities) that allow you to have one full-screen desktop that's a traditional "Show me the contents of ~/Desktop" setup [2], and another that's chock-full of crazy Plasmoids. (Or whatever strikes your fancy.) [2] And even *this* is configurable in the "Folder View" mode. Right click on the Folder View desktop, and click on "Folder View Settings". You can change what directory you're looking at in the first section that comes up.
Here's some basic functionality that I'm missing. Maybe you know where it has gone?
Where is the "Administrator Mode" button for things like the KDM configuration panel? This button is present and functional for the same user in 3.5 Am I to edit config files until this button makes a reappearance?:(
The KDE crew doesn't have the manpower that MSFT does. If they didn't do periodic public releases, KDE wouldn't be quite as tested as it is. Perhaps some of us have forgotten the long road to KDE 3.5, and the "Release early, release often" mantra?
*sigh* Drop it already. Mistakes were made and have been admitted to. Enjoy the current release, and please report any new bugs that you find. (Or, if you're so inclined, please consider providing patches for the same!)
In a large number of intersections in SF (and a few in my hometown) the "Walk/Don't Walk" pedestrian signals are equipped with a highly-legible timer that starts counting down the last thirty seconds of the associated green light.
In other words, I was right all along: you don't care about evidence.
*sigh* You obviously haven't been paying attention to MSFT for the past fifteen, twenty years or so, have you? Unless it's legally binding, they'll back out of any promise or plan they have at a moment's notice. Unless you have fat stacks of cash to fork over, you cannot depend on their word.
What? Look. *You* might not have the foggiest notion about the interactions between EM radiation and the human body, but the scientific community does. It has been intensely studying EM radiation for far more than fifty years.
There comes a time when you have to say things like "You know, containing explosions in a strong metal vessel for the purpose of propelling a mass really has turned out to be a good idea with a safe implementation. I *should* believe the engineers and scientists -who have spent the better part of their lives working in their fields- when they tell me that I'm not going to blow myself up using one of these 'internal combustion engines'." [1]
Curie died in 1934, BTW. Do you have any more recent examples of scientists who've expired due to EM exposure as part of routine research?
[1] The point being made here is that the engine is safe for the operator. The environmental impact of widespread fossil fuel combustion is ignored for the purpose of this comment. (Also, the same basic design can be used with fuels that have a *much* lower environmental impact, so let's not even start the OMG Global Warming debate.)
Slashdot Mirror
To do a linux Keyboard Viewer, you'd have to get samples of all commercial keyboards (including some that haven't been sold yet), and figure out how to identify their layout.
*Have* you *really* been running Linux? ;) Half-baked things happen here all the time, that's one of the platform's strengths.
It would seem that the POC for Phantom is speaking with slashdot:
http://slashdot.org/comments.pl?sid=1119163&cid=26762879
Microsoft doesn't have that with Ubuntu,
Ah, but they *do*! Everything that they have ever written for Win32 can probably be run under Wine. (And if it can't, then MSFT could fix the broken parts of Wine.)
the post I replied to was saying that nobody needs objects 'cause files are the same.
Gotcha. Your "file" system is something like JavaBeans or OLE for processing/parsing file formats? If so, then is it required that the application programmer provide the "Print" methods for each new data format that he wants the system to handle?
PS: Phanom's native language is very C++/Java alike, of course. I don't want to create a thing which looks completely alien. :)
Makes sense.
1. It is available. To root at least.
On an SELinux (or similarly configured) system, that file might only be available to the user who created it. It truly could be unavailable to the public. :)
Anyway, I was under the impression that "Only readable by the user who created the file" was not "publicly available". So, what is the "rest of the world" in your scenario? A single process and those that it deigns to communicate with? If so, how does a process indicate that another process is permitted to have access to its data?
2. Now repeat that for unrelated processes and show me the code size.
Oh. You're moving the goalposts. Thanks. I imagine that I'd use something like DBUS to do what it seems like you are proposing.
3. Now call me that file's method.
What is a file's method? I get the feeling that we're running into a language barrier here. (Don't worry too much about it, though. Your English is far better than any non-English human language that *I* know. :) )
run = new
boot_object.18(run);
run.store_boot_reference(boot_object);
This looks like plain old C++ to me.
3. method of passed object is available to receiver, not just some bytes.
4. class of object is known to receiver and can be used to access it's structure thriugh reflections mechanism
This strongly smells of a wrapper around DBUS or something *very* similar.
Take text processing for example. Would you really write that in C/C++?
Why not? With std::string and boost::regex, text processing isn't *that* much of a chore.
And I would rather rip my eyes out than writing a GUI with C.
Have you ever used GLADE?
#include <sys/stat.h>
#include <stdio.h>
#include <unistd.h>
const char fn[]= "randomFileName.txt"; /* Making file publically inavailable */ /* Pointer to file has obviously been passed to other app */ /*Calling close method on file */
int main()
{
pid_t pid;
FILE * fh;
fh = fopen(fn, "w");
fclose(fh);
chmod(fn, 0600);
fh = fopen(fn, "w");
pid = fork();
if(!pid)
{
char data[] = "Writing to publically inavailable file\n";
fwrite(data, sizeof(char), sizeof(data)/sizeof(char), fh);
fclose(fh);
}
else
while(waitpid(-1, NULL, 0) != -1) ;
return 0;
}
WAIT! So This LIVE TV, Can You Get The INTERNET CHANNEL On It?
We know it is all broadband now, right?
Not with a 250GB/month cap it's not!
NB, outrage freaks: http://letmegooglethatforyou.com/?q=hyperbole
I'm TV free. Now I hang out on slashdot!
As of at *least* KDE 4.2, you've been able to have zero or more "plasmoid bars". They may be on any edge of the screen. I've played with the majority of the plasmoids that ship with the default Gentoo installation. They all seem to be able to be contained within a "bar", or float freely on the workspace.
I've been told that Gnome applets are kind of like OS X's widgets? (In that there's a separate dashboard that they live on?) What I've read on the internet tells me that Gnome applets are programs that have functional UI and live in a task bar. Is either (or both) of these descriptions correct?
Aye. The flashy transitions and animations are dumb. I *really* dig the various translucent window options, though... ESPECIALLY when working on a low-rez screen.
The reason I ended up disliking KDE4 was because of the lack of options in putting things neatly at the edges,
I'm not sure I follow. Are you saying that Plasmoids need to a) snap to each other, and b) snap to the edge of the screen? If not, would you please elaborate?
Plasmoids *only* work on the desktop.
This is incorrect. Amarok 2 is a plasmoid container. *Any* app can contain Plasmoids, assuming that it's been modified to do so.
Also, you've used KDE 4.2, right? You know that taskbar with the K menu, and the system tray, and the pager, & etc? Those were all Plasmoids contained within a single panel. (Windows would call that panel the Taskbar.)
As RoccamOccam says, the "Plasmoids on the Desktop" notion is optional. Here's how to get your traditional desktop back in KDE 4.2:
1) Right click on desktop.
2) Click on "Appearance Settings"
3) Find the "Type" pulldown in the "Desktop Activity" section of the window that has appeared.
4) Change the "Type" from "Desktop" to "Folder View".
5) Click "Ok"
6) Remove any existing Plasmoids that may be still on your desktop. [1]
HTH.
[1] See? You can have your traditional "Desktop as a Folder" metaphor, while simultaneously keeping any Plasmoids on the desktop that you may like. Or you can have no extra plasmoids at all! Moreover, try clicking on the "Cashew" in the upper right corner and zooming out. You can add NEW desktops (called Activities) that allow you to have one full-screen desktop that's a traditional "Show me the contents of ~/Desktop" setup [2], and another that's chock-full of crazy Plasmoids. (Or whatever strikes your fancy.)
[2] And even *this* is configurable in the "Folder View" mode. Right click on the Folder View desktop, and click on "Folder View Settings". You can change what directory you're looking at in the first section that comes up.
Here's some basic functionality that I'm missing. Maybe you know where it has gone?
Where is the "Administrator Mode" button for things like the KDM configuration panel? This button is present and functional for the same user in 3.5 Am I to edit config files until this button makes a reappearance? :(
Hey.
I have a fix for you.
Add krandrtray to your list of Autostarted applications.
See this bug for more information:
https://bugs.kde.org/show_bug.cgi?id=163707
The KDE crew doesn't have the manpower that MSFT does. If they didn't do periodic public releases, KDE wouldn't be quite as tested as it is.
Perhaps some of us have forgotten the long road to KDE 3.5, and the "Release early, release often" mantra?
*sigh* Drop it already.
Mistakes were made and have been admitted to. Enjoy the current release, and please report any new bugs that you find. (Or, if you're so inclined, please consider providing patches for the same!)
I'm honestly boggles that any ISP would implement a cap and not provide such a measurement.
You forget. We're talking about a USian telecom. These caps are all about short-term profit increases. :/
symbolset thinks that you're a MSFT employee. Making such sidelong suggestions is his favorite game.
It's limited to the publicly exposed interfaces of Windows...so it has access to about 10% of the real environment?
Man! I love playing this game!
Is your claim that 90% of the Windows interfaces are private and/or undocumented?
In a large number of intersections in SF (and a few in my hometown) the "Walk/Don't Walk" pedestrian signals are equipped with a highly-legible timer that starts counting down the last thirty seconds of the associated green light.
*Everyone* on the road *loves* these signals.
In other words, I was right all along: you don't care about evidence.
*sigh* You obviously haven't been paying attention to MSFT for the past fifteen, twenty years or so, have you?
Unless it's legally binding, they'll back out of any promise or plan they have at a moment's notice. Unless you have fat stacks of cash to fork over, you cannot depend on their word.
you've just disproved your own point.
What? Look. *You* might not have the foggiest notion about the interactions between EM radiation and the human body, but the scientific community does. It has been intensely studying EM radiation for far more than fifty years.
There comes a time when you have to say things like "You know, containing explosions in a strong metal vessel for the purpose of propelling a mass really has turned out to be a good idea with a safe implementation. I *should* believe the engineers and scientists -who have spent the better part of their lives working in their fields- when they tell me that I'm not going to blow myself up using one of these 'internal combustion engines'." [1]
Curie died in 1934, BTW. Do you have any more recent examples of scientists who've expired due to EM exposure as part of routine research?
[1] The point being made here is that the engine is safe for the operator. The environmental impact of widespread fossil fuel combustion is ignored for the purpose of this comment. (Also, the same basic design can be used with fuels that have a *much* lower environmental impact, so let's not even start the OMG Global Warming debate.)