Submitted by markbj on 2021/11/29 11:04

Care view is a very interesting function, while it does have limitations.

Recently I also like Notion very much but I think it have 2 sharp shortcomings:

  1. It's pages and database records seems to be same as IQ items, but actually in 2 separate structures: pages are in hierarchy but db records are not, pages and db records can link to each other but clumsy.
    IQ does so nicely in this point, just like ECCO Pro.
  2. I like MS OneNote's free positioning of blocks very much, it could be very useful for concept diagrams/brain storming etc.
    Notion's page layout support multiple columns and can embed databases and varied types of blocks, this is very strong but totally misses OneNote's free positioned blocks.
    IQ's dashboard grid is so nice for inter-grid compositions, and the card view is a prototype for inter-term compositions, compared with OneNote's free positioned blocks.

I would suggest to make the card view function better in below directions:

  • Create as many as needed card views for any grid
    A grid can hold hundreds of items or more, but a card view is only convenient whey the items are 10 or 20 or so.
    So it's reasonable to have multiple card views for one grid, each for a different subset of the grid's items.
    (Similarily, why not multiple calender/surface views for each grid?)
  • Support direct editting of the cards
    In a card view we can edit the cards through a popup editor or document pane, but not directly in the card, this is not convenient and intuitive, at list we shall support the direct editing of the item field in each card.
    Further more, if we can combine the form function with the cards, to view and edit a card as a form, this would be interesting.
  • Support links in card views
    If we can jump from a card to another card, even which is in a different card view of the same or a different grid, this would be fantastic.
    A link can be embedded in the item field's text, or as separate link fields in a form-like card.
  • Support embedded grids in card views
    Till now, in a card view, each card is an item. How about a card can also be an embedded grid? and some columns/cells of the embedded grid can be clickable links?
  • Merge surface function into card views
    I didn't try surface function much yet, but at least it support freely positioned items, each with sub/linked items.
    If we can merge surface function into card views, it will turn into a more unique feature?
    We can layout the items freely, with sub and linked items, filter them by top level and sub items ...

 

Suggestions