FTXUI/include/ftxui/component/deprecated.hpp

#ifndef FTXUI_COMPONENT_DEPRECATED_HPP
#define FTXUI_COMPONENT_DEPRECATED_HPP

#include "ftxui/component/component.hpp"

namespace ftxui {

[[deprecated("use Input with normal std::string instead.")]] Component Input(
    WideStringRef content,
    ConstStringRef placeholder,
    Ref<InputOption> option = {});
}  // namespace ftxui

#endif /* FTXUI_COMPONENT_DEPRECATED_HPP */

// Copyright 2021 Arthur Sonzogni. All rights reserved.
// Use of this source code is governed by the MIT license that can be found in
// the LICENSE file.
Prefer std::string over std::wstring. (#179) In the past, FTXUI switched from std::string to std::wstring to support fullwidth characters. The reasons was that fullwidth characters can be stored inside a single wchar_t. Then FTXUI added support for combining characters. A single glygh doesn't even fit a wchar_t. Instead, a glyph can be arbitrary large. The usage of wstring doesn't really fit the new model and have several drawbacks: 1. It doesn't simplify the implementation of FTXUI, because of combining characters. 2. It reduces drawing performance by 2x. 3. It increase Screen's memory allocation by 2x. This patch converts FTXUI to use std::string internally. It now exposes std::string based API. The std::wstring API remains, but is now deprecated. Tests and examples haven't been update to show the breakage is limited. They will be updated in a second set of patches. Bug: https://github.com/ArthurSonzogni/FTXUI/issues/153 Co-authored-by: Tushar Maheshwari <tushar27192@gmail.com> 2021-08-09 05:25:20 +08:00			`#ifndef FTXUI_COMPONENT_DEPRECATED_HPP`
			`#define FTXUI_COMPONENT_DEPRECATED_HPP`

			`#include "ftxui/component/component.hpp"`

			`namespace ftxui {`

Component decorators (#354) Add decorator variants for decorator components Add the "pipe" operator for components, similar to what was done for Elements. We are able to put something like: ``` Button(...) \| Maybe(&show_button) ``` Add decorators for: - `Maybe` - `CatchEvent` - `Renderer` Signed-off-by: Kefu Chai <tchaikov@gmail.com> Co-authored-by: ArthurSonzogni <sonzogniarthur@gmail.com> 2022-03-12 22:18:36 +08:00			`[[deprecated("use Input with normal std::string instead.")]] Component Input(`
			`WideStringRef content,`
			`ConstStringRef placeholder,`
			`Ref<InputOption> option = {});`
Prefer std::string over std::wstring. (#179) In the past, FTXUI switched from std::string to std::wstring to support fullwidth characters. The reasons was that fullwidth characters can be stored inside a single wchar_t. Then FTXUI added support for combining characters. A single glygh doesn't even fit a wchar_t. Instead, a glyph can be arbitrary large. The usage of wstring doesn't really fit the new model and have several drawbacks: 1. It doesn't simplify the implementation of FTXUI, because of combining characters. 2. It reduces drawing performance by 2x. 3. It increase Screen's memory allocation by 2x. This patch converts FTXUI to use std::string internally. It now exposes std::string based API. The std::wstring API remains, but is now deprecated. Tests and examples haven't been update to show the breakage is limited. They will be updated in a second set of patches. Bug: https://github.com/ArthurSonzogni/FTXUI/issues/153 Co-authored-by: Tushar Maheshwari <tushar27192@gmail.com> 2021-08-09 05:25:20 +08:00			`} // namespace ftxui`

			`#endif /* FTXUI_COMPONENT_DEPRECATED_HPP */`

			`// Copyright 2021 Arthur Sonzogni. All rights reserved.`
			`// Use of this source code is governed by the MIT license that can be found in`
			`// the LICENSE file.`