Wow, thats quite a bit I hadn't even considered, mostly because I wouldn't know where, or, for that matter, how to begin.
I'll look at them one by one.
"Development of a script for some specific USB device support": Hmm, while interesting, I wouldn't have a clue how, though I'm more than willing to learn if you can point out something that could explain that.
"Create a new client-server app": Ooh, this is something I've wanted to try to do for a while, but I've never gotten over that first major hurdle of figuring out how to get them to talk to each other, any suggestions?
"Find a pair of file types that need conversion...": My biggest flaw at the moment may very well be that I have a rediculously hard time understanding the anatomy of a file format. I've never really worked with anything becides plain text. Once again, if you have any suggestions as to how I could get better, just say so :)
"[Improve Perl I/O support]": Hmm, interesting, are you refering to the IO modules, or to something else though?
#5: Well, umm... could you explain that in a little more detail (/me has minimal knowledge of network systems & program interaction)
I know, I'm helpless! Hehe. Seriously, all of those sound interesting, but for most, I'd have no idea how to do it. That's part of why I'm doing this project though, to try to learn something I don't already know. So if you can answer any of those questions, I'll appreciate it. Thanks!
Note: Yes, by some freak accident I made it to "Friar" here without any of that knowledge.
My code doesn't have bugs, it just develops random features.
Flame ~ Lead Programmer: GMS | GMS | [reply] |
Dear Flame,
USB -support - there are a few USB test kit vendors out there who provide drivers and small USB test boards. They usally read switches and light LEDs. There are USB ref docs on the web. I'd contact a vendor and see if they would help you out.
Client-server apps are documented with code in several Perl books. They usually let you send and receive a buffer full of bytes between two ports on two machines. You would add some structure to the buffer content and possibly use simple TK to display the results. You might make a master/follower mouse display or perhaps a "public scratchpad" app. Check out "Perl in a Nutshell" - Chapter 13.
The file server converter is interesting. Use hex mode in vi (or similar editor) to look at the byte by byte content of a file. Start with a simple text file. You'll see the text and the "whitespace" characters, like line feeds, spaces etc. You can use Perl to read and parse this file and then spit out a different format. Consider a simple Unix /PC converter. You might also try a simple encryption technique.
In the broader sense think about any app that needs to move info of one type to another in a consistent way. The term often used is "Data Munging" and there is a good book by that title for Perl (by David Cross). This sounds pedestrian, but a whole lot of people get paid a whole lot of money to come up with fast and accurate format conversions.
Good luck and use strict
Diskcrash
| [reply] |
Thanks for the explanation, a lot of this looks like it'd be really fun to mess around with. I'll add most of these to my list of possibilities.
/me runs off to grab a copy of "Perl in a Nutshell"; meanwhile becoming luckier and using strict
My code doesn't have bugs, it just develops random features.
Flame ~ Lead Programmer: GMS | GMS
| [reply] |