Mix image component and text component is not a solution. Because text is
not a line element in weex.
So I suggest , if richtext is poor design, maybe refactor it or create
new compatible component for it.
The old components should maintain unless new compatible component is
released, but dont add new functions to it.
For customer, their requirement is continual. For any production,
compatibility is very important, so does weex.
Once some bugs effect the requirement because of the component, the
developer using weex maybe down-hearted.
In turn more developers are more cautious about using weex or not in new
projects.
------------------------------------------------------------------
发件人：York Shen <shenyua...@gmail.com>
发送时间：2019年3月27日(星期三) 14:32
收件人：dev <dev@weex.incubator.apache.org>; wcxwave <wcxw...@aliyun.com>
主 题：Re: [DISCUSS] Deprecation of weex components.
You can mix image component and text component to simulate RichText, thought it
is not a perfect solution.
The main reason I want to deprecate RichText is its poor design, which is full
of hack and inconsistent with front-end tech.
We have a plan to rewrite the all the UI components according to W3C standards,
but no schedule yet. I’d suggest you should deprecate RichText as the time
goes, as it is no longer under maintenance except security related bugs.
Best Regards,
York Shen
申远
在 2019年3月27日，11:09，wcxwave <wcxw...@aliyun.com.INVALID> 写道：
is Richtext deprecation?
If it's ture, I want to know which component is the backup component for it?
------------------------------------------------------------------
发件人：York Shen <shenyua...@gmail.com>
发送时间：2019年3月26日(星期二) 14:50
收件人：dev <d...@weex.apache.org>
主 题：[DISCUSS] Deprecation of weex components.
Hi, there
I’d like to make some weex component as deprecation due to the following
reasons:
These components are designed and implemented in a hack way, which makes them
difficult to maintain.
As Weex is lack of active committers, we need to concentrate on more important
things, not just fix bug for the poor design.
I think we have backup component for the deprecation ones, developer could
switch to the backup component.
The code for the deprecation components still remain for a long time, but they
are not under maintenance unless there is a security bug.
The deprecation components are listed below:
Richtext <https://weex.apache.org/docs/components/richtext.html>
recycle-list <https://weex.apache.org/docs/components/recycle-list.html>
I’d like to hear your advice before I mark them as deprecation in the document.
Best Regards,
York Shen
申远
