We have always been looking at possibility o f using Dolphin at BoonEx.com and normally we'd keep using iterations of "Trident" framework to custom-build BoonEx pages. The reason for that almost always came from time contraints - we had to rely on existing BoonEx code to build faster.
Now, however, we decided to "bridge" Dolphin 7 with Trident and finally focus on one and only platform. The work is be doen as we speak and this time around ti definitely will be just Dolphin see more everywhere.
Well the idea of using Dolphin here strikes me as a very good one & always has. It would really help to be able to root out bugs, increase speed, security etc.. It would even provide a platform by which the developers can test out new features and functions in advance of putting them in an official release. There is a huge user base here that can act as beta testers by default that way.
Does using Dolphin for Boonex.com mean we are looking at a facelift here on Unity again then too? (I'm see more assuming Unity will replicate Dolphin) (?)
Yes, it would certainly change the way BoonEx.com looks. What we are trying to do is to make default Dolphin package work for BoonEx needs. Obviously license activation won't be a default package module, but everything else would. This is a challenging task, but we have finally settled our opinion on a few "principal" aspects that should make it happen. I will start posting details very soon.
Besides the tickets is that where alot of delay time came in from releasing next versions? BoonEx working on multiple platforms at one time.
I like the idea of bridging D7 with Trident :)
Now, however, we decided to "bridge" Dolphin 7 with Trident and finally focus on one and only platform. The work is be doen as we speak and this time around ti definitely will be just Dolphin see more
Does using Dolphin for Boonex.com mean we are looking at a facelift here on Unity again then too? (I'm see more
I like the idea of bridging D7 with Trident :)