Conversation
- CoffeeScript isn't supported now
@rdpanek how about official 2.0 ? https://github.com/ariya/phantomjs/tree/2.0 edit: powned !!! Yata phantomjs 2 is alive ! <3 |
@@ -1498,8 +1498,9 @@ Casper.prototype.resourceExists = function resourceExists(test) { | |||
break; | |||
case "function": | |||
testFn = test; | |||
if (phantom.casperEngine !== "slimerjs") | |||
testFn.name = "_testResourceExists_Function"; | |||
// if (phantom.casperEngine !== "slimerjs") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need this to work, what is the issue with slimerjs at this point ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this point was problem with bug in Phantom, not Slimer. The code is not removed, because I need your opinion.
After this edit, test passed in both engines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 , CasperJS will be the first and only tool to support triffleJS, phantomJS (1&2) and slimerJS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🌈
@n1k0 do we need to keep the "coffee support" ? I never see anyone contribute to this files. |
I have problem with build officialy branch 2.0, I work on it. |
@mickaelandrieu we love of coffee - it's very useful, but I understand the reason ariya/phantomjs#12410 |
👍 for support phantomjs 2.0 in casperjs |
👍 for subj |
Problem is backward compatibility. If it was just me, I'd discard its support, but we need to avoid breaking existing usage. |
+1 |
@n1k0 you are right, but can we plan the next "next" release will drop coffee support ? The easy way will be to release 1.1 without this pull request and then a 1.2 with phantomjs 2 support. And finally, deprecate 1.0 (the legacy branch will be at least the 1.1). What do you think ? @rdpanek can you rebase master branch please, and your tests will pass 👍 |
@mickaelandrieu I tried rebase my changes on casperjs/master (88c59f8)
|
👍 |
👍 I can't wait to see this happen! |
@mickaelandrieu sorry, maybe I not understand, but what now? waiting for the milestone, or even on me? |
@rdpanek I guess casperjs.exe has to be fixed too? since build failed due to tests for .NET not able to run? Or it is always expected? |
@ohenak I don't know, because, I haven't windows environment. so I do not know the status of |
Backward compatibility unless you release it as a 2.0.0 branch and drop the support of Phantom 1 as well. |
@oncletom 👍 this may be the best solution. |
Ok, this will would be merged right after releasing |
I prepared docker images with functional versions of casperjs and phantomjs2.0
|
@n1k0 can I create 2.0 branch? |
👍 |
2 similar comments
👍 |
👍 |
@xescoder do someone at Yandex actualy use CasperJS ? o_O |
👍 |
2 similar comments
👍 |
👍 |
👍 from yandex) |
👍 |
👍 |
ping @n1k0 can we consider that phantomjs 2 and (so on) coffee support discard is the start of CasperJS 2 ? |
👍 |
1 similar comment
👍 |
+1 for keeping the CoffeeScript support. |
@mitar we can't because phantomjs2 has dropped CoffeeScript support. |
I can contribute updated install docs if this would be helpful? See stack overflow answer by pilavdzice for the state of installing on windows: +1 to remove coffeescript dependency - those who love coffeescript can get the latest version themselves and use that, but it should be optional, having more dependencies is a disadvantage and makes installation more of a barrier to folks who want to just simply start to use casperjs for something simple. This is a very useful tool because it makes things simpler. Phantomjs folks are smart too and did not think it was worth it to have more dependence, so I think it would be good to follow that example. Can we support coffescript without making it a required dependency? |
Hey. Maybe it's time to merge this PR? ;) |
Perhaps this PR should be made against the |
I didn't see any progress for a long time. This makes me sad. |
@mickaelandrieu it exists on mac os x, and there is no rocket science in build from source ;) It's about ~15-30 minutes :) I'll wait.. |
So while you seem quite comfortable doing this, thanks for sending a PR with the travis.yml file tweaked so we can build Phantom2 there and run the unit test suite. Thanks again, we truly appreciate. |
Any update on this branch? I'd love to be able to use the window.performance feature in Phantom2.0 with casperjs |
PhantomJS 2.0 (non-develop), branch: master, latest revision (a2912c216d06df4d8b51f12ad4082a48c5fc7ba6)
this is very small victory ;-)
Bud, problem is with Phantomjs. For fully support you must cherry-picked these revision from my repository:
https://github.com/rdpanek/phantomjs/commit/c8abe25ce09bfdac995ef9970efe582ad9a79ee5
This is heavy for production use, but please to code review.
Next steps: