Non sei loggato!
Oggi: 2
Ieri: 2
Totali: 5820
Ultimo: 
Ospiti : 16
Iscritti : 4
Totali: 20
Aggiornamenti
Aggiornamenti Recenti
| Code::Blocks and D programmin... | Planet Fedora | |
| Hello dear reader,The latest code::blocks revision support now ldc compiller (LLVM D compiler). Now you can DevellopDapplication with this great IDE.Install codeblocks repoInstall dany repo (thanks to sharkcz's )fedora_12fedora_13fedora_14Install or update code::blocks$ su -c 'yum install codeblocks'or$ su -c 'yum updtate codeblocks'Configuration of ProjectsGo in Settings -> Compiler and DebuggerIn search directories tabs set path to /usr/include/dIn linkker tabs for 64bits set path to /usr/lib64In compiler setting tabs -> #defines a Tango and Posix |
||
| Những phần mềm nguồn ... | Planet Fedora | |
| Danh sách Những ứng dụng nguồn mở dành cho doanh nghiệp xuất sắc nhất năm 2010 đã được InfoWorld bình chọn bao gồm bốn nhóm: Ứng dụng, phần mềm phát triển ứng dụng, nền tảng và tầng trung, phần mềm mạng. Giải thưởng BOSSIE Awards 2010 –Nguồn: InfoWorld Chín chương trình thuộc nhóm Ứng dụng nhận giải [...] | ||
| Everyone can contributenicu -... | Planet Fedora | |
| In an earlier post I talked aboutFedora supplemental wallpapersand our effort to check the license, the replies are positive but I wanted to share with the world one heart warming reply from one of thephotographersI contacted:I'm honored that you chose one of my photos, and I'm quite happy with your attribution mechanisms.Feel free to contact me if I can be of any further help.Thanks,NicP.S. I teach computer science at the University of Minnesota, Morris, the public liberal arts campus of the U of M. Our CS lab has approximately 35 clients, all running Fedora Core. Thanks for your good work - it's nice to be able to contribute something small back.See? Is not hard at all to become a contributor to FLOSS and Fedora.ThankyouNic. | ||
| How to setup Lexmark X4650 wi... | Planet Fedora | |
| This is a big step for Lexmark. In the past they have generally entirely ignored Linux users (and often Mac users, too). When my old HP printer bit the dust and Target had a deal for an all-in-one wireless printer for $50, I was surprised to find that Lexmark offered full support for Linux. Granted, Lexmark has opted to dothis by packaging their own driver rather than contributing a ps or ppd to foomatic, but I’m willing to acknowledge progress. Here’s the steps to get it to work wirelessly.1. You must first go through the setup with a Windows machine and keep the paper it prints out with the network info. There is no way around this. The CD that comes with the printer won’t help. Once you get the printer connected wirelessly, we can set it up on Fedora. If you don’t need wireless skip to the next step.2. Download the Lexmark driver fromtheir support site. The file extension is rpm.sh. Note that they only have 32-bit drivers, but they will work in x86_64.3. Open a terminal and login as root. cd to the folder where you downloaded the file from step 2.4. chmod a+x lexmark-08z-series-driver-1.0-1.i386.rpm.sh.tar.gz. If your filename is different, adjust accordingly.5. ./lexmark-08z-series-driver-1.0-1.i386.rpm.sh.tar.gzshould now start the installation program. Just follow the steps and plug in the USB cable when it asks.6. After the wizard finishes, as root, run‘system-config-printer’. The printer should now show up here.7. Right click on the printer and select Properties.8. Under Settings, click on the button that says “Change…” next to the right of “Device URI”.9. Click on Network Printer, Find Network Printer. Next to “Host:” Enter the IP Address listed under TCP/IP, Address on the network settings print out. The application should automatically set port 9100. Enter a Description and click Apply.10. Congrats. Print a test.*Printing works wirelessly, but‘Scan to Network’ only seems to work with Windows clients.Filed under:FedoraTagged:driver,Fedora,hardware,lexmark,linux,printer,X4650 | ||
| Wacom support in LinuxWho-T | Planet Fedora | |
| This article should have been written a long long time ago. Anyway, here's the gist of Wacom tablet support under Linux and that hopefully clears up the confusion about the various packages.The role of linuxwacomlinuxwacom is two things. It is the project name used for wacom-specific implementations and thus in theURLas well (in this post, I will always use"linuxwacom project"to refer to the project).It is also the name of the tarball shipped by the linuxwacom project. Or at least the name of one tarball, anyway. Now, this tarball includes virtually everything linuxwacom as a project wants to provide, most notably a kernel driver, an X driver and several utilities. More on these later.The main (and long-term) contributor to linuxwacom is still Ping Cheng, aWacomemployee. Wacom naturally has a strong focus on its customers and thus linuxwacom goes into some pains supporting systems all the way back to XFree86-4.However, the X server hasmoved quite a bit.xf86-input-wacomIn August 2009, I split out the X11 driver from the linuxwacom package and imported it intoa git repository called xf86-input-wacom. This driver has seen quite a bit of rework, including dropping of some features (like XFree86-4 support but also old-style serial tablets) and gaining some features (like input device properties). The driver includes a simple tool calledxsetwacomthat provides some options to manipulate driver settings at runtime.xsetwacomused to be part of the linuxwacom tarball and I've tried to keep xsetwacom's interface as close to the original as possible.As of a couple of weeks ago, the xf86-input-wacom driver also includes a simpleisdv4-serial-debuggerto print information about serial tablets. That's it though, xf86-input-wacom does not contain any other tools.xf86-input-wacom supports serial devices directly and USB devices provided the kernel supports them. In that regard, it is quite similar to evdev or synaptics - both rely on the kernel for actual hardware support. If your kernel doesn't support a particular device, then xf86-input-wacom won't help.Note that xf86-input-wacom is the replacement for the linuxwacom X driver, that driver will not compile on X servers 1.7 or later. And the name does not imply that it is for Wacom tablets only, we have code to handle some Waltop tablets and recently added a patch for Fujitsu serial devices. More devices will be added as needed.kernel driversThe linuxwacom tarball ships with several kernel drivers for various kernel versions. Note that these are out-of-tree drivers and thus if you compile them and then update your kernel, you must recompile and re-install the driver. This out-of-tree development is mostly due to Wacom's commitment to its customers.Personally I would love to see kernel development happening on LKML only but this is not the case right now. Especially for newer models that support touch the upstream kernel requires the use of the MT protocol, something that the X drivers (neither xf86-input-wacom nor the old linuxwacom one) can handle right now. Especially Bamboos are affected by this. AFAIK, no distribution supports them out-of-the box and users must compile the kernel driver from the linuxwacom tarball. Once that driver is installed, xf86-input-wacom works fine with it.This is a source of much confusion but while I intended to start working at the kernel drivers, I have enough things on my slate and I have yet to actually do so. Luckily,Henrik and others are working on it.However, when I read"You may be tempted to download the 0.10.8 version if you have an X server>= 1.7. I tried this, but it did not work. Stick with the production driver, it will work."and (after compiling the kernel driver)"Now, plug in your tablet. It SHOULD be recognized and immediately function as a mouse."onlinux.comI cringed. What happens here is that after the kernel driver from the linuxwacom tarball was installed, xf86-input-wacom automatically picked it up. You need both parts, kernel and X driver.wacdump, wacomcpl, and other toolsAll these are still available in the linuxwacom tarball.wacdumpprovides similar functionality to evtest so I don't see the need for maintaining two tools that do the same thing.xidumpdoes the same as xinput --test. Hence both tools are not available anymore on newer distributions.wacomcplis a major source of headache. It's a TCL wrapper around xsetwacom to provide a basic graphical configuration utility. It doesn't work anymore due to a number of subtle changes in the xsetwacom interface but also because it partially expects options that don't exist anymore (or in other forms) in the xf86-input-wacom driver. I thought about fixing it up but after looking at it I ran away screaming. I've traded some bugs withBastienand he'll write a GNOME configuration utility. That's currently holding up on the need for an actual UI (and as engineers we both shouldn't do that one ourselves...) but it will hopefully see the light at some point in the near future. Meanwhile, no GUI configuration tool.Future progressThe linuxwacom project is still largely controlled by Wacom, with the exception of xf86-input-wacom that's maintained by me but is heavily contributed to by Ping Cheng, both in patches and code review.Wacom's internal processes aredifferentto the ones we use in distributions and upstream and that can make life hard for us. (Likewise, our processes make life harder for Wacom so the finger-pointing goes both ways :) Ping and I have had plenty of discussions about this and we try to meet somewhere in the middle where possible, disrupting the project completely helps no-one.xf86-input-wacom is in a reasonably good state now though the cleanup has taken much longer than expected and there are still several items to be removed or rewritten to fit into the new X server behaviours. I expect this work to take another couple of months but much of it is aimed ad making the driver easier to maintain and develop for. For the average user, it won't have as much impact.As I said above, I'd like to see kernel development happen on LKML in upstream kernels, not in a separate tarball. This is - aside from the GUI tool - the most pressing issue right now.How to helpAs usual, the best way of helping out is to test the code that is available. I'm not a designer so if the tablet doesn't crash the server that's pretty close to 100% functional to me. I rely on others to tell me when behaviours change.If you're a coder, get right in. If your device doesn't work, go for the upstream kernel and try to get it working there. Anything upstream will feed back into distros and thus improve the out-of-the-box experience. If you have feature-requests for xf86-input-wacom, dig in and write it. Thedeveloper's mailing listis useful in any case. Finally, there's thewikithat will eventually be a useful one, but I keep getting distracted with other stuff whenever I try to move info over. So any help there will be useful to others looking for documentation.And as I pointed out above - we're in desparate need for a UI for the GNOME config utility. If you're interested in helping out here, please contact me.Finally, I want to point out that Ping (and by inference Wacom Inc.) has been excellent and though we sometimes disagree on technical issues there is no question that Wacom is supportive of the project and their contributions are invaluable. | ||
| fedoraproject.org redesign up... | Planet Fedora | |
| So it’sbeen a while,a month really, since I’ve given you an update on the Fedora website redesign. Well, in the past month Fedora design ninjaJef van Schendeland I have been cranking out mockups and Sijis Aviles has been doing an awesome job making the mockups a reality and getting things into staging and building things out. So we’ve got quite a few things to go over here.Too professional?One piece of feedback we heard from several of you aboutthe last mockup for the front page of fedoraproject.orglooked a littletooprofessional.“This looks like it’s trying to sell me something,” one of my colleagues told me about it recently, “this doesn’t primarily say community or freedom to me at all first glance.”Well, crap. Freedom& friends are two main values of Fedora. If folks don’t get a feeling about community and freedom from looking at our website, we’ve got issues. How did this happen?Well, when designing the first mockup and even wheniterating through the header designs, I was reviewing many application websites for general formatting& conventions for some inspiration and to make sure that our website didn’t violate any conventions that would confuse users. If our website follows patterns users have experience with at other software-related websites that involve downloads, then they’ll probably be able to have a smoother experience since they’ll have to expend less active brain power on figuring out what the website is for and what they are meant to be doing with it. It was through this quick& unscientific survey that I figured out wording for the navbar items– I chose words I saw that were the most frequently used – “Download,” “Help,” etc.I think this influence probably ended up giving a bit too commercial of a flavor to the resulting mockup. Whoopsie!How to fix it?Well, let’s take a quick peek at the “too commercial” mockup:“How to fix this, how to fix this?” I stewed. First I tried to figure out, what might have given it the commercial flavor? I asked a couple of the folks who felt it was commercial, and they just couldn’t put their finger on it. So I poured over it and figured out a few things:While there are people on the page, the product itself stands out much more loudly than anything else.The color palette is mostly grey, and the main background color is white. Very conservative.There isn’t a single header on the page referring to community – the words “community,” “forum,” “people” are just not in the large and prominent headers on the page.“All right, this is fixable,” I thought to myself, looking at the list of mistakes. Not many people featured prominently on the page? Add some. The color palette is conservative and grey? Make it more colorful! No prominent community-centric keywords? Add them! Not too hard, right? So here’s what we did:The main navbar is now a bright Fedora blue, buh-bye grey!The screenshot is backed by a colorful illustration rather than a plain dark grey gradient.One of the first things I see on the page is the photo of Tatica and Pedrito– the darkness of their clothing contrasts with the much lighter& brighter colors around them, I think making them stand out right away.The headers for the page are backed by a pale blue, and the media quotes under the banner are backed by a pale yellow. More color!“Community” has been added to the navbar and falls towards the center of the screen, much more prominent than the word was in the previous mockup.The revealSo this is the course-correction to attempt to mistakes of the previous mockup, hopefully making for a mockup that better reflects Fedora’s values of freedom& community. The initial feedback we’ve gotten on it has been positive; what do you think, does it work?But wait, there’s more!Once Sijis, Jef, and I finally settled on this mockup being something we could live with, Jef and I went ahead and started fleshing out more of the screens needed. Jef took on the“Community” page (which will be roughly equivalent totoday’s join.fedoraproject.org). I fleshed out the features page and also filledour recently-updated download pagesinto the new template. Let’s take a look!Features MockupFor each of the five major feature areas (Collaboration, Entertainment& Media, Creativity, Office/Productivity, and Desktop Basics,) I wanted to highlight a major feature of the desktop or a killer app in that category. You know, there are cool features in Fedora that a lot of long-time Fedora users aren’t even aware of. Let’s let them shine, right?This mockup fleshes a couple of the six sections out. One piece of feedback I’ve gotten so far is that the text is just too long, “too long, didn’t read.” So it’ll definitely need to be tightened up a bit more.One thing I think would be really sexy is to add a“download now!” button for folks already running Fedora. The kickassnew Fedora PackageDB web applicationhas this feature, so maybe it’s possible! Anyway, the mockup:Download Pages MockupThis mockup really isn’t anything remarkable; it’s just the recently-updatedhttp://get.fedoraproject.orgdesign in the new template. The mockup below is for the first page.There’s also other download mockupsand they show the detailed options view and the download splash in the new template as well.Community Page MockupJef did a kick-ass job on this mockup, and he worked very closely with Sijis and me as he iterated on the design, posting revisions in IRC and discussing them with us real-time, then making changes based on our discussion and posting another iteration (so on and so forth.) He also picked the right color for it– magenta is the Fedora “friends” color. The green on the features page will probably have to be changed to “features orange” and the orange on the downloads page to “First green.”One cool component to this design is the idea of a watermark-style Flickr group/tag gallery behind the much larger, masked photo of Fedora community members. Jef also integrated the Fedora microblog feed, and made our current join graphics look a whole lot nicer!Other mentionable itemsfedoraproject.org redesign in stagingSijis set up a staging environment for the redesign athttp://stg.fedoraproject.org. Right now it has the base template with HTML& CSS Sijis and I worked on, but none of the new design meat I’ve showcased above… we’re working on it! (If you’re interested in helping…pop into #fedora-websites on irc.freenode.net and let’s talk!) So watch our staging environment; as we check in content it’ll appear within an hour or so of checkin.Download splash systemAnother cool development Sijis made was a functioning download splash system! This was a feature we had to drop in thehttp://get.fedoraproject.orgredesign for Fedora 13 because there wasn’t enough time to implement. Sijis figured out a way to do it with Javascript, making it a much lighter and impactful feature – way to go! While there’s still some issues to be worked out as I understand from IRC today, you can try it out now by clicking on a download link athttp://get.fedoraproject.org.Embedded fonts!We’ve got free and open souce fonts Comfortaa and Cantarell embedded in the page, so you’ll note all the mockups use Cantarell as the base font – and the feedback we’ve gotten on the use of Cantarell thus far, by the way, has been overwhelmingly positive.And yet even more…But it will have to wait for another blog post. We’ve got some really amazing updates on thefedoracommunity.orgproject, including some super-slick jQuery-based javascript from new Fedora design team memberMarc Stewart!Where the action is atIf you want to jump in on this project or just learn more about it:Our project page on the wikiis a great place to start.Pull up a virtual chair in #fedora-websites on irc.freenode.org and poke me (mizmo), Sijis (sijis), or Jef (Schendje) and chat us up!Filed under:Fedora,Fedora Design Team,Websites | ||
| XTS censusWho-T | Planet Fedora | |
| Tiago's X 1.9 Censusincludes the commits to the X Test Suite for the 1.9 window. IMO, this isn't particularly expressive since XTS follows its own cycle and the server merge windows have no meaning to it.The short history of XTS is:The X Test Suite was written back in the day of yonder (possibly more than two yonks ago) and it is designed to perform a number ofprotocoltests to verify whether the server has changed behaviour. This includes simple things like creating a window and making sure the MapNotify is sent through to more complex interactions with modifiers and grabs.XTS was still in CVS until 2009 when I wanted to figure out how much I really broke with MPX. So I imported it into git and started autotooling it. XTS is a bit of a beast and at some point I gave up and asked Dan Nicholson for help; his autotooling skills exceed mine by some unmeasurable amount. A few months later and some 80-something commits later Dan came back with a fully autotooled XTS. So building XTS went from requiring awiki pageto git clone, autogen.sh, make.From then on, we continued working on making it more sane and easier to run, along with misc code cleanups (DECNET support? Really?) and one of my favourite issues: that after 4 hours of runtime one realised that every test had failed because DISPLAY wasn't set. Anyway, I digress.We found a couple of issues in the X server as well, with 1.7.7, 1.8.1 and 1.9.0 being the first three releases that pass the test suite without crashing.XTS is still a bit from being really useful, at the moment many of the test results are write-only (though a few test errors have fed back into the server or even libxcb). Anyway, here are the raw numbers from gitdm (that 1 employer is Unknown because I couldn't be bothered setting up a gitdm.config file).Note: 1024 of my changesets are a semi-automatic rename of files and that skews the statistic.Processed 1275 csets from 5 developers1 employers foundA total of 33380 lines added, 30758 removed (delta 2622)Developers with the most changesetsPeter Hutterer 1061 (83.2%)Dan Nicholson 192 (15.1%)Aaron Plattner 12 (0.9%)Jon TURNEY 4 (0.3%)Tinderbox user 4 (0.3%)Developers with the most changed linesDan Nicholson 20545 (50.0%)Peter Hutterer 10296 (25.0%)Aaron Plattner 3854 (9.4%)Tinderbox user 655 (1.6%)Jon TURNEY 30 (0.1%)Developers with the most lines removedAaron Plattner 2000 (6.5%)Developers with the most signoffs (total 5)Dan Nicholson 3 (60.0%)Peter Hutterer 2 (40.0%)Developers with the most reviews (total 10)Dan Nicholson 7 (70.0%)Peter Hutterer 3 (30.0%)Developers with the most test credits (total 1)Pat Kane 1 (100.0%)Developers who gave the most tested-by credits (total 1)Dan Nicholson 1 (100.0%)The point of this blog post? Give credit to Dan for his magnificent work on XTS because he's been carrying the load for quite a while. And of course, many thanks to Aaron, Jon and Pat for their contributions. | ||
| If I could walk away from Twi... | Planet Fedora | |
| Sadly, I can’t. Why not? Because I cater to users in the education world now, and by and large, my users are Twitter users who don’t even know what identi.ca is.See, this is the danger inherent to monolithic web services:the network is the lock-in.And if the web services provider changes access policies to that network in a way that you don’t like, then buddy, you’re out of luck.So Twitter broke the entire open source world today with their move to OAuth. So what? Are all those Twitter users gonna move over to identi.ca?Let me answer that rhetorical question for you: no. No, they won’t.What’s more, the question of “open source or closed source” doesn’t even enter into it. Twitter could open source their codebase tomorrow, and people could set up their own Twitter servers, and it wouldn’t matter; all the users are at twitter.com, and no force on Earth would move them to fredsmicrobloggingservice.com.The network is the lock-in. | ||
| On updates and user experienc... | Planet Fedora | |
| So, the debate about update policies and user experience etc is spilling onto the Planet, with some constructive posts fromMáirínandJonso far. Thought I’d throw in a few cents.In the end, it doesn’t matter hugely to me how this gets settled – I work QA, and as I figure it, our job is to do the best testing job we can in the context of the overall aims and development method of the project. You sometimes see cases where QA people want to dictate the way development happens on the basis ofbeing able to test things properly, but I think that’s ass-backward; whoever is leading the project should set the goals and development methods, and QA should work within those. If whoever’s in charge is unhappy with the resulting product’s quality they might want to tweak the process, but it’s not really QA’s job to dictate that. So I’m fine with working with whatever process gets decided in the end.From an entirely personal point of view, though, I have to say I kinda wind up on a slightly different side of the question to Máirín and Jon. Máirín has Caroline Casual User; Jon talks about what Windows and Mac OS do, what “users” want, and stuff like “can feel quite confident doing an update as a matter of best practice, even ten minutes before a big presentation, or even during the presentation if I want to”.I’m kind of sympathetic towards the point of view that that’s a perfectly sound goal for an operating system, but it may not necessarily be the best goal for the Fedora operating system to pick. Just because that’s the target of Windows and OS X doesn’t mean it has to be ours.For a start, there’s already plenty of Linux distributions besides Fedora with those goals. To put it bluntly, there’s Ubuntu, and Ubuntu’s doing a fairly decent job of being Ubuntu. I’ve argued before that it’s somewhat dangerous for the overall ecosystem for Ubuntu to drive out all competitors, and to anextent I stand by that, but OTOH, I’m not entirely sure that being Ubuntu’s token competition is the best thing Fedora can be. For a start, Fedora isn’t set up for it. Exactly this kind of debate makes the advantages of Ubuntu’s Benevolent Dictator model apparent; this just wouldn’t reallyhappen in Ubuntu-land, or if it did, it’d be in a conference room with Mark and ten other people and it’d be over in an hour. The Fedora project is built in a different way; being run by a chain of partly-elected committees is great for openness and transparency and defending community values,but it does lose the benefits of focus and swiftness that come from having one person in charge and defining the project’s scope and vision.I like the idea that’s mostly being proposed by the ‘radical’ side of the debate that the best and most efficient way to use the resources of the Fedora project going forwards is to be something different from what Windows and OS X and Ubuntu are. One of the advantages of the F/OSS world is that we’re supposedto be better at co-operation than competition. I think it would be kind of cool to have a world where everyone knows that Fedora is the distribution with the latest bleeding-edge stuff and Ubuntu is what you install on grandpa’s computer, or yours if you want to trade off a quiet life for not getting the latest everything all the time.In fact I could be quite happy if we revised Fedora’s process completely. I can see a future where we aim to be a rolling distribution, and put out a point release only when we *have* to; when I asked people within Fedora a while back why point releases still exist, the only really valid answer was more or less ‘because sometimes changes happenthat we can’t handle with an in-place update’. That’s fine, but in that case, there’s no real reason besides PR to schedule releases every six months; why not just do a release when some change means we *have* to do one? When such a change comes along we put out a set of images and give people six months to reinstall or upgrade, pushing security fixes for the previous codebase during that period, and then just declare it dead and say everyone needs to be on the new code now? Most of the objections to this kind of thing are about providing stable platforms and dependable updates and yadda yadda, but I already said, there’s no reason Fedora has to be that project. In a lot of ways I think Fedora could be a much more interesting and useful project in the long term if it wasn’t.tl;dr summary: let’s let Ubuntu be Ubuntu, and let’s us be something different, and that should be the most efficient way for the whole F/OSS / Linux world to use its resources. | ||
| Disponibile Equinox 1.30 (GTK... | Planet Fedora | |
| Rilasciato fresco fresco Equinox 1.30:link per download più istruzioniSui repository fedora ancora nonè stato aggiornato, quindi se volete passare alla nuova versione vi consiglio di disinstallare la 1.20 e compilare i sorgenti della nuova versione.Filed under:Flash NewsTagged:Equinox,Fedora,GTK2 | ||
| python-slip-0.2.13-1.fc13.src | Fedora 13 | |
| aespipe-2.4b-3.fc13.src | Fedora 13 | |
| aespipe-2.4b-3.fc12.src | Fedora 12 | |
| merkaartor-0.16.3-1.fc13.src | Fedora 13 | |
| xorg-x11-xinit-1.0.9-18.fc13.... | Fedora 13 | |
| xorg-x11-xinit-1.0.9-18.fc12.... | Fedora 12 | |
| kernel-2.6.34.6-47.fc13.src | Fedora 13 | |
| ibus-pinyin-1.3.10-1.fc13.src | Fedora 13 | |
| kernel-2.6.32.21-166.fc12.src | Fedora 12 | |
| gabedit-2.3.0-1.fc12.src | Fedora 12 | |
| opencv-2.0.0-9.fc13.src | Fedora 13 | |
