Glamour-Seaside updates?
Locked
 
|
Hello,
We are working to port our tools (browsers) to the web. Mostly, these are developed using Glamour. So, Glamour-seaside can save us time because, in this way, we can reuse existing presentation logic with a different renderer. I worked with Andrei during one of his visits to Lille and we ported one of our browsers to the web. I didn't take us very long. However, there were some missing widgets (e.g. table). So, Andrei wanted to improve the existing set of widgets and probably reuse a new library (such as Bootstrap) make them more glamourous (as in sexy ;).
I think it can be helpful for us to use this infrastructure as there is some major progress made already. The participation of the initial contributors will be essential in the effort because rendering is just one aspect, we also have the transmissions, panes, and ports in Glamour. So my questions:
- How does Glamour-Seaside manage transmissions, ports and panes? - What are the missing widgets? - How about using Bootstrap? - Would you be interested in participating in the effort of improving Glamour-Seaside infrastructure?
- Is there any doc that we can start looking at to understand implemented/missing features? A glimpse of our tools that we need to port to the web can be found here: tx, Usman _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Glamour-Seaside updates?
|
|
Today we finished porting the magritte demo to the
new version of bootstrap in TorstenBergmann/Bootstrap. Next step would be to use that as a basis for the QCMagritte demo. There we have live editing & filtering of tables, multi-language support, ajax validation etc. Diego & Stephan _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by Usman Bhatti
Hi!
I think our effort on Roassal @ Amber may be interesting. You can try on: http://pestefo.github.io/roamber/# I guess this can be combined to a seaside server. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Dec 4, 2013, at 4:49 PM, Usman Bhatti <[hidden email]> wrote: > Hello, > > We are working to port our tools (browsers) to the web. Mostly, these are developed using Glamour. So, Glamour-seaside can save us time because, in this way, we can reuse existing presentation logic with a different renderer. I worked with Andrei during one of his visits to Lille and we ported one of our browsers to the web. I didn't take us very long. However, there were some missing widgets (e.g. table). So, Andrei wanted to improve the existing set of widgets and probably reuse a new library (such as Bootstrap) make them more glamourous (as in sexy ;). > > I think it can be helpful for us to use this infrastructure as there is some major progress made already. The participation of the initial contributors will be essential in the effort because rendering is just one aspect, we also have the transmissions, panes, and ports in Glamour. So my questions: > > - How does Glamour-Seaside manage transmissions, ports and panes? > - What are the missing widgets? > - How about using Bootstrap? > - Would you be interested in participating in the effort of improving Glamour-Seaside infrastructure? > - Is there any doc that we can start looking at to understand implemented/missing features? > > A glimpse of our tools that we need to port to the web can be found here: > http://www.synectique.eu/en/files/4D-Flyer-eng.pdf > > tx, > > Usman > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by Usman Bhatti
Hi!
I think our effort on Roassal @ Amber may be interesting. You can try on: http://pestefo.github.io/roamber/# I guess this can be combined to a seaside server. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Dec 4, 2013, at 4:49 PM, Usman Bhatti <[hidden email]> wrote: > Hello, > > We are working to port our tools (browsers) to the web. Mostly, these are developed using Glamour. So, Glamour-seaside can save us time because, in this way, we can reuse existing presentation logic with a different renderer. I worked with Andrei during one of his visits to Lille and we ported one of our browsers to the web. I didn't take us very long. However, there were some missing widgets (e.g. table). So, Andrei wanted to improve the existing set of widgets and probably reuse a new library (such as Bootstrap) make them more glamourous (as in sexy ;). > > I think it can be helpful for us to use this infrastructure as there is some major progress made already. The participation of the initial contributors will be essential in the effort because rendering is just one aspect, we also have the transmissions, panes, and ports in Glamour. So my questions: > > - How does Glamour-Seaside manage transmissions, ports and panes? > - What are the missing widgets? > - How about using Bootstrap? > - Would you be interested in participating in the effort of improving Glamour-Seaside infrastructure? > - Is there any doc that we can start looking at to understand implemented/missing features? > > A glimpse of our tools that we need to port to the web can be found here: > http://www.synectique.eu/en/files/4D-Flyer-eng.pdf > > tx, > > Usman > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by Usman Bhatti
Hi,
On Wed, Dec 4, 2013 at 8:49 PM, Usman Bhatti <[hidden email]> wrote:
Short answer: it doesn't. Long answer: transmissions and panes are handled by Glamour. The Seaside renderer just populates ports and reacts to port events. For example if in a widget the selection from a list is used to select text in an editor, when the user selects something in a list, a request is send to the server and values are propagated by Glamour. Then for every change in the model the Seaside renderer generates JQuery code that will update the widget. In this case, code to set the selection.
The most important ones are tables and roassal presentations.
Also the test widget just displays text :). There is no support for color highlighting.
That would be very nice. Most widgets are implemented from scratch, just because when I did them there weren't many alternatives.
Yes, I would.
Unfortunately not. What you could do is take a look at how some simple widgets are implemented (drop down presentation,
or text editor). There is a, more or less, standard way to add a new widget.
From a first look, if there will be a table and a roassal widget they should work. Then we could start improving the widgets one by one. As a first step I'll suggest reviving the Glamour-Seaside build from Jenkins.
At the moment there are some problems because Glamour-Seaside still uses an old version of JQuery. Cheers, Andrei
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
On Thu, Dec 5, 2013 at 1:17 AM, Andrei Chis <[hidden email]> wrote:
Ok. What I am thinking is that Glamour is an excellent tool for creating browser in desktop world where we didn't have Spec until recently. Glamour provides high-level widgets so we don't think in terms of morphs but in terms of panes. So, instead of managing individual morphs, I am managing a browser and gaining in productivity.
With Seaside, we are already dealing with components and callbacks given that we get widgets from Bootstrap. Since, you have done Glamour-Seaside, my question is what is the gain that we get in using Glamour-Seaside instead of Seaside alone given that we write something from scratch? Is it easier to manage callbacks with Seaside or transmissions in Glamour?
So, do you think that reimplementing widgets would require some deep changes in the system?
Excellent.
Ok. I remember this part from our discussion.
Exactly.
So, currently, we are doing a controlled experiment to learn Seaside without using Glamour to port one of our browsers to the web. Once done, we'll be able to evaluate the tools at our disposition and see what is the best approach (Seaside or Seaside/Glamour). I'll inform you but it'll be happening some time around the start of next year.
I'll keep you posted on the subject. regards, Usman
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by Stephan Eggermont-3
Hi Stephan,
On Wed, Dec 4, 2013 at 9:59 PM, Stephan Eggermont <[hidden email]> wrote: Today we finished porting the magritte demo to the Do we the demo live somewhere so that we can have a look at it?
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Glamour-Seaside updates?
|
|
In reply to this post by Usman Bhatti
Usman wrote:
>Do we the demo live somewhere so that we can have a look at it? QCMagritte is on https://ci.inria.fr/pharo-contribution/job/QCMagritte ZnZincServerAdapter startOn: 8080 Click through the welcome app, set browse as default and start the qcmagritte web app Stephan _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |