snunn wrote:Ummm...did you look at the java code below. It is *very* easy to control the pi via java.winscp the results of a maven/ant build done via the eclipse ide. Then use a simple putty window on the pc which is connected to the pi so you can run the program. You don't have to "write" the code directly on the pi.
-Simon
As I stated, I wasn't starting a debate, nor stating it was the only way to do things. Also note that I'm a linux developer. I don't use putty (I don't use windows). I'd simply use ssh/scp.
To write that reply I simply did what any hobbyist would do. I googled for "raspberry pi blink LED" and ended up on the python solution. I threw in the setup details based on MPH's "plug in keyboard and monitor" part, hence the reason I mentioned writing the code ON the pi. To me, therein lies another potential "problem" for hobbyists and the pi. There's two dozen ways to do things. I could have shown a bash script that echoed values to the /sys filesystem for GPIO, I could have shown java code as you mentioned, c code, probably tcl, and a dozen others. This'll be my last post about this because it's getting closer to a debate than I already wanted and I don't want to derail this thread any more than I already have.
Materdaddy wrote:As I stated, I wasn't starting a debate, nor stating it was the only way to do things. Also note that I'm a linux developer. I don't use putty (I don't use windows). I'd simply use ssh/scp.To write that reply I simply did what any hobbyist would do. I googled for "raspberry pi blink LED" and ended up on the python solution. I threw in the setup details based on MPH's "plug in keyboard and monitor" part, hence the reason I mentioned writing the code ON the pi. To me, therein lies another potential "problem" for hobbyists and the pi. There's two dozen ways to do things. I could have shown a bash script that echoed values to the /sys filesystem for GPIO, I could have shown java code as you mentioned, c code, probably tcl, and a dozen others. This'll be my last post about this because it's getting closer to a debate than I already wanted and I don't want to derail this thread any more than I already have.
Well, the monitor and the keyboard are optional.. you could just plug it in on teh USB port, or on the ethernet.. And if you dont' like the PI.. ( i'm not using it any longer, but i dont' dislike it ) then you dont' have to use it, just like we dont' *have* to do a lot of thigns...
Do you have a PI? And have you done some work with it?
mrpackethead wrote:Well, the monitor and the keyboard are optional.. you could just plug it in on teh USB port, or on the ethernet.. And if you dont' like the PI.. ( i'm not using it any longer, but i dont' dislike it ) then you dont' have to use it, just like we dont' *have* to do a lot of thigns...Do you have a PI? And have you done some work with it?
I do have a PI. Unfortunately I haven't done too much with it. I've run XBMC on it, and done some minimal GPIO tinkering (using the /sys filesystem). Nothing of significance, which is part of the reason I want to bow out of this thread. I'm not contributing, simply stating why I think there's a much higher entry point for pi use by hobbyists.
Mat er daddy - you make valid points and are correct to comment.
Your standard Home PC - plug it in (mess with the first start up stuff) and then it shouts at you "I can do all this stuff, which one shall I do first for you"
Where as a PI - plug it in (mess with the first start up stuff) and then it just sits there untill you tell it what you want it to do and how to do it.
Most people are not going to be able to order a PI, pulg it in and start writing code to run pixels. But with the tutorials available, from opening the box, they can be writing (promted by a tutorial) their own programs (Hello world) inside 2 hours.
I do think it is an excerlant learning tool - it's powerfull enough to be usefull to us at DIYC - uses human understandable programs (unlike pics) that people can mess about without needing compilers and pic programmers.
The end result: whilst most people, proberbly won't program for their shows, they have the chance (with some reading, watching (you tube) and experimenting) to follow what is going on, and mostly understand how and why things are changing. Some people, however will play and come up with cool stuff.
Some of the stuff we end up using the PI for, I'm sure could be done with a pic (or other device with lower cost and possably they could do it better). But most of the people here like to get involved. For many soldering has been their limit. I believe that the Pi (apart from being a good platform) offers the oppertunity for greater inclusion than has been perviously available.
There are down sides - my Son (12 years old) and my self have been learning Python from (I had typed from 'scratch' and realised why scratch is named that way) so will say as newbies. He has been off school for 3 days now with a chest infection, however he is feeling a little better today. Good news, if he hadent spent this afternoon watching tutorials on you tube and prepearing a list of "modifications" that "I may wish to consider" as I returned from 12 hours on site today.
To finish - I would not recomend that anyone buys a PI based on what we are doing at the moment. There are Windows emulaters for the PI (download it - run - and it pretends its a PI and shows you what it would be doing if it was a PI - mostly). So you can learn how it all works and follow what we are doing at no cost. If we come up with someting good that is usefull to you - get your wallet out and spend $35.
Unless someone beats me to it, which is likely, I'm planing to do a show player that will play HLS files for the Pi. The question is will XLights, with HLS support, get ported to the Pi first. If its going to get ported to the Pi then I'll likely self mine.
That said the Pi can make a very nice show player using both audio and video files. Why dedicate a PC when the Pi can do EVERYTHING the PC can when it comes to running a show.
