At the moment the HWA version is still a beta version and there are many changes in the source code, we don't want to mess up the normal version of MMF2, it's a little risky to merge both source codes, even after the release version will be validated, so we might keep it as a different EXE file even after the release version will have been validated, just in case of... I'm not sure yet...
That's really not a bad idea Yves. Having things, especially when things are new or it just makes more sense, to have the set up in a modular fashion.
That does mean, however, that HWA won't make it past #249
I think in terms of practicality, people are not going to actually use HWA on serious projects until it *is* integrated/finalized. And thats something that can't be done until it is assuredly bugproof, since creating incompatibilities would be a terrible thing. So just being cautious and giving it all the time it needs instead of rushing it out is always the best chocie.
That depends on what you mean, since that's a rather vague statement.Originally Posted by MechaBowser
It appears that you mean that HWA will not last longer then one build? That's rather bold to say, especially since you have no hand in the development of MMF.
If they keep the source codes spereate for MMF2 standard and MMF2 HWA, it means that when MMF2 standard is upgraded, MMF2 HWA is not.
Oh yeah btw, HWA doesn't support text underline for some odd reason.
Is it possible that we could get some information on what extensions have been optimized, which will not run, etc? I mean if it doesn't take much time, like if you keep a "TODO" list somewhere while you are working.
It would be very helpful for developers because it lets us know which limitations we might be able to overcome with future versions, so we can put up with them for now. For example, the project I'm working on essentially *needs* the Background Image Object, which currently does not work. But if it will in the next build, I could keep all that code and just not use it yet, instead of rewriting the entire program to use different methods.
>.> or at the very least, will the BIO see functionality in 250?
The Background Image object seems to work with the new version, however it's not optimized, so it's probably slow. It can be optimized, I'll try to do it or I'll explain Greyhill what he can do to optimize it.
I'll check all the objects.
EDIT: removed, out of topic.
Posting Permissions
Reply With Quote