![]() ![]() It's meant to be a "does-it-all" piece of software that is closer to bloatware than anything else. It's that simple.īut there's something Apple could do, and the API's for that are all there too: If I need something better than that, I usually go for InDesign and import the RTF text I typed on TextEdit. ![]() I am not looking into Mac app development anymore since I've been more into web development for the past 4 years.īut it seems pretty easy, with the Cocoa API's for text handling, to write a full blown word processor. Whether it will be there now or when it will show up? No idea. PDFKit, Web Kit, Core Image, Core Video, Core Data, Image I/O and the other dozens of "really cool stuff" I've seen, allow for an architecture of applications and, really, documents that have immersive content. (Obviously, check the facts on that as I have not the time, and it's been a while).Īnd as for OpenDoc. Apple could possible save some reverse engineering time if OO were like that. The license on the Gecko code allows you to copy code directly out of it. (I haven't checked in the project in a long time, since there are no new Mac OS X compatible releases for a while, but I'm getting the impression their making massive changes in 2.0 to allow for better "cross-GUI" work.) Still, Apple shouldn't get involved in this project.Īnother thing comes to mind. ![]() And as far as I can tell, one that isn't easily seperated from the code. Apple had to build that up and then add Safari on top. KHTML is a rendering engine, just like Gecko. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |