On 01/03/2013 07:43 PM, Kene Meniru wrote:
Mitya Sirenef wrote:
That's what I thought, just wanted to confirm.
However, if your objective to make it as easy for the user as possible,
is it not easier to bind dining to a name and then do this?:
dining.move(x, y, z)
Absolutely. I just found t
Mitya Sirenef wrote:
> That's what I thought, just wanted to confirm.
>
> However, if your objective to make it as easy for the user as possible,
> is it not easier to bind dining to a name and then do this?:
>
> dining.move(x, y, z)
>
Absolutely. I just found that out after replying to your c
On 01/03/2013 07:08 PM, Kene Meniru wrote:
LinearSide.put("Dining", (x,y,z)) # moves 'Dining' to x,y,z location
The put function of the LinearSide boundary class finds "Dining" (which is
an entity class called LinearSideData) in the dictionary and then allows
this LinearSideData class to calcul
Mitya Sirenef wrote:
> Ok but if the user creates two sites, how does he then manipulate them,
> if you are not binding instances in A? (e.g. you are not doing site1 =
> Site("New Site")).
>
> If the user only ever needs one site, that's fine.
>
> -m
In case of situations where the user need
Mitya Sirenef wrote:
>
> Ok but if the user creates two sites, how does he then manipulate them,
> if you are not binding instances in A? (e.g. you are not doing site1 =
> Site("New Site")).
>
> If the user only ever needs one site, that's fine.
>
> -m
>
There can only be one site for each
On 01/03/2013 02:30 PM, Kene Meniru wrote:
Mitya Sirenef wrote:
>
>>
>> I'm not familiar with POV-Ray. I want to note that with python standard
>> style, class names look like this: ClassName, instances look like this:
>> instance_name; it sounds like you want LMark to be an instance? Or you
>>
Mitya Sirenef wrote:
>
> I'm not familiar with POV-Ray. I want to note that with python standard
> style, class names look like this: ClassName, instances look like this:
> instance_name; it sounds like you want LMark to be an instance? Or you
> want instances in A to use class naming style?
>
On 01/03/2013 07:53 AM, Kene Meniru wrote:
Mitya Sirenef wrote:
>
>
>> So, how many instances do you want to make.. what kind of different
>> functionality / properties they will have?
>>
>> - mitya
>>
>
> I am porting a modeling system I created using POV-Ray scene description
> language availa
D'Arcy J.M. Cain wrote:
> That works too. It's just that you had users writing Python code but
> assumed that a three line subclass was beyond them. Not requiring them
> to write any Python code is a better option than the first one (global
> variables) that you proposed. That's all I am trying
On Thu, 03 Jan 2013 09:59:04 -0500
Kene Meniru wrote:
> Yes, I guess that is the main thing. I do not want users to have to
> write python code unless they are interested in customizing how the
That works too. It's just that you had users writing Python code but
assumed that a three line subclas
D'Arcy J.M. Cain wrote:
>> As I mentioned, the file "A" can be considered a scene file. I do not
>
> I don't know what a "scene" file is.
>
A scene file is applicable to programs like POV-Ray at www.povray.org. It is
a file that is used to describe 3D objects such as box, sphere, polygon,
etc
On Thu, 03 Jan 2013 09:06:55 -0500
Kene Meniru wrote:
> > OK, "global variables" is the clue that you need to rethink this.
> > Try to stay away from global variables as much as possible except
> > for maybe some simple setup variables within the same file.
> > Consider something like this instead
D'Arcy J.M. Cain wrote:
>
> OK, "global variables" is the clue that you need to rethink this. Try
> to stay away from global variables as much as possible except for maybe
> some simple setup variables within the same file. Consider something
> like this instead.
>
The global variable is not
On Wed, 02 Jan 2013 23:32:33 -0500
Kene Meniru wrote:
> This sounds so simple but being new to python I am finding it hard to
> get started. I want to create a module which I will call "B". There
> will be other modules called "C", "D", etc, which will most likely be
> imported in "B". Then I want
Mitya Sirenef wrote:
> So, how many instances do you want to make.. what kind of different
> functionality / properties they will have?
>
> - mitya
>
I am porting a modeling system I created using POV-Ray scene description
language available at sourceforge at
http://sourceforge.net/project
On 01/03/2013 12:32 AM, Kene Meniru wrote:
Mitya Sirenef wrote:
>
>
>>
>> Where is snap_size from? Where is LinearMark from? You don't need to
>> instantiate LinearMark in B, do it in A.
>>
>
> I want to hide as much of the python syntax from the file "A" so the
user
> just concentrates on usin
Mitya Sirenef wrote:
>
> Where is snap_size from? Where is LinearMark from? You don't need to
> instantiate LinearMark in B, do it in A.
>
I want to hide as much of the python syntax from the file "A" so the user
just concentrates on using the classes as illustrated. snap_size is a global
se
On 01/02/2013 11:32 PM, Kene Meniru wrote:
This sounds so simple but being new to python I am finding it hard to get
> started. I want to create a module which I will call "B". There will be
> other modules called "C", "D", etc, which will most likely be
imported in
> "B". Then I want the user
This sounds so simple but being new to python I am finding it hard to get
started. I want to create a module which I will call "B". There will be
other modules called "C", "D", etc, which will most likely be imported in
"B". Then I want the user to import "B" ONLY into another file I will call
19 matches
Mail list logo
