Tryton Web Client

[Nicolas Évrard]

Hello Trytonistas,

Lately we have received a lot of demands for a Tryton web client. The
major stopper for such a development is that it is too heavy for only
one customer.

The project would be to have a web client based on the proteus.js
prototype with almost all the current client features adapted to the
web.

The idea is to group all interested parties under one contract.

If you are interested to be part of it, please contact us at
sa...@b2ck.com so that we can organize everything.

--
Nicolas Évrard

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

[Phillip Heller]

On Mar 9, 2012, at 10:44 AM, Nicolas Évrard wrote:

> Hello Trytonistas,
>
> Lately we have received a lot of demands for a Tryton web client. The
> major stopper for such a development is that it is too heavy for only
> one customer.
>
> The project would be to have a web client based on the proteus.js
> prototype with almost all the current client features adapted to the
> web.
>
> The idea is to group all interested parties under one contract.
>
> If you are interested to be part of it, please contact us at
> sa...@b2ck.com so that we can organize everything.

Why don't you make a proposal via the shared funding system that was used for the production module?

Regards,

Phil

[Nicolas Évrard]

* Phillip Heller [2012-03-09 16:48 +0100]:

Well the status of elveos is a bit in limbo:

https://elveos.org/en/documentation/stop_elveos

So we are trying something else.

[Dominique Chabord]

Le 09/03/2012 16:44, Nicolas �vrard a �crit :

>
> The project would be to have a web client based on the proteus.js
> prototype with almost all the current client features adapted to the
> web.

Do you mean that gtk3 through web will be deceptive ?

--
Dominique Chabord - SISalp

[Cédric Krier]

On 09/03/12 17:21 +0100, Dominique Chabord wrote:

>
> Le 09/03/2012 16:44, Nicolas Évrard a écrit :
>
> >
> > The project would be to have a web client based on the proteus.js
> > prototype with almost all the current client features adapted to the
> > web.
>
> Do you mean that gtk3 through web will be deceptive ?

Python binding of gtk3 is not yet production ready.
And it is not the best design for a large scale deployment of an
application.

--
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4

4000 Liège
Belgium
Tel: +32 472 54 46 59

Email/Jabber: cedric...@b2ck.com
Website: http://www.b2ck.com/

[Sharoon Thomas]

On Mar 9, 2012, at 10:44 AM, Nicolas Évrard wrote:

Hello Trytonistas,

Lately we have received a lot of demands for a Tryton web client. The
major stopper for such a development is that it is too heavy for only
one customer.

The project would be to have a web client based on the proteus.js
prototype with almost all the current client features adapted to the
web.

I did some work this weekend on a POC for the web client, but based on

ExtJS. It was mostly an experiment to try/learn the framework and I think it

is a much better candidate for the job.

It tries to be just like the desktop client and currently implements profile

management, login and fetching of preferences. It also includes a Tryton

model proxy to easily make RPCs on model objects.

The implementation allows the client to connect to a different location where

the tryton daemon could be running as the RPC is built over CORS [1]. This

however needs an extremely light WSGI middleware to make the Trytond 

WSGI process CORS aware [2]. 

I have uploaded the source code of the work so far on github [3] and also 

uploaded a few screenshots on my blog [4]. There is also a hosted version

on the openlabs site [5].

[1] http://en.wikipedia.org/wiki/Cross-origin_resource_sharing

[2] https://gist.github.com/2019037

[3] https://github.com/openlabs/trytonweb

[4] http://www.sharoonthomas.com/2012/03/tryton-web-client.html

[5] http://openlabs.co.in/~st/trytonweb/

Thanks,

Sharoon Thomas

Openlabs Technologies & Consulting (P) Limited

w: http://www.openlabs.co.in

m: +1 786 247 1317

t: @sharoonthomas 

[himanshu patel]

Awesome 

Thanks

Himanshu

Skype: himanshu.launchpad

[Cédric Krier]

