wxWindows is pretty heavy weight compared to Qt, FLTK, FOX, etc., and the other toolkits (with the exception of Qt) are totally open-sourced with "designer" apps.
We shied away from wxWindows several years ago because of binary compatibility issues (in the vendor GUI libraries, not in WxWindows) and because of the bloat. I'd be interested to see how wxEmbedded measures up...
Cold temperatures don't make you sick. More than likely you either were having an allergic reaction to the dust/pollen/spores in the rooms or outside (something that will manifest itself as a head cold usually)
The biggest problem I have with AC is that in order to make homes "more energy efficient" you have to make them as airtight as possible, which means that you get no exchange of outside (fresh) air. We're in the process of putting in a fresh air exchanger (actually, its a full heat exchanger, too, to improve on the efficiency) for our office now, because the air quality indoors royally sucks.
Actually, you can file a FOIA request for any gov't software, including source code. As with printed documents, they can either blank out sensitive information (leave out code) or deny the request for national security or privacy reasons.
... Only minor nit is they could've used broadcasts to announce print servers, instead of having to configure that on the client. Then it would really be zero-maintenance.
CUPS already does this if you configure the server to do the broadcast - see the BrowseAddress directive. Do this with multiple servers for the same printers and the clients will automatically load-balance between the available servers and ignore servers that are down (failsafe).
But there have been accelerated 3D boards for a lot longer - I was programming some boards from SubLogic (remember them?) and then from SGI (IRISvision - Personal IRIS graphics on a PC with a *blazing* 14k polygons/second with hardware Z-buffer!:)
The article might better be titled "7 Years of *Consumer* 3D Graphics Cards"...
Re:Interoperability? then why LPD is default?
on
Apple Licenses CUPS
·
· Score: 2
Actually, most recent Linux distros are coming with CUPS; some make it the default, some offer it as a choice.
RH 8.0 is also coming with CUPS...
Re:GNU and CUPS patches that were submitted?
on
Apple Licenses CUPS
·
· Score: 2
Well, the CUPS FAQ and guidelines for submission are very clear that the copyright of contributions to the CUPS baseline must be assigned to ESP so we can license the code to others.
As for the "monetary exchange", there is not a single Linux distributor that has paid money to us, even for support, yet they (and all Linux users) get to use CUPS for free as a result.
Also, before you criticize us, you might want to look at our web sites - we provide most of our software under GNU licenses, and we regularly contribute to other open source projects like SAMBA, GIMP-print, FLTK, GNOME, etc.
Actually, we make most of our money from packaging CUPS along with GUIs and drivers in our ESP Print Pro software; that's where you can get a commercially supported version of CUPS, which is what most businesses and many end-users are looking for.
And BTW, we've been in business since 1993 and have been making money, not from licensing CUPS, but by selling commercially-packaged printing solutions for UNIX. Licensing CUPS only increases the money we have to put back into CUPS, etc.
Similarly, our HTMLDOC software was not popular until we started packaging it with support. We make money for HTMLDOC not by licensing it but by *supporting* it and providing that turn-key solution...
Well, Apple's use of CUPS will make it easier for printer manufacturers to provide drivers for Linux, since the time & money they spend on developing OS X drivers will yield drivers that will compile under Linux as well. I personally know of two printer manufacturers that are very excited about the prospect, and it may be the "push" that is needed to get upper management to support Linux, etc. natively.
Well, as one of the companies involved in the deal, I can say that the whole purpose of this licensing arrangement is to satisfy the lawyers, and Apple has been working with us to make sure that the standard CUPS distribution 1) builds out of the box for OS X/Darwin, and 2) contains as much functionality as possible (e.g. USB support will appear in the near future, etc.)
The only thing that won't be part of the open-source CUPS is the Aqua interface and PDF RIP technology, both of which already have suitable open-source replacements in the Linux and *BSD worlds.
The problem with this is that is requires the RPM software on all target systems. This won't be popular with a lot of sysadmins because most want to stick with the vendor packaging systems whenever possible so that only 1 install tool needs to be learned and so that dependencies between packages are handled consistently.
RPM's source-centric view (where you have to rebuild everything from scratch all the time, making development of the initial distributions extremely time consuming) is also a major problem, because a lot of packages take a long time to compile (we have one that takes several hours on older hardware), and you may be testing fixes, etc. that only affect a single executable in your package.
Anyways, for people that want something a lot more portable and flexible, see my (also free) EPM software at "http://www.easysw.com/epm/". It does native RPM, DPKG, *BSD pkg, System V pkg, IRIX inst, HP-UX swinstall, Tru64 setld, and AIX installp packages, or so-called "portable" install scripts with tar files, all from the same software description/list files. Utilities are provided to automate the building of the list files from already-installed files/directories (the classic RPM BuildRoot stuff) or by intercepting "install" commands, making it very easy to create and/or maintain them.
HTMLDOC downloads regularly surpass all of our other products combined, and we are actively developing it to support newer stuff like CSS1/2, XHTML, Unicode text, embedded fonts, etc.
Best of all, of course, is that HTMLDOC is (and always shall be) open-source software, with commercial support for those that need it.
A lot of doctors ran out an bought their own mini-lab test equipment when it first came out. Not only did it cost them less than sending it out to be processed, but they got results faster.
*However*, the insurance companies have put a stop to that. My doctor has to send out my bloodwork and wait almost a week to check my cholesterol, instead of using his own equipment and getting me an answer within an hour or so... In the process, I end up paying *more* to my insurance company and they get to negotiate mass-quantity lab work with the lowest bidder.
There's a web site out there (sorry, can't find the link) that describes why DVD Audio will be no improvement over CD Audio.
Basically, DVD Audio provides 88.2kHz, 24-bit audio with up to 6 channels (well, 5.1), same as you can get with regular DVD Video, along with CSS encryption. In theory, this could provide dramatically better quality than the 2-channel, 44.1kHz, 16-bit audio on a regular CD-ROM.
However, most/all current CDs do not utilize the dynamic range of current CDs, and the extra channels would probably only be useful for reproducing the performance environment (e.g. an amphitheatre, stage, etc.) and not for providing you with 1 channel per instrument, or anything like that.
There is also the cost involved - producing DVDs costs more money than CDs (not just the media costs, but licensing, etc.), and consumers aren't likely to shell out an extra $10 for a DVD that sounds marginally better than a CD and can't be played by their current equipment.
There are certain color management and color profiling technologies that are patented, however the process of printing using cyan, magenta, yellow, and black is very old.
Um, CUPS does not use "its own rasterizing program", it uses GNU Ghostscript with the "cups" driver which outputs a generic raster stream that can be configured as needed by the printer driver (i.e. the driver can say it needs a 6-color image at 720 DPI, and Ghostscript will generate it through the cups driver)
We include a version of Ghostscript with CUPS because 1) most non-Linux operating systems don't come with Ghostscript pre-installed, and 2) the standard Ghostscript is bug-filled and doesn't come with that all-important cups driver compiled in. See the ESP Ghostscript project on SourceForge for a more generic replacement that can be configured with the standard Ghostscript drivers + cups.
CUPS also provides an image file RIP which provides faster/better image printing than is possible with Ghostscript.
Similarly, the GNOME folks could provide a rasterizer for GNOME metafiles that would be used for printing - the metafiles are generally a more compact representation than PostScript, and would provide faster printing for clients in a network configuration.
In short, it is the very design of CUPS that will allow it to support a wide variety of devices and applications today and in the future.
Unfortunately, there is a *lot* to printer drivers, and you really don't want a kernel driver doing dithering, etc!
Now, for special printer interfaces (say, the FireWire interface that the EPSON Stylus Pro 10000 can use) you may want/need a special kernel driver for the printer *interface*, but leave the printer driver itself in user space.
The trailing space problem was indeed fixed a while back.
Also, the default is now to preserve the last 500 jobs (not every job ever printed), so disabling job history shouldn't be necessary unless you want to eliminate any extra memory use on your system.
I *think* the web interface has a "purge jobs" button, and you can do "cancel -a printer" to purge the job history for a printer.
Slashdot Mirror
This is the same thing as the Cappucino PC... FWIW, we recently bought one and it works great as a low-end web server...
wxWindows is pretty heavy weight compared to Qt, FLTK, FOX, etc., and the other toolkits (with the exception of Qt) are totally open-sourced with "designer" apps.
We shied away from wxWindows several years ago because of binary compatibility issues (in the vendor GUI libraries, not in WxWindows) and because of the bloat. I'd be interested to see how wxEmbedded measures up...
Apple CUPS does not come with Ghostscript pre-installed; MacOS X apps print using PDF, so Apple uses a Quartz-based PDF RIP in place of Ghostscript.
Just grab ESP Ghostscript from the CUPS site, compile, and install. osxgnu.org might have binary packages as well...
LSB requires the lpr command, not the lpr software. CUPS, LPRng, Berkeley lpr, and GNU lpr all satisfy the LSB requirement IIRC.
Cold temperatures don't make you sick. More than likely you either were having an allergic reaction to the dust/pollen/spores in the rooms or outside (something that will manifest itself as a head cold usually)
The biggest problem I have with AC is that in order to make homes "more energy efficient" you have to make them as airtight as possible, which means that you get no exchange of outside (fresh) air. We're in the process of putting in a fresh air exchanger (actually, its a full heat exchanger, too, to improve on the efficiency) for our office now, because the air quality indoors royally sucks.
Actually, you can file a FOIA request for any gov't software, including source code. As with printed documents, they can either blank out sensitive information (leave out code) or deny the request for national security or privacy reasons.
CUPS already does this if you configure the server to do the broadcast - see the BrowseAddress directive. Do this with multiple servers for the same printers and the clients will automatically load-balance between the available servers and ignore servers that are down (failsafe).
The N64 uses a MIPS processor, not an ALPHA processor. MIPS processors have been 64-bit capable for a very long time...
But when fossil fuels are burned, they produce CO2 (among other things) which plants can convert to O2...
But there have been accelerated 3D boards for a lot longer - I was programming some boards from SubLogic (remember them?) and then from SGI (IRISvision - Personal IRIS graphics on a PC with a *blazing* 14k polygons/second with hardware Z-buffer! :)
The article might better be titled "7 Years of *Consumer* 3D Graphics Cards"...
Actually, most recent Linux distros are coming with CUPS; some make it the default, some offer it as a choice.
RH 8.0 is also coming with CUPS...
Well, the CUPS FAQ and guidelines for submission are very clear that the copyright of contributions to the CUPS baseline must be assigned to ESP so we can license the code to others.
As for the "monetary exchange", there is not a single Linux distributor that has paid money to us, even for support, yet they (and all Linux users) get to use CUPS for free as a result.
Also, before you criticize us, you might want to look at our web sites - we provide most of our software under GNU licenses, and we regularly contribute to other open source projects like SAMBA, GIMP-print, FLTK, GNOME, etc.
Actually, we make most of our money from packaging CUPS along with GUIs and drivers in our ESP Print Pro software; that's where you can get a commercially supported version of CUPS, which is what most businesses and many end-users are looking for.
And BTW, we've been in business since 1993 and have been making money, not from licensing CUPS, but by selling commercially-packaged printing solutions for UNIX. Licensing CUPS only increases the money we have to put back into CUPS, etc.
Similarly, our HTMLDOC software was not popular until we started packaging it with support. We make money for HTMLDOC not by licensing it but by *supporting* it and providing that turn-key solution...
Well, Apple's use of CUPS will make it easier for printer manufacturers to provide drivers for Linux, since the time & money they spend on developing OS X drivers will yield drivers that will compile under Linux as well. I personally know of two printer manufacturers that are very excited about the prospect, and it may be the "push" that is needed to get upper management to support Linux, etc. natively.
Well, as one of the companies involved in the deal, I can say that the whole purpose of this licensing arrangement is to satisfy the lawyers, and Apple has been working with us to make sure that the standard CUPS distribution 1) builds out of the box for OS X/Darwin, and 2) contains as much functionality as possible (e.g. USB support will appear in the near future, etc.)
The only thing that won't be part of the open-source CUPS is the Aqua interface and PDF RIP technology, both of which already have suitable open-source replacements in the Linux and *BSD worlds.
Tell me about it...
This weekend I went to get a replacement battery for my wife's cell phone. The cost? A mere $50, *or* I could buy a replacement phone for $39.95.
Someone tell me again why the battery (that comes with the phone in the first place) should cost so much more than the phone?!?
The problem with this is that is requires the RPM software on all target systems. This won't be popular with a lot of sysadmins because most want to stick with the vendor packaging systems whenever possible so that only 1 install tool needs to be learned and so that dependencies between packages are handled consistently.
RPM's source-centric view (where you have to rebuild everything from scratch all the time, making development of the initial distributions extremely time consuming) is also a major problem, because a lot of packages take a long time to compile (we have one that takes several hours on older hardware), and you may be testing fixes, etc. that only affect a single executable in your package.
Anyways, for people that want something a lot more portable and flexible, see my (also free) EPM software at "http://www.easysw.com/epm/". It does native RPM, DPKG, *BSD pkg, System V pkg, IRIX inst, HP-UX swinstall, Tru64 setld, and AIX installp packages, or so-called "portable" install scripts with tar files, all from the same software description/list files. Utilities are provided to automate the building of the list files from already-installed files/directories (the classic RPM BuildRoot stuff) or by intercepting "install" commands, making it very easy to create and/or maintain them.
Abandonware? Quite the opposite!
HTMLDOC downloads regularly surpass all of our other products combined, and we are actively developing it to support newer stuff like CSS1/2, XHTML, Unicode text, embedded fonts, etc.
Best of all, of course, is that HTMLDOC is (and always shall be) open-source software, with commercial support for those that need it.
A lot of doctors ran out an bought their own mini-lab test equipment when it first came out. Not only did it cost them less than sending it out to be processed, but they got results faster.
*However*, the insurance companies have put a stop to that. My doctor has to send out my bloodwork and wait almost a week to check my cholesterol, instead of using his own equipment and getting me an answer within an hour or so... In the process, I end up paying *more* to my insurance company and they get to negotiate mass-quantity lab work with the lowest bidder.
There's a web site out there (sorry, can't find the link) that describes why DVD Audio will be no improvement over CD Audio.
Basically, DVD Audio provides 88.2kHz, 24-bit audio with up to 6 channels (well, 5.1), same as you can get with regular DVD Video, along with CSS encryption. In theory, this could provide dramatically better quality than the 2-channel, 44.1kHz, 16-bit audio on a regular CD-ROM.
However, most/all current CDs do not utilize the dynamic range of current CDs, and the extra channels would probably only be useful for reproducing the performance environment (e.g. an amphitheatre, stage, etc.) and not for providing you with 1 channel per instrument, or anything like that.
There is also the cost involved - producing DVDs costs more money than CDs (not just the media costs, but licensing, etc.), and consumers aren't likely to shell out an extra $10 for a DVD that sounds marginally better than a CD and can't be played by their current equipment.
CMYK is not patented.
There are certain color management and color profiling technologies that are patented, however the process of printing using cyan, magenta, yellow, and black is very old.
Um, CUPS does not use "its own rasterizing program", it uses GNU Ghostscript with the "cups" driver which outputs a generic raster stream that can be configured as needed by the printer driver (i.e. the driver can say it needs a 6-color image at 720 DPI, and Ghostscript will generate it through the cups driver)
We include a version of Ghostscript with CUPS because 1) most non-Linux operating systems don't come with Ghostscript pre-installed, and 2) the standard Ghostscript is bug-filled and doesn't come with that all-important cups driver compiled in. See the ESP Ghostscript project on SourceForge for a more generic replacement that can be configured with the standard Ghostscript drivers + cups.
CUPS also provides an image file RIP which provides faster/better image printing than is possible with Ghostscript.
Similarly, the GNOME folks could provide a rasterizer for GNOME metafiles that would be used for printing - the metafiles are generally a more compact representation than PostScript, and would provide faster printing for clients in a network configuration.
In short, it is the very design of CUPS that will allow it to support a wide variety of devices and applications today and in the future.
Unfortunately, there is a *lot* to printer drivers, and you really don't want a kernel driver doing dithering, etc!
Now, for special printer interfaces (say, the FireWire interface that the EPSON Stylus Pro 10000 can use) you may want/need a special kernel driver for the printer *interface*, but leave the printer driver itself in user space.
The trailing space problem was indeed fixed a while back.
Also, the default is now to preserve the last 500 jobs (not every job ever printed), so disabling job history shouldn't be necessary unless you want to eliminate any extra memory use on your system.
I *think* the web interface has a "purge jobs" button, and you can do "cancel -a printer" to purge the job history for a printer.
CUPS (http://www.cups.org/) and GIMP-print (http://gimp-print.sourceforge.net/)