Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-28 Thread Vinicius Santos
Hello, I did several tests and seems to be working good. If you have any suggestion for improvement, please let me know. Thanks! 0031-Implemeting-auto-save-feature-in-the-SQL-Editor.patch Description: Binary data -- Sent via pgadmin-hackers mailing list ([email protected]) To ma

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-28 Thread Vinicius Santos
Hello! I finished the patch. I'm testing deeper, on W7 and Ubuntu. I will probably send it tonight. Thanks!

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-26 Thread Vinicius Santos
> Do you have any progress on this patch? > Yes. I am finishing a preview. I'm testing on Windows 7 and Ubuntu. I think I should finish by the end of today.

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-26 Thread Guillaume Lelarge
On Wed, 2012-08-08 at 12:50 -0300, Vinicius Santos wrote: > > Where is it saved? > > You also need to have a way to delete those files. > > I thought to create a specific directory for it. > > > Yeah, I think the informations should be available in the

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-08 Thread Vinicius Santos
> Where is it saved? > > You also need to have a way to delete those files. > I thought to create a specific directory for it. > Yeah, I think the informations should be available in the file (for > example if your database has a _ in its name, it will be hard to decode > the informations from

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-08 Thread Guillaume Lelarge
On Tue, 2012-08-07 at 18:20 -0300, Vinicius Santos wrote: > > > Well, this seems good but there's an issue I don't know how > you want to > deal with it: what's happens if I had more than one window > opened? > > I'm saving a file for each window. > Each window ha

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-07 Thread Vinicius Santos
> Well, this seems good but there's an issue I don't know how you want to > deal with it: what's happens if I had more than one window opened? I'm saving a file for each window. Each window have a private variable called "fileNameAutoSave" The query is salved from time-to-time. As configuration.

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-07 Thread Guillaume Lelarge
On Tue, 2012-08-07 at 08:44 -0300, Vinicius Santos wrote: > > Seems good to me. We are talking about the query tool, right? > > > Right. > > > > Be careful > > that users may have many query tool windows open at the same time. > > > > Actually I thought of something simple. > > One file per w

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-07 Thread Vinicius Santos
> Seems good to me. We are talking about the query tool, right? Right. > Be careful > that users may have many query tool windows open at the same time. > Actually I thought of something simple. One file per window, when the window is closed, the pgAdmin will delete it. We avoid the loss of

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-07 Thread Guillaume Lelarge
On Mon, 2012-08-06 at 20:30 -0600, Adam Scott wrote: > MySQL Workbench has a similar feature. > > This does pose an exposure to save sensitive information without the user > knowing. How to solve this? A complicated development path: encrypt saved > document. We won't go that road for sure. Too

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-07 Thread Guillaume Lelarge
On Mon, 2012-08-06 at 20:22 -0300, Vinicius Santos wrote: > Hello, > > I started to implement the feature "autosave" present in many text editors. > > I would like to listen your opnions about this feature. > > I put a option "Minutes to save the document automatically" in the > frmOptions. > >

Re: [pgadmin-hackers] Autosave in the SQL Editor

2012-08-06 Thread Adam Scott
MySQL Workbench has a similar feature. This does pose an exposure to save sensitive information without the user knowing. How to solve this? A complicated development path: encrypt saved document. Of course any of the files the user saves should be privileged to that user (not group). So anot