8 Dec
2013
8 Dec
'13
9:23 p.m.
On Thu, Dec 5, 2013 at 1:17 AM, Andrei Chis <chisvasileandrei(a)gmail.com>wrote;wrote:
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.
Hi,
On Wed, Dec 4, 2013 at 8:49 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote;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?
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?
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.
- What are the missing widgets?
The most important ones are tables and roassal presentations.
Also the test widget just displays text :). There is no support for color
highlighting.
- How about using Bootstrap?
That would be very nice.
Most widgets are implemented from scratch, just because when I did them
there weren't many alternatives.
- Would you be interested in participating in the
effort of improving
Glamour-Seaside infrastructure?
Yes, I would.
- Is there any doc that we can start looking at
to understand
implemented/missing features?
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.
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
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.
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
Cheers,
Andrei
tx,
Usman
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev