Re: [tryton] Bootstrap TUL2012

[Emma]

I'l try to attend too but November is still far away and I am not certain 
of my schedule at the time yet

-- 
-- 
tryton@googlegroups.com mailing list

Re: [tryton] Invoice with a percentage of the sold quantity

[guly200]

Le mercredi 18 juillet 2012 00:29:31 UTC+2, Cédric Krier a écrit :
>
> On 17/07/12 03:19 -0700, guly200 wrote: 
> > Thanks Cedric 
> > 
> > I thought of doing the following on the invoice line object: 
> > - add one function field "base_quantity" 
> > - add one function field "percentage" 
> > 
> > on each of these function fields, declare a "setter" function that will 
> > calculate : base_quantity x percentage / 100 
> > The result will be written by the setter function in the original tryton 
> > "quantity" field ? 
> > I will hide the original quantity field and make sure a uom of "unit" 
> gets 
> > enought digits to be relevant ? 
> > 
> > Doing this I would not break anything ? 
> > And I could create invoices with a wizard requesting a percentage for 
> each 
> > line and checking that it does not exceed the reminder ? 
> > what do you think ? Did I overlook something ? 
>
> I think it is a bad idea. 
> What is exactly your purpose? 
>
>
Let me clarify the situation:
We are a service company. We have a sale order with big item lines which we 
invoice in steps, let's say:
30% upon milestone A
50% upon milestone B
20% upon milestone C

So if in the sale order we have:
description quantity unit priceamount
my service  1 100100 

The customer wants to see 3 invoices with lines like:
description quantity percentageunit priceamount
my service  1   30%   100 30 

I hope the situation is more clear for you

 

-- 
-- 
tryton@googlegroups.com mailing list

Re: [tryton] About external module and README

[Raimon Esteve]

2012/7/18 Cédric Krier :
> It is http://pypi.python.org/pypi?:action=browse&show=all&c=551

I think "the problem" is modules are available in pypi site, not the module name

Raimon

-- 
-- 
tryton@googlegroups.com mailing list

Re: [tryton] Display function field in a One2Many widget

[Tristian Paul Lopez Azuara]

On Wednesday, July 18, 2012 11:50:27 PM UTC-7, Cédric Krier wrote:
>
> On 18/07/12 16:23 -0700, Tristian Paul Lopez Azuara wrote: 
> > Hi all, I think the title sums it all, I want to display a function 
> field 
> > using a One2Many widget, 
> > the reason for this is that I compute the the values of the list lazily 
> > (Basically a list of dictionaries) 
> > and I do not store them in the database, so there's no **id** to be 
> > referenced, I'v tried implementing 
> > said functionality, but I can't seem to set the correct return values 
> for 
> > the function field. No errors get 
> > thrown if I return a list of numbers, which I suspect are used to 
> reference 
> > the One2Many relation, but 
> > I also want to supply the values for each reference. 
> > 
> > How would this situation be approached? 
>
> You can not. 
> You must provide ids, they can come from a Model based on a query if you 
> want. 
>
> -- 
> Cédric Krier 
>
> B2CK SPRL 
> Rue de Rotterdam, 4 
> 4000 Liège 
> Belgium 
> Tel: +32 472 54 46 59 
> Email/Jabber: cedric.kr...@b2ck.com 
> Website: http://www.b2ck.com/ 
>


Hi, thanks for the reply, 

Then how would I supply values that are not in the database and do not have 
an
id for a one2many field.

Or maybe how to custom load a one2many widget,  I've done it in wizards, 
but in the wizard the models only inherit from ModelView so I just override 
the default_get method, but on models that inherit from ModelSQL and where 
the model has values, I need to compute the data based on other fields of 
said 
model.

Regards, Tristian.

-- 
-- 
tryton@googlegroups.com mailing list

Re: [tryton] About external module and README

[Nicolas Évrard]

* Raimon Esteve  [2012-07-19 18:20 +0200]: 

2012/7/18 Cédric Krier :

It is http://pypi.python.org/pypi?:action=browse&show=all&c=551


I think "the problem" is modules are available in pypi site, not the module name


I disagree.
As I told you on twitter, we have two ways to denote tryton packages
in pypi:

- The classifier
- The name

