seaside March 2009

seaside@lists.squeakfoundation.org

59 participants
57 discussions

How to turn off Seaside toolbar in a new window?
by Sophie (itsme213) 18 Jul '10

18 Jul '10

html popupAnchor callback: [self renderNewWindow]; toolbar: false; with: 'No Toolbar'. But that turns out to control the Browser toolbar, not the Seaside one. Thanks - Sophie

3 3

[ANN] Phantasia: A CSS Framework
by Hernán Morales 27 Oct '09

27 Oct '09

Dear anyone interested in working with Smalltalk objects: Now you can write in Smalltalk to style pages with CSS. Instead of styling with ugly, boring and long Strings (where you must perform a continuous visual sweeping of the code to make the most trivial modification), you can create high-level super sexy CSS constructs, track and review your styles with the standard Smalltalk tools (XReferences), and share constructs and configurations easily. The framework includes a set of 40 fixed layout templates ready for use, and let you compose the basic CSS elements as objects. A note: If your department, office, ark, whatever, have graphical designers, they rarely would love to learn this new strange prolific ninja environment called Smalltalk just for writing CSS - besides, a lot of them are already in love with anything after the word "Adobe" -, but, for smalltalkers, by far we believe that's easier to work inside Smalltalk with objects than in a file-based way. Sincerely, Hernán PD: The I-almost-forget-it part of this mail: Juan Burella and me wrote Phantasia. Download it from http://www.squeaksource.com/Phantasia.html

9 10

[Ann] Beach-Seaside
by Keith Hodges 30 May '09

30 May '09

Ok so someone has already got "beach" on google code, so I grabbed "beaches". http://code.google.com/p/beaches/ So Beach or Beaches? What do you prefer? In the following introduction(s) I will use "Beach". cheers Keith ================================================== "Beach" - Frameworks, and components for putting seaside to commercial use. "Beach" will eventually be showcased by an all new "Sushi Store"... (or Surf Store) http://code.google.com/p/beaches/ ===== Beach-Seaside ===== Central to "Beach" is the idea of a Site, the "Beach-Site" if you like, this is the main class for a Beach website. Let's give it a name: BESiteSeaside subclass: #BEBondi ===== Key Feature - Easy Installation ===== BEBondi knows how to configure itself as a seaside application (or a pier application), it knows how to initialize its databases if required. [the manual way: add BESiteConfiguration to a seaside application] ===== Key Feature - Upload and Go ===== BEBondi, knows when it is deployed, by checking its IP address. BEBondi, manages the preferences for the application, in code. (no need for seaside/config). Combining the two e.g. BEBondi-#prefSmtpHost ^ self isDeployed ifTrue: [ 'smtp.blahmail.com' ] ifFalse: [ 'server.flat' ] Upload your image to your server, and all the preferences can be set for the deployed state in advance. *seaside/config displays which settings are controlled by the "site" instance BEBondi. ==== Anywhere in seaside, your per-session instance of BEBondi is available via: self site ===== Anywhere outside of a seaside session (i.e. in a workspace) a per-session instance of BEBondi (with a seaside psuedo session) is available via: BEBondi current. ===== Key Feature - Switchable Backends ===== While your site is running in #live mode. You can hit the site with db=mock in the url and have a private test session, running from an in memory mock backend. Standard backend modes are: 1) #live 2) #test 3) #backup 4) #mock These can also be selected in seaside/config. live/test/backup are expected to be the same db engine (or engines) but with databases simply named with suffixes "-test" "-backup" e.g. sushi_store, sushi_store-test, and sushi_store-backup ===== Key Features - Plug In Backend/Frontend Components ===== See next emails ===== Key Features - Expose as much as possible to customization by subclassing ===== The "site" is effectively a "factory" hub for everything. So you can subclass it, and customise it to use whatever custom subclasses of plugins/models/backends/components your prefer. ===== Other Features - startUp hook ===== Sites that are configured (i.e. serving), are sent #onStartUp. ===== Other Features - Standard Caches ===== Places to cache data are provided as standard, per-session and per-application caches. e.g. self site sessionCacheAt: key ifAbsentPut: aBlock ===== Other Features - Per-Session properties ===== self session properties at: key ifAbsent: [ ] ===== Other Features - Helpers ===== 1. keepAliveHelper - while the user has the browser open, his session stays alive. 2. ShoreComponentsHelper - use shore components without needing a specialized WASession class. 3. ToolbarHelper - enable/disable toolbar on the fly 4. CometHelper - use comet without needing a specialized WASession class. (also available - MagmaHelper for using Magma without needing a specialised WASession class)

2 14

SEO and Seaside
by Richard Eng 27 Apr '09

27 Apr '09

Is Seaside/Squeak SEO-friendly? My website isn't showing up in any search results on Google, Yahoo!, or MSN. Apparently, spiders have a hard time scanning my website. Perhaps because of the "dynamic" nature of the application? Thanks, Richard

11 13

client side validation with jQuery
by Steven Noble 01 Apr '09

01 Apr '09

