SimpleIDE Request
Phil Pilgrim (PhiPi)
Posts: 23,514
jazzed,
Please allow the terminal to use a different serial port than the program loader -- without having to change back and forth between loading and terminal use. My class is using XBees to interact with their running programs. Although I've told them they can start another instance of SimpleIDE to have an independent terminal window, that's a lot of extra machinery to bring to bear on such a simple problem.
Thanks,
-Phil
Please allow the terminal to use a different serial port than the program loader -- without having to change back and forth between loading and terminal use. My class is using XBees to interact with their running programs. Although I've told them they can start another instance of SimpleIDE to have an independent terminal window, that's a lot of extra machinery to bring to bear on such a simple problem.
Thanks,
-Phil
Comments
-Phil
What is better losing the "I" or the "Simple"?
Hi Phil,
I gave Jeff Martin a heads-up about your request. He's in charge of prioritizing SimpleIDE feature enhancements and coordinating releases from Parallax.
-Steph
-Phil
Hi Phil,
If it's easier (or just as easy) to implement on our side, would it be preferable to have Simple Terminal be available and included (with the SimpleIDE Installer) as a separate executable- that way it can also be launched separately (multiple instances) that are not connected to any SimpleIDE... IDE? :-)
Ideally, it could be included as a separate program but still be able to launch from SimpleIDE with a serial port that's set separately from the load port -- similar to the way PropTool/PST works. That way people have both convenience and options. My students are most comfortable working from within SimpleIDE. With only an hour a week class time, convenience rules.
Thanks,
-Phil
Why not just fire up minicom or gtkterm to communicate with that other port?
-Phil
I have no idea who "My class" is or how old they might be or what level of sophistication we can expect then to achieve.
I tend to lean towards providing continuity as this is what customers and educators have come to expect. One can get too simple.
The biggest suggestion I would make, would be make search clearer that it searches. When I hit ctrlF it lookedlike it wanted to do a replace by default, yikes
Check time stamps before build, as many people will want to use their own editor.
Maybe hide some of the options for the neophyte user, like the ones in the lower left.
Why not add #included files to the projject automatically?
Why have a print that does a subset of printf and not just call it printf?
Iam unclear on CMM, as I had a program that was probably too large for that, and it just went into nevrr neverland, but ran in LMM with no changes
Probably the tooughest issue, is how to take advantage of multplie COGs
Because printf has requirements dictated by C standards that make it too big for most usages. Parallax's print method is much more lean.
Do you have a thread on this?
Yep. I've run into this with my students as well.
As for CMM crash, it was set up as the default (probably should not be), and the program just went south without any warning. But I switched to LMM and it ran fine. Like most people the last thing I do is open a manual anymore, but that might force me to do it, or I can post the question here (lazy that I am). I will post the code later, as this was the coremark test I ran.