--- title: Migrating from Vaadin 6 order: 12 layout: page --- [[gwt.vaadin-6-migration]] = Migrating from Vaadin 6 ((("Vaadin 6 Migration", "add-ons", id="term.gwt.vaadin-6-migration", range="startofrange"))) The client-side architecture was redesigned almost entirely in Vaadin 7. In Vaadin 6, state synchronization was done explicitly by serializing and deserializing the state on the server- and client-side. In Vaadin 7, the serialization is handled automatically by the framework using state objects. In Vaadin 6, a server-side component serialized its state to the client-side using the [interfacename]#Paintable# interface in the client-side and deserialized the state through the [interfacename]#VariableOwner# interface. In Vaadin 7, these are done through the [interfacename]#ClientConnector# interface. On the client-side, a widget deserialized its state through the [interfacename]#Paintable# interface and sent state changes through the [interfacename]#ApplicationConnection# object. In Vaadin 7, these are replaced with the [interfacename]#ServerConnector#. In addition to state synchronization, Vaadin 7 has an RPC mechanism that can be used for communicating events. They are especially useful for events that are not associated with a state change, such as a button click. The framework ensures that the connector hierarchy and states are up-to-date when listeners are called. [[gwt.vaadin-6-migration.quick]] == Quick (and Dirty) Migration Vaadin 7 has a compatibility layer that allows quick conversion of a widget. . Create a connector class, such as [classname]#MyConnector#, that extends [classname]#LegacyConnector#. Implement the [methodname]#getWidget()# method. . Move the [literal]#++@ClientWidget(MyWidget.class)++# from the server-side component, say [classname]#MyComponent#, to the [classname]#MyConnector# class and make it [literal]#++@Connect(MyComponent.class)++#. . Have the server-side component implement the LegacyComponent interface to enable compatibility handling. . Remove any calls to [literal]#++super.paintContent()++# . Update any imports on the client-side (((range="endofrange", startref="term.gwt.vaadin-6-migration"))) hares-parameter-better-distinction Nextcloud server, a safe home for all your data: https://github.com/nextcloud/serverwww-data
aboutsummaryrefslogtreecommitdiffstats
path: root/lib/public/DataCollector/AbstractDataCollector.php
blob: ffb3cbe7b7930ac874263543e6c9c9625eeda212 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
<?php

declare(strict_types=1);
/**
 * SPDX-FileCopyrightText: 2022 Nextcloud GmbH and Nextcloud contributors
 * SPDX-License-Identifier: AGPL-3.0-or-later
 */

namespace OCP\DataCollector;

/**
 * Children of this class must store the collected data in
 * the data property.
 *
 * @author Fabien Potencier <fabien@symfony.com>
 * @author Bernhard Schussek <bschussek@symfony.com>
 * @author Carl Schwan <carl@carlschwan.eu>
 * @since 24.0.0
 */
abstract class AbstractDataCollector implements IDataCollector, \JsonSerializable {
	/** @var array */
	protected $data = [];

	/**
	 * @since 24.0.0
	 */
	public function getName(): string {
		return static::class;
	}

	/**
	 * Reset the state of the profiler. By default it only empties the
	 * $this->data contents, but you can override this method to do
	 * additional cleaning.
	 * @since 24.0.0
	 */
	public function reset(): void {
		$this->data = [];
	}

	/**
	 * @since 24.0.0
	 */
	public function __sleep(): array {
		return ['data'];
	}

	/**
	 * @internal to prevent implementing \Serializable
	 * @since 24.0.0
	 */
	final protected function serialize() {
	}

	/**
	 * @internal to prevent implementing \Serializable
	 * @since 24.0.0
	 */
	final protected function unserialize(string $data) {
	}

	/**
	 * @since 24.0.0
	 */
	#[\ReturnTypeWillChange]
	public function jsonSerialize() {
		return $this->data;
	}
}