Re: [PyKDE] [eric3] file/class browser
1) how can I do to use the ``windowproject browser'' on a site-package. Just use the built in file browser. You can even have it remember the sqlobject site-package and display it on the top level. great . how do you do that eric remember it ? Just use the context menu over the directory you want to remember and select Add as toplevel directory. Alternatively you may use New toplevel directory of the context menu and select it via a directory selection dialog. ok, I was using eric from sarge which was the 3.6.5 version. I upgraded to the 3.7.1 and now I sew what you are talking about. ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] [eric3] file/class browser
Am Sonntag, 17. Juli 2005 21:48 schrieb Diez B. Roggisch: How should the editor know, which class a variable belongs to. Python is a dynamically typed language. This means, that the type of an object is determined at runtime. This is a very big difference to C++ or Java, where a scanner can parse the source and determine the type of an object even before the code is compiled. I'm pretty well aware of that - but I'm talking about visiting a file via the tabs, detecting code in it like self.foobar() and then one wants to visit foobar - which is located in the same file. So syncing the classbrowser with the currently visited file is nice. No reflection/type inference here. Somebody recommended to make a toolbar with an entry for the search expression and a find and find next button. The search should use the flags set last time the search dialog was used. How about that? The important part for me would be that it's fully Key-operated - in emacs, I press C-s for forward search, then start typing which does incrementally search. Pressing C-c twice makes the last search expression appear. C-r does the same backwards. Displaying the search term in a toolbar is ok, but the advantage of the minibuffer-style is that it occupies precious screenspace only when needed. And the ability to search forward/backward from the current cursor position with possible wrap arounds instead of always beginning at the top would also be great. Any chances for this? That is in. Just select the backwards checkbox and select Find Again (or press F3). It's not about searching backward, but about searching from the cursor position - instead of the beginnig, which is AFAIK the eric behaviour .I'm on my mac now and haven't eric running, so I can't check that out - but I was annoyed by that, and usually I know how to operate GUIs so I'd seen an option that changes that behaviour - I hope at least. Search next does exactly that. It searches the entered string starting at the cursor position. Regards, Diez Detlev -- Detlev Offenbach [EMAIL PROTECTED] ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] [eric3] file/class browser
How should the editor know, which class a variable belongs to. Python is a dynamically typed language. This means, that the type of an object is determined at runtime. This is a very big difference to C++ or Java, where a scanner can parse the source and determine the type of an object even before the code is compiled. I'm pretty well aware of that - but I'm talking about visiting a file via the tabs, detecting code in it like self.foobar() and then one wants to visit foobar - which is located in the same file. So syncing the classbrowser with the currently visited file is nice. No reflection/type inference here. Somebody recommended to make a toolbar with an entry for the search expression and a find and find next button. The search should use the flags set last time the search dialog was used. How about that? The important part for me would be that it's fully Key-operated - in emacs, I press C-s for forward search, then start typing which does incrementally search. Pressing C-c twice makes the last search expression appear. C-r does the same backwards. Displaying the search term in a toolbar is ok, but the advantage of the minibuffer-style is that it occupies precious screenspace only when needed. And the ability to search forward/backward from the current cursor position with possible wrap arounds instead of always beginning at the top would also be great. Any chances for this? That is in. Just select the backwards checkbox and select Find Again (or press F3). It's not about searching backward, but about searching from the cursor position - instead of the beginnig, which is AFAIK the eric behaviour .I'm on my mac now and haven't eric running, so I can't check that out - but I was annoyed by that, and usually I know how to operate GUIs so I'd seen an option that changes that behaviour - I hope at least. Regards, Diez ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] [eric3] file/class browser
Am Dienstag, 12. Juli 2005 21:08 schrieb Cedric BRINER: 1) how can I do to use the ``windowproject browser'' on a site-package. Just use the built in file browser. You can even have it remember the sqlobject site-package and display it on the top level. great . how do you do that eric remember it ? Just use the context menu over the directory you want to remember and select Add as toplevel directory. Alternatively you may use New toplevel directory of the context menu and select it via a directory selection dialog. the built in file browser comes with the debuger window. It consumes a lot of space to have both windows: project and debugger. Maybe, the best will be to have in the source browser the source of the project in a certain color and in a more shaded color the python file belonging to the distribution ( not all, but only the one that people wants to see) The file browser can be changed to be part of the project browser window (see configuration dialog, Interface page). 2) is there a way to point out in the project browser, where we are. eg: we are in the module test.py, inside a class Foo, inside the definition bar and then we ask ``point me in the project borwser'' and then project browser goes from: |-- test1.py `-- test2.py |-- cFoo21 `-- cFoo22 `-- fBar221 to: |-- test1.py | | |-- cFooWhatEver | |-- cFoo | | | | |-- dBarWhatElse | | | | `-- dBar - with this line enlighted ?? | | `-- cFooOrWhat `-- test2.py |-- cFoo21 `-- cFoo22 `-- fBar221 Ced. That could be added. What would it be good for? mmh. firstly, for coherence. from a window you can point out in the other window and vice-versa. Secondly, as I told you, if you start using a new module or a new site-package when you use a method/class in your python project. You can desire to see how the stuff that you use is made off. But now, you only have the half of the tool. You can find a definition, but you cannot see how this method/function in is oo space. So you cannot easily browse this part of the project (yeah I know, this part is not really belonging to the project :) ) Detlev -- Detlev Offenbach [EMAIL PROTECTED] Detlev -- Detlev Offenbach [EMAIL PROTECTED] ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] [eric3] file/class browser
Am Dienstag, 12. Juli 2005 20:00 schrieb Diez B. Roggisch: That could be added. What would it be good for? It's sometimes nice in larger projects when you browse a file that e.g. contains a class which has a method foo, which in turn calls a bar method in that very class. Then you can simply use the object browser to jump there instead of skimming through the file. How should the editor know, which class a variable belongs to. Python is a dynamically typed language. This means, that the type of an object is determined at runtime. This is a very big difference to C++ or Java, where a scanner can parse the source and determine the type of an object even before the code is compiled. BTW, a feature that I'm personally missing most in all not emacs/vi-flavoured editors is an incremental search with a minibuffer-style search dialog.The reason is simply that the rather large search dialog obstructs the editor view. Somebody recommended to make a toolbar with an entry for the search expression and a find and find next button. The search should use the flags set last time the search dialog was used. How about that? And the ability to search forward/backward from the current cursor position with possible wrap arounds instead of always beginning at the top would also be great. Any chances for this? That is in. Just select the backwards checkbox and select Find Again (or press F3). Thanks, Diez Detlev -- Detlev Offenbach [EMAIL PROTECTED] ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] [eric3] file/class browser
hi, 1) how can I do to use the ``windowproject browser'' on a site-package. for eg. I start using the sqlobject site-packages. This site-package is quite complex to me, and I'd like to browse the class from inside my test project. the only solution that I found is to copy all my site-package on the project directory. : ( 2) is there a way to point out in the project browser, where we are. eg: we are in the module test.py, inside a class Foo, inside the definition bar and then we ask ``point me in the project borwser'' and then project browser goes from: | |-- test1.py | `-- test2.py |-- cFoo21 `-- cFoo22 `-- fBar221 to: | |-- test1.py | |-- cFooWhatEver | |-- cFoo | | |-- dBarWhatElse | | `-- dBar - with this line enlighted ?? | `-- cFooOrWhat | `-- test2.py |-- cFoo21 `-- cFoo22 `-- fBar221 Ced. -- Cedric BRINER ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] [eric3] file/class browser
That could be added. What would it be good for? It's sometimes nice in larger projects when you browse a file that e.g. contains a class which has a method foo, which in turn calls a bar method in that very class. Then you can simply use the object browser to jump there instead of skimming through the file. BTW, a feature that I'm personally missing most in all not emacs/vi-flavoured editors is an incremental search with a minibuffer-style search dialog.The reason is simply that the rather large search dialog obstructs the editor view. And the ability to search forward/backward from the current cursor position with possible wrap arounds instead of always beginning at the top would also be great. Any chances for this? Thanks, Diez ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
