Aloe Express undeprecated!


No more deprecations in Aloe Express:-)

Lessons learned:
Deprecated things don’t come with an undeprecate example in the help
exp.: how to to ChrB with MemoryBlock -> a little hint would have been helpful
exp.: AbbreviatedDate -> use FormatStyles -> ok, but how?
As I think, now we have three dates? Date, DateTime, Xojo.Core.Date?
Do build a class wrapper for future API changes earlier than You think.
Xojo “crash-a-lot” when things are Nil and accessed -> save-a-lot;-)
Use the forum a lot: You guys are all great people, indeed!
Calm down; very often things look worse than they are

I still do not understand how Aloe Express works; of course, I now how web sockets work internally, etc. but don’t exactly know the code and don’t want it to know.
That’s why it is an add-on.

Thanks a lot for the help while converting the source!

Is this available on github? I’m currently using Aloe Micro and seeing someone else’s migration would really help.

Sorry, I don’t use github and don’t know how to pack all the things together from the spreaded classes.

Ok, this seems to be a good reason to finally learn github commandline.

Ah, that was the problem as I remember: proxy with no available user name in my office.

I will hopefully have it available on github next week.

Tim Dietrich is d’accord with this?

Sorry… I didn’t see this response before replying to your other post. Since Tim’s original code is made public on github and the ‘fork’ feature is available, I would assume that it would be ok to fork it and modify it to make your own. Also, it doesn’t seem that he has included a license file or even a readme that would indicate that the code comes with any conditions so I’m sure he’d be ok with it.

Again, thanks for sharing!

@Kristin Green : The license is included in the Aloe Express module as note.

Also, @Jonathan Eisen has just made his repo of AE available on Github:

Sorry for the delay in responding. I’m not on the Xojo forum much these days.