If you want to send a file from your phone to another bluetooth device. Use this Intent with the file details:
Intent intent = new Intent();
intent.putExtra(Intent.EXTRA_STREAM, Uri.fromFile(f) );
This will open up a built-in application chooser, listing all applications that can handle the item – based on the type property. Once you choose bluetooth, the android bluetooth application will launch and let you pick the device to send it too.
And on a related note, If you want to register your application so it can be on this list and do something with a specific file when someone tries to send it.. For instance if your writing a custom email client. Add this to one of your activities in the manifest, then add a if/else check in your onCreate method.
Intent intent = new Intent();
intent.putExtra(Intent.EXTRA_STREAM, Uri.fromFile(f) );
Easy-to-deploy, simplified Product Data Management (PDM)
Without basic CAD data management, it’s difficult for organizations to effectively collaborate and improve their productivity. PTC Windchill PDM Essentials empowers smaller organizations to effectively organize and manage their product content so they can improve design reuse, broaden access to product information across roles and ensure control over design versions and release processes.
Based on PTC’s production-proven PLM software, PTC Windchill PDM Essentials offers a quick to deploy, easy–to-use offering that can improve your ROI. By managing product data from PTC Creo, as well as many other CAD systems, you can ensure data integrity and enable concurrent engineering.
PTC Windchill PDM Essentials is right-sized for the existing needs of smaller teams and companies. And it provides the foundation for additional capabilities that a growing company may require in the future.
Features & Benefits
- Installation and configuration wizards greatly simplify and accelerate the deployment process, providing customers with greater value in less time and at a much lower cost.
- Centralized vaulting and revision control of CAD models, their structures and relationships (PTC Creo, AutoCAD, SolidWorks, Inventor, Pro/ENGINEER, PTC Creo Elements/Direct, and PTC Mathcad).
- Efficiently manage office documents, such as Microsoft Word and Excel, by controlling changes through check in and check out functionality.
- Powerful searching tools and easy copying / renaming of existing designs accelerate product information discovery and promote design reuse.
- Schedule and automatically publish viewables and other formats such as thumbnails and PDFs.
- Embedded 3-D view and markup utilities empower non-CAD consumers to view, section, measure and markup designs.
- Lifecycle states control when various roles are able to view, use and update product items. This ensures that areas such as manufacturing and purchasing can only access released items.
Adopting a cashless payment environment at your festival or event can open up a world of
possibilities and enhancements.
Savinirs RFID wristbands and event passes have been used for thousands of cashless transactions, giving organisers complete control over revenues,
while festival-goers enjoy a convenient and highly secure method of payment.
Possible benefits include:
- Real time sales reporting for complete control
- Dramatically reduced queuing and transaction times at vendors
- Cost savings from carriage, security and administration of cash
- A safer, more convenient way to transact at events
As Copied from Huffington Post
I’ve seen it too many times: starry-eyed would-be Internet entrepreneur meets real developer, dream in hand. This is culture clash. More often than not, it ends up with wasted time, wasted money and dashed dreams. Concept meets computer code.
In 30+ years in the software business I’ve been a developer, a dreamer, a consultant to the dreamers and an employer to the developers. So maybe I can help. With thanks to several contributors (below), here are 10 tips for the dreamer side of the equation:
- Software is usually a compromise between the dream scenario, on the one hand, and what’s actually do-able in software. Think of whatever your favorite productivity software, or app and how, as you learn to work with it, you learn to accept its way of doing things instead of your way. Everybody hates their accounting software, right? But you make do because it’s easier than balancing your checkbook with a pencil and a calculator. Real development takes compromising what’s ideal for what’s actually possible.
- You have to listen. Developers think and talk in code (double meaning intended.) Most of the time, as you explain to them what you want, they’re trying to translate between what you imagine and what software code will actually let them do. They are not necessarily articulate, tactful, or very good at explaining. You have to shut up and listen. Catch the clues. Don’t think they’re not understanding you. They probably are, and they’re jumping ahead of you to what they can implement in code.
- Understand critical relationship factors. Figure out whether your developer is a partner or just a vendor. It’s really hard to succeed in software, especially at the early stages, without brainstorming, collaboration and excitement about ideas. If you want a developer to just shut up and write code you’re probably doomed from the start. Please re-read points 1 and 2 above.
- Who owns the product? You can’t get around this sticking point. The road to startup success is littered with the carcasses of failure caused by disputes over ownership of ideas, ownership of code and points in between. You have to talk about it. Painful, maybe; awkward, maybe, but establish with your developer that you own the work, or that it’s shared. My suggestion: own the work, but listen, collaborate, own it legally and technically (because you’re the one writing checks) but not emotionally or creatively.
- Pay for results, not hours. I learned that the hard way, and from both sides of the table. Don’t pay too much in advance. Set milestones together. Pay for achievements. Programmer hours are more volatile than Midwestern summer weather. They’re like airplane seats, where one passenger pays 20 times what it cost the passenger across the aisle.
- Identify which developer personality is which. Developers are often multiple people, like schizophrenics. They want security, steady income, power, big entrepreneurial jackpots, ownership, and days off without worrying about anything. They’re geniuses in good moments and pains in the royal ass in bad moments. Which makes them a lot like the rest of us. Try to figure out which personality is which, so you can let the genius soar at the right times, and avoid the pains. Careful with egos. It’s really stupid to shut down creativity with discipline.
- Know your developer. Check references before hiring. Call some past relationships. We all work with the assumption that programmers are super smart and eclectic, but some pseudo-programmers are smart as scammers. Ideas get stolen and it’s not illegal. Watch the movie Social Network and realize that the law supports the Mark Zuckerberg character in that script. The twins might have thought of it, but he did it. And keep in mind that most developers are good at some things, but not all things. Some focus on interface, some on system back end and so on.
- Design an early check-in point into the project. Never contract a whole project from the start. Instead, find a quick first step that can also be an abandonment point. It’s like in a personal relationship, meeting new people, you want to get a cup of coffee first, before jumping into bed together.
- Get the key points in writing. No, I don’t mean some big fat contract, or expensive legal work; but have your developer sign a short letter — in English, not legalese — that establishes who owns what, when the money changes hands and what you’re agreeing to.
- Remember the dragons. One of my favorite programmers compared software development to Columbus setting out from the Canary Islands sailing west:
He hoped he’d end up on the coast of India, but I bet he still feared falling off the end of the Earth into the mouths of the dragons. Software development is like that. You think you’re going to reach land, but you might not.
And good luck. Enjoy the journey. And may you reach the other shore.
Well, from last one month i was facing one issue with my PHP pages when i run on IE8.
Finally got the reason and the solution-
Reason – IE was pulling the content from the old files stored in its Temp folder.
Solution – Pass some unique parameter with the URL (say, time stamp).
A small example -
In the above statement you can see, i am passing a parameter called timestamp, which will be unique each time you access this URL , so the browser will not take the old file from its temp folder.
For more information you can browse through internet… there is lot of information available.
Active RFID tags have a transmitter and their own power source (typically a battery), which is used to run the microchip’s circuitry and to broadcast a signal to a reader. Where as Passive tags does not have their own power supply, but are read through electromagnetic waves from a reader. Semi-passive tags use a battery to run the chip’s circuitry, but communicate by drawing power from the reader. Active and semi-passive tags are useful for tracking high-value goods that need to be scanned over long ranges, such as railway cars on a track, but they cost more than passive tags, which means they can’t be used on low-cost items. Savinirs is actively involved in providing the Active RFID solutions at affordable prices.