Skip to main content
Known Participant
July 18, 2010
Question

TLF 2.0: feature requests

  • July 18, 2010
  • 1 reply
  • 1393 views

I am not sure if you are accepting feature requests for TLF 2.0, but in the case you are maybe it's a good idea to dedicate a thread to this?

I know lists and floats are already being under development, I hope you'll consider these too:

  • straddle heads (column spanning)
  • drop caps
  • column balancing
  • paging (columns fill page, when page is full a new page is composed on which a new column starts, benefits: user no longer has to scroll up and down per column but moves simply to next page. Example Times Reader 2.0)
  • nested (group of) inline elements
  • background & border properties per CSS3 specs (at least for (inline-)block type elements)
  • box padding
  • custom images for the list marker as per CSS3 specs
  • tables


  • split TLF SWZ lib into three libs: one containing the render code, one for the select code and one with all edit stuff.
  • make TLF 2.0 an excellent performer on any platform including smart phones.
  • stay away from final classes (after all it's a framework)
  • don't declare variables of a type of a sub class but of the super class so that when we need to override the super class we won't get stuck because the framework is expecting an instance of the TLF sub class.
  • if a function is protected make sure that it doens't depend on private properties or functions whenever possible (just make those properties also protected instead of private).

Thanks.

This topic has been closed for replies.

1 reply

bvlAuthor
Known Participant
July 20, 2010

@TLF Team, regarding my wish list above:

  1. Is my wish list very different than yours for 2.0?
  2. Is my list to ambiguous for 2.0? If so what are the things most likely won't get implemented (at least not in 2.0).
  3. Are you still considering new feature requests?
  4. Is this the right place (and moment) to discuss new features/requests?
Adobe Employee
July 21, 2010

This is a great place to put feature requests - we're always open to requests - no guarantees we'll act on them though.

I can respond to a copule of the requests.

tables are for sure not part of 2.0

originally TLF was split into three libraries but clients found it difficult to manage loading and unloading the swzs so we ended up merging it.

Sorry for the delay in responding.  It was a long list and we haven't had time to organize any response.

Richard

bvlAuthor
Known Participant
July 21, 2010

> originally TLF was split into three libraries but clients found it difficult to manage loading and unloading the swzs

Why not load the three libraries by default - just like the single library now - but give a bit more skilled, user experience concerned, developer the option to load only the actually used libraries on demand?

I would love to hear how you and the fellow forum participants think about this and the other things I listed, or things they would want to add.

- Benny