A first release of the official MorphOS SDK is immediately available to members of the MDC in the files section. Info here and here.
MorphOS SDK 1.0-pre1 Released
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
MorphOS Developer Connection??
uhhh… Don’t show this to Apple.
There is no EULA for hardware?!
🙂
R&B
Has anyone here done any programming with the SDK yet? How do you like it? What’s the MorphOS API like?
I’d also not point out the PDC to Apple either then, as the MDC is based on much the same ideas as the Phoenix Developers Consortium, aka PDC.
I work for Genesi, so I’ve had access to developing on MorphOS for a little while now. It’s API’s are the AmigaOS’s API’s for the most part, altho with a lot of improvements. Being a cloned API system, it follows the published docs, which means unpublished tricks used in some old demo programs won’t work.
I find the API nice, concise, and quite amazing for what it provides. It’s very low-overhead, and built from the ground up on the shared-library concept. I really like it.
He’s another -DC for ya: IDC. Intel Developer’s Conference. They’re just acronyms, but then again Apple’s been patenting a lot of things…
” There is no EULA for hardware?! ”
Eh, its not like you’d respect it if there was one, since you don’t respect the software EULA. Genesi’s advertising that you can Mac-On-Linux as one of its technical features.
Hi Nat,
>altho with a lot of improvements.
What are these improvements, can you list them please?
> I find the API nice, concise, and quite amazing for what it >provides. It’s very low-overhead, and built from the ground >up on the shared-library concept. I really like it.
This can be also told for the Amiga API or does the improvements you spoke about make the all difference ?
Thanks
kml
Other than some corrective measures to eliminate known bugs, there’s nothing one would see from the API’s that would be different from the old Amiga API’s.
The differences are under the hood. For good example, on MorphOS, all of it’s cloned libraries and devices are PowerPC native. AmigaOS remains 68k-bound, even the next-version remains a 68k based OS, much like the old mac OS when they moved from 68k to PPC.
Another good example is that the front-end GUI is build out of MUI, rather than being a three-tiered approach of Workbench, Intuition and MUI/ReAction. By using a single, all-encompassing API system for the front-end, MorphOS provides the potential that always lay within MUI. While, again, AmigaOS remains a half-done design, with 3-4 solutions to any given equasion.
So, I guess the best way to put it is:
MorphOS is PPC native, and provides all of the tools needed as part of the OS, rather than relying on 3rd party add-ons to deliver the core segments needed for the day-to-day operation of the OS.
But, this is just my personal viewpoint.
MorphOS API (Abox) is AmigaOS API with some changes/enhancements…
Hopefully it will change with the QBox.
Leo.
are there any api docs up there for random curious people to look at?
There are docs on the MDC page, I can ask Felix to move them into a simple “just want to look” page.
Do you want full docs, or just an overview so as to get a feeling?
@Vincent:
> ” There is no EULA for hardware?! ”
> Eh, its not like you’d respect it if there was one, since you don’t respect the software EULA. Genesi’s advertising that you can Mac-On-Linux as one of its technical features.
Vincent, I don’t see running Mac-On-Linux advertised at the Genesi site anywhere. Could you point it out? All I see are the operating systems listed here:
http://pegasosppc.com/operating_systems.php
— gary_c
gary is right, but try looking here in one package…;-)
http://uk.geocities.com/david260179/
😉
The power of the AltOS development community!
R&B
Its in the Technical Specs section of the site. You’re right I am being overly picky. Since it just advertises that you can run Mac-On-Linux in bold instead of explicitly saying you can run a MacOS on Mac-On-Linux.
http://www.pegasosppc.com/tech_specs.php
If you can give a better explanation for singling out that particular debian package and bolding it above any other debian feature by all means please do so.
Additionally, bbrv’s subsequent posting of david’s of david’s project which has no disclaimer or notice about it breaking the Apple EULA if you use Mac-On-Linux for what the programs name suggests.
I don’t really see how this can fit in with respecting EULAs, it be more than happy for you to enlighten me
>I don’t really see how this can fit in with respecting
>EULAs
A EULA is a contract. You don’t have to agree to this
contract. I think most people confuse the EULA with some
kind of law that you could break which it simply is not.
When after all the EULA leads to a valid contract then
between the customer and Apple but of course not between
Apple and some other mainboard distributor.