Eric -- Python IDE

headers Detlev Offenbach | 1 May 2012 13:17

_______________________________________________
Eric mailing list
Eric@...
http://www.riverbankcomputing.com/mailman/listinfo/eric

_______________________________________________
Eric mailing list
Eric@...
http://www.riverbankcomputing.com/mailman/listinfo/eric

_______________________________________________
Eric mailing list
Eric@...
http://www.riverbankcomputing.com/mailman/listinfo/eric

_______________________________________________
Eric mailing list
Eric@...
http://www.riverbankcomputing.com/mailman/listinfo/eric

On 12-05-01 10:14 AM, Detlev Offenbach wrote:
> Hello eric users,
>
> I am planning to simplify the eric code a bit. Currently eric supports 
> four different window layouts. These are
>
> 1. floating windows
> 2. docking windows
> 3. toolbox windows (on the left and the bottom)
> 4. sidebars (on the left and on the bottom)
>
> I am planning to delete the support for 1. and 2. What does the 
> community say to this plan?
Fine with me (if I understand the question).  I never use anything but a 
two-pane "tiled" configuration with project viewer on the left and 
editor on the right, with all of the toolbars hidden.  I believe that's 
just one "sidebar" (the project "vertical toolbar"?)

As an aside: I'd disable the Multi project and Template views in the 
"vertical toolbar" if I could (never use them and they mess up 
scrolling-with-the-trackpad (when you reach the bottom of the project 
list you switch to template view, then scroll back up, but you wind up 
with the project viewer scrolled up slightly unless you are very precise 
so you have to scroll down again, which...)).

Feel free to rip out things *other* people like ;) :) ,
Mike

We have this setup here where the project file cannot be saved at the
root of the project directory. It was meant for a single build file (a
Makefile, SConstruct, CMakeLists, or whatever.. with includes/imports
to more files in the "buildsys/" when necessary) and a small textfile
like README.txt describing what the project is, how to build it (what
build system used, dependencies, commands, etc.), contact info. to
people who responsible/maintain this, repository location, location of
files, and so on.

I don't like it but that's the way it is. I've been using (g)vim for
Python for quite sometime, and this "requirements" didn't actually
constrain me because vim just don't care about file locations. But
once I bring eric to the table, I realize that I have to bend either
the IDE (eric) or the rule because it seems eric project file (eg.
project.c4p) expects to be located at the root of the project
directory (http://www.riverbankcomputing.com/pipermail/eric/2010-June/002622.html).

Well, I decided to "bend" eric (ie. because I cant change the rules)
and this is what I came up with:

   https://gist.github.com/2584467

I use a rather ugly "^^PROJECTPATH" key because it's a hack, of course
the preferable name should be pdata["PROJECTPATH"] or something like
that should the author(s) agree to my code.

I hope the author(s) can consider it for adoption.

ps. I'm sorry for any grammatical error(s), English is not my native language.

Hello,

thanks for the patch. I'll have a look at it. Please be aware, that eric 
creates a hidden directory in the project directory for storing it's 
management data (like sessions, tasks, ...). If the rope refactoring plug-in 
is installed, it will create another hidden directory for the rope data.

Regards,
Detlev

Am Donnerstag, 3. Mai 2012, 16:14:20 schrieb Klenongan:
> We have this setup here where the project file cannot be saved at the
> root of the project directory. It was meant for a single build file (a
> Makefile, SConstruct, CMakeLists, or whatever.. with includes/imports
> to more files in the "buildsys/" when necessary) and a small textfile
> like README.txt describing what the project is, how to build it (what
> build system used, dependencies, commands, etc.), contact info. to
> people who responsible/maintain this, repository location, location of
> files, and so on.
> 
> I don't like it but that's the way it is. I've been using (g)vim for
> Python for quite sometime, and this "requirements" didn't actually
> constrain me because vim just don't care about file locations. But
> once I bring eric to the table, I realize that I have to bend either
> the IDE (eric) or the rule because it seems eric project file (eg.
> project.c4p) expects to be located at the root of the project
> directory
> (http://www.riverbankcomputing.com/pipermail/eric/2010-June/002622.html).
> 
> Well, I decided to "bend" eric (ie. because I cant change the rules)
> and this is what I came up with:
> 
>    https://gist.github.com/2584467
> 
> I use a rather ugly "^^PROJECTPATH" key because it's a hack, of course
> the preferable name should be pdata["PROJECTPATH"] or something like
> that should the author(s) agree to my code.
> 
> I hope the author(s) can consider it for adoption.
> 
> ps. I'm sorry for any grammatical error(s), English is not my native
> language. _______________________________________________
> Eric mailing list
> Eric@...
> http://www.riverbankcomputing.com/mailman/listinfo/eric
--

-- 
Detlev Offenbach
detlev@...

Am Mittwoch, 2. Mai 2012, 08:33:45 schrieb Mike C. Fletcher:
> On 12-05-01 10:14 AM, Detlev Offenbach wrote:
> > Hello eric users,
> > 
> > I am planning to simplify the eric code a bit. Currently eric supports
> > four different window layouts. These are
> > 
> > 1. floating windows
> > 2. docking windows
> > 3. toolbox windows (on the left and the bottom)
> > 4. sidebars (on the left and on the bottom)
> > 
> > I am planning to delete the support for 1. and 2. What does the
> > community say to this plan?
> 
> Fine with me (if I understand the question).  I never use anything but a
> two-pane "tiled" configuration with project viewer on the left and
> editor on the right, with all of the toolbars hidden.  I believe that's
> just one "sidebar" (the project "vertical toolbar"?)
> 
> As an aside: I'd disable the Multi project and Template views in the
> "vertical toolbar" if I could (never use them and they mess up
> scrolling-with-the-trackpad (when you reach the bottom of the project
> list you switch to template view, then scroll back up, but you wind up
> with the project viewer scrolled up slightly unless you are very precise
> so you have to scroll down again, which...)).

Did you retest this with latest releases? It was fixed since 4.5.0.

> 
> Feel free to rip out things *other* people like ;) :) ,
> Mike
> 
> _______________________________________________
> Eric mailing list
> Eric@...
> http://www.riverbankcomputing.com/mailman/listinfo/eric
--

