Propeller Tool not updated?
davidsaunders
Posts: 1,559
Realizing that attempting to save every watt is ridiculous (especially when I have more solar sourced power than I could use) as a result of a conversation on another forum. As a result I am in the process of setting up an x86 with Win32 among its operating systems.
As the only worthwhile Spin/PASM IDE I have yet found for the Propeller is the Propeller tool I am downloading it. Though I am surprised to see that it has neither been updated, nor opened. I would have expected at least some small updates to this great x86/IA32 Win32/NT assembly language application, though none to be seen.
Is there any plan to implement an open source IDE that is at least as usable as the propeller tool for Spin/PASM? Or are we going to see the Propeller Tool be lost to time, when everyone starts using features unique to other IDE's/Compilers (like preprocessors).
As the only worthwhile Spin/PASM IDE I have yet found for the Propeller is the Propeller tool I am downloading it. Though I am surprised to see that it has neither been updated, nor opened. I would have expected at least some small updates to this great x86/IA32 Win32/NT assembly language application, though none to be seen.
Is there any plan to implement an open source IDE that is at least as usable as the propeller tool for Spin/PASM? Or are we going to see the Propeller Tool be lost to time, when everyone starts using features unique to other IDE's/Compilers (like preprocessors).
Comments
Definitely NOT. I am looking for the Propeller Tool or something equally usable, not something less usable (for me).
Care to elaborate in a constructive manner what issues you're having with it? There are many users on the forum that are quite happy with that product.
I use the Propeller Tool on Windows 10 with only one little bug. Permissions in the "library" folder are all messed up, unless you run as administrator or "fix" the NTFS permissions.
What has any of this to do with saving power?
I was just surprised that the Propeller tool had not been updated, no need of it, it is written in assembly if I remember what Chip said about it correctly, and thus will never be portable across CPU's.
I just figured that by now there would have been an update, if for no other reason than to make new users of the Propeller feel a little more comfortable (as I would not curse them with the likes of the more "advanced" propeller IDEs).
No issues, it is fighter jet where I need only a pellet rifle. It makes no since to use an F14 tomcat to hunt sparrow when you need only a pellet gun.
I do not need a more generalized language IDE to do the basics, nor do I need something that tries to copy the newer IDE paradigm that I feel is poorly thought out, though unfortunately what is now taught.
Edit: Ok... and a propeller-loader... but they are not Unobtainium...
What feature does it LACK?
It is the bloat of extra unneeded features that I do not like.
Do you use a D9 CAT to dig up your onions from the garden, or a spade? A D9 CAT will do the job, though it has a lot you do not need, and is a bit wastefull of doing it.
Apart from the fact that the prop Tool is x86 only and those machines happen to be a bit more power hungry than some others.
I suggest using OpenSpin and Vim. Lean mean and fast. Also updated with some new language features.
As to the suggestion of OpenSpin and Vim that is fairly close to what I was doing on Raspbian on the Raspberry Pi. Though I have always liked the Propeller Tool.
The propeller tool is small enough for the needs at hand (especially when you look at the fact that most of the package is Propeller Objects and documentation). And it has nice color coding for the sections of code, and makes commenting in the Propeller font easy (even getting a version of the propeller font to work with ARM Linux is a hassle, then still missing characters).
Remember I am the person that does not like XFCE because it is to big for what I need. I am also the person that complains that Windows 7 takes up nearly 400MB of disk space once everything that can be stripped and is not needed is removed. And on the x86 I also complain the the Linux I use takes nearly 20MB of disk space with just the GNU tools, X, TWM, and a few basic X applications. For that matter I complain that FreeDOS 1.2 takes up nearly 8MB of disk space with everything I need (including DPMI, packet driver, modern Web Browser, a couple compilers, some games, and the utilities I use).
Sounds to me like you're the person that complains a lot
Does PropellerIDE support the different color blocks like the Propeller Tool uses?
I tried PropellerIDE a while ago but I found I was so used to seeing the colors used by the Propeller Tool that I had a hard time thinking correctly when using the unfamiliar IDE of PropellerIDE.
One thing I hear PropellerIDE has which the Propeller Tool doesn't is the ability to use as many constants as one may desire.
I'm guessing this isn't a problem for you but it's something to keep in mind in case you end up with a large program in the future.
Another advantage PropellerIDE has over the Propeller Tool is the way it uses memory. localroger mentioned the Propeller Tool has a problem with duplicate objects but BST doesn't have this issue. I'm not sure, but I seem to recall reading PropellerIDE also doesn't have a problem with duplicate objects.
These features were enough for me to try using PropellerIDE but I found I missed the colors of the Propeller Tool too much to continue using PropellerIDE. And yes, I think this is a silly reason for not using PropellerIDE but my brain was insistent I keep using the Propeller tool. Sometimes I think my brain has a mind of its own.
Turns out it is unusable.
No coloured PUB, DAT etc areas. Only black edit and search panels
No Syntax highlighting.
Hardly visible font colour.
Compilation errors give no line numbers.
Menus, tabs etc scaled horribly. I might try and get a postable screen shot later.
For some reason after a couple of edit/compile cycles of a simple Spin file I had a dozen tabs with various versions of the code in.
2. See other points.
3/4/5. Excellent. Thanks.
6. So they are. Thanks. Takes some dicking around with the far too small text box that pops up with text crammed into it.
7. Scaling is a problem on a Surface Pro which has a massively high resolution display. To be fair very many other Windows programs have a problem with this.
8. No idea.
And yet there are millions of applications that run perfectly well on Windows. Blaming the OS because it's not 'free' or because you can't tweak it does not detract from the fact that it is possible to write Windows applications that run reliably on all versions.
And yet...of all the applications I run on my Surface Pro 4 the ones that work best are designed to be cross-platform:
Chrome,
Firefox,
QtCreator,
Visual Studio Code (Based on Electron)
Gimp,
etc.
I have exactly two Windows only applications I need to use from time to time. They both display terribly on the Surface screen.
Even if one does not "blame" the OS for not being "free" or tweakable does not help the fact that those millions of Windows Applications are not portable.
My arguments against using Windows are not really based on "free" or "tweakable" alternatives or any particular technical or usability shorty comings. It's just that I think it's nuts fro the worlds computing systems to be dependent on a single supplier in what is for most a foreign country.
I never understand why people are so quick to jump to the defence of MS and the Windows world. I think MS is grown up enough to defend itself.
And clicking on another spin document in explorer opens another instance of PropellerIDE along with a copy of what I was originally working with. And then neither copy of PropellerIDE will communicate with the Propeller.
But what do you mean "Unicode". Have you accidentally thrown some UTF-8 in there or some such?
I don't think PropellerIDE ever got much testing on Linux.
There is more to it than that. There are very real issues with Windows, do to the way it is done. Win32 which evolved from a combination of Win16 and OS/2 (OS/2 was much better, even while M$ was still involved), has evolved in ways that often cause problems with Windows programs, it is the way it is. No blame here, it is just how things are.
I use ReactOS as much as possible for running Win32 applications, even though for now I have to run it in a virtual machine like VirtualBox because it chokes on my USB on all of my x86 computers (except one that does not have USB). Though ReactOS is still alpha, and it is a very usable replacement for Win32. Think about the fact that so long as it does not have any issues with your Hardware ReactOS in its early alpha state is more stable than M$ WinNT/32 implementations, and runs more software correctly, that should say something.
No blame on any here, it is just the way things evolved in Win32 land.
While I do not like Windows either, I can say that we are no longer reliant on one supplier for an OS to run Win32 software and drivers natively. Now there is ReactOS, which while still early alpha runs more Win32 software correctly than M$ Windows does.
Weird. Worked fine on my SurfacePro with Windows 10.
Problem is scaling becomes a lottery as I plug and unplug my big Samsung monitor. Things come up differently every time!
While I am not familiar with this "Surface Pro" that you speak of, I assume by context it is some kind of laptop.
As such would not it make better sense to just use a desktop computer, and reasonable monitor?
Need a smiley on that.
The Surface Pro is more like a tablet. It weighs almost nothing and it goes with me everywhere. A traditional laptop could never do that.
But it's actually a full up x86 machine that runs Win 10 out of the box.
It's faster than any old PC I have in the house. Or office for that matter.
At home the Surface is connected to my big Samsung monitor and I commune with it via a good old "clunketty clunk" keyboard and mouse.
It is basically, the best computer I ever owned.
Only problem is the Win 10 weirdness.
But as it turns out MS has been going out of their way to provide the open source VS Code IDE, the Linux run time for Windows etc...
Sometimes I forget this is not my old Linux running PC !
Check this everybody: Heater is commending an MS product!
How weird can life get?
That extra work is why a lot of Windows applications have font sizing or layout issues when scaling isn't at 100%.
Windows...
...that may explain the vast amounts of empty lines trailing your posts now... :-Þ
Edit: Or do you hide code in "whitespace" in those trailing lines?