What kind of getting started would you like to see?
1) how to use the IDE? Assumes you have prior C an Propeller background.
2) how to use the IDE and Getting started with C? Assumes a Propeller programming background with Spin/PASM.
3) how to use the IDE and getting started with the Propeller? Assumes a C background, hopefully with some sort of micro experience
4) how to use everything: IDE, C, Propeller? Assumes no background at all.
There are at least those 4 audiences to address with guides and tutorials. I'm not sure if there will be gaps with what Parallax Education, the PropGCC team and Steve are producing. There seems to be a lot of work going on in the background to support these launches.
I've been successful in installing and running SIDE on Window 7 inside of a Parallels VM and with Boot Camp on my Mac Pro. I was able to fiddle my way through it fairly easily. Some small stumbles at first but once I figured out memory mode I was getting hello.c running on a Quickstart Board just fine.
Thanks for your effort on this!
Paul
EDIT: I see I missed the thread about 0.5.0 -- so I'm a little behind with 0.3.0
I've been successful in installing and running SIDE on Window 7 inside of a Parallels VM and with Boot Camp on my Mac Pro. I was able to fiddle my way through it fairly easily. Some small stumbles at first but once I figured out memory mode I was getting hello.c running on a Quickstart Board just fine.
Thanks for your effort on this!
Paul
EDIT: I see I missed the thread about 0.5.0 -- so I'm a little behind with 0.3.0
I just tried the OS X version. Everything went well until it came time to load and I was told " error: can't find board configuration ''. I then noticed that there wasn't anything selected in the board selection drop-down and there weren't any items to choose from.
Other functions seem to be working fine. Just a wee problem should I want to load some code.
I had a similar issue, but I copied the files in the SimpleIDE Volume and put it at the root directory. (Just drag the folder to the hard disk) Then I changed the paths in Properties to reflect the changes, e.g. /SimpleIDE/parallax/bin/propeller-elf-gcc and /SimpleIDE/parallax/propeller-load/ respectively. Then relaunched SimpleIDE by double clicking it from it's new location. It seems to work fine now, although I'm not sure why that would have made a difference.
The other thing is judicious use of the "Reset Port" button.
I just tried the OS X version. Everything went well until it came time to load and I was told " error: can't find board configuration ''. I then noticed that there wasn't anything selected in the board selection drop-down and there weren't any items to choose from.
Other functions seem to be working fine. Just a wee problem should I want to load some code.
No icons were intentionally graphically abused while making the user guide .
The user guide does not go too deeply into all the memory models.
@doggiedoc and mindrobots,
Sorry about the MacOSX problems. I'll find a better solution. Thanks for letting me know there are issues. I'll post another attempt later - maybe tomorrow.
@pinedust,
I haven't posted a Ubuntu/Debian or a Fedora x86_64 image yet - sorry about that. Will do soon. The i686 image is for generic 32 bit Linux.
Looking forward to more feedback. Beat it up! We want to enter Propeller-GCC Beta Test next week before the Parallax EXPO.
Finally found a moment to fire up SimpleIDE on Windows 7.
Download, install, clickety click, bingo. Hello world is running on on my ASC.
Change to LMM mode. Clickety click, there it is running again.
Fabulous work Jazzed.
Now to get back to my Debian box. Hopefully after 3 months of intense work I have some spare hours to get back to propgcc things.
I'm working on x86_64 packages today. There has been a change in RTS/DTR reset selection, so i have to adapt to that before releasing another test package. It will take a little time.
Is there a way to reset the Prop without compiling or loading anything?
My ASC has a reset button but such buttons might not always be readily accessible.
Ah, you mean that big red button labeled "Do Not Push":)
Totally missed it what with being dead tired after a one week business trip and only having a few mins to play. Always wondered what those pretty little pictures you see across the top of programs were, you see them a lot.
Which reminds of some thoughts I have been having about icons recently.
There are kids playing with computers today that have never seen a floppy disk. How would they connect that funny blue square thing with saving a file?
I suspect the young generation has never used those brown cardboard files in real life. So what has that funny brown square got to do with opening a file? By the way what is a "file".
Then we often see spanner and hammer icons for things like tools and projects. I suspect that since dad stopped being able to fix his all digital car a decade or more ago and they stopped teaching any kind of "shop" in schools (to dangerous) the young generations have no idea what they might be or mean.
Then, 90% of the worlds population does not live in that idyllic house used as the "home" button in web browsers.
We are only left with simple things like arrow icons to indicate some kind of direction (which stopped looking like real arrows a long time ago) or check marks to indicate "yes".
These comments are no reflection on SimpleIDE just an observation of general practice. What would be good abstract symbols for these things?
There are kids playing with computers today that have never seen a floppy disk. How would they connect that funny blue square thing with saving a file?
I've wondered about this too. I haven't touched a 3.5" disk in about 10 years.
Did anyone look at this user guide link?
@mindrobots, all the icons used are there if you want them for a quickstart.
The help site needs lots of work and will be my main focus after I fix up the Mac .dmg and post the x86_64 package today.
Ah, you mean that big red button labeled "Do Not Push":)
Totally missed it what with being dead tired after a one week business trip and only having a few mins to play. Always wondered what those pretty little pictures you see across the top of programs were, you see them a lot.
Which reminds of some thoughts I have been having about icons recently.
There are kids playing with computers today that have never seen a floppy disk. How would they connect that funny blue square thing with saving a file?
I suspect the young generation has never used those brown cardboard files in real life. So what has that funny brown square got to do with opening a file? By the way what is a "file".
Then we often see spanner and hammer icons for things like tools and projects. I suspect that since dad stopped being able to fix his all digital car a decade or more ago and they stopped teaching any kind of "shop" in schools (to dangerous) the young generations have no idea what they might be or mean.
Then, 90% of the worlds population does not live in that idyllic house used as the "home" button in web browsers.
We are only left with simple things like arrow icons to indicate some kind of direction (which stopped looking like real arrows a long time ago) or check marks to indicate "yes".
These comments are no reflection on SimpleIDE just an observation of general practice. What would be good abstract symbols for these things?
This conversation reminds me of how I learned what "Upper Case" and "Lower Case" letters truly meant. I was in my 40's and visiting Sturbridge Village (a living history museum) and watching the printer manually setting moveable type into a frame, when he made an offhand comment about the letters in the "upper case" and "lower case" - said cases being actual cases that held bins of type, one being in the upper part of the typesetting stand and holding capital and accented letters and numbers, the other in the lower part holding the more common smaller letters.
The point of the story is that I knew how to use the words "upper case" and "lower case" for nearly 40 years without thinking twice what it meant. None of the iconology has to make sense, it just has to be in common use and recognizable, and everybody just learns it and moves on; nobody really cares. That is until they learn the actual history of it, and then it produces a happy "aha moment" - a little Easter egg in the waiting.
This conversation reminds me of how I learned what "Upper Case" and "Lower Case" letters truly meant. I was in my 40's and visiting Sturbridge Village (a living history museum) and watching the printer manually setting moveable type into a frame, when he made an offhand comment about the letters in the "upper case" and "lower case" - said cases being actual cases that held bins of type, one being in the upper part of the typesetting stand and holding capital and accented letters and numbers, the other in the lower part holding the more common smaller letters.
The point of the story is that I knew how to use the words "upper case" and "lower case" for nearly 40 years without thinking twice what it meant. None of the iconology has to make sense, it just has to be in common use and recognizable, and everybody just learns it and moves on; nobody really cares. That is until they learn the actual history of it, and then it produces a happy "aha moment" - a little Easter egg in the waiting.
Cool story. Thanks for sharing. Wonder if there is an icon dictionary with etymology.
Thanks for putting up the latest version for 64 bit debian, I was checking if it was there often. It works great!!!
I have a question though, I have a bunch of common routines I keep in a different directory, my home brew libraries. Is there any way to add a C file to the project without automatically copying the file to the project directory? It messes with my #includes and I will end up with a bunch of redundant files. Plus if I have to make a change there are a whole lot of files I need to modify instead of just one. I found that I can manually edit the .side file and that seems to work, but thought I would ask first.
Thanks for putting up the latest version for 64 bit debian, I was checking if it was there often. It works great!!!
You're welcome. Sorry it took so long. I would have announced this, but I'm not really done yet.
The Debian package has Propeller-GCC inside it ... that may be a one time occurrence. A Fedora 64 SimpleIDE package is also posted. Propeller-GCC is posted separately.
I have a question though, I have a bunch of common routines I keep in a different directory, my home brew libraries. Is there any way to add a C file to the project without automatically copying the file to the project directory? It messes with my #includes and I will end up with a bunch of redundant files. Plus if I have to make a change there are a whole lot of files I need to modify instead of just one. I found that I can manually edit the .side file and that seems to work, but thought I would ask first.
Thanks again for your great work on this project.
I'll look at adding "Add Link" the project manager for this case. How do your #include lines look? Do they contain special path info? I.E. #include "../../foo.h"
You're welcome. Sorry it took so long. I would have announced this, but I'm not really done yet.
The Debian package has Propeller-GCC inside it ... that may be a one time occurrence. A Fedora 64 SimpleIDE package is also posted. Propeller-GCC is posted separately.
I'll look at adding "Add Link" the project manager for this case. How do your #include lines look? Do they contain special path info? I.E. #include "../../foo.h"
An example of what I am doing, I have some code to interface with a ds1620 chip. It uses a utility with a relative path ../utils/shiftinout.c and I include a header for some declarations.
#include "../utils/include/shiftio.h"
In the shiftinout.c file it includes the same header.
#include "include/shiftio.h"
If I add shiftinout.c to the project in SimpleIDE it gets copied to the project directory and the relative path is invalid. There are obviously a number of ways to get around this, and the easiest for me is to just manually edit the .side file to use ../utils/shiftio.c, as my Makefile does. This not a show stopper and it's easy enough to work around.
This not a show stopper and it's easy enough to work around.
You should be able to add -I <include path> to other compiler options to solve most of this.
You shouldn't really need to add headers to the project list.
I'm happy to work with you on this to see if we can make it fit your needs in a SimpleIDE way.
The -I compiler option works fine, I am now able to do things the SimpleIDE way, thank you.
I am still thinking about the idea of copying a version of a file for each project that uses it versus having a single instance of a file that many projects are able to link into the project. What is the advantage of copying a file?
The -I compiler option works fine, I am now able to do things the SimpleIDE way, thank you.
I am still thinking about the idea of copying a version of a file for each project that uses it versus having a single instance of a file that many projects are able to link into the project. What is the advantage of copying a file?
Thanks again!
Good to hear things are working for you.
I have an "Add File Link" project menu option in test now. It makes sense to reuse code without having to make copies.
The main reason for making copies into the project directory is to make sharing easy with zip or tar. Having "Add File Link" in the project manager makes sharing with zip much more difficult. Using real source control solves it of course, but that and other features are reserved for Eclipse.
Comments
I'm producing new packages today for all platforms.
What kind of getting started would you like to see?
1) how to use the IDE? Assumes you have prior C an Propeller background.
2) how to use the IDE and Getting started with C? Assumes a Propeller programming background with Spin/PASM.
3) how to use the IDE and getting started with the Propeller? Assumes a C background, hopefully with some sort of micro experience
4) how to use everything: IDE, C, Propeller? Assumes no background at all.
There are at least those 4 audiences to address with guides and tutorials. I'm not sure if there will be gaps with what Parallax Education, the PropGCC team and Steve are producing. There seems to be a lot of work going on in the background to support these launches.
We have a web page dedicated to all this and it needs some scrubbing and additions.
All doc efforts will be credited appropriately.
BTW, the v0.6.2 package will have a new feature you requested. I was looking at the .pdf output on Linux for example ....
I've been successful in installing and running SIDE on Window 7 inside of a Parallels VM and with Boot Camp on my Mac Pro. I was able to fiddle my way through it fairly easily. Some small stumbles at first but once I figured out memory mode I was getting hello.c running on a Quickstart Board just fine.
Thanks for your effort on this!
Paul
EDIT: I see I missed the thread about 0.5.0 -- so I'm a little behind with 0.3.0
And this: http://code.google.com/p/propside/downloads/list
Sorry about that.
I just tried the OS X version. Everything went well until it came time to load and I was told " error: can't find board configuration ''. I then noticed that there wasn't anything selected in the board selection drop-down and there weren't any items to choose from.
Other functions seem to be working fine. Just a wee problem should I want to load some code.
Thanks!
Installing it and attempting to run on my Ubuntu 10.04, 64 bit box resulted in:
~/SimpleIDE-0-6-2$ ./simpleide
~/SimpleIDE-0-6-2$ Cannot mix incompatible Qt libraries
Aborted
Which Qt library version should I be using?
SimpleIDE-0-5-0 works great.
The other thing is judicious use of the "Reset Port" button.
Hope this helps.
Paul
https://sites.google.com/site/jsdenson/simpleide-userguide
No icons were intentionally graphically abused while making the user guide
The user guide does not go too deeply into all the memory models.
@doggiedoc and mindrobots,
Sorry about the MacOSX problems. I'll find a better solution. Thanks for letting me know there are issues. I'll post another attempt later - maybe tomorrow.
@pinedust,
I haven't posted a Ubuntu/Debian or a Fedora x86_64 image yet - sorry about that. Will do soon. The i686 image is for generic 32 bit Linux.
Looking forward to more feedback. Beat it up! We want to enter Propeller-GCC Beta Test next week before the Parallax EXPO.
Thanks,
--Steve
Download, install, clickety click, bingo. Hello world is running on on my ASC.
Change to LMM mode. Clickety click, there it is running again.
Fabulous work Jazzed.
Now to get back to my Debian box. Hopefully after 3 months of intense work I have some spare hours to get back to propgcc things.
Everything goes as expected. Wonderful.
I'm working on x86_64 packages today. There has been a change in RTS/DTR reset selection, so i have to adapt to that before releasing another test package. It will take a little time.
My ASC has a reset button but such buttons might not always be readily accessible.
Next up is to get this running on my ARM boards.
@Steve: Thanks again for all your hard work on SimpleIDE.
Thanks, Steve.
Totally missed it what with being dead tired after a one week business trip and only having a few mins to play. Always wondered what those pretty little pictures you see across the top of programs were, you see them a lot.
Which reminds of some thoughts I have been having about icons recently.
There are kids playing with computers today that have never seen a floppy disk. How would they connect that funny blue square thing with saving a file?
I suspect the young generation has never used those brown cardboard files in real life. So what has that funny brown square got to do with opening a file? By the way what is a "file".
Then we often see spanner and hammer icons for things like tools and projects. I suspect that since dad stopped being able to fix his all digital car a decade or more ago and they stopped teaching any kind of "shop" in schools (to dangerous) the young generations have no idea what they might be or mean.
Then, 90% of the worlds population does not live in that idyllic house used as the "home" button in web browsers.
We are only left with simple things like arrow icons to indicate some kind of direction (which stopped looking like real arrows a long time ago) or check marks to indicate "yes".
These comments are no reflection on SimpleIDE just an observation of general practice. What would be good abstract symbols for these things?
I've wondered about this too. I haven't touched a 3.5" disk in about 10 years.
Did anyone look at this user guide link?
@mindrobots, all the icons used are there if you want them for a quickstart.
The help site needs lots of work and will be my main focus after I fix up the Mac .dmg and post the x86_64 package today.
Thanks,
--Steve
This conversation reminds me of how I learned what "Upper Case" and "Lower Case" letters truly meant. I was in my 40's and visiting Sturbridge Village (a living history museum) and watching the printer manually setting moveable type into a frame, when he made an offhand comment about the letters in the "upper case" and "lower case" - said cases being actual cases that held bins of type, one being in the upper part of the typesetting stand and holding capital and accented letters and numbers, the other in the lower part holding the more common smaller letters.
The point of the story is that I knew how to use the words "upper case" and "lower case" for nearly 40 years without thinking twice what it meant. None of the iconology has to make sense, it just has to be in common use and recognizable, and everybody just learns it and moves on; nobody really cares. That is until they learn the actual history of it, and then it produces a happy "aha moment" - a little Easter egg in the waiting.
Cool story. Thanks for sharing. Wonder if there is an icon dictionary with etymology.
Ray
Run all the demos without any problem.
Very good work !
Thank you !
Reinhard
I have a question though, I have a bunch of common routines I keep in a different directory, my home brew libraries. Is there any way to add a C file to the project without automatically copying the file to the project directory? It messes with my #includes and I will end up with a bunch of redundant files. Plus if I have to make a change there are a whole lot of files I need to modify instead of just one. I found that I can manually edit the .side file and that seems to work, but thought I would ask first.
Thanks again for your great work on this project.
You're welcome. Sorry it took so long. I would have announced this, but I'm not really done yet.
The Debian package has Propeller-GCC inside it ... that may be a one time occurrence. A Fedora 64 SimpleIDE package is also posted. Propeller-GCC is posted separately.
I'll look at adding "Add Link" the project manager for this case. How do your #include lines look? Do they contain special path info? I.E. #include "../../foo.h"
You should be able to add -I <include path> to other compiler options to solve most of this.
You shouldn't really need to add headers to the project list.
I'm happy to work with you on this to see if we can make it fit your needs in a SimpleIDE way.
Thanks,
--Steve
I am still thinking about the idea of copying a version of a file for each project that uses it versus having a single instance of a file that many projects are able to link into the project. What is the advantage of copying a file?
Thanks again!
Good to hear things are working for you.
I have an "Add File Link" project menu option in test now. It makes sense to reuse code without having to make copies.
The main reason for making copies into the project directory is to make sharing easy with zip or tar. Having "Add File Link" in the project manager makes sharing with zip much more difficult. Using real source control solves it of course, but that and other features are reserved for Eclipse.
Thanks,
--Steve