IRC Log Viewer » #firebreath » 2016-03-14

IRC Nick Time (GMT-7) Message
agouaillard 14:03 hi
taxilian 14:03 hello
agouaillard 14:03 hi richard
in short
i m back
taxilian 14:03 welcome back =]
agouaillard 14:03 i have two pcs, one win7 one win10 with edge
and i will resume working on FB2
taxilian 14:03 awesome.
agouaillard 14:03 i saw that you cleaned all the cmake thingy i bumped into last year
my plan is still the same
taxilian 14:03 you'll have to refresh my memory -- it's been awhile
agouaillard 14:03 have both fvtestplugin and echotest
compile
and run
and run
with fb2
NPAPI version
for IE and safari
then document
then document
taxilian 14:03 that would be awesome
that would be awesome
agouaillard 14:03 i m leading an effort at w3c and IETF
to include that as part of the “test the web forward” effort
with support from browser vendors
so the idea is that, once stability is reached
so the idea is that, once stability is reached
it would be tested automatically by all
which would make maintenance MUCH easier ;-)
so, practically
i reinstalled everythign last week end
regenerate the FBTestPlugin
tried to cmpile
tried to cmpile
and ended up with two strange errors
which I posted on the mailing list
taxilian 14:03 ahh, yeah, I saw that.. haven't had a chance to try to repro. I've not seen them come up myself, but I haven't built trunk for a bit so it's possible a pull request broke something I suppose
agouaillard 14:03 then i expect to bump into the problem i left FB2 with last year: the onloaded varaiables are not mapped correctly anymore, which might require actually keeping in the code a map of all of them
then i expect to bump into the problem i left FB2 with last year: the onloaded varaiables are not mapped correctly anymore, which might require actually keeping in the code a map of all of them
simple question
I understand from the design that
FB:error is suppose to result in an exception
?
taxilian 14:03 I'm honestly not remembering what FB::error is; I'll have to go look at the code. that might be part of the rework to retain exception info through to the browser layer
agouaillard 14:03 FB::script_error' to 'std::exception_ptr
FB::script_error' to 'std::exception_ptr
ok
taxilian 14:03 those I recognize =]
agouaillard 14:03 I think it s a std:exception vs std::exception_ptr problem here again
(there is another one earlier)
taxilian 14:03 it's entirely possible
agouaillard 14:03 i m new to those constructs in C++
i tried to read the documentation last week end
taxilian 14:03 it was fully working, but I haven't had time to work on it in about 6 months, and a few people have submitted fixes which they said were fully tested but I haven't had time to test personally
agouaillard 14:03 ok, so
will you have some time for this, or shoudl I idg myself ?
taxilian 15:03 I can try building it myself, but I have very little time right now
agouaillard 15:03 and maybe put a CI with some test bots in place to make sure there is no regression ?
taxilian 15:03 sorry :-/
agouaillard 15:03 fair enough, I ll dig then .
cheers
taxilian 15:03 yeah, that would be good. I used to have one, but it's been down for awhile
agouaillard 15:03 no worries, I ll put my own “safety net” in place :)
taxilian 15:03 =]
building on mac now
agouaillard 15:03 yeah, i shoudl do that in parallel as well. I might be hitting an oddity of MSVC 2013
on win.
taxilian 15:03 builds on mac, btw
my machine is too bogged down right now to try windows
hmm. no it doesn't, actualy
oh, check to make sure you aren't having trouble with the unit tests
those haven't been fixed
you're right, it's not building
and it's probably actually a bug in FBTestPlugin