-- 
Detlev Offenbach
detlev@...

On 12-05-06 10:05 AM, Detlev Offenbach wrote:
> Am Mittwoch, 2. Mai 2012, 08:33:45 schrieb Mike C. Fletcher:
>> On 12-05-01 10:14 AM, Detlev Offenbach wrote:
...
>> As an aside: I'd disable the Multi project and Template views in the 
>> "vertical toolbar" if I could (never use them and they mess up 
>> scrolling-with-the-trackpad (when you reach the bottom of the project 
>> list you switch to template view, then scroll back up, but you wind 
>> up with the project viewer scrolled up slightly unless you are very 
>> precise so you have to scroll down again, which...)). 
> Did you retest this with latest releases? It was fixed since 4.5.0.
Nope, sorry. Afraid Kubuntu Precise is still on 4.4.18.  I'm not quite 
adventurous enough to move my main work machines over to Quantal pre-alpha.

Good to know it will be fixed in 6 months :) ,
Mike

Am Montag, 7. Mai 2012, 09:53:13 schrieb Mike C. Fletcher:
> On 12-05-06 10:05 AM, Detlev Offenbach wrote:
> > Am Mittwoch, 2. Mai 2012, 08:33:45 schrieb Mike C. Fletcher:
> >> On 12-05-01 10:14 AM, Detlev Offenbach wrote:
> ...
> 
> >> As an aside: I'd disable the Multi project and Template views in the
> >> "vertical toolbar" if I could (never use them and they mess up
> >> scrolling-with-the-trackpad (when you reach the bottom of the project
> >> list you switch to template view, then scroll back up, but you wind
> >> up with the project viewer scrolled up slightly unless you are very
> >> precise so you have to scroll down again, which...)).
> > 
> > Did you retest this with latest releases? It was fixed since 4.5.0.
> 
> Nope, sorry. Afraid Kubuntu Precise is still on 4.4.18.  I'm not quite
> adventurous enough to move my main work machines over to Quantal pre-alpha.
> 
> Good to know it will be fixed in 6 months :) ,
> Mike

or you fix this one yourself by editing E4Toolbox.py and remove the wheelEvent 
method from E4VerticalToolbox (which basically makes it a standard QToolBox).

Regards,
Detlev
--

-- 
Detlev Offenbach
detlev@...

Mon	Tue	Wed	Thu	Fri	Sat	Sun

	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31

4	May 2013
13	April 2013
24	March 2013
14	February 2013
5	January 2013
20	December 2012
24	November 2012
19	October 2012
6	September 2012
7	August 2012
22	July 2012
13	June 2012
21	May 2012
24	April 2012
23	March 2012
31	February 2012
28	January 2012
19	December 2011
37	November 2011
38	October 2011
27	September 2011
25	August 2011
28	July 2011
26	June 2011
51	May 2011
68	April 2011
41	March 2011
35	February 2011
58	January 2011
10	December 2010
10	November 2010
69	October 2010
37	September 2010
35	August 2010
51	July 2010
91	June 2010
44	May 2010
41	April 2010
40	March 2010
135	February 2010
64	January 2010
58	December 2009
37	November 2009
41	October 2009
42	September 2009
55	August 2009
61	July 2009
41	June 2009
90	May 2009
94	April 2009
63	March 2009
76	February 2009
73	January 2009
93	December 2008
51	November 2008
90	October 2008
35	September 2008
66	August 2008
65	July 2008
51	June 2008
46	May 2008
83	April 2008
69	March 2008
60	February 2008
50	January 2008
77	December 2007
27	November 2007
46	October 2007
35	September 2007
62	August 2007
41	July 2007
114	June 2007
4	May 2007
60	April 2007
35	March 2007
25	February 2007
62	January 2007
34	December 2006
8	November 2006
33	October 2006
34	September 2006

ANN: eric 4.5.3 released

ANN: eric 5.2.2 released

Planned eric changes

Re: Planned eric changes

Re: Planned eric changes

Relative project path for project files

Re: Relative project path for project files

Re: Planned eric changes

Re: Planned eric changes

Re: Planned eric changes