How is the upgrade from version 4 -> 5 compared to 3 -> 4?
Is it much bigger or same effort?
Thanks
So far, for my projects, migrating from Phalcon 4 to Phalcon 5.0.0RC2 has been SIGNIFICANTLY smaller than any previous upgrade. Of course I'm not using the full weight of Phalcon. But the lift for two of my projects (out of four that I manage) has been less than one page of work and dealt mostly with changing some Phalcon names and such. I posted a list of these in the Phalcon Discord general chat.
Related
Hi I have wanted to learn Scrapy and use it to scrape dynamic data off of webpages, and use it in a website backend.
When I went to the official docs, I go to know that V.2.0 just came out.
Given that I'm new to scrappy, and plan to develop an autonomous hosted application, I was wondering whether I should choose v 1.8 over v 2.0 because bugs would've been worked out better and there'll be more tutorials etc. But on the other hand, I'll end up learning 2.0 anyway in the future, so maybe I should start with 2.0 itself.
So I have two questions:
Are there any major changes from v1.8 to v.2.0 (I am aware that there are release notes that accompany each version, but the only thing that I can really understand is that Python 2 support was removed; everything else uses terminology that I don't understand.)
I'd be grateful for your advice on which one I should opt for.
I have worked with Selenium & BeatifulSoup4 on 1 project before hand, which involved scraping stock price and relative strength index, and using that as a part of Flask backed web app.
Always use the latest Scrapy release for a new project, unless you cannot for some reason.
There are no major changes in how Scrapy works between 1.8 and 2.0; upgrading from 1.8 to 2.0 should be as easy as upgrading from 1.7 to 1.8.
i face some conflict using bootstrap 3 and liferay framework for example the navbar class stop in the framework when we put the main bootstrap style .
I need to limit scope of bootstrap using unique class on body
any help
Liferay 6.2, out of the box, uses bootstrap 2.3 (see the reason behind this) and conflicts with bootstrap 3 are (kind of) expected.
In order to get started creating a bs-2.3 theme, you might want to check Juan Gonzalez's blog (released today, just in time). In case you insist on integrating bootstrap 3 with Liferay 6.2, you'll have to do a lot more work than with 2.3. To "face some conflict" is not quite a sufficient explanation for whatever you're experiencing. And if bs3-integration would be as easy as mitigating some conflict you face, trust me, it would have long been done.
We know all that JGraph is a very powerful graphic library and now we are in version 6 (JGraphx).
Me I have an application (by the way I am newbye in JGraph) coded in JGraph 5 and I want to migrate it to Graphx.
Is there any tut to know what is the main differences between these two versions?
That migration, is it easy to do (in general)?
JGraph (the last version of which was version 5) and JGraphX (which was originally going to be called JGraph 6) are completely different code-bases. JGraphX was a complete rewrite from scratch, which is why we made the naming change to avoid the idea you could upgrade from 5 to 6.
So no, there is no migration route, you'd need to re-write your part of the application that interfaces with JGraph(X).
I'm currently converting a fairly large Rails 2 app to Rails 3. The app uses activemessaging in its plugin form. It's used with Amazon SQS primarily for file uploads, among a few other things. I have the all the queues I use defined in messaging.rb and there are existing processors to handle messages. In the Rails 3 version I'm switching over to the activemesssaging gem, version 0.9.0. Aside from getting rid of the old plugin version is there much else I need to do to my existing messaging.rb and processors? Also right now I manually start the poller script, is that the same? I can't seem to find much info about Rails 3 and activemessaging so if anyone can give me the basic steps of what I need to do it would be much appreciated. Thanks.
I don't remember there being a big difference with using the gem - I did not change the way messaging.rb or broker.yml are loaded, and you still have to start the poller yourself.
In general there is not a big difference with Rails 3, which is why you aren't seeing much about it.
I recently inherited a Rails 2.3 application that I'm now trying to upgrade to Rails 3. Cache-money is an integral part of the application so I want to make sure we have the same functionality in place when we go to Rails 3. However, my research on the subject has shown that cache-money is not compatible with Rails 3 (due to the use of unsupported AR methods :find_every and :find_from_ids).
I've seen a couple of comments and blogs mention that implementing the type of write through caching with Rails 3 that cache-money provided should be a trivial task. Any ideas on how to approach implementing write through caching with Rails 3?
Last week I launched a new write-through-cache gem for Rails 3, see
https://github.com/orslumen/record-cache.
The reason I built it, is because we were using cache money in a Rails 2.3 project and recently migrated to Rails 3. So chances are, it will also serve you well.
Writing your own write-though caching in Rails 3 does not sound like a trivial task to me. If you do find a trivial way, please be sure to copy me in on that.