I was wondering, how often does DHTMLX offer a new version and how hard do you find it to upgrade your applications to the new version. This is namely a critical part in my research, but I cant seem to find any problems with updates. This question is just to make sure that my findings are correct.
Please suffice with: version number, DHTMLX component.
I work for DHTMLX. During the past 3 years we released one major update per year. Currently we're preparing the next version which we hope will be available in beta till the end of April 2012. We try to make the new releases backwards compatible and provide the upgrade path to the latest release (like here).
I've used many controls from the dhtmlxsuite in our app for the past 5 yrs. They are pretty good at making things backwards compatible, but not always. When going from v3 to v4 just a few months ago, there was quite a lot I had to do get my code back up and running. Also there dropped a few features that were supported in v3, this is not so good in my opinion. But overall, I really like the dhtmlx controls, they are an integral part of our product which now is used all over the world by thousands of users (http://www.ecosys.net/ecosys-epc/).
Related
I have to upgrade my store, because my server won't support the PHP version required for PS 1.6 anymore.
From my research so far it looks as if PS 1.7 might as well be a completely different ecommerce platform when it comes to themes.
What's my best bet to convert my current, custom PS 1.6 theme and make it compatible with PS 1.7?
I don't wanna have to code the whole thing from scratch. I wanna be able to get at least 80 or 90% of the way there, and then fix the remaining glitches.
How can I make it so that the upgrade from PS 1.6 to 1.7 won't cost me several months of development work?
Edit:
The workaround solution is to use ThirtyBees. Details in my own answer below.
As this question was posted on Prestahop Forum as well I'll add here my reply there for future similar questions.
There is no conversion from a 1.6+ to a 1.7 theme or from 1.6+ to 1.7+ modules.
You need new theme and modules and that's it.
All you can upgrade are the Prestashop files and the database.
my server won't support the PHP version required for PS 1.6
What's my best bet to convert my current, custom PS 1.6 theme
I don't wanna have to code the whole thing from scratch. I wanna be
able to get at least 80 or 90% of the way there, and then fix the
remaining glitches.
How can I make it so that the upgrade won't cost me
several months of development work?
The best solution for this, really, is to USE THIRTYBEES
ThirtyBees is a Prestashop fork, it was forked after 1.6, and is it's own platform.
The team over at Prestashop is making some massive changes to the Prestashop core, which removes lots of documented functionality. And as they slowly transition over, it's probably better to not rely on the architecture, if you're not able to constantly implement upgrades and changes.
Reference:
https://build.prestashop.com/news/prestashop-in-2019-and-beyond-part-2-pain-points/
https://thirtybees.com/
After trying to adapt my store to PS 1.7, which took 2 weeks and I hit roadblock after roadblock, I switched to Thirtybees. It took me 1 day to make the same progress that it took me 2 weeks on PS. I can see myself being done with this upgrade progress soon, and I can soon focus on more crucial business activities again.
I have developed bot application using Microsoft bot framework V4 preview(4.0.1 Preview)
Now i want to migrate to new stable version (4.0.8)
Can anyone tell me what are the breaking changes and how to fix those..
The downvotes are probably because this is a very broad question, as the framework went through some pretty significant changes from Preview to Stable. For example, if I'm not mistaken, what you call DialogContainer is probably ComponentDialog now. No one's going to be able to say what the breaking changes are, because they broke in different places for different bots, depending on the the bot's code. If you attempt to upgrade to 4.0.8 and run into errors, you can post those errors and get better assistance in solving each one.
I am aware that XSQL is not supported anymore by Oracle (i.e. there is no release since 2004 or 2006). In other words, Oracle stopped supporting the XSQL many years back.
XDK or XSQL Link
However, I couldn't see any official page confirming the same. Could you please point me to the correct URL where I can get some information?
Some of my applications were written using XSQL. We would like to upgrade it. However, we are not sure whether it has latest version or need to look for alternate technologies.
Kindly suggest alternate technologies to replace XSQL pages with some minimum changes. We don't want to rewrite all the functionalities again from scratch due to timeline or budget constraints.
Newb here learning rails... any advice/comparison of community engine v. social stream? I'll be writing a dating site, so especially if either lends themselves to that development I'd appreciate the advice.
I have tried CommunityEngine in the old days. Currently to use it with rails3, you will have to use a specific branch mainly updated by the community to make it stable. i'm not sure if that rails3 branch is production ready yet.
I don't know community engine, but have been looking at social stream and it looks very well put together.
We upgraded social stream to a mobile platform by exposing api end points - it took a couple of months. We built separate controllers for each call rather than modifying the core classes. The platform is now flexible enough to cater for any use case and we can hook in to updates on the trunk. It's really well thought architecture and has had iterations of refactoring. (I think the webviews / javascript is a bit of a mess though)
I suggest you have a look at this - it took my tech lead a couple of weeks to be comfortable with this.
https://github.com/ging/social_stream/wiki/Social-Stream-Base-database-schema
WRT communityengine - I abandoned this over 4 years ago.
https://github.com/jdp-global/communityengine/commit/31f9b267706157a63bfc103a290bd6e3d874066a
Any platform you choose needs to have a focus on APIs / web services.
As the question states, I am preparing to deploy my first couple modules on the Magento Connect store and want to make sure I am targeting the best versions. Testing on 1.3 is proving to be a bit of a pain, and if only a few people use that version I would rather spend the time making the modules better!
Google hasn't helped as yet, though I think the keywords I use are getting picked up as other more specific technical questions (Google Base, for example).
Does this information exist? What about your personal experience? For me, I have only encountered installations below 1.5 Community (1.10 Enterprise) for upgrade projects. I haven't personally encountered a client that is on 1.4 and plans to stay on 1.4.
Thanks!
Tim
There are a signification amount of people who have older versions and wont upgrade because of the complexity and the amount of modification they have done to their stores.
Most people right now who are on community version seem to be on 1.5 or 1.6, but if you want to test older versions just download from the archive install locally and see if it works for the older versions.
Here is a link to the downloadable versions of magento, in case you decide to test on those older versions:
http://www.magentocommerce.com/download - click released archived tab at the top