[jira] Commented: (CAY-366) Add progress/log view

From: Kevin Menard (JIRA) ("Kevin)
Date: Tue Jul 01 2008 - 20:26:52 EDT

  • Next message: Kevin Menard (JIRA): "[jira] Commented: (CAY-1077) ObjRelationship Mapping Dialog Improvements"

        [ https://issues.apache.org/cayenne/browse/CAY-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995#action_12995 ]

    Kevin Menard commented on CAY-366:
    ----------------------------------

    I've just started playing with this. It's pretty nifty, but there were some issues I'd like to see resolved:

    1) The "Copy" button is confusing. One needs to highlight text in order for the button to do anything. So, either the button should be disabled until there is a text selection or, in the absence of any selection, the button should copy the whole buffer. I think the latter is the best default.

    2) I would look at the level of effort involved in saving the window position. I could see this log window being used a lot on multi-monitor displays and it would be nice if the window could appear on the other monitor if that where it was last used. Of course, it would have to do the right thing when the second monitor is absent. This may just be too much to ask for, but it'd be nice to have an idea of what's involved to do it at the very least.

    3) Although not in the original spec or any follow up conversation, I think it would be really nice if the log window could be pinned to the main modeler pane.

    4) It would be nice if different log levels were written out in different colors. It would help draw attention to error conditions.

    5) Most errors actually occur with interaction with a modal dialog. This makes it very difficult to work with the log view without closing the dialog. We may want to reconsider the modality of such dialogs. That should likely be a separate JIRA issue, but was something I noticed.

    > Add progress/log view
    > ---------------------
    >
    > Key: CAY-366
    > URL: https://issues.apache.org/cayenne/browse/CAY-366
    > Project: Cayenne
    > Issue Type: New Feature
    > Components: CayenneModeler GUI
    > Affects Versions: 1.2 [STABLE]
    > Environment: all
    > Reporter: Øyvind Harboe
    > Assignee: Kevin Menard
    > Attachments: patch-CAY-366.txt
    >
    >
    > From: Andrus Adamchik <andru..bjectstyle.org>
    > Reply-To: cayenne-use..bjectstyle.org
    > To: cayenne-use..bjectstyle.org
    > Subject: Re: Detailed log/progress view?
    > Date: Fri, 2 Sep 2005 10:17:38 -0400 (16:17 CEST)
    > Care to file an improvement request in Jira?
    > http://objectstyle.org/cayenne/bugs-features.html
    > Andrus
    > On Sep 2, 2005, at 10:01 AM, Øyvind Harboe wrote:
    > > Writeup of some Cayenne experiences follows...
    > >
    > > I've been using the Cayenne modeler for a couple of projects now
    > > and the
    > > thing I miss the most is a detailed log/progress view where I can see
    > > everything that was attempted and the g(l)ory details of all
    > > exceptions/error messages.
    > >
    > > - Connecting to a database gives very limited feedback when it fails.
    > > E.g. I had a misconfigured MS SQL server and Cayenne gave me
    > > a "something went wrong" error message, whereas the exception in
    > > my JDBC hello world program contained much more information. When
    > > translating error message to corrective action using Google, *any*
    > > little piece of information, no matter how insignificant it may seem
    > > at the time can be of vital importance :-)
    > >
    > > - Reengineering an MS SQL database is an atomic user interface
    > > operation
    > > where there are crucial configuration steps that must be in place on
    > > the SQLServer end. E.g. I accidentally created a user without enough
    > > access rights to access the tables I wanted to reverse engineer.
    > > This
    > > didn't give me an error message, but rather nothing was reverse
    > > engineered. Zero feedback can be frustrating when trying to
    > > figure out
    > > whats going wrong.
    > >
    > > - The Cayenne modeler reports ambiguously "Schema Generation Complete"
    > > after I've clicked "Generate". It puts up this message even if it
    > > has failed. E.g. when I try to generate
    > > a schema which contains a field called "position" w/HSQLDB, it
    > > causes HSQLDB to choke. The exceptions contain enough information to
    > > clue me in on what's wrong, it is just the modeler which seems to
    > > sensor this information.
    > >
    > > - Weird error messages when switching between databases is business
    > > as usual. The tricky part is when these error messages are not
    > > propagated to the user. There is valuable information tucked away in
    > > ~/.cayenne/modeler.log
    > >
    > > - Generated columns is supported by Cayenne if the underlying JDBC
    > > driver + database adapter supports it. However, if the system
    > > is somehow misconfigured, the "Generated" flag is silently ignored.
    > > Some sort of feedback here(possibly via the log/progress view),
    > > would
    > > be nice. (I'm currently investigating why this does not work for SQL
    > > server + jDTS, Cayenne 1.2M5).
    > >
    > >
    > >
    > >
    > >
    > > --
    > > Øyvind Harboe
    > > http://www.zylin.com
    > >
    > >
    > >

    -- 
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
    



    This archive was generated by hypermail 2.0.0 : Tue Jul 01 2008 - 20:27:55 EDT