On 11/03/12 22:30 -0400, Sharoon Thomas wrote:
> On Mar 9, 2012, at 10:44 AM, Nicolas Évrard wrote:
>
> > Hello Trytonistas,
> >
> > Lately we have received a lot of demands for a Tryton web client. The
> > major stopper for such a development is that it is too heavy for only
> > one customer.
> >
> > The project would be to have a web client based on the proteus.js
> > prototype with almost all the current client features adapted to the
> > web.
> >
>
> I did some work this weekend on a POC for the web client, but based on
> ExtJS. It was mostly an experiment to try/learn the framework and I think it
> is a much better candidate for the job.

Why would it be better?

--
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4

4000 Liège
Belgium
Tel: +32 472 54 46 59

[Sharoon Thomas]

On Mar 12, 2012, at 5:54 AM, Cédric Krier wrote:

On 11/03/12 22:30 -0400, Sharoon Thomas wrote:

On Mar 9, 2012, at 10:44 AM, Nicolas Évrard wrote:

Hello Trytonistas,

Lately we have received a lot of demands for a Tryton web client. The

major stopper for such a development is that it is too heavy for only

one customer.

The project would be to have a web client based on the proteus.js

prototype with almost all the current client features adapted to the

web.

I did some work this weekend on a POC for the web client, but based on

ExtJS. It was mostly an experiment to try/learn the framework and I think it

is a much better candidate for the job.

Why would it be better?

1. ExtJS is full fledged library with widgets (components) while jQuery itself can only be

compared to Ext core for DOM manipulation. Now a better comparison would be between 

jQuery UI and Ext JS where Ext JS would still be a better candidate because it has many of

the components/widgets we would require for Tryton client like Grids, Tree panels in the 

standard package itself.

2. As you can see in my current code, with just configuration we already have a Tryton GTK

client like layout with a viewport. While this would require an original design and styling with 

jQuery (UI). Which means less code, less bugs and faster development. On the other hand

this could be a disadvantage if what we want with the web client is a flashy looking website

like feel.

3.  Clean data model: ExtJS has a clean data model / storage proxy implementation which

can be/is already extended for Tryton models.

4. Less cross browser issues: ExtJS I feel is the best of the JS frameworks available which

take away the pain of cross browser look/feel/functionality issues away from the developer.

5. A compatible license. Its GPL too. 

Also the main reason why the ExtJS community seems to use the framework is for JS application

development like admin panels. This seems to be driving the focus of the development as well 

while jQuery itself seems to be focused on being a lightweight DOM manipulation tool.

You could see a few example applications here:http://dev.sencha.com/deploy/ext-4.0.1/examples/

Thanks

[Ovnicraft]

On Mon, Mar 12, 2012 at 4:54 AM, Cédric Krier <cedric...@b2ck.com> wrote:

On 11/03/12 22:30 -0400, Sharoon Thomas wrote:
> On Mar 9, 2012, at 10:44 AM, Nicolas Évrard wrote:
>
> > Hello Trytonistas,
> >
> > Lately we have received a lot of demands for a Tryton web client. The
> > major stopper for such a development is that it is too heavy for only
> > one customer.
> >
> > The project would be to have a web client based on the proteus.js
> > prototype with almost all the current client features adapted to the
> > web.
> >
>
> I did some work this weekend on a POC for the web client, but based on
> ExtJS. It was mostly an experiment to try/learn the framework and I think it
> is a much better candidate for the job.

Why would it be better?

Also you can check this http://twitter.github.com/bootstrap/index.html, IMO it shows a good users experience, i have worked with ExtJS (specially geoext) and performance is not the better feature.

My 2 cents.

Regards, 

--
Cédric Krier

B2CK SPRL

Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59

Email/Jabber: cedric...@b2ck.com
Website: http://www.b2ck.com/

--
Cristian Salamea
@ovnicraft

[zodman]

i think ExtJS its great for tryton web client. But exist more
fashionist technology like http://sproutcore.com/ and
http://demos.kendoui.com/

But ExtJS it is fine!

> --
> try...@googlegroups.com mailing list

[Cédric Krier]

