I have looked all over the wiki and can't find a download option for the font. Are you supposed to be logged into the wiki to view download options? I see font info, but that's it.
Originator said...
I have looked all over the wiki and can't find a download option for the font. Are you supposed to be logged into the wiki to view download options? I see font info, but that's it.
Rsadeika said...
This is probably a very trivial observation, in the text area when I type in the small cap 'n' it looks like a small cap 'r', when I type in an 'm' it looks like an 'n'. I you type an 'i' along side of another letter, it looks like the 'i' has become part of that letter. Those are a couple of examples, I do not know if this is happening with anybody else, or if it has already been reported. My setup, Ubuntu 8.10 64 bit, on a 1200 x 800 screen laptop. I am still getting around to doing a real program, to see how it all works.
Your text is getting clipped. Which font are you using? Unfortunately the quirks in rendering the Propeller font required some changes to my editor component such that it does odd things on any font that is not strictly monospaced. Courier_10 is a usable replacement under Linux, or preferably install the propeller font from the Wiki.
I'm using a 1600x1200 screen on Ubuntu 8.04 for development.
Other than that is it running ok on 64 bit? I've been thinking about adding a 64bit build environment to my collection and compiling for it separately. If it's running ok for you with the i386 binaries I might delay that a little while.
Ok, so I've been hacking around with fonts and display attributes a little bit.
The syntax highlighter is somewhat improved under Linux and Win32 now.
I've included a hack that makes dud fonts more reliable (on all platforms). it's not perfect, and it won't and can't fix fonts that refuse to specify valid character widths, but hopefully it'll assist with some of the problems people are seeing before they have the Parallax font installed.
Mac users, I'm afraid things will remain status quo for a little while. The Parallax font does not have any BOLD attributes in it and unlike windows and Linux, the font renderer will not fake them if you ask for it. I've got some font creation tools now and I'm getting familiar with how fonts work under OSX with the ultimate goal to create a version of the Parallax font that behaves itself under OSX. In the meantime I'm afraid OSX users are stuck with using other highlighter colours to substitute for bold font. I _am_ working on it though.
I _have_ managed to squeeze another ~25% performance out of the compiler, so that is the other major change in this release.
Linux users who do use the syntax highlighter, you are going to want to upgrade [noparse]:)[/noparse] Otherwise there's not a lot in it.
Brad: The listing is beautiful ! and more than that: useful! (I hoped and asked Parallax for a listing more than a year ago). If you close the compiled listing window and re-open it, the list is gone :-(, maybe you can save it to disk
Syntax highlight works well, you may want to disable it inside comments.
Ale said...
Brad: The listing is beautiful ! and more than that: useful! (I hoped and asked Parallax for a listing more than a year ago). If you close the compiled listing window and re-open it, the list is gone :-(, maybe you can save it to disk
Yes, I'll make sure there is a save listfile option in the next release.
bstc allows you to drop a list file on the disk, but I'd not thought about saving it inside the editor itself.
Ale said...
Syntax highlight works well, you may want to disable it inside comments.
Yep, the highlighter is still very much a work in progress. Comments and block identification are next on the list. Spin block folding works, but I intend to take it down to repeat/case/if block granularity when I do the block indent indicators. Comments and Document Comments will fall out of this.
Nothing much new for Linux or Windows users, but I managed to find a workaround for the font rendering problems I've been having on MacOS... soooooo...
The Editor and highlighter have been modified to provide the same highlighting on OSX as on the other platforms. If you are used to the Parallax highlighter then this is a pretty big upgrade. If not then I wouldn't worry about it too much.
There are one or two odd font sizes that will cause stuff to mis-render. Just knock it up or down a notch and the problem goes away. I know about it but I'm not quite sure what is causing it as yet.
0038(0000) F0 A7 BC A0 | ntry mov t1,par 'get structure address
003C(0001) 10 A6 FC 80 | add t1,#4 << 2 'skip past heads and tails
.
.
.
0088(0014) 5E EC AB 68 | if_z or dira,txmask
008C(0015) 33 C6 FC A0 | mov txcode,#transmit 'initialize ping-pong multitasking
receive jmpret rxcode,txcode 'run a chunk of transmit code, then return
0090(0016) 63 BA BC 5C | eceive jmpret rxcode,txcode 'run a chunk of transmit code, then return
Ps It is mising every first letter in listing
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ 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.
Thanks Sapieha.. I know why that is..
25% increase in compiler performance at the cost of the first letter in the listing [noparse];)[/noparse]
I'll get it fixed. Sorry about that and very well spotted!
@BradC, I tried the courier_10 font, that did not correct the problem, I tried a couple of different fonts, like a Sans instead of a monospace, that did not help either. So at the moment I do not know what else todo to solve the problem, there are a lot of fonts to pick from.
I have not tried to run any real programs just yet, was trying to resolve the font problem.
Rsadeika said...
@BradC, I tried the courier_10 font, that did not correct the problem, I tried a couple of different fonts, like a Sans instead of a monospace, that did not help either. So at the moment I do not know what else todo to solve the problem, there are a lot of fonts to pick from.
I have not tried to run any real programs just yet, was trying to resolve the font problem.
OK, an over_the_top wish list that expects no response
1. Expandable(hide-able) PUB's
2. Floating popup mudule with user defined markers, that when a marker name is clicked, the screen pops the PUB to the top
There are some obvious challenges with these concepts, but these are things I am daily wishing were available on the Parallax version.
Post Edited (Originator) : 11/3/2008 8:20:52 PM GMT
This is a little nit picky.. but with the program being almost perfect (IMHO)..
When you double click to open a file, it displays with the bottom bar slid one character too far to the right.
Programs look like this until you grab the slider bar and push it back left...
ON
I/O SETTINGS
clkmode = xtal1 + pll16x
xinfreq = 6_000_000
AT
Like I said, nit picky, but reported.. [noparse]:)[/noparse]
Originator said...
OK, an over_the_top wish list that expects no response
1. Expandable(hide-able) PUB's
It has this already. Turn line numbering on and you will find a little box next to each block in the far left column. Click it and the block collapses.
There is a right click menu to expand all collapsed blocks and I'm working on a way to collapse all expanded blocks the same way.
Oldbitcollector said...
This is a little nit picky.. but with the program being almost perfect (IMHO)..
When you double click to open a file, it displays with the bottom bar slid one character too far to the right.
Programs look like this until you grab the slider bar and push it back left...
ON
I/O SETTINGS
clkmode = xtal1 + pll16x
xinfreq = 6_000_000
Appreciate that one OBC. It's one I know about but have not got around to rooting out the cause yet. It's been like that since day one.
Originator said...
That is great Brad, but what am I missing? I don't see anything like what you describe in 08 11/2
Ahh.. you don't have the syntax highlighter turned on.
Sorry, the block folder is an integral part of the syntax highlighter. You need that enabled to be able to fold the blocks.
If you are going to use the highlighter, it's worth your while to upgrade to version 0.10 also.
I've just found 2 bugs, both potentially not good.
A) Memory corruption in compiler dialog. Will cause a crash if you come across it. Extremely unlikely you'll hit it as it was really only revealed by recent changes I made in my unreleased tree.
Endless loop in Highlighter causing application to spin into infinity if it encounters a <tab>. Won't hit it if you are not dealing with files that have tabs in them.
(I hit it opening the spin interpreter.spin file)
I'll get a new release out with the fixes for these tonight when I'm back at my build system.
Brad: Would you mind telling me what control you are using for the editor or it it a home brew? If its a standard control do you know if it works in VB Express 2008 (or VB6)?
I must download your windows version and give it a try.
Cluso99 said...
Brad: Would you mind telling me what control you are using for the editor or it it a home brew? If its a standard control do you know if it works in VB Express 2008 (or VB6)?
I must download your windows version and give it a try.
It's a modified version of the synedit component in Lazarus which is based on an earlyish version of http://synedit.sourceforge.net/
Most of the smarts are in the highlighter which is written from the ground up. There are 2 patches to the lazarus synedit component I have in my local tree that I need to clean up and feed back into the project, but I'm not entirely sure they are applicable to general usage.
It certainly won't work in VB.
I'd be interested to see how fast the compiler is in windows vs the Parallax tool. I've made some considerable speed tweaks to it lately.
I know the font rendering in bst is nowhere near as clean as the way the Parallax tool renders in Windows. It's on my todo list to see if I can fix though.
heater said...
Commenting out blocks of spin or pasm with {} or {{}} does not show up in the syntax highlighting.
The compiler window will show a compiler listing if you have it open when you compile a file. I did it that way as compilation takes nearly twice as long if its generating a list file, so if the window is closed the compiler runs much quicker. It's also setup to make sure the window is clear when you open it up as it has no way of knowing the result of the previous compilation. I just leave it open in the background when I want to see what is going on.
The syntax highlighter is very much an early proof of concept / work in progress. I have not started on context sensitive parsing yet and that is what is required to support the { and {{ comments. They will come with the block group indicators when I get that far.
At the moment I seem to be running around fighting fires and squashing bugs. Hopefully after I get it settled a little I'll have some time to dedicate to finishing off the highlighter.
I've really been struggling with accurate font rendering on Linux/MacOS but I think I'm getting that to a vaguely reliable usable point now, so hopefully it all settles down a little.
The "Release Notes" in the Help menu document a bit of what is what, what works, what doesn't and why..
I had planned a bugfix only release tonight, but while I was in there I could not help adding a few extra features. I really need to stop doing that.
I was sent some code that was written on Developer Studio. That uses tabs instead of spaces and will lock up the highlighter on 0.09 & 0.10. It'll be fixed in the next release though.
There are some minor oddities in the editor when blocks are folded. See the release notes (Help -> Release Notes) for details.
I've seen some horrible font rendering on Windows with 17 point. I've put a workaround in to stop things crashing with broken font rendering, but it looks completely useless. Just knock the font up or down a point and it seems to go away.
Mac users, I can't seem to make it render the font properly under size 14 point. I'm looking into it, but if you use 14 or bigger it tends to look pretty right.
Hopefully this has squashed most of the big outstanding bugs. Originator, enjoy the block folding.
Now you can fold the whole file with one click, select the routine you want by either double clicking on it or expanding it in the left hand gutter, then unfold the whole file while the editor remains centered on where you chose initially.
OBC, I've taken care of the off by 1 when you open from the shell. It still does it though when it's recovering files after a crash.
Goto Line is (Ctrl+G) or (Cmd+G) respectively.
You can just Ctrl+G, Line Number, Enter and it will take you there, you don't need to click the GO button in the dialog.
As always, feedback warmly welcomed.
Thanks to sevs who sent me some test files written in Developer Studio so I could see what it was doing with Tabs.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ 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.
Comments
Try these.
http://propeller.wikispaces.com/Propeller+Font
http://forums.parallax.com/forums/default.aspx?f=25&m=225653&p=1
http://forums.parallax.com/forums/attach.aspx?a=22474
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Your text is getting clipped. Which font are you using? Unfortunately the quirks in rendering the Propeller font required some changes to my editor component such that it does odd things on any font that is not strictly monospaced. Courier_10 is a usable replacement under Linux, or preferably install the propeller font from the Wiki.
I'm using a 1600x1200 screen on Ubuntu 8.04 for development.
Other than that is it running ok on 64 bit? I've been thinking about adding a 64bit build environment to my collection and compiling for it separately. If it's running ok for you with the i386 binaries I might delay that a little while.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Thanks for adding the BG color too, much nicer.
The syntax highlighter is somewhat improved under Linux and Win32 now.
I've included a hack that makes dud fonts more reliable (on all platforms). it's not perfect, and it won't and can't fix fonts that refuse to specify valid character widths, but hopefully it'll assist with some of the problems people are seeing before they have the Parallax font installed.
Mac users, I'm afraid things will remain status quo for a little while. The Parallax font does not have any BOLD attributes in it and unlike windows and Linux, the font renderer will not fake them if you ask for it. I've got some font creation tools now and I'm getting familiar with how fonts work under OSX with the ultimate goal to create a version of the Parallax font that behaves itself under OSX. In the meantime I'm afraid OSX users are stuck with using other highlighter colours to substitute for bold font. I _am_ working on it though.
I _have_ managed to squeeze another ~25% performance out of the compiler, so that is the other major change in this release.
Linux users who do use the syntax highlighter, you are going to want to upgrade [noparse]:)[/noparse] Otherwise there's not a lot in it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Syntax highlight works well, you may want to disable it inside comments.
Thanks!
Yes, I'll make sure there is a save listfile option in the next release.
bstc allows you to drop a list file on the disk, but I'd not thought about saving it inside the editor itself.
Yep, the highlighter is still very much a work in progress. Comments and block identification are next on the list. Spin block folding works, but I intend to take it down to repeat/case/if block granularity when I do the block indent indicators. Comments and Document Comments will fall out of this.
Thanks for the feedback.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Nothing much new for Linux or Windows users, but I managed to find a workaround for the font rendering problems I've been having on MacOS... soooooo...
The Editor and highlighter have been modified to provide the same highlighting on OSX as on the other platforms. If you are used to the Parallax highlighter then this is a pretty big upgrade. If not then I wouldn't worry about it too much.
There are one or two odd font sizes that will cause stuff to mis-render. Just knock it up or down a notch and the problem goes away. I know about it but I'm not quite sure what is causing it as yet.
Ale, you can now save the listfile output.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Look in this listing. It mising first letter
entry mov t1,par 'get structure address
0038(0000) F0 A7 BC A0 | ntry mov t1,par 'get structure address
003C(0001) 10 A6 FC 80 | add t1,#4 << 2 'skip past heads and tails
.
.
.
0088(0014) 5E EC AB 68 | if_z or dira,txmask
008C(0015) 33 C6 FC A0 | mov txcode,#transmit 'initialize ping-pong multitasking
receive jmpret rxcode,txcode 'run a chunk of transmit code, then return
0090(0016) 63 BA BC 5C | eceive jmpret rxcode,txcode 'run a chunk of transmit code, then return
Ps It is mising every first letter in listing
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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/3/2008 3:24:04 PM GMT
25% increase in compiler performance at the cost of the first letter in the listing [noparse];)[/noparse]
I'll get it fixed. Sorry about that and very well spotted!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
I have not tried to run any real programs just yet, was trying to resolve the font problem.
Have you tried with the fixed Parallax font?
propeller.wikispaces.com/Propeller+Font
If that does not do the job then if you could send me a screenshot I'll install ubuntu-64 and see if I can reproduce it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
1. Expandable(hide-able) PUB's
2. Floating popup mudule with user defined markers, that when a marker name is clicked, the screen pops the PUB to the top
There are some obvious challenges with these concepts, but these are things I am daily wishing were available on the Parallax version.
Post Edited (Originator) : 11/3/2008 8:20:52 PM GMT
When you double click to open a file, it displays with the bottom bar slid one character too far to the right.
Programs look like this until you grab the slider bar and push it back left...
ON
I/O SETTINGS
clkmode = xtal1 + pll16x
xinfreq = 6_000_000
AT
Like I said, nit picky, but reported.. [noparse]:)[/noparse]
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
It has this already. Turn line numbering on and you will find a little box next to each block in the far left column. Click it and the block collapses.
There is a right click menu to expand all collapsed blocks and I'm working on a way to collapse all expanded blocks the same way.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Appreciate that one OBC. It's one I know about but have not got around to rooting out the cause yet. It's been like that since day one.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Ahh.. you don't have the syntax highlighter turned on.
Sorry, the block folder is an integral part of the syntax highlighter. You need that enabled to be able to fold the blocks.
If you are going to use the highlighter, it's worth your while to upgrade to version 0.10 also.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Edit: Compiles fine, I love the collapse-able blocks. What is involved in storing the state of the blocks for recall?
Thanks again.
Post Edited (Originator) : 11/4/2008 6:12:52 AM GMT
A) Memory corruption in compiler dialog. Will cause a crash if you come across it. Extremely unlikely you'll hit it as it was really only revealed by recent changes I made in my unreleased tree.
(I hit it opening the spin interpreter.spin file)
I'll get a new release out with the fixes for these tonight when I'm back at my build system.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
I must download your windows version and give it a try.
It's a modified version of the synedit component in Lazarus which is based on an earlyish version of http://synedit.sourceforge.net/
Most of the smarts are in the highlighter which is written from the ground up. There are 2 patches to the lazarus synedit component I have in my local tree that I need to clean up and feed back into the project, but I'm not entirely sure they are applicable to general usage.
It certainly won't work in VB.
I'd be interested to see how fast the compiler is in windows vs the Parallax tool. I've made some considerable speed tweaks to it lately.
I know the font rendering in bst is nowhere near as clean as the way the Parallax tool renders in Windows. It's on my todo list to see if I can fix though.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
So far all goes well but what should happen in the compiler listing window? I only get an empty white window.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
The compiler window will show a compiler listing if you have it open when you compile a file. I did it that way as compilation takes nearly twice as long if its generating a list file, so if the window is closed the compiler runs much quicker. It's also setup to make sure the window is clear when you open it up as it has no way of knowing the result of the previous compilation. I just leave it open in the background when I want to see what is going on.
The syntax highlighter is very much an early proof of concept / work in progress. I have not started on context sensitive parsing yet and that is what is required to support the { and {{ comments. They will come with the block group indicators when I get that far.
At the moment I seem to be running around fighting fires and squashing bugs. Hopefully after I get it settled a little I'll have some time to dedicate to finishing off the highlighter.
I've really been struggling with accurate font rendering on Linux/MacOS but I think I'm getting that to a vaguely reliable usable point now, so hopefully it all settles down a little.
The "Release Notes" in the Help menu document a bit of what is what, what works, what doesn't and why..
I had planned a bugfix only release tonight, but while I was in there I could not help adding a few extra features. I really need to stop doing that.
I was sent some code that was written on Developer Studio. That uses tabs instead of spaces and will lock up the highlighter on 0.09 & 0.10. It'll be fixed in the next release though.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
For me, the past is not over yet.
There are some minor oddities in the editor when blocks are folded. See the release notes (Help -> Release Notes) for details.
I've seen some horrible font rendering on Windows with 17 point. I've put a workaround in to stop things crashing with broken font rendering, but it looks completely useless. Just knock the font up or down a point and it seems to go away.
Mac users, I can't seem to make it render the font properly under size 14 point. I'm looking into it, but if you use 14 or bigger it tends to look pretty right.
Hopefully this has squashed most of the big outstanding bugs. Originator, enjoy the block folding.
Now you can fold the whole file with one click, select the routine you want by either double clicking on it or expanding it in the left hand gutter, then unfold the whole file while the editor remains centered on where you chose initially.
OBC, I've taken care of the off by 1 when you open from the shell. It still does it though when it's recovering files after a crash.
Goto Line is (Ctrl+G) or (Cmd+G) respectively.
You can just Ctrl+G, Line Number, Enter and it will take you there, you don't need to click the GO button in the dialog.
As always, feedback warmly welcomed.
Thanks to sevs who sent me some test files written in Developer Studio so I could see what it was doing with Tabs.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Pull my finger!
Awesome! Thanks for these! Your editor has inspired me to finish LOADRUNNER.
BST is fast, lite, and comfortable.. [noparse]:)[/noparse]
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
One suggestion
Add one OK buton to that
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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