I propose that names starting by 'trytond_' denote official tryton
packages. All other packages should be named just like people want as
long as they use the correct classifier then users of pypi will be
able to find them easily.

--
Nicolas Évrard

B2CK SPRL
rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
E-mail/Jabber: nicolas.evr...@b2ck.com
Website: http://www.b2ck.com/


signature.asc
Description: Digital signature

Re: [tryton] About external module and README

[Sergi Almacellas Abellana]

Al 19/07/12 21:51, En/na Nicolas Évrard ha escrit:

* Raimon Esteve  [2012-07-19 18:20 +0200]:

2012/7/18 Cédric Krier :

It is http://pypi.python.org/pypi?:action=browse&show=all&c=551


I think "the problem" is modules are available in pypi site, not the 
module name

I think that pypi is a good place to find all the tryton related modules.



I disagree.
As I told you on twitter, we have two ways to denote tryton packages
in pypi:

- The classifier
- The name

I propose that names starting by 'trytond_' denote official tryton
packages. All other packages should be named just like people want as
long as they use the correct classifier then users of pypi will be
able to find them easily.


It's good to separate official packages than unofficial ones, but I 
think that a name convention is not a easy way to differ it, specially 
for newcomers.


Why we don't add tryton.org (or the tryton foundation) in Package Index 
Owner and Package Index Maintainer to denote an official module? The 
rest of the modules will have it's own maintainer denoting that it isn't 
an official module.


It makes sense to me. What do you think?

Just my 2 cents!

--
Sergi Almacellas Abellana
www.koolpi.com 
se...@koolpi.com 
Twitter: @pokoli_srk 
Mov: 690 95 92 95

--
--
tryton@googlegroups.com mailing list

Re: [tryton] About external module and README

[Cédric Krier]

On 19/07/12 22:03 +0200, Sergi Almacellas Abellana wrote:
> Why we don't add tryton.org (or the tryton foundation) in Package
> Index Owner and Package Index Maintainer to denote an official
> module? The rest of the modules will have it's own maintainer
> denoting that it isn't an official module.
> 
> It makes sense to me. What do you think?

Because it doesn't prevent name collision.
Let's take an example, if anyone create a package named trytond_hr,
there are a lot of chances that one day or an other Tryton will have a
module with the same name.
We must see the "trytond_" as a name space and this name space is
devoted to Tryton.

By the way having let say a package named b2ck_hr doesn't prevent it to
install a module named "hr".

By the way, I did not yet see any good explaination why non-Tryton
packages should be prefixed by "trytond_" ?

-- 
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: cedric.kr...@b2ck.com
Website: http://www.b2ck.com/


pgpozMdUMQ6rO.pgp
Description: PGP signature

Re: [tryton] About external module and README

[Sergi Almacellas Abellana]

Al 19/07/12 22:24, En/na Cédric Krier ha escrit:

On 19/07/12 22:03 +0200, Sergi Almacellas Abellana wrote:

Why we don't add tryton.org (or the tryton foundation) in Package
Index Owner and Package Index Maintainer to denote an official
module? The rest of the modules will have it's own maintainer
denoting that it isn't an official module.

It makes sense to me. What do you think?

Because it doesn't prevent name collision.
Your solution only prevents name collision on the official modules. The 
collision will exists always in unofficial modules.



Let's take an example, if anyone create a package named trytond_hr,
there are a lot of chances that one day or an other Tryton will have a
module with the same name.
We must see the "trytond_" as a name space and this name space is
devoted to Tryton.
To tryton or to tryton related packages? IMHO makes more sense to tryton 
related packages.


By the way having let say a package named b2ck_hr doesn't prevent it to
install a module named "hr".

By the way, I did not yet see any good explaination why non-Tryton
packages should be prefixed by "trytond_" ?
And I did not yet see any good explanation why Tryton packages should 
not be prefixed by "trytond_"?





--
Sergi Almacellas Abellana
www.koolpi.com 
se...@koolpi.com 
Twitter: @pokoli_srk 
Mov: 690 95 92 95

--
--
tryton@googlegroups.com mailing list

Re: [tryton] About external module and README

[Cédric Krier]

