Quote:

Effectively it’s just mixing objc and c++ code. For instance having a std::list member in a objc class instance or using object references as arguments to objc methods (weird shit that can easily go very wrong;) This is mostly due to the fact that the email engine is written in c++ so I needed a way to use c++ shared pointers in a primarily objc source.

Btw excluding the ported vmime library and Odyssey changes Iris is already over 30k lines of code... Filtering should be closed tonight and then I’ll be moving towards local storage with an smtp out manager being the first to make use of this for a local Outgoing folder.

[ Edited by jacadcaps 19.02.2018 - 15:21 ]

The ObjC runtime comes with a bunch of classes including collections like lists (NSArray), dictionaries (NSDictionary), etc.
Also string (NSString) and number (NSNumber) classes, so that mixing with C++ is actually only necessary when you have a C++ library you want to use.


Manfred

Quote:

Jadacaps said that the email engine he is using is written in C++ (not just a library), but most of what he has written is done in ObjC, which is why Iris is written in both.

@Jadacaps,
is part of the reason MorphOS3.10 is taking so long because it has so many added features, or is it more due to the replacement of the code removed, from the one team member who left the MorphOS Dev. Team, and took his code with him?

Also, is there anything that can be done to prevent such a problem from happening again? Could all the code within MorphOS3.9 and earlier contributed by the departing team member have been purchased by the team, or the community and donated back to the team, or a combination of both? Or was the team member who left angry and unwilling to part with his code at any price? I haven't researched the individual team member who decided to leave and take his code with him, so I have no idea why he left, or if there was any conflict that caused him to leave on unpleasant terms, but I hope the team can come to some kind of agreement with each member, to prevent a similar problem from happening in the future.

Edit: Manfred surely understands all of this far better than I do, so I probably just misunderstood his comment.

[ Edited by amigadave 19.02.2018 - 16:07 ]

Dave, the release notes for 3.10 will answer many of your questions. It is coming...

Quote:

At which stage is the Objective-C runtime implementation?
Is it Objective-C 2.0 (with properties, etc.)? With garbage-collection, or manual memory management?


Manfred

Quote:

Wasn't GC replaced with ARC years ago?

Quote:

Yes, Apple's runtime. But that's based on LLVM-Clang.
I doubt LLVM-Clang will be available in MorphOS, but who knows.
The GCC implementation of the compiler is a little bit abandoned. Before Clang Apple had it's own version of GCC.

I'm assuming the MorphOS implementation is a GNUStep port, but well, maybe not.
http://wiki.gnustep.org/index.php/ObjC2_FAQ



Manfred

Quote:

..interesting that you think so... ;)


- CISC

Quote:

Well, what does that tell us. :)
Maybe we'll be happily surprised. :)

> I'm assuming the MorphOS implementation is a GNUStep port

It has been so far at least:
http://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=11539&forum=12&start=7

Quote:

It's 2.0 but with no GC (yuck) or ARC (sadly).

Quote:
OK, that's fine. Manual memory management in Objective-C isn't that bad. And there is also autorelease pool.
As for ARC, yeah, would be nice.
But it's not useful for all cases. In a larger project with a C++ backend library I'm having a lot of trouble with ARC where it does release C++ backend objects too early and such.


Manfred

Decided to take a breath before tackling local storage, partly due to the increased load at work. Tweaking little things right now, like adding CC/BCC into the email writer view. Or making email addresses in the email viewer clickable. That means I've had to add ARexx / OpenURL handling to Iris since the only way the embedded OWB can tell me that someone's clicked on an email is by handling a href with a mailto address and that means delegating this to OpenURL...

Gearing towards beta22 - mostly working on local storage related internals, like saving and loading messages. For now this should let me manage a queue of outgoing mail.

Hopefully beta23 will be the first public one, the ETA is about the time of MorphOS 3.11 release :)

By the way, did I mention the app has no busy mouse pointer?

Quote:

OMG!

"MorphOS 3.11"

Quote:

2 years or what?

Quote:

Odd number -> bugfix release

Could be anything from a few days to months after 3.10 (and no I'm not commenting on when that will be).....

Quote:

Too soon (for that to be a good joke).

Quote:

MorphOS for workgroups?

Now that 3.10 is out I'll be working towards the 1st public release. ETA: couple of days.

Cool !

PS : SDL 2 one day ?.... i have a lot of games waiting to port....

Good luck for Iris and many thanks for all your work.

BeWorld

Quote:

Wow!

Looking forward to this!

This is great news. I am looking forward to trying Iris out!

Looking forward to trying it out. :)

Iris beta 22 is now available at tunkki

Now this is all in the README, but let me re-iterate: this is a BETA release. I take no responsibility for whatever happens to your mailbox. If you're uncertain / don't want to take the risk: do NOT download this.

I will be releasing those betas once in a while. Probably every 2nd or 3rd closed beta release will be made public.

What works:

IMAP, SSL, email autoconfiguration, OAuth2 (for gmail and outlook.com)
POP3 to some extent (slow)
Browsing email folders, reading emails in a HTML view
Saving attachments, viewing image attachments
Sending HTML emails, with attachments
Multiple accounts
Encryption of passwords & keys via cryptostorage.library

Does not work:

There's no settings. No really, they're there, there's just no UI for them. Settings
will happen at the very end, sorry :)
There's no local storage (other than headers)
There's no outgoing folder - if there's an error when you're writing an email,
the email is lost.
Iris on MorphOS 3.9

Feature requests and stuff:
Feel free to ask in this thread, but don't expect things to happen quickly. I have an internal
roadmap and many systems depend on each other - I cannot just hop over some things :)
For instance some stuff can now be painfully slow because the systems that are not yet
online will take care of this later (like the local storage will make loading emails
pretty fast).

Installation and usage:
Extract files. Make sure OpenURL is set up for OWB 1.24. Make sure OWB defaults to JS enabled if you're using gmail or outlook.com. Make sure OpenURL is set up for Iris (notes on that are in the README file).