Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STRUCTURE - TABLE or any other context #3661

Open
DingBEN opened this issue Feb 2, 2020 · 0 comments
Open

STRUCTURE - TABLE or any other context #3661

DingBEN opened this issue Feb 2, 2020 · 0 comments

Comments

@DingBEN
Copy link

@DingBEN DingBEN commented Feb 2, 2020

Details

not clean not clean... KLUGY - PAY ATTENTION, SIMPLIFY YOUR WORKLOAD


The hardest thing a programmer faces is to abandon a streak to someone else's suggestions especially when it addresses broad changes in approach.
The best suggestion I may offer is

  • that you found a way to implement what I suggest separately,
  • basically leaving what you have going status quo, and apply fixes and updates as usual
  • but add a big YELLOW button with intellisense that states "Alternative SQLiteStudio app design, test it, comment if you like it or not".
  • when one presses the button, it brings up config
    -- @ Standard SQLiteStudio
    -- . Alternative SQLiteStudio (User should spend enough time on this version before criticizing)
    -- . when I click the yellow button, do not bring me here, just toggle to the other side

We have a table that lists the columns structure...
yet some columns(like size) are buried in a sub dialog

  • put all columns of definition in the row, no 2 ways yet to think of something, to remember and to navigate - match the way one navigates thru a table... CONSISTENT, intuitive, nothing to learn or trip on

  • so, we right-click on a cell to address that context, CLONK nothing
    we must learn that the convention is not respected, so we have to double-click or double right-click
    and when we make it, we are presented with a HUB dialog that yet shows all contexts and we need to drill down a list to find the context we just clicked for (NOT conventional, and a double take) aarhrhrh!

  • we also find that double-click or double-right-click to get to the same dialog
    -- single click is for picking/choosing/highlighting to make current
    -- right-click is for drilling down to a context of choice
    -- any superfluous ways(different triggers) to get to the same context just create a hodgepodge of inconsistencies that are NOT intuitive nor to be remembered! (MESSY, really MESSY!)

- SIMPLY GO STRAIGHT to the CONTEXT on one right-click on a CELL, no HUB interim panel that creates a double take!
if a choice requires a large dialog with multiple points of input, OPEN that once the choice is picked!
if only one choice -> GO DIRECTLY TO THE LARGE INPUT PANEL.

  • if a need for a general hub to do all the work, just have a button that does that and goes DIRECTLY TO THE LARGE PANEL with TABS at top to select the input options... NEVER an interim pigeonhole dialog.

  • avoid specifically designed small dialogs that result in pigeonhole size work spaces that you will forever readjust/redesign as you progress, instead take a browser style general approach FAST UP AND DOWN SCROLL that stays consistent thru-out the entire app and is easy to add to... one panel can be used to receive templates as needed.
    Avoid panning unless in the context of a table, that takes at least a full page width center screen 8 1/2x11 format(roughly) with a full screen width zoom toggle trigger.

  • tiny dialogs have their place such as intellisense, quick alert messages(no too tiny, if message is large), etc..

  • even if a context of input has one box to address, present the same large panel for consistency
    I cannot stress this point enough!

I could vomit at the massive amounts of M...cro..S...ft pigeonhole dialogs
AND ALL THE APPS that have been developed on that lame model all over the world!

  • that force scrolling in tiny windows, panning left and right in a ridiculously narrow space,
  • or are never the same upgrade after upgrade...
  • or that drill down over and over till one has no clue of the exact context, much less later remember where the SH TE was buried
    -... and all the while the screen real-estate is unused!

Steps to reproduce - self evident

Operating system - WIN7 Pro

SQLiteStudio version - 3 .2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.