On 19/07/12 22:31 +0200, Sergi Almacellas Abellana wrote:
> Al 19/07/12 22:24, En/na Cédric Krier ha escrit:
> >On 19/07/12 22:03 +0200, Sergi Almacellas Abellana wrote:
> >>Why we don't add tryton.org (or the tryton foundation) in Package
> >>Index Owner and Package Index Maintainer to denote an official
> >>module? The rest of the modules will have it's own maintainer
> >>denoting that it isn't an official module.
> >>
> >>It makes sense to me. What do you think?
> >Because it doesn't prevent name collision.
> Your solution only prevents name collision on the official modules.
> The collision will exists always in unofficial modules.

Except if "unofficial" also follow a schema.
I think B2CK will publish his packages under the prefix "b2ck_" because
it is the name of the project from where it comes.

> >Let's take an example, if anyone create a package named trytond_hr,
> >there are a lot of chances that one day or an other Tryton will have a
> >module with the same name.
> >We must see the "trytond_" as a name space and this name space is
> >devoted to Tryton.
> To tryton or to tryton related packages? IMHO makes more sense to
> tryton related packages.

When I say "Tryton" I mean the project/community.

> >By the way having let say a package named b2ck_hr doesn't prevent it to
> >install a module named "hr".
> >
> >By the way, I did not yet see any good explaination why non-Tryton
> >packages should be prefixed by "trytond_" ?
> And I did not yet see any good explanation why Tryton packages
> should not be prefixed by "trytond_"?

- It brings confusion
- It will create name collision:
  We can expect in the long term that there will be more
  "unofficial" packages than "official". So each time a new
  "official" package will be created, its name will part of a long
  process to find a free name (which could be not the more accurate
  one).

Finally, I would like to remember that if people wants to have a module
be part of the "official" modules. He should join the community and
follow the standard process:

- blueprint
- talks/mailing list
- codereview…

Otherwise, it could be feel as a hijacking of the project/community.

-- 
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: cedric.kr...@b2ck.com
Website: http://www.b2ck.com/


pgpivbUSHBF7H.pgp
Description: PGP signature

Re: [tryton] About external module and README

[Craig Barnes]

On 19 July 2012 21:43, Cédric Krier  wrote:
> On 19/07/12 22:31 +0200, Sergi Almacellas Abellana wrote:
>> Al 19/07/12 22:24, En/na Cédric Krier ha escrit:
>> >On 19/07/12 22:03 +0200, Sergi Almacellas Abellana wrote:
>> >>Why we don't add tryton.org (or the tryton foundation) in Package
>> >>Index Owner and Package Index Maintainer to denote an official
>> >>module? The rest of the modules will have it's own maintainer
>> >>denoting that it isn't an official module.
>> >>
>> >>It makes sense to me. What do you think?
>> >Because it doesn't prevent name collision.
>> Your solution only prevents name collision on the official modules.
>> The collision will exists always in unofficial modules.
>
> Except if "unofficial" also follow a schema.
> I think B2CK will publish his packages under the prefix "b2ck_" because
> it is the name of the project from where it comes.
>
>> >Let's take an example, if anyone create a package named trytond_hr,
>> >there are a lot of chances that one day or an other Tryton will have a
>> >module with the same name.
>> >We must see the "trytond_" as a name space and this name space is
>> >devoted to Tryton.
>> To tryton or to tryton related packages? IMHO makes more sense to
>> tryton related packages.
>
> When I say "Tryton" I mean the project/community.
>
>> >By the way having let say a package named b2ck_hr doesn't prevent it to
>> >install a module named "hr".
>> >
>> >By the way, I did not yet see any good explaination why non-Tryton
>> >packages should be prefixed by "trytond_" ?
>> And I did not yet see any good explanation why Tryton packages
>> should not be prefixed by "trytond_"?
>
> - It brings confusion
> - It will create name collision:
>   We can expect in the long term that there will be more
>   "unofficial" packages than "official". So each time a new
>   "official" package will be created, its name will part of a long
>   process to find a free name (which could be not the more accurate
>   one).
>
> Finally, I would like to remember that if people wants to have a module
> be part of the "official" modules. He should join the community and
> follow the standard process:
>
> - blueprint
> - talks/mailing list
> - codereview…
>
> Otherwise, it could be feel as a hijacking of the project/community.
>
Maybe we should adopt a convention for community pipy package names i.e.

trytond_community_packagename

I don't believe we can reserve prefixes in pypi so we cant stop those
that would choose to hijack the name AFAIK.