I have another (hopefully quick) seaside jQuery question. I've been putting together a little ajax app that uses onChange a fair amount and now I want to throw in some client side validation and I'm a little stumped. I realize I also need server side validation but client side validation is nice for responsiveness. So I have something like ... onChange: (html jQuery getJson serialize: (html jQuery this parent find: 'input'); html: [ :h | h text: self jsonOfStrategies ]; onComplete: 'some javascript to deal with json' which gives me something like ... onchange="$.getJSON ..." in the rendered html and I need to have a javascript if statement wrapped around the quoted text but I'm not sure how to get it there. Any thoughts? Thanks again, Steven

2 5

Squeak Oversight Board Blog
by Ken Causey 01 Apr '09

01 Apr '09

It has been mentioned before but I want to make it clear that the current Squeak Oversight Board (the team previously known as either the SqueakFoundation Board or the Squeak Leadership Team) has started a blog where we will post our thoughts and plans and where we want to receive your comments. http://squeakboard.wordpress.com/ Please visit this site if you have not already and check back regularly. Thanks, Ken

2 2

Seaside hosting alternatives
by Mariano Martinez Peck 01 Apr '09

01 Apr '09

Hi folks, I was wondering which are the seaside hosting alternatives in the market. 1) free ? I only know seasidehosting.st but this, only support squeak 3.9.1. I would love to use pharo. Is any other free ? 2) pharo support ? any ? is on the plans of pharo getting a free pharo seaside hosting ? 3) For non commercial but with needs of several pictures o commercial application, any alternatives ? how much ? how can I contact them. I tried to google a bit but didn't get any real results. I think hosting is a very very important think for most of us. Is one on the think I put into account when deciding the technology to use. Thanks a lot in advance. Mariano

8 11

Problem with seasidehosting "503 Service Temporarily Unavailable"
by Mariano Martinez Peck 01 Apr '09

01 Apr '09

Hi people. This is my first post in the list :) However, I am playing with Seaside since last year. I was trying to deploy a app to seasidehosting, but I was no succeed. I register, and I update my pier.image and pier.changes. Y also start my image and seems to be ok. There is nothing in the logs, but when I enter to here: http://destinomochila.seasidehosting.st/seaside/pier (yes, I didn't change appname yet haha) I get the well know 503: Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. So, the question is, is seasidehosting really doing a maitainance or I did something wrong ? Thanks in advance for the help. Mariano

2 6

[Ann] Beach-Pier and BeachLogin-Pier
by Keith Hodges 31 Mar '09

31 Mar '09

================================================ Beach-Pier - "Frame" - One Stop Configuration of Layout and Style ================================================ ALL configuration of the pier site, its styles and layout, javascript, error handlers etc, is provided by the root "Frame" component that you choose. If you switch root component, you switch style and layout instantly. You can have different seaside applications showing the same site with different root "Frame" components. Pick your css framework, subclass your "Frame" (BEBondiFrame) from frames providing "Content With Style" or "Blueprint" out of the box. "Content With Style" is particularly effective, since the layout to give to the designer is fixed. ======================= Beach-Pier unbreakable admin ======================= (sounds a bit like the unsinkable titanic) We initialize two applications per Beach "site". /seaside/bondi /seaside/bondiadmin The admin site, has a fixed themeable (you can change the colors, and icons) appearance, that the pier-users can't break by editing styles or layouts. When deployed the BEAuthorizationHelper is enabled on the admin site, so that a user/password and appropriate permissions are enforced. ======================== BeachLogin-Pier - Pier users vs external users ======================== Anticipating that your site will have millions of users, the user login itself is handled by BeachLogin, and the data is managed externally in whatever backed that is configured. Beach-MySql is available. I look forward to having Beach-Magma, and Beach-TokoyoTyrant to play with. Pier-Users the ones that pier uses internally are used as "roles", and are initialized as follows. 1) role-user 2) role-admin 3) role-dev ==================================== Pier - Seaside integration - call/answer within pier ==================================== Embed seaside components, into pier pages, to give them a bit of surrounding content, e.g. "Forgot Password". When the user clicks on the link to view the component page, the component is usable in the middle of the page, AND when the seaside component "returns", pier goes back to where it was before the user click on the link. Embed components in pier wiki markup as simply as +login:forgotpassword+ (* not avaialble yet) ========= Beach-Pier ========= Custom mark-up renderings, add your own BEViewRenderer. and misc.... ========= Beach-Tides ========= Schedule periodic services/events. ========= BeachFlotsam-PostBox ========= STMPConfiguration and EMail Sender with rudimentary data merge ========= BeachFlotsam-CreditCard ========= validate the numbers component.

1 0

[Ann] Beach-Login
by Keith Hodges 31 Mar '09

31 Mar '09

===== Beach - Key Features - Plug In Backend/Frontend Components ===== a) Publish a suite of UI components, that front onto a Beach plugin API. b) Publish a suite of DB model classes and Interface code, that backs onto a Beach plugin API. =========================================== Announcing - BeachLogin-Seaside - BEPluginSeasideLogin =========================================== BEPluginSeasideLogin takes this a bit further using Magritte described models. SQL is generated from the description at the persistence end, and Seaside components are generated at the UI end. | UI | < magritte-described-model > | BEPluginLogin | <magritte-described-model> | RDB/OODB BeachLogin-Seaside = Seaside UI Components a) BERegisterUserComponent b) BEForgotPasswordComponent c) BEMyAccountViewThenEditComponent generate their UI forms from: BeachLogin-Users - User model classes with full Magritte Descriptions BEUserModel BEUserLogin BEUserPeronalData BEUserUSAddressBilling BEUserUSAddressShipping BEPluginSeasideLogin is the man in the middle BEPluginSeasideLogin-#doLoginWithUserLogin: userLogin BEPluginSeasideLogin-#doLogout BEPluginSeasideLogin-#doLogout BEPluginSeasideLogin-#emailForgottonPasswordMessage BEPluginSeasideLogin-#emailNewUserWelcomeMessage BEPluginSeasideLogin-#userLoggedInCanChangeEmailTo: email And at the back BeachLogin-MySql BEDataMySql-#userLoginForUsername: username password: secret BEDataMySql-#userLoginsForUsername

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside March 2009