I have working code written a couple of years ago using the old version of visjs (https://almende.github.io/vis/). I would like to switch to the new code base (https://visjs.org/).
My code uses Network, Timeline, Graph2D, and Dataset/Dataview.
Are there any instructions on migrating code from the old version to the new one?
Things I have found, so far:
vis.moment is now moment from moment.js (with some minor changes in default parameters)
network has moveNode (which is much nicer than the old way of updating x/y in a node).
I needed to set a scale for the timeline to get around the problem of too many grid lines.
I would be happy with something that discusses migrating from 4.21 to 5.0.
My current issue is with getting the Timeline to show up,
so a migration guide for Timeline would be most appreciated.
Related
Hi there I'm creating a inventory database system using oracle apex currently my place of employment is using apex 5.1 but are looking to upgrade to the new version (19.1) shortly after my contract ends I'm curious if anyone is aware of anything, in particular, that is going to break or is more likely to break, (ie master detail) so that it can be avoided or documented
From my experience, nothing will "break" (meaning: you won't get any ORA-xxxxx errors), but some things won't work any more (which is maybe even worse; if there was an error, you'd look at it and, possibly, fix it).
The old tabular forms were ugly and kind of difficult to work with. Interactive grid is prettier, but I hate it & try not to use it whenever possible (what do I do, then? Use Interactive report + form). If you decide to upgrade tabular forms into interactive grids, note that code you might have written probably won't work.
Yet another thing: charts. The ones I had in 5.1 simply disappeared in 18.2 (OK, you'll upgrade to 19.1, but nonetheless ...). New charts are beautiful, but it'll take some time to fix them.
Finally, trees. I've used icons which helped users to easily distinguish values that are ON (green icons) from those that are OFF (red icons). In a new version, icons aren't visible any more and everything looks just the same; I have no idea what's ON and what's OFF.
Now, a question for you: why don't you upgrade now, before you create that application? If that isn't possible, consider installing XE database, put Apex 19.1 onto it and develop the application there. When the company you work with does the upgrade, the application should be OK.
I have a game which was built on the older versions of the Kinect SDK. It doesn't seem to work on the latest Kinect SDK v1.6. I get many errors.
What are the changes that I need to make, so I can play the game using the Kinect sensor?
Several changes were made to the SDK in version 1.5, which breaks coded from older versions. The namespace has changed and how the skeleton is stored and referenced changed quite a bit. Other items changed too, and I am not aware of a complete comprehensive list.
Depending on the code you may just need to modify a few things, or really dig into the code more. Know that many of the errors you are getting are probably the same error happening multiple times. Fr example, when the skeleton is being referenced - it happens a lot, but after you fix it once you can easily fix it again and quickly.
You need to understand the latest SDK first. I suggest working through many of the examples, which do a good job of showing the basics. Then you can work through the game code and start to see how things are not referenced correctly... and fix them.
I was doing a bit research and I came across this comment.
I have been working with Sencha products since Ext2. Throughout all
these years I have been rewriting my code numerous time just to adapt
to their freaking changing coding pattern.
From the troublesome Class.superclass.method.call() to the new
me.callParent(), till the recent adoption of initialize & removal of
initComponent in ST2, I would suggest you to go for the newest release
since whatever in the past will not be reuse again. Learn the new
coding style, don't waste time on the old structure. It won't help you
much, considering our web is changing very fast and ST1 and ST2 is
pretty disjoint as well.
While 1.1 is good old solid (much like Ext), v2 is much fun to work
with with the auto loader.
I'm ok with change, but I don't feel like revising my application every 6months or so.
My question is: how often does Sencha bring out a new version? (Can be EXTJS or Touch).
I did already try to find it on the website of Sencha but I think previous versions are banned to the dark ages or something.
There isn't a public road map available but like any software that is still growing, expect newer versions to be released. With the mobile space changing at a rapid pace, the Sencha team has to address those changes and meet the needs of their customers. It shouldn't be a deterrent from using Sencha products. In fact, with the release of ST2 and many adoptions from Ext JS4, they have not only simplified their path/direction but made it easier for us developers.
A very quick google for ext js wiki.
A very quick google for sencha touch wiki.
We are in the middle of a relatively large project which uses ExtJS3 and have already invested ~4 man-years, using several plugins and we have written some plugins ourselfs. After a quick glance at ExtJS4, it seems that we would have a lot of work to do to migrate the project to ExtJS4. Are there any strong reasons to switch to ExtJS4? Currently, it seems to me that compatibility with future browsers (or the lack thereof) is the only one.
We're in similar situation and our conclusion was to wait a bit more as Ext 3 is doing it's job. We experienced many problems in our "test" migration and I would say that it's more a rewrite of the application than a migration :(. Also, our experience showed that Ext JS 4 has some performance problems, forms are a bit different, store cannot reject changes, it's bigger. There are some very good new features like the new class system, mixins, new charts, ...
We have upgraded our application to ExtJS4 without fail.We are happy to say that ExtJS4 is fast compare to ExtJS3.A new class system,mixins,plugin-free charts,focus management...etc.,. But if you want to upgrade you need to change a lot of code because class system and config options are changed.We have tested the performance of our application using ExtJS3 and ExtJS4,so as per our observation ExtJS4 is fast and it will not break.As per our observation,CSS selectors are also changed if you want to customize the component you can easily do the thing in ExtJS4.
We tried to migrate from ExtJS3 to ExtJS4 previous week. Unfortunately I must say it is like translate english to german. A lot of work. From our point of view more or less just the charting system is plus, minus - a lot of components that we use are not supported, a lot of css customization shoud be done, working code in ExtJS3 breaks easily and there is sometimes almost impossible to find an error.
Not an expert but personally I'd start new project with extjs4 but leave exiting project alone. The charting stuff is amazing in 4!
I relased version 1 in appstore that contain coredata database , in version 2 I added new fields to the database how to modify dynamically the old database , with keeping the data
I already did without versioning and don't have the old version , and the application will crash on the customer ipad
any suggestion please
take a look at the Core Data Model Versioning and Data Migration Programming Guide
I would encourage you to start using source control. XCode 4 has SVN and Git built in, you should give it a try - both are pretty easy to learn, and prepares you for when you need to have multiple people working on a project. Having your code in source control would have made this a straightforward problem to fix, you can get previous versions of any file at any point in time.
The WWDC 2011 videos have some good content on using source control effectively and efficiently as well.