Ticket #56 (closed review: fixed)

Opened 1 year ago

Last modified 1 year ago

Deprecate f.memo() in favor of f.unicode(multiline=True); favor f.string() and f.bytes() over f.unicode() and f.string()/f.blob()

Reported by: mscott Assigned to: mscott
Priority: normal Milestone: Schevo 3.1a1
Component: Schevo Keywords:
Cc:

Description (Last modified by mscott)

Instead of a Memo field, the Unicode field should accept multiline=True or a similar keyword argument.

The Memo field would be deprecated to encourage the use of Unicode instead.

For discussion, should it behave like this:

  • multiline=True - does not fail if there is a newline; hint to UI to show mutiline widget
  • multiline=False - fails if there is a newline

Or should it behave like this:

  • multiline=True - OK to have newlines; hint to UI to show mutiline widget
  • multiline=False - fails if there is a newline; hint to UI to show single-line widget
  • mutliline=None (default) - never fails for lack of newline; UI typically shows single-line widget

Instead of having Unicode store unicode strings, have String store unicode strings. Deprecate Unicode.

Instead of having Blob store byte sequences, have Bytes store byte sequences. Deprecate Blob.

Change History

10/18/07 13:57:34 changed by mscott

  • owner set to mscott.
  • status changed from new to assigned.
  • type changed from discussion to implementation.

Any thoughts on the behavior of multiline on Unicode fields?

I'm leaning toward the latter.

10/18/07 16:21:46 changed by mscott

  • description changed.
  • summary changed from Deprecate f.memo() in favor of f.unicode(multiline=True) to Deprecate f.memo() in favor of f.unicode(multiline=True); favor f.string() and f.bytes() over f.unicode() and f.string()/f.blob().

10/18/07 16:32:40 changed by mscott

  • type changed from implementation to review.

ready for review

12/05/07 15:43:32 changed by mscott

  • status changed from assigned to closed.
  • resolution set to fixed.

merged at r3670.