 |
No items matching your keywords were found.
Cool Graffiti Tag Names
Is it legal to shine a computer projector onto the side of a building?
I got a cool app for my back that uses a webcam to see where ever I am pointing with my green laser pointer, and then using the projector it leaves a trail where ever I shine the laser.
so basicly If I was to draw something on the building or write a name with my laserpointer, the projector would continue to show it until I cleared it or turned it off.
What are the legality's of doing this here in the USA?
http://www.engadget.com/2007/02/20/graffiti-research-labs-l-a-s-e-r-tag/
Someoe would probably try to sell you a life.~!
|
No items matching your keywords were found.
| We did not find any matches for your request. |
Graffiti - POS - All In the Name
RSS Feeds
Thank you! That was very helpful, I just Dugg your url.
Hi Sean and John. According to the people who wrote our FO, it's the “most complex one they've ever seen.” Nice. The content model itself makes perfect sense to us, because it reflects our products. The tag names and the concept around how they all fit together aren't that obvious to outsiders though. We have documentation and in the past when vendors have had to work with our XML, they've eventually got it. But in the case of reprint corrections, the project is too small for them to get acquainted with the content model, and definitely too small for them to develop their own transformations to get it to output.
As for the corrections themselves, if they're just text corrections, then anybody could do them in a text editor as you point out. I'm actually not sure that that's the extent of it though since I haven't been provided with them yet. If stuff needs to be moved around on the page or other big restructuring has to happen, the problem of familiarity with the content model comes into play again. I'm crossing my fingers that's it's just text changes which can be done in the PDF files. Then I'll gather the corrections and stuff them in a folder to go in the archive, so if we ever need to use the XML again we'll know that corrections will have to be made. The “what could possibly go wrong” solution seems the most workable–if it's just text corrections. If they go deeper, then even the PDF solution may not work, so we're back to finding someone to work in the system to fix the XML. More to come, I guess.