[Cocoapsql-developer] Fwd: Improvement ideas

[Al K. <al...@ki...>]

Begin forwarded message:

> From: Olaf van Oudenallen <ol...@ad...>
> Date: Fri May 24, 2002  03:13:12 AM US/Central
> To: Al Kirkus <al...@ki...>
> Subject: Re: Improvement ideas
> Return-Path: <ol...@ad...>
> Delivered-To: al...@ki...
> Received: (qmail 27181 invoked from network); 24 May 2002 07:13:18 =
-0000
> Received: from cmailenv4.svr.pol.co.uk (213.218.77.56) by 66.99.20.75=20=

> with SMTP; 24 May 2002 07:13:18 -0000
> Received: from [62.21.159.212] (helo=3Dserver.kantoor.tvo) by=20
> cmailENV4.svr.pol.co.uk with smtp (Exim 3.35 #1) id 17BAEY-0000Vf-00=20=

> for al...@ki...; Fri, 24 May 2002 08:15:34 +0000
> Received: from [192.168.1.3] by server.kantoor.tvo (AppleShare IP Mail=20=

> Server 6.3.1) id 167674 via TCP with SMTP; Fri, 24 May 2002 10:13:22=20=

> +0200
> Mime-Version: 1.0
> X-Sender: Ol...@ms...o (Unverified)
> Message-Id: <a05100300b913980c657a@[192.168.1.3]>
> In-Reply-To: <DAD...@ki...>
> References: <DAD...@ki...>
> Content-Type: multipart/alternative;=20
> boundary=3D"=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D_-1189894496=3D=3D_ma=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D"
>
> Hi Al,
>
> (1) I planned to have the queries stay in the query view and be=20
> reusable by navigating the cursor into a paragraph (=3Dhistorical =
query),=20
> edit the paragraph when needed and enter. On enter, the modified=20
> paragraph will be added to the bottom of the historical list of =
queries=20
> and the queryView will be reset to the history plus the new query =
(plus=20
> a return to seperate the added query/paragraph).
> So we can get rid of the history window and make my splitView -see =
(4)-=20
> more effective.
>
> (2) Further I added an line so that on enter, after the query is=20
> processed, the queryView becomes first responder again.
>
> (3) I replaced the ScrollView with my own subclass of a scrollView the=20=

> be able to enyoy the -(void)becomesFirstResponder and=20
> -(void)resignsFirstResponder. With the use of these messages that (try=20=

> to) send a message to the ScrollViews delegate, I managed to set the=20=

> "Submit" button's keyEquivalent and remove the keyEquivalent when the=20=

> ScrollView becoms / resings first responder properly. (I hate Apple's=20=

> default button wich responds to any enter / return)
>
> (4) I planned to alter the window by adding a splitView with the split=20=

> between the queryView and the tableView.
>
> (5) I added two checkBoxes near the tableView's Clear button: =
(somthing=20
> like) "AutoSize table columns" and "Table can be edited"
>
> (6) I managed to auto-size the column widths by calculating the text=20=

> size of every headercell and evry datacell (rows * columns) based on=20=

> the attributed value (stringValue and font). This does not work=20
> properly on the first query so I think I have to set the tableView's=20=

> datasource to an empty datasource on awakeFromNib. Did not do that =
yet.
>
> (7) I added the validateMenuItem (or so) to enable/disable the=20
> "connect" and "disconnect" menuitems, depending on the reply of the =
msg=20
> "connected". To have it working I replaced your menu with a copy of a=20=

> new File-menu wich I reconfigured to eye like your connection window=20=

> and made connections to the FirstResponder instead of the=20
> PSQLController.
>
> (8) As implementation of the "Table can be edited" checkBox I did no=20=

> more than adding an action to the PSQLController that sets the=20
> TableColumns editable to YES or NO. When done with (all of these 9)=20
> goals I planned to look into the actual work: make the tableView edit=20=

> the datasource and on "Save" write to the database.
>
> (9) I planned to alter the UI of the tableView as follows:
> - skip one cell to the right on return or enter=A0 - or -
> - skip to the first cell of the next row on return or enter
> - Add a preference option to enable/disable this feature
>
> (10) I am very pleased with your work on the postgre-classes while it=20=

> works and gave me a good idea of how to start. On the other hand,=20
> reading the Query class, I got a little confused by the class-,=20
> message- and variable names you used. I am not sure=A0 at this moment =
if=20
> I can think of more "descriptive" names. On the other hand I planned =
to=20
> seriously reconsider things in this stage, before writing more code.=20=

> For example: my feeling says tha PSQLQuery should be PSQLResult or so.=20=

> And=A0 as I am interested in multiple windows and multiple connections=20=

> (as I will be using one database for every costomer of mine), have=20
> another sort of dataClass to store all the available PSQLStatus =
objects=20
> paired with initiated connections. Thinking to do. (My girlfriend=20
> sometimes hates me while floating away of our conversations).
>
> Sorry if I did not use all the proper message names but I am not =
behind=20
> the right computer and starting may dayly work now.
>
> Sorry too for not using the cocoapsql-developer list now for the same=20=

> reason (and for the reason that I don't know now how to address this=20=

> message to be send to the mailing list too) Maybe you can sent a copy=20=

> of this message for archiving reasons for me...?
>
> That's all for now. Please be convinced, now and forever, that I never=20=

> intend to=A0 have critics in the negative way!
>
> Please comment on the 10 goals I have poited out above as I will,=20
> depending on your answer, implement them as soon as I have the CVS set=20=

> up properly.
>
> Before actually implementing, I will be more precise - point by point =
-=20
> about what class, method or menu I will alter at that moment to=20
> implement a feature.
>
> See you, Olaf
>
> Hi all.
>
>
>
> When I originally conceived how cocoapsql might work, I thought that=20=

> the SQL queries themselves should be objects. That was the idea of the=20=

> history window above the query line. I wanted the queries which would=20=

> appear in the history window to be individually=A0 clickable, like a =
url,=20
> and then have that query replace anything that might be in the main=20
> query window. There should also be an option to save the queries into =
a=20
> list accessible through a pull down menu, kind of like favorites might=20=

> be in a browser.
>
>
>
> Any comments on this?
>
>
>
> Al
>
>
>
> Input, Input, need more INPUT!!!!
>
>
>
> Note: I have copied that cocoapsql-developer list with this message.
>
>
>
> Please join at:
>
>
>
>
>
> http://lists.sourceforge.net/lists/listinfo/cocoapsql-developer
>
>
>
> --
>
> O. van Oudenallen, mailto: ol...@ad...
> Administratiekantoor Tersteeg Van Oudenallen
> Grift 11 - 1423 DH=A0 Uithoorn - The Netherlands
> Phone: +31(297)531929=A0 Fax: +31(297)523826