[Seaside] Using Polymer Webcomponents in seaside
maarten.mostert at wanadoo.fr
Tue Dec 1 08:04:54 UTC 2015
He Guys If you’re like me and never managed to really understand seaside, you should have a look at Cincoms AppeX, which really makes a gréât difference in writing web applications the natural way if that is the bottom line of your concern.
28 Av Alphonse Denis
83400 Hyères, France
> Le 1 déc. 2015 à 01:39, Sebastian Heidbrink <sebastian_heidbrink at yahoo.de> a écrit :
> Hi Andy,
> I use/d Amber and Seaside and there is one particular thing that I never really liked.
> You still do not feel like writing web content in a comfortable way. Even though development speed pick's up as soon as you have implemented your basic framework and components I always thought it might be more convenient to use the specialized IDEs for HTML, JS and CSS for the first visualization of your proof of concept.
> Now I stumbled across Polymer and I finally had the impression that one can, just like in Seaside, built small easy to understand components and grow from there. I actually like the separation of JS, HTML and CSS in Polymer as well as the loosely coupling of the application parts via events,.... just like in Smalltalk.
> BUT! I can not yet imagine on how to debug a complex Polymer application where some components might even be developed by other developers or teams....
> This is why I thought,.... PharoJS and Polymer might be a good fit.
> Unfortunately I was very close to write you anyways that it currently seems to me as if PharoSJ is not really there yet. I understood the concept behind PharoJS but to integrate the needed websocket proxy layer of PharoJS into Polymer is something I still have trouble to wrap my head around.
> I think Noury or Dave will first have to tell me how they would integrate something like jQuery into PharoJS in order to enable me to take what I already have and finish the Polymer parts missing.
> One might be able to use Polymer right now, but the resulting JS code would not be comparable to the one used in the Polymer documentation and that does not really make sense to me. One would implement PharoJS Code that accesses/manipulates an existing polymer object based on http://polymer.github.io/polymer/ <http://polymer.github.io/polymer/> Polymer.Base and not just provide a json specification as a configuration for a Polymer constructor.
> I am not sure yet if PharoJS is the right thing for me. I still feel like writing Amber or Seaside code but this time against a wall of proxy objects (document, window, WebSocket, ... ). I, again, need to know and learn the api of those first class objects and their particular behaviors...
> But if you would like to implement pure logic, independent from third party libraries then PharoJS is alreay providing a lot to accomplish that.
> The only thing that needs more attention is the layer that takes care of the proxy and web socket live cycles. I have to restart my image too often to have a working JbBridge again...
> What did you try so far?
> On 2015-11-30 8:47 AM, Andy Burnett wrote:
>> >>> Sebastian Heidbrink said
>> Hi Andy,
>> I actually just started to write a little PolymerWorkbench as a
>> proof-of-concept to integrate Glamour, PharoJS and Polymer. I have no
>> idea if that will work at all yet, since I have only little PharoJS
>> experience so far. Seaside is no target of mine. I parse the web
>> component definition files and will edit CSS and HTML directly.
>> Eventhandling and script generation shall be done via PharoJS. I think
>> this could open the PharoIDE to the web dev world if successful.
>> My impression on Polymer is the same as yours.
>> I have the impression that Polymer finally adds some software
>> engineering level sanity to the JS web world...
>> I'll let you know once I will have made sources available.
>> That sounds very interesting indeed. I have just started playing with PharoJS. So, I am keen to learn about your experience.
>> seaside mailing list
>> seaside at lists.squeakfoundation.org <mailto:seaside at lists.squeakfoundation.org>
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside