Right, well I used GoldED a long time ago, and it was always a quality piece of software, so I decided to bite the bullet and buy it. I went to the website, but couldn't work out what to click on to actually buy it.

If anyone has actually got it, how integrated does it get with the OS4 SDK, which is where I would ideally like it.

I remember the days of old, and the excellent integration with StormC.

_________________
Simon

Comments made by me on any public fora are not representative of, or on behalf of, any company I may have, or assumed by the reader to have, any association with.

Any comments are a personal opinion, and should be accepted as such.

Quote:

Right, well I used GoldED a long time ago, and it was always a quality piece of software, so I decided to bite the bullet and buy it. I went to the website, but couldn't work out what to click on to actually buy it.

Please contact the developer, ie. in terms of clicking, click on contact and speak to me. There is no 1-click buy option. It's is a hobby project, it isn't available at any time. I apologize for the inconvenience. If the developer isn't away in Spain getting tanned, hammered or in a foul mood, he will get back to you quickly ;)

Quote:

If anyone has actually got it, how integrated does it get with the OS4 SDK, which is where I would ideally like it.

It is not integrated with the OS4 SDK. Not because I wouldn't want to integrate it but because the OS4 SDK is not made available. GoldED's C/C++ mode can still be used, with limitations. Basic syntax highlighting and such. It sucks a bit but what can I do, it's not my decision.

Quote:

I remember the days of old, and the excellent integration with StormC.

The integration was made for StormC3 in cooperation with Jochen Becher and went quite far (displaying debugger breakpoints in the editor). It also integrates with SAS/C, still my preferred compiler, with gcc 2.95.3 and gcc 3 on classic Amigas, with vbcc (for classic Amigas, WarpOS and PowerUp) and with gcc 2.95.3 and gcc 2.95.4 on MorphOS. The last five compilers are all included as contributions and installed for the user. The system is designed so that all compilers can be installed at the same time.

@dietmar
How hard would it be to integrate it into the SDK that comes with OS4? One of the main things that has been holding me back is the lack of IDE on OS4. That and lack of OpenGL support for right now.

What is the upgrade path for when the SDK is available to you(for arguements sake)? Meaning would I need to buy an upgrade to GoldEd over AIX?

Quote:

How hard would it be to integrate it into the SDK that comes with OS4?

There are several sides to integration of any SDK. A quick breakdown:

1. Configuration

Update syntax highlighting dictionaries, prototypes dictionary (for plug-in that shows prototypes for words under cursor), autocase dictionary, header lookup, the menu (include links to documentation and specific tools in the SDK, new compiler menu) etc. This is a configuration job and requires no changes to the software. Still, it needs time because the process is not automated. It'll be necessaray to go through many files manually: clib, autodocs, other headers. I suppose two days.

2. Make a compiler installation

GoldED only works with compilers that are integrated into its devkits framework (which ensures that any number of conflicting compilers can be installed on the same machine). It can not deal with an 'alien' compiler installed under gg: that has lines in user-startup. In other words, new compiler installations must be written. If the SDK's compilers are installed with an installer script, it's a quick job. If it's a binary, help is needed. Communication slows things dows. Could take a week.

3. Some tools must be adjusted. For example, the gccprefs program and the vbccprefs program might have to get new options (whatever new options the SDK's compilers have). The sdk plugin and error browser might have to be adjusted to the error format of the compilers. Communication and implementation might take a few days.

4. Installation and testing.

The installation scripts of the editor, of the C/C++ mode and of devkits must be changed and tested. I don't have an A1, testing would have to be delegated. GoldED is a package of several hundred MB, sending that around for testing and getting feedback and then sending it again would take a lot of time. A week or two.

5. Legal aspects

If the SDK's owner is informal and practical, as Amiga Inc's Gary Peak and Olaf Barthel were, it's a few emails and a gentleman's agreement. If the owner is formal, as Genesi was, you have to deal with lawyers, drafts, final revisions and signed papers in the mail. That takes months :)

Quote:

What is the upgrade path for when the SDK is available to you (for arguements sake)? Meaning would I need to buy an upgrade to GoldEd over AIX?

Frankly, I don't expect the SDK to be made available. As far as my software is concerned, the upgrade model will change (as announced): not "big" updates on CD and free updates inbetween but a small price for every update, determined by its quality. Nothing that would scare people away, rather in the range of a cup of coffee at Starbucks. I want all upgrades to be downloadable. To that end, the site has only recently been upgraded by 10 GB/month. The system is designed so that you can jump in at any time and not fear that the very next update is a costly "big" update.

GoldED working together with OS4 SDK. Now there's a product we all want. Hyperion should talk to Dietmar.

Coder

_________________
Can't get enough of me?
The Bucket Diary Blog
The Bucket Diary Twitter Account

Hi Dietmar,

Quote:

a small price for every update, determined by its quality. Nothing that would scare people away, rather in the range of a cup of coffee at Starbucks.

Well I wouldn't have anything against this scheme if I could pay for the update using a credit card. If I had to pay via bank transfer, the fees (currently about 8 EUR) would likely exceed the cost of the update.

Regards,
Trixie

_________________
The Rear Window blog

AmigaOne X5000/020 @ 2GHz / 4GB RAM / Radeon RX 560 / ESI Juli@ / AmigaOS 4.1 Final Edition
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition