![]() |
2009-04-01
, 06:43
|
Posts: 1,213 |
Thanked: 356 times |
Joined on Jan 2008
@ California and Virginia
|
#12
|
![]() |
2009-04-01
, 15:47
|
|
Posts: 3,397 |
Thanked: 1,212 times |
Joined on Jul 2008
@ Netherlands
|
#13
|
Well, what does ipod touch run off... n810 runs off linux but... is it still like c++ or something? Anyway, I'm getting an iTouch and will get the new RX-51 (hopefully it may be slightly easier on this as it supposedly will have better processing) In the meantime, I'm gonna learn all this programming. If iTouch is the same, it is probably better to start with it... well, either way, ill have to learn the programming of it and therefore, programming for it will be better to learn it while programming for it...
Anyway, JmJanzen, that is a very good thought... it's similar only, mine kind of combines the two... which is pretty hard to do. Easy enough to break up the bits and then transfer peices to RX-51 or n810 but, to figure out which ones are necessary and break them up in the correct groups is impossible. My idea is this and it's probably impossible:
The computer begins the processing after an app is launched on the IT, it decides what the first screen needs to function in the beginning, processes it a little to make it easier for the IT. Then, it figures out what the responses of the user of the first page could be, processes it like the first page and sends it to the n810. By now, the user has hit a link, the IT sends that information about the link to the computer and the IT processes into the already processed link and dumps all the rest. Then the computer finds the links or responses to the next action... and it goes on.
Simple to say but, as you all have pointed out, impossible to do... well, it would be very hard. I think this would be a great project but, would be kind of pointless if there is no multitouch or accelerometer. Accelerometer we will get with Craves1's project but, multitouc, we will never get. IDK, I think that I'll start off with some basic processing, get to know the itouch and then, figure out all of this when my RX-51 arrives.
![]() |
2009-04-01
, 15:53
|
|
Posts: 610 |
Thanked: 391 times |
Joined on Feb 2006
@ DC, USA
|
#14
|
![]() |
2009-04-01
, 15:54
|
|
Posts: 274 |
Thanked: 62 times |
Joined on Jul 2007
@ Helotes, TX
|
#15
|
...But really, you don't start with learning programming the way you do. Again, like I said, you start with small things, for existing projects. For example you make a small Python panel for Maemo. Or a shell script which parses some data. This has been explained to you by various folks in this thread and you still do not appear to adapt your ideas to this harsh fact.
![]() |
2009-04-01
, 19:11
|
|
Posts: 192 |
Thanked: 60 times |
Joined on Sep 2008
@ Wichita, KS
|
#16
|
... it figures out what the responses of the user of the first page could be, processes it like the first page and sends it to the n810. By now, the user has hit a link, the IT sends that information about the link to the computer and the IT processes into the already processed link and dumps all the rest. Then the computer finds the links or responses to the next action... and it goes on.
The Following User Says Thank You to jmjanzen For This Useful Post: | ||
![]() |
2009-04-01
, 19:38
|
Posts: 5,335 |
Thanked: 8,187 times |
Joined on Mar 2007
@ Pennsylvania, USA
|
#17
|
The computer begins the processing after an app is launched on the IT, it decides what the first screen needs to function in the beginning, processes it a little to make it easier for the IT. Then, it figures out what the responses of the user of the first page could be, processes it like the first page and sends it to the n810.
![]() |
2009-04-01
, 19:43
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#18
|
The device is called iPod touch or iPod Touch. Not iTouch. It is not the name of the device, and the name 'iTouch' makes no sense whatsoever. iPod touch runs same OS as iPhone. Its called 'OSX' or 'iPhoneOS'. What it is? A stripped down embedded version of MacOSX.
![]() |
2009-04-04
, 03:53
|
Posts: 18 |
Thanked: 1 time |
Joined on Mar 2009
|
#19
|
![]() |
2010-03-30
, 07:25
|
Posts: 28 |
Thanked: 7 times |
Joined on Mar 2010
|
#20
|
![]() |
Tags |
i nominate lowtek for a, tmo razzie. seconds? |
|
Anyway, JmJanzen, that is a very good thought... it's similar only, mine kind of combines the two... which is pretty hard to do. Easy enough to break up the bits and then transfer peices to RX-51 or n810 but, to figure out which ones are necessary and break them up in the correct groups is impossible. My idea is this and it's probably impossible:
The computer begins the processing after an app is launched on the IT, it decides what the first screen needs to function in the beginning, processes it a little to make it easier for the IT. Then, it figures out what the responses of the user of the first page could be, processes it like the first page and sends it to the n810. By now, the user has hit a link, the IT sends that information about the link to the computer and the IT processes into the already processed link and dumps all the rest. Then the computer finds the links or responses to the next action... and it goes on.
Simple to say but, as you all have pointed out, impossible to do... well, it would be very hard. I think this would be a great project but, would be kind of pointless if there is no multitouch or accelerometer. Accelerometer we will get with Craves1's project but, multitouc, we will never get. IDK, I think that I'll start off with some basic processing, get to know the itouch and then, figure out all of this when my RX-51 arrives.