I think a bigger problem will be the module name collisions at
installation, if there is an official trytond_party_bank and a
joebloggs_bank and both install modules/party_bank, what will the
result be when both are installed?

Neither neso or proteus are listed in Framework :: Tryton is this expected?

pip search tryton and regular web search for tryton finds those with
tryton in the description, so as long as it is in the description it
can be found with a trivial and web pip search.

-- 
Craig

'The first time any man's freedom is trodden on - we are all damaged.'
Jean-Luc Picard
()  ascii ribbon campaign - against html mail
/\

-- 
-- 
tryton@googlegroups.com mailing list

Re: [tryton] About external module and README

[Cédric Krier]

On 19/07/12 22:03 +0100, Craig Barnes wrote:
> Maybe we should adopt a convention for community pipy package names i.e.
> 
> trytond_community_packagename

I find "trytond_community" also confusing because Tryton is a community.

> I don't believe we can reserve prefixes in pypi so we cant stop those
> that would choose to hijack the name AFAIK.

Yeps but we could point them as not fair people :-)

> I think a bigger problem will be the module name collisions at
> installation, if there is an official trytond_party_bank and a
> joebloggs_bank and both install modules/party_bank, what will the
> result be when both are installed?

We could expect pip to prevent collisions but from what I find on it it
doesn't seem to manage it. (Could be a good improvement)

> Neither neso or proteus are listed in Framework :: Tryton is this expected?

It seems to be a forget. Patch is welcome.

-- 
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: cedric.kr...@b2ck.com
Website: http://www.b2ck.com/


pgpM1rnNIOV0H.pgp
Description: PGP signature

Re: [tryton] About external module and README

[Craig Barnes]

On 19 July 2012 22:17, Cédric Krier  wrote:
> On 19/07/12 22:03 +0100, Craig Barnes wrote:
>> Maybe we should adopt a convention for community pipy package names i.e.
>>
>> trytond_community_packagename
>
> I find "trytond_community" also confusing because Tryton is a community.

Fair comment, but this is a common convention for community maintained
packages in community distros.

Maybe a more appropriate term like 3rdparty or the more vague 3p, or
any other ideas?

>
>> I don't believe we can reserve prefixes in pypi so we cant stop those
>> that would choose to hijack the name AFAIK.
>
> Yeps but we could point them as not fair people :-)
>
>> I think a bigger problem will be the module name collisions at
>> installation, if there is an official trytond_party_bank and a
>> joebloggs_bank and both install modules/party_bank, what will the
>> result be when both are installed?
>
> We could expect pip to prevent collisions but from what I find on it it
> doesn't seem to manage it. (Could be a good improvement)
>
>> Neither neso or proteus are listed in Framework :: Tryton is this expected?
>
> It seems to be a forget. Patch is welcome.

done

-- 
Craig

'The first time any man's freedom is trodden on - we are all damaged.'
Jean-Luc Picard
()  ascii ribbon campaign - against html mail
/\

-- 
-- 
tryton@googlegroups.com mailing list

Re: [tryton] About external module and README

[Teagarden]

On 20-Jul-2012, at 1:54 AM, Cédric Krier  wrote:

> On 19/07/12 22:03 +0200, Sergi Almacellas Abellana wrote:
>> Why we don't add tryton.org (or the tryton foundation) in Package
>> Index Owner and Package Index Maintainer to denote an official
>> module? The rest of the modules will have it's own maintainer
>> denoting that it isn't an official module.
>> 
>> It makes sense to me. What do you think?
> 
> Because it doesn't prevent name collision.

Name collision seems to be the primary problem we are trying to solve. I agree 
with the issue and we are ready to move our modules to a *new* naming scheme 
too, and may be most of us in this community will too, but that doesn't really 
solve the problem because anybody could still create packages on pypi under the 
tryton namespace ? And if it is his *intention* to do it, we might have little 
or no influence over it either.

My preferred solution to the problem would be hosting our own pypi which serves 
the official modules and perhaps the community ones too. The package index 
could perhaps be regulated by a 'packaging sig', which could arbitrate on name 
clashes and disputes. 

I have never made a separate installation of pypi myself, but I think there are 
already projects which have done this.

Thanks

Sharoon Thomas

-- 
-- 
tryton@googlegroups.com mailing list