'Operation Street Sweep'
WTAP Apr 9 2007 7:14AM GMT
Filip Bondy - New York Daily News
 Carlisle Sentinel | Filip Bondy New York Daily News - HE SEEMED to just appear from nowhere two years ago, from Tainan City, Taiwan, by way of the Columbus Clippers. And when Chien-Ming Wang came to the Bronx in 2005, he was little more than an amiable curiosity item to those who do not spend their ... Sunday Night Baseball: New York Mets at New York Yankees Yankees 8, Mets 2 |
Summer Test: Electric Lawn Mowers
Grass Smells Sweeter When Cut With an Al Gore-Friendly Lawn Mower
Manhattan iPhone Watch: T minus 2.5 days
Blog: The downtown SoHo location now sports a short line, but the 5th Avenue line has not gotten any longer.
IntelliChoice.com's ``Best Deals'' for July Show Little Impact from New Round of Automaker Incentive
PRIMEDIA's IntelliChoice.com (www.intellichoice.com), the leading source for automotive ownership cost and value analysis, today announced its "Best Deals of the Month" for cars, trucks and SUVs for July 2007. Winners for July reveal that the recent increase in incentives and rebates, especially among American automakers, are thus far having little impact on overall value. (PRWeb Jul 5, 2007) Post Comment:Trackback URL: http://www.prweb.com/pingpr.php/SGFsZi1Db3VwLUhhbGYtUGlnZy1UaGlyLVplcm8=
Printing Problem
Hi Guys,
I have a form, which is a multi record form.
The form has a field which, contain the name of a pdf file and its location.
Now i have to place a button in the form that will open up the "Print..." Screen (the one which we get when we select the "Print..." command from the File menu).
This button will not open the pdf but will open the Print screen and on selecting OK there it will print the file.
Can anyone tell me how to go about it, or can provide me some sample code.
Thanks in advance
Rajiv
Kernel Space: Progress on ACPI and Power Management
LinuxWorld: "Len Brown can only be a glutton for punishment; he is, after all, the maintainer of the Linux ACPI subsystem..."
DataWiz Learning Introduces Computer-Based Training for Sri Lankans
... Learning Introduces Computer-Based Training for Sri Lankans Affordable eLearning for Students Provides Courses in Web Design, Microsoft, Business and Enterprise Networking COLOMBO, Sri Lanka--(BUSINESS WIRE)--DataWiz Learning, the leading eLearning provider, ...
Damsels In Success: Networking For Professional Women
Damsels In Success has officially launched with a networking platform that is targeted strictly at professional women. The service positions itself away from the usual range of social networking style clone sites by being more LinkedIn than MySpace and Facebook, with a dose of content chucked in for good measure. (Read on Source)
Bortolami missing for Scots clash
Alessandro Troncon will lead Italy against Scotland, with Marco Bortolami failing to recover from injury. (Read on Source)
Taverna Workshop, Hinxton, UK
I arrived at the EBI last night for the Taverna workshop, during which the design of Taverna2 is presented and workflow examples are discussed. Several 'colleagues' from Wageningen and the SARA computing center in Amsterdam are present, along with many other interesting people. This afternoon is my presentation. Paul Fisher just presented his PhD ... (Read on Source)
Cisco cautious on Brazil tax scandal
Cisco Systems on Monday appeared to further distance itself from a tax scandal in Brazil, saying it can't vouch for everything its channel partners do.
In the case, in which four Cisco employees and 44 other people reportedly have been arrested, Cisco's Brazilian unit has been accused of importing $500 million worth of telecommunications and networking equipment without paying the necessary duties, according to a Reuters report.
The case has shed a rare negative light on Cisco's business practices. The company, which operates around the world and is experiencing strong growth in developing countries, has a reputation for conservative practices and solid accounting.
In its latest statement, the networking vendor explained its indirect sales model and said more than 90 percent of its business in Brazil goes through channel partners. That's more than the worldwide rate, which is over 80 percent, Cisco said.
"If fiscal fraud occurred in the companies that distribute or resell Cisco products, Cisco is not necessarily responsible for these misdeeds," the statement said. "While we hire highly respected audit firms to perform random audits of our distributors, no corporation engaging in an indirect sales model can directly vouch for or control every action of its distributors."
The company has used a channel model around the world for years, letting local distributors and value-added resellers customize products locally, Cisco said. The company works with more than 55 certified channel partners to sell products in Brazil. Some channel partners buy products directly from Cisco and some from authorized Cisco distributors, it said.
The company has more than 250 employees in Brazil, which represents 1 percent of the company's worldwide business, it said. Cisco said it remains fully committed to doing business in the country.
Cisco said it is cooperating with the authorities and conducting its own inquiry to understand the situation and provide as much information as possible, but said it would be wrong to comment further now. Cisco has said before that it does not believe it acted inappropriately.
PictPicture: Vote on your favorite photos
PictPicture is a new website for photographers (pros and amateurs) to find and share the best pictures online. It gives photographers a place to post their pictures and have them voted on. Once a photo receives enough votes it graduates from the Up-Coming page to the Front page. Shooters can create a profile, add friends, and gain exposure for ... (Read on Source)
What's Holding OpenOffice Back?
Why doesn't free trump expensive? Every Microsoft product has a free, open source counterpart created by dedicated programmers who loathe everything the company stands for. The free stuff is darn good. Yet companies and individuals continue to buy billions of dollars worth of Microsoft products.
Bigfoot Hunters Fail to Produce Creature's Corpse
A high-profile press conference raises more questions than it answers about two Georgia men's cryptozoological claim to have found a Sasquatch.
U.S. Women Take Gymnastics Gold Silver
In the individual competition, that is. Nastia Liukin took the gold; Shawn Johnson, thenbsp;silver.Funny, that: We#39;ve got the consensus two best gy... . . . (Read on Source)
Red Hat: The money's in JBoss, not the desktop
Linux specialist is starting to create friction, as well as money, with partners by moving up the software stack. Should it stop with mission-critical middleware?
Blogger Kyle Payne sentenced to six months in county jail
Stating that a major violation of trust had occurred, District Court Judge Don Courtney sentenced Iowa blogger and self-proclaimed male feminist Kyle Payne to serve time in the Buena Vista County Jail for invasion of privacy. (Read on Source)
Akademy Redux: Release Team Members Propose New Development Process
At Akademy 2008, KDE Release Team members Sebastian Kügler and Dirk Müller discussed the future of KDE's development process. Describing the challenges KDE faces and proposing some solutions, they spawned a lot of discussion. Read on for a summary of what has been said and done around this topic at Akademy.
Our current development model has served us for over 10 years now. We did a transition to Subversion some years ago, and we now use CMake, but basically we still work like we did a long time ago: only some tools have changed slightly. But times are changing. Just have a look at the numbers:
- KDE 0.0 to 3.5 took 420.000 new revisions in 8 years
- KDE 3.5 to 4.0 took 300.000 new revisions in 2 years
This enormous growth creates issues both for the wider community, for developers, and for the release team. Patches have to be reviewed, their status has to be tracked - these things become progressively harder when the size of the project balloons like it currently does. The centralized development system in Subversion's trunk doesn't support team-based development very well, and our 6-month release cycle - while theoretically allowing 4 months development and 2 months stabilizing - often boils down to barely 50% of the available time suitable for new feature development.
KDE's current revision control system doesn't allow for offline commits, making life harder for people without a stable internet connection. Furthermore we're still looking for more contributors, so lowering the barrier for entry is another important concern.
Changing requirements
We will have to allow for more diversity and we must be able to accommodate individual workflows. Not everyone is happy with a 6-month schedule, not everyone prefers Subversion. Companies have their schedules and obligations, and what is stable for one user or developer is unsuitable for another. Meanwhile, new development tools have surfaced, such as the much-praised distributed revision control tool Git. Together with new tools for collaborating, new development models are emerging. KDE is in the process of adopting a much wider range of hardware devices, Operating systems (OpenSolaris, Windows, Mac OS) and mobile platforms such as Maemo. And we have an increased need for flexible and efficient collaboration with third parties and other Free Software projects. Sebastian and Dirk believe it is time for a new way of working. In their view, KDE's development process should be agile, distributed, and trunk freezes should be avoided when possible. While there are still a lot of culprits in their proposal, KDE needs to get ready for the future and further growth.
Agile Development
The most fundamental idea behind Agile Development is "power to the people". Policies are there to avoid chaos, and to guide (but not force) people in any way.
What is Agile Development supposed to offer us?- Shorter time-to-market, in other words, less time between the development of a feature and the time users can actually use it
- More cooperation and shortened feedback cycles between users and developers
- Faster and more efficient development by eliminating some current limitations in team-based development processes.
- Simplicity. Not only good in its own right, but it also makes it easier to understand and thus contribute to KDE development.
How can we do this?
To achieve this, we have to reflect upon our experiences as developers and share our thoughts on this. Our process should be in our conscious thoughts. Sebastian and Dirk talked about a specific lesson they have learned: plans rarely work out. As a Free Software project, we don't have fixed resources, and even if we did, the world changes too fast to allow us to reliably predict and plan anything. We have to let go. We should set up a process aimed at adaptation and flexibility, a process optimized for unplanned change.This needs to be done in one area in particular: our release cycle. Currently, our release cycle is limiting, up to the point of almost strangling our development cycle. So Dirk and Sebastian propose a solution:
"Always Summer in Trunk"
Our current release process, depicted in the graphic below, can be described as using technical limitations to fix what is essentially a social issue: getting people into "release mode". Over 4 months, we develop features, then enter a 2 month freeze period in which increasingly strict rules apply to what can be committed to trunk. This essentially forces developers to work on stabilizing trunk before a release. Furthermore, developers need to keep track of trunk's current status, which changes depending on where in the release cycle KDE currently is, not taking into account diverse time schedules of both upstream and downstream entities. At the same time, many developers complain about Subversion making it hard to maintain "work branches" (branches of the code that are used to develop and stabilize new features or larger changes in the code), subsequent code merges are time-consuming and an error-prone process.
The proposal would essentially remove these limitations, instead relying on discipline in the community to get everyone on the same page and focus on stability. To facilitate this change, we need to get the users to help us: a testing team establishing a feedback cycle to the developers about the quality and bugs. Using a more distributed development model would allow for more flexibility in working in branches, until they are stabilized enough to be merged back to trunk. Trunk, therefore, has to become more stable and predicable, to allow for branching at essentially any point in time. A set of rules and common understanding of the new role of trunk is needed. Also, as the switch to a distributed version control system (which is pretty much mandatory in this development model) is not as trivial as our previous change in revision control systems, from CVS to Subversion. Good documentation, best practice guides, and the right infrastructure is needed. The need for better support for tools (such as Git) in KDE's development process does not only come from the ideas for a new development model though. Developers are already moving towards these tools and ignoring such a trend would mean that KDE's development process will clutter and ultimately become harder to control.
In Sebastian and Dirk's vision, KDE's current system of alpha, beta and release candidate releases will be replaced by a system which has three milestones:
The Publish Milestone
This is the moment we ask all developers to publish the branches they want to get merged in trunk before the release. Of course, it is important to have a good overview of the different branches at all times to prevent people from duplicating work and allow testers to help stabilize things. But the "Publish Milestone" is the moment to have a final look at what will be merged, solve issues, give feedback and finally decide what will go in and what not. The publish milestone is essentially the cut-off date for new features that are planned for the next release.
The Branch Milestone
This is the moment we branch from trunk, creating a tree which will be stabilized over the next couple of months until it is ready for release. Developers will be responsible for their own code, just like they used to be, but one might continue using trunk for development of new features. To facilitate those developers who do not want switch between branches, we could have a tree which replicates the classic development model. Developers are encouraged and expected to help testing and stabilizing the next-release-branch.
The Tested Milestone
The "tested" milestone represents the cut-off date. Features that do not meet the criteria at this point will be excluded from the release. The resulting codebase will be released as KDE 4.x.0 and subsequently updated with 4.x.1, 4.x.2, etc. It might be a good idea to appoint someone who will be the maintainer for this release, ensuring timely regular bugfix releases and coordinating backports of fixes that go into trunk.
Technology
A prerequisite for this new development model would be a proper distributed source code management system. Git has already stolen the hearts of many KDE developers, but there are other options out there which should be seriously assessed. Furthermore we need tools to support easy working with the branches and infrastructure for publishing them. Getting fellow developers to review code has always been a challenge, and we should make this as easy as possible. We also need to make it easy for testers to contribute, so having regularly updated packages for specific branches would be an additional bonus. Trunk always needs to be stable and compilable, so it might be a good idea to use some automated testing framework.
Under discussion are ideas like having some kind of "KDE-next" tree containing the branches which will be merged with trunk soon; or maybe have such trees for each sub-project in KDE. Another question is which criteria branches have to meet to get merged into the "new" trunk. Especially in kdelibs, we want to ensure the code is stable already to keep trunk usable. Criteria for merges into various modules have to be made clear. What happens if bad code ends up in trunk? We need clear rules of engagement here. How can we make it as easy as possible to merge and unmerge (in the case the code that has been merged is not ready in time for a release)?
Having a page on TechBase advertising the different branches (including a short explanation of their purpose and information about who's responsible for the work) will go a long way in ensuring discoverability of the now-distributed source trees. A solution also needs to be found for the workload around managing trunk. Especially if we have tight, time-based releases, a whole team of release managers needs to take responsibility. KDE's current release team has come a long way in finding module coordinators for various parts shipped with KDE, but currently not every module has a maintainer.
While there are still a lot of questions open, we'd like to work them out in collaboration with the KDE community. KDE's future revision control system is discussed on the scm-interest mailing list. Discussion on a higher level can be held on the Release Team's mailing list, and naturally KDE's main developer forum, kde-core-devel.
With the release of KDE 4.0, the KDE community has entered the future technologically. Though timescales for the above changes have not yet been decided upon, Dirk and Sebastian took the talk as an opportunity to start discussing and refining these ideas: it's time that KDE's primary processes are made more future-proof and ready for the new phase of growth we have entered.
Buffalo Bills turn to veteran Reed, who delivers
Rochester Democrat & Chronicle Lee Evans gets most of the opposing defense's attention when Buffalo is looking to pass because he is the team's No. 1 wide receiver. Roscoe Parrish is a popular character on the ESPN highlights because when he touches the ball — be it on a pass reception or more likely on a punt return — you'd swear the elusive ... (Read on Source)
Back from the dead brunch... To quote Mark Twain,...
Yes, it's true. Due to the fact I've had a few problems with the old ticker lately. And the episode in Spain (which was not a heart related thing, although nobody knew in the early stages) some folk started to assume that I had popped my clogs! (Read on Source)
Al Franken Bears Brunt of Republican Web Attacks
As liberal advocacy group MoveOn and the Democratic National Committee use Web ads to go to bat for Barack Obama, the Republicans are taking aim in several tight Senate races. Al Franken, "Saturday Night Live" star, turned pundit, turned candidate for Senate candidate, is bearing the brunt. (Read on Source)
Serra upset of Bellarmine opens up open division
The state football championship bowl games are not until December, but the chatter has begun. The favorites to represent Northern California shifted over the weekend after Serra's 31-23 win over Bellarmine. De La Salle-Concord coach Bob Ladouceur called Serra... (Read on Source)
Mobile Web Carriers' Future Uncertain
Panelists at Mass Network Communications Council consult their crystal balls.
Three good reasons to venture into Windows' Registry
Featured links from the CNET Blog Network
Three good reasons to venture into Windows' Registry--Close non-responsive programs automatically, adjust the position of your desktop wallpaper, and prevent specific programs from appearing on the Start menu's most-frequent list.
New honeycomb tire is "bulletproof"--New airless tire designed to carry soldiers to safety.
Hulu's ad revenue to catch up to YouTube's?--An analyst is forecasting that Hulu's revenue will rival YouTube's next year.
Eleven years later, 'Zaireeka's' within reach--When the Flaming Lips released this psychedelic masterpiece in 1997, nobody had four portable CD players lying around. Now, thanks to notebook computers, lots of people do.
FDA's Fraud Finding In Study Means Claims Against Company Are Not Preempted, Court Says
PHILADELPHIA - A plaintiff's claims against a contract research organization are not preempted because the Food and Drug Administration found that the company engaged in fraudulent reporting of clinical study data, a Pennsylvania federal judge said Oct. 25 in denying summary judgment (Eileen Wawrzynek, et al. v. Statprobe, Inc., et al., No. 05-1342, E.D. Pa.). Full story on lexis.com
Web Host WebaZilla Increases Network Capacity to 120 Gbps
... allow us to get into peering agreements with the largest American ISP's available." More web hosting news for Tuesday, December 23, 2008 ...
Both Major Theories About Human Cellular Aging Supported By New Research
Aging yeast cells accumulate damage over time, but they do so by following a pattern laid down earlier in their life by diet as well as the genes that control metabolism and the dynamics of cell structures such as mitochondria, the power plants of cells.
name: MAGPIE