I'm sorry if someone already asked this, but I didn't see an answer scanning through previous posts. Is there a way to change the short-cuts in the OS X version? I'd like to make CMD-r to load RAM, CMD-e to load EEPROM, etc.
Jay Kickliter said...
I'm sorry if someone already asked this, but I didn't see an answer scanning through previous posts. Is there a way to change the short-cuts in the OS X version? I'd like to make CMD-r to load RAM, CMD-e to load EEPROM, etc.
Sorry but no there isn't. Oldbitcollector has already asked for it and user defined keymapping is now very high on my todo list. So it's not a hugely long way off.
I'm trying to stabilise the feature and menu set first so I can come up with a compact, extensible and stable way of defining the keymaps in the configuration data without having to make major changes to it as the thing evolves.
And here we go with the latest entry in the saga that is the bst collection.
0.13 0.12 (getting ahead of myself there) is a release I actually feel quite happy with. I managed to find and squash a very longstanding endian bug in the tools I'm using to build it, and subsequently those on PPC Macs should find the font rendering greatly improved. On a Mac, Monaco still looks much nicer than the Parallax font if you don't need the unicode chars.
Lots of polish and little niggles fixed. I've tried to address every issue people have raised. If I've missed your pet peeve or bug, please yell at me.
The compiler is about 50% faster than it was. I found another major slow point with the wonders of valgrind, and thus overall since 0.06 my regression test has come down from about 29 minutes to just a little under 3. It compiles a lot quicker now (or on my 400Mhz PPC an acceptable period of time. No more coffee breaks for compiles)
Mac users can disable the editor anti-aliasing (in the ide options) if they are using a nice font. Windows and Linux users can click the little box to their hearts content, it just does not seem to do much. It was a late entry in the race and I'm still playing with it.
Im still having intermittent trouble detecting the propeller on Windows, but I've not had a great deal of time to dedicate to that recently.
Macs and Linux seem pretty rock solid.
Still have the reset on disconnect on the Mac serial terminal. I am looking into it though.
Changes in the top post as usual.
Please read the release notes (Help -> Release Notes).
I'll be updating the command line tools in the next couple of days. No real bugfixes (except the segfault in bstl from agodwin) but the compiler now goes like greased lightning.
I have yet to try your tools, but i just though of a feature for you that would be very handy for pasm optimizations: Preprocessor commands for automatic loop unrolling (not sure if anyone already suggested this)
something like:
<code A>
UNROLL_START 3
<code B>
UNROLL_END
<code C>
would result in the following right before compilation
<code A>
<code B>
<code B>
<code B>
<code C>
Sure you'd agree the former is much more maintainable than the latter one
One can also introduce macro like CUR_ITER, which will be substituted with a literal corresponding to the current iteration of unrolling.
pems said...
i guess the below is out of consideration?
No, it's not and I apologise for not replying to you specifically. I've been giving quite a lot of thought to macros and conditional compilation but I've not yet reached a point where I have the time to sit down and dedicate some real runtime to it. Unfortunately this is a hobby for me, and like everyone else I have to put food on the table so my programming time is a little more limited that I'd otherwise like.
On top of that, anything I do really needs to be compatible with Homespun, as mpark already has #ifdef and friends in place, so I need to seriously think about how I do what I do to not fragment the community more than is absolutely required to move things forward. At the moment I'm trying to stay as Parallax compatible as I can, but I do realise that at some point we are going to have to move things along.
With last version I not have problems to find Propeler chip
My system ... XP Sp3 Swedish
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Nothing is impossible, there are only different degrees of difficulty. For every stupid question there is at least one intelligent answer. Don't guess - ask instead. If you don't ask you won't know. If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
In Tools menu "Compiler Preferences" You have "Close" buton
Can You extend it to al menu's
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Nothing is impossible, there are only different degrees of difficulty. For every stupid question there is at least one intelligent answer. Don't guess - ask instead. If you don't ask you won't know. If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Still one problem on my system
IDE recognise Prop and load it but Terminal can't comunicate with Prop
Ps. Else reset it
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Nothing is impossible, there are only different degrees of difficulty. For every stupid question there is at least one intelligent answer. Don't guess - ask instead. If you don't ask you won't know. If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Jay Kickliter said...
I'm sorry if someone already asked this, but I didn't see an answer scanning through previous posts. Is there a way to change the short-cuts in the OS X version? I'd like to make CMD-r to load RAM, CMD-e to load EEPROM, etc.
If you install QuicKeys or one of the QuicKeys clones, you can remap any application to use any key commands.
pems said...
i guess the below is out of consideration?
No, it's not and I apologise for not replying to you specifically. I've been giving quite a lot of thought to macros and conditional compilation but I've not yet reached a point where I have the time to sit down and dedicate some real runtime to it. Unfortunately this is a hobby for me, and like everyone else I have to put food on the table so my programming time is a little more limited that I'd otherwise like.
On top of that, anything I do really needs to be compatible with Homespun, as mpark already has #ifdef and friends in place, so I need to seriously think about how I do what I do to not fragment the community more than is absolutely required to move things forward. At the moment I'm trying to stay as Parallax compatible as I can, but I do realise that at some point we are going to have to move things along.
no, no apology is necessary [noparse]:)[/noparse] just wanted to make sure my request is reasonable (in terms of cost/benefit for the community)
wholeheartedly understand the limited time/effort thing
just at the moment I felt like this feature would be really useful for those trying to squeeze as much performance as possible (i.e reduce instruction count to the max)
This could make such difference as being able to run my prop SPI slave @2Mhz as opposed to current max of 1Mhz and avoid the mess of manual unrolling
More polish is needed! The font rendering is ugly on OS X now because anti aliasing seems to be taken out. A minor thing, but a couple pixels on the left of the text window are the color of the bottom block(ie PRI colors or DAT colors), also when a new window is open on OS X, with no text or file, the whole thing is yellow. On Propeller Tool, it only turns CON yellow when there is text without a block. Also, there seems to be syntax highlighting in comments. Sorry if I seem to be a perfectionist!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
I am 1011, so be surprised!
Advertisement sponsored by dfletch:
Come and join us on the Propeller IRC channel for fast and easy help!
Channel: #propeller
Server: irc.freenode.net or freenode.net
If you don't want to bother installing an IRC client, use Mibbit. www.mibbit.com
tpw_man said...
More polish is needed! The font rendering is ugly on OS X now because anti aliasing seems to be taken out. A minor thing, but a couple pixels on the left of the text window are the color of the bottom block(ie PRI colors or DAT colors), also when a new window is open on OS X, with no text or file, the whole thing is yellow. On Propeller Tool, it only turns CON yellow when there is text without a block. Also, there seems to be syntax highlighting in comments. Sorry if I seem to be a perfectionist!
I noticed that to, but I turned anti aliasing back on in the options an it looks great.
tpw_man said...
More polish is needed! The font rendering is ugly on OS X now because anti aliasing seems to be taken out.
As Chuck said below, turn the anti-aliasing back on [noparse]:)[/noparse]
I did it as I've gone from Parallax font to Monaco on my Macs (I don't use unicode chars) and Monaco at 14 point looks excellent with the anti-aliasing switched off.
tpw_man said...
A minor thing, but a couple pixels on the left of the text window are the color of the bottom block(ie PRI colors or DAT colors), also when a new window is open on OS X, with no text or file, the whole thing is yellow. On Propeller Tool, it only turns CON yellow when there is text without a block.
Yep, know about both of those. Yes I intend to fix them, although the 2 pixels of colour on the left do have me a little stumped at the moment.
tpw_man said...
Also, there seems to be syntax highlighting in comments. Sorry if I seem to be a perfectionist!
Yes there is syntax highlighting in comments that span more than one line. I've not got around to implementing block group indicators yet. When I do that the multi-line comment problem will go away.
Still one problem on my system
IDE recognise Prop and load it but Terminal can't comunicate with Prop
Ps. Else reset it
Yes on windows the trick is to open the serial terminal and connect it *then* download the program to the prop and it will work fine.
I know about the problem (there are several with comms on Windows at the moment) but I've not had a chance to really debug it.
Thank you very much for this IDE. It works beautifully on my MacBookPro (OSX 10.5.5) and means I no longer need to be tethered to
either the PC or Windows running inside VirtualBox to play with the Propeller. Your IDE works beautifully on all the cases I've tried.
Parallax should consider putting a link to this directly in their Propeller support materials and downloads, as this opens up the use
of the Propeller to the non-Windows community.
Hey Brad, thought I'd pass this on for your notes. I found an error today when using ~Variable as sign extend, it said it was expecting a Spin command etc. Complies OK in Ptool.
Originator said...
Hey Brad, thought I'd pass this on for your notes. I found an error today when using ~Variable as sign extend, it said it was expecting a Spin command etc. Complies OK in Ptool.
Can you show me a quick example that won't compile please?
@OBC What version of linux are you running right now. I believe there may be a bug in later versions of GTK but I need to know precisely how to reproduce it to fix it.
Don't fix this on my account, I scrubbed this whole idea, but this line gives the error. PropTool compiles the same line. Remove the ~ and it works in bst.
Ok, one more odd issue I experienced on PC. When I rename a file, or rather bump up the revision number as in either 1.01 to 1.02, or using 1_01 to 1_02, the never files get saved in the directory without .spin, and then, when I try to compile it as the new name, it tells me it cannot find the new name, and wont compile.
Originator said...
Ok, one more odd issue I experienced on PC. When I rename a file, or rather bump up the revision number as in either 1.01 to 1.02, or using 1_01 to 1_02, the never files get saved in the directory without .spin, and then, when I try to compile it as the new name, it tells me it cannot find the new name, and wont compile.
Right, I see. It's easy to accidentally knock the .spin off the end of the filename when you change it.
I'll figure out a way around it. If you add .spin to the end of the filename it should work around it for now.
Comments
Sorry but no there isn't. Oldbitcollector has already asked for it and user defined keymapping is now very high on my todo list. So it's not a hugely long way off.
I'm trying to stabilise the feature and menu set first so I can come up with a compact, extensible and stable way of defining the keymaps in the configuration data without having to make major changes to it as the thing evolves.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
0.13 0.12 (getting ahead of myself there) is a release I actually feel quite happy with. I managed to find and squash a very longstanding endian bug in the tools I'm using to build it, and subsequently those on PPC Macs should find the font rendering greatly improved. On a Mac, Monaco still looks much nicer than the Parallax font if you don't need the unicode chars.
Lots of polish and little niggles fixed. I've tried to address every issue people have raised. If I've missed your pet peeve or bug, please yell at me.
The compiler is about 50% faster than it was. I found another major slow point with the wonders of valgrind, and thus overall since 0.06 my regression test has come down from about 29 minutes to just a little under 3. It compiles a lot quicker now (or on my 400Mhz PPC an acceptable period of time. No more coffee breaks for compiles)
Mac users can disable the editor anti-aliasing (in the ide options) if they are using a nice font. Windows and Linux users can click the little box to their hearts content, it just does not seem to do much. It was a late entry in the race and I'm still playing with it.
Im still having intermittent trouble detecting the propeller on Windows, but I've not had a great deal of time to dedicate to that recently.
Macs and Linux seem pretty rock solid.
Still have the reset on disconnect on the Mac serial terminal. I am looking into it though.
Changes in the top post as usual.
Please read the release notes (Help -> Release Notes).
I'll be updating the command line tools in the next couple of days. No real bugfixes (except the segfault in bstl from agodwin) but the compiler now goes like greased lightning.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Post Edited (BradC) : 11/10/2008 5:59:18 PM GMT
No, it's not and I apologise for not replying to you specifically. I've been giving quite a lot of thought to macros and conditional compilation but I've not yet reached a point where I have the time to sit down and dedicate some real runtime to it. Unfortunately this is a hobby for me, and like everyone else I have to put food on the table so my programming time is a little more limited that I'd otherwise like.
On top of that, anything I do really needs to be compatible with Homespun, as mpark already has #ifdef and friends in place, so I need to seriously think about how I do what I do to not fragment the community more than is absolutely required to move things forward. At the moment I'm trying to stay as Parallax compatible as I can, but I do realise that at some point we are going to have to move things along.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
With last version I not have problems to find Propeler chip
My system ... XP Sp3 Swedish
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
I'm glad it works for you.
Thanks Sapieha, I really appreciate the feedback [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
In Tools menu "Compiler Preferences" You have "Close" buton
Can You extend it to al menu's
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
Still one problem on my system
IDE recognise Prop and load it but Terminal can't comunicate with Prop
Ps. Else reset it
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Nothing is impossible, there are only different degrees of difficulty.
For every stupid question there is at least one intelligent answer.
Don't guess - ask instead.
If you don't ask you won't know.
If your gonna construct something, make it·as simple as·possible yet as versatile as posible.
Sapieha
Post Edited (Sapieha) : 11/10/2008 8:14:04 PM GMT
If you install QuicKeys or one of the QuicKeys clones, you can remap any application to use any key commands.
.
no, no apology is necessary [noparse]:)[/noparse] just wanted to make sure my request is reasonable (in terms of cost/benefit for the community)
wholeheartedly understand the limited time/effort thing
just at the moment I felt like this feature would be really useful for those trying to squeeze as much performance as possible (i.e reduce instruction count to the max)
This could make such difference as being able to run my prop SPI slave @2Mhz as opposed to current max of 1Mhz and avoid the mess of manual unrolling
Cheers
Post Edited (pems) : 11/10/2008 9:35:32 PM GMT
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
I am 1011, so be surprised!
Advertisement sponsored by dfletch:
Come and join us on the Propeller IRC channel for fast and easy help!
Channel: #propeller
Server: irc.freenode.net or freenode.net
If you don't want to bother installing an IRC client, use Mibbit. www.mibbit.com
I noticed that to, but I turned anti aliasing back on in the options an it looks great.
.
As Chuck said below, turn the anti-aliasing back on [noparse]:)[/noparse]
I did it as I've gone from Parallax font to Monaco on my Macs (I don't use unicode chars) and Monaco at 14 point looks excellent with the anti-aliasing switched off.
Yep, know about both of those. Yes I intend to fix them, although the 2 pixels of colour on the left do have me a little stumped at the moment.
Yes there is syntax highlighting in comments that span more than one line. I've not got around to implementing block group indicators yet. When I do that the multi-line comment problem will go away.
Appreciate the feedback.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Yes on windows the trick is to open the serial terminal and connect it *then* download the program to the prop and it will work fine.
I know about the problem (there are several with comms on Windows at the moment) but I've not had a chance to really debug it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Thank you very much for this IDE. It works beautifully on my MacBookPro (OSX 10.5.5) and means I no longer need to be tethered to
either the PC or Windows running inside VirtualBox to play with the Propeller. Your IDE works beautifully on all the cases I've tried.
Parallax should consider putting a link to this directly in their Propeller support materials and downloads, as this opens up the use
of the Propeller to the non-Windows community.
Thanks again
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
---
Jo
I can't copy/paste any longer without the following message:
Clipboard copy operation failed.
Ouch.. gonna research this a little and see if any outside factors have created this.
OBC
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
New to the Propeller?
Getting started with a Propeller Protoboard?
Check out: Introduction to the Proboard & Propeller Cookbook 1.4
Updates to the Cookbook are now posted to: Propeller.warrantyvoid.us
Got an SD card connected? - PropDOS
Can you show me a quick example that won't compile please?
@OBC What version of linux are you running right now. I believe there may be a bug in later versions of GTK but I need to know precisely how to reproduce it to fix it.
Cheers [noparse]:)[/noparse]
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Don't fix this on my account, I scrubbed this whole idea, but this line gives the error. PropTool compiles the same line. Remove the ~ and it works in bst.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
You doing a "Save As" with a new name?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Right, I see. It's easy to accidentally knock the .spin off the end of the filename when you change it.
I'll figure out a way around it. If you add .spin to the end of the filename it should work around it for now.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!