On 12/03/12 11:37 -0400, Sharoon Thomas wrote:
>
> On Mar 12, 2012, at 5:54 AM, Cédric Krier wrote:
>
> > On 11/03/12 22:30 -0400, Sharoon Thomas wrote:
> >> On Mar 9, 2012, at 10:44 AM, Nicolas Évrard wrote:
> >>
> >>> Hello Trytonistas,
> >>>
> >>> Lately we have received a lot of demands for a Tryton web client. The
> >>> major stopper for such a development is that it is too heavy for only
> >>> one customer.
> >>>
> >>> The project would be to have a web client based on the proteus.js
> >>> prototype with almost all the current client features adapted to the
> >>> web.
> >>>
> >>
> >> I did some work this weekend on a POC for the web client, but based on
> >> ExtJS. It was mostly an experiment to try/learn the framework and I think it
> >> is a much better candidate for the job.
> >
> > Why would it be better?
> >
> 1. ExtJS is full fledged library with widgets (components) while jQuery itself can only be
> compared to Ext core for DOM manipulation. Now a better comparison would be between
> jQuery UI and Ext JS where Ext JS would still be a better candidate because it has many of
> the components/widgets we would require for Tryton client like Grids, Tree panels in the
> standard package itself.

We always need to customize widgets.

> 2. As you can see in my current code, with just configuration we already have a Tryton GTK
> client like layout with a viewport. While this would require an original design and styling with
> jQuery (UI). Which means less code, less bugs and faster development. On the other hand
> this could be a disadvantage if what we want with the web client is a flashy looking website
> like feel.

We (B2CK) don't think that a web client should be an exact copy of the
current client because it will run in a browser so it should be adapted
to this medium.
Moreover the goal with proteus.js is to be able to embed it in any
specific web development. But it is seems very complicate to do it with
ExtJS.

> 3. Clean data model: ExtJS has a clean data model / storage proxy implementation which
> can be/is already extended for Tryton models.

I don't think so. It will always require to define Models that behaves
as Tryton expect.

> 4. Less cross browser issues: ExtJS I feel is the best of the JS frameworks available which
> take away the pain of cross browser look/feel/functionality issues away from the developer.

This is not objective. I think any JS framework today is cross browser.

> 5. A compatible license. Its GPL too.

It is an other application so any license is possible.

> Also the main reason why the ExtJS community seems to use the framework is for JS application
> development like admin panels. This seems to be driving the focus of the development as well
> while jQuery itself seems to be focused on being a lightweight DOM manipulation tool.

But we already have an application. There will be less benefit to just
have a copy than something able to behave differently.

[Luis Falcon]

On Sun, Mar 11, 2012 at 11:30 PM, Sharoon Thomas
<sharoo...@teagarden.in> wrote:
> On Mar 9, 2012, at 10:44 AM, Nicolas Évrard wrote:
>
> Hello Trytonistas,
>
> Lately we have received a lot of demands for a Tryton web client. The
> major stopper for such a development is that it is too heavy for only
> one customer.
>
> The project would be to have a web client based on the proteus.js
> prototype with almost all the current client features adapted to the
> web.
>
>
> I did some work this weekend on a POC for the web client, but based on
> ExtJS. It was mostly an experiment to try/learn the framework and I think it
> is a much better candidate for the job.
>
> It tries to be just like the desktop client and currently implements profile
> management, login and fetching of preferences. It also includes a Tryton
> model proxy to easily make RPCs on model objects.
>
> The implementation allows the client to connect to a different location
> where
> the tryton daemon could be running as the RPC is built over CORS [1]. This
> however needs an extremely light WSGI middleware to make the Trytond
> WSGI process CORS aware [2].
>
> I have uploaded the source code of the work so far on github [3] and also
> uploaded a few screenshots on my blog [4]. There is also a hosted version
> on the openlabs site [5].

It looks great ! Thanks for sharing !

[Bruno Ricardo]

Hi,

I really got interested in make part of the team, I have enough skill in OOP with Java and Python, and ORM with Hibernate and SQLAlchemy, and design, once I was a webdesigner.

How can i work together with you guys? I really got interested in do something better then other open-sources ERP's.

Thanks.