bad44f8fc9
This was resulting in a whole lot of rebuilding whenever a new IDL interface was added. Instead, just directly include the prototype in every C++ file which needs it. While we only really need a forward declaration in each cpp file; including the full prototype header (which itself only includes LibJS/Object.h, which is already transitively brought in by PlatformObject) - it seems like a small price to pay compared to what feels like a full rebuild of LibWeb whenever a new IDL file is added. Given all of these includes are only needed for the ::initialize method, there is probably a smart way of avoiding this problem altogether. I've considered both using some macro trickery or generating these functions somehow instead.
35 lines
881 B
C++
35 lines
881 B
C++
/*
|
|
* Copyright (c) 2023, MacDue <macdue@dueutil.tech>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <LibWeb/Bindings/Intrinsics.h>
|
|
#include <LibWeb/Bindings/SVGAnimatedNumberPrototype.h>
|
|
#include <LibWeb/SVG/SVGAnimatedNumber.h>
|
|
|
|
namespace Web::SVG {
|
|
|
|
JS_DEFINE_ALLOCATOR(SVGAnimatedNumber);
|
|
|
|
JS::NonnullGCPtr<SVGAnimatedNumber> SVGAnimatedNumber::create(JS::Realm& realm, float base_val, float anim_val)
|
|
{
|
|
return realm.heap().allocate<SVGAnimatedNumber>(realm, realm, base_val, anim_val);
|
|
}
|
|
|
|
SVGAnimatedNumber::SVGAnimatedNumber(JS::Realm& realm, float base_val, float anim_val)
|
|
: PlatformObject(realm)
|
|
, m_base_val(base_val)
|
|
, m_anim_val(anim_val)
|
|
{
|
|
}
|
|
|
|
SVGAnimatedNumber::~SVGAnimatedNumber() = default;
|
|
|
|
void SVGAnimatedNumber::initialize(JS::Realm& realm)
|
|
{
|
|
Base::initialize(realm);
|
|
WEB_SET_PROTOTYPE_FOR_INTERFACE(SVGAnimatedNumber);
|
|
}
|
|
|
|
}
|