Greg, Do you have time to quickly summarize what text based components & containers you envision for Pivot 2.0?
Names are not so important here, I am just trying to understand the features that would be available. I suppose the most important points are whether they would be editable or not, components or containers, and support rich or plain text. For instance Label - As per Pivot 1.5.1 - Non-editable single line, plain text control (component) TextInput - As per Pivot 1.5.1 - User editable single line, plain text control (component) ... All the points you have made seem reasonable, especially given your in depth knowledge and previous work on these components. I'm all for starting simple and adding functionality (and often complexity) as and when the need arises. My immediate needs would be met with an editable plain text component, but would probably find uses for a rich text equivalent if it existed. Chris On 11 September 2010 01:10, Greg Brown <[email protected]> wrote: > > I think it depends on a few factors such as the actual code complexity > > As I mentioned earlier, the code is simply more complex than it needs to be > at the moment. Removing what I would consider to be non-essential code from > the existing rich TextArea component and related DOM classes will streamline > the codebase (i.e. reduce the overall complexity) and will most likely allow > us to create a more efficient solution for editing in the future, if we so > choose. > > > Its not clear it's a high-priority area for pivot as a project. > > > I agree that it may not be the highest priority right now. However, that > doesn't make the concept any less valuable. At least one user has already > requested such a feature, and I imagine that many developers might benefit > from it. > > >
