Actually, Seaside does figure prominently in the campaign. You can see it in my article "The Smalltalk Revolution" where it's visible in the two graphics. Seaside is also mentioned, both explicitly and implicitly, at the Smalltalk Renaissance website. I regard Pharo, Seaside, and Amber as a troika for promoting Smalltalk as "the future of Smart Web Development."
-- I will try to solicit some input from the Seaside community for the campaign. Since I've not used Seaside for a number of years, I am no longer technically qualified to discuss Seaside. For that matter, I'm not really technically qualified to discuss Pharo, either. I've only ever used Squeak, and that was 8 years ago! On Friday, 23 January 2015 02:11:28 UTC-5, StephaneDucasse wrote:
You received this message because you are subscribed to the Google Groups "Smalltalk Research" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
In reply to this post by Ben Coman-3
Excerpts from Ben Coman's message of 2015-01-23 18:07:44 +0100:
> Thanks Martin. I see where you are coming from. btw, maybe these two > frameworks fit your philosophy... > * Flow - https://github.com/flow-stack/flow > * Tide - https://github.com/tide-framework/tide i looked at those briefly. problem is i can't figure out how closely coupled front and backend are. the appeal of using a RESTful API is that it fully decouples the front and backend. i can write either in any way i want, and change them or even replace them at will without having to make any changes on the other side. that means, if i build a site with tide or flow, at any point i want to be able to replace the amber frontend with one basedon angular, ember or something else. even better, i expect to be able to run multiple different frontends side-by-side. likewise i expect to be able to replace the pharo backend with something completely different . the reverse is true too: if i write a frontend with amber, against some existing backend, will tide or flow be able to pick that up, or will they force me to rewrite the frontend to match? can i switch between flow and tide without rewriting the amber frontend? how much does flow depend on mongo? can i use a different database? (do i even need one? for simple apps saving in the image should be enough) the choice for a database very much depends on the data model, which depends on the application. limiting a framework to a specific database reduces the usability for cases where that database is the right fit. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/ -- You received this message because you are subscribed to the Google Groups "Smalltalk Research" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
In reply to this post by horrido
I've published a new essay on the Seaside framework: https://smalltalkrenaissance.wordpress.com/2015/01/24/the-heretic-web-framework/
-- Your feedback is appreciated. Thanks. On Friday, 23 January 2015 22:36:00 UTC-5, Richard Eng wrote:
You received this message because you are subscribed to the Google Groups "Smalltalk Research" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
In reply to this post by horrido
Good!
-- Lets do it On Friday, January 23, 2015 at 2:32:11 AM UTC-2, Richard Eng wrote:
You received this message because you are subscribed to the Google Groups "Smalltalk Research" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
In reply to this post by cedreek
Hey Cedrick,
-- no worries! The last flow version has a tutorial-like sample application (furiously coded without CSS in mind :D) https://github.com/flow-stack/flow Also this should give you an idea: https://medium.com/@sebastianconcpt/app-main-and-other-controller-accessors-84abe31e483e Reviews and all kind of feedback is welcome! On Friday, January 23, 2015 at 3:34:31 PM UTC-2, Cédrick Béler wrote:
You received this message because you are subscribed to the Google Groups "Smalltalk Research" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
Free forum by Nabble | Edit this page |