Stephan Eggermont | 1 Mar 01:07 2011
Picon

Re: Startup weekend success

Yanni asked:
>- was that the whole team - the four of you?

Yes. This startup weekend was about a hundred participants.
On friday evening, there were some 45 pitches, of which 12 were
chosen to be developed further. Some of them had a product ready
and needed a marketing plan, others were just an idea. Ours was
just an idea.

The groups had different sizes, ours was one of the smallest.

>- was Diego a Smalltalker too; did you meet at the event or did you know 
>each other beforehand?

The past year I've worked with Diego a few days a week on a
GLASS site. We thought most of what we have build to be reusable in
other startups, and wanted to verify that hypothesis. 

>- was there anything in particular that led you to build the "Parent 
>Support" app instead of joining another group (i.e. was the app well 
>suited to Seaside/Pharo)?

It was a combination of factors that made this the right project.
There were two or three other proposals that would have been 
a better technology fit (no iPhone app needed) but were not
as inspiring. This pitch was well liked by the audience, it had a 
very recognizable problem that was neither trivial nor extremely
difficult to approach, and one that Diego and I both experience.
The people in the team were all experienced and we had the 
right 'click'. 
(Continue reading)

Stephan Eggermont | 1 Mar 01:41 2011
Picon

Re: website maintenance/feedback

Sebastian wrote:
>that list needs the profile that makes the whole difference:
>- as investor

Yes of course. Something like:

The Seaside framework allows small teams to build (complex) web applications fast.
It is interesting for startups needing:
- small time-to-market;
- complex functionality;
- extreme short development and deployment cycles.
It is not optimal for startups having:
- extreme scalability or (real time) performance requirements;
- existing libraries already covering most needed functionality.
For those startups Seaside can be suitable for proof of concepts.

Stephan
Yanni Chiu | 1 Mar 04:15 2011

Re: Startup weekend success

On 28/02/11 7:07 PM, Stephan Eggermont wrote:
> Yanni asked:
>> - was that the whole team - the four of you?
>
> Yes. This startup weekend was about a hundred participants.
> On friday evening, there were some 45 pitches, of which 12 were
> chosen to be developed further. Some of them had a product ready
> and needed a marketing plan, others were just an idea. Ours was
> just an idea.

Thanks for the answers. Looking forward to any other writings you post 
on the experience.
Eduard Maydanik | 1 Mar 12:11 2011
Picon

Open popup window after button click

Hi, code sample:

 

WARenderLoop new call: PopupComponent new

 

From  http://www.seaside.st/documentation/faq/how-to#20704718

 

Doesn’t work in current version.

 

I am using WebVelocity 1.1a.

 

WARenderLoopMain has no “call:” method.

 

What is a right implementation?

 

I need to open separate window with print version of document.

 

Best regards,

Eduard Maydanik

 

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Julian Fitzell | 1 Mar 12:31 2011
Picon

Re: Open popup window after button click

Hi Eduard,

As I recall, I think the simplest (more or less) equivalent is:

self session presenter call: PopupComponent new

The render loop code now operates on the presenter stored by the
session, so although it is possible to start a new loop, there is
little benefit to doing so.

Julian

On Tue, Mar 1, 2011 at 11:11 AM, Eduard Maydanik <eduard <at> maydanik.de> wrote:
> Hi, code sample:
>
>
>
> WARenderLoop new call: PopupComponent new
>
>
>
> From  http://www.seaside.st/documentation/faq/how-to#20704718
>
>
>
> Doesn’t work in current version.
>
>
>
> I am using WebVelocity 1.1a.
>
>
>
> WARenderLoopMain has no “call:” method.
>
>
>
> What is a right implementation?
>
>
>
> I need to open separate window with print version of document.
>
>
>
> Best regards,
>
> Eduard Maydanik
>
>
>
> _______________________________________________
> seaside mailing list
> seaside <at> lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
Eduard Maydanik | 1 Mar 12:59 2011
Picon

RE: Open popup window after button click

Thanks!

-----Original Message-----
From: seaside-bounces <at> lists.squeakfoundation.org
[mailto:seaside-bounces <at> lists.squeakfoundation.org] On Behalf Of Julian
Fitzell
Sent: Tuesday, March 01, 2011 12:31 PM
To: Seaside - general discussion
Subject: Re: [Seaside] Open popup window after button click

Hi Eduard,

As I recall, I think the simplest (more or less) equivalent is:

self session presenter call: PopupComponent new

The render loop code now operates on the presenter stored by the
session, so although it is possible to start a new loop, there is
little benefit to doing so.

Julian

On Tue, Mar 1, 2011 at 11:11 AM, Eduard Maydanik <eduard <at> maydanik.de> wrote:
> Hi, code sample:
>
>
>
> WARenderLoop new call: PopupComponent new
>
>
>
> From  http://www.seaside.st/documentation/faq/how-to#20704718
>
>
>
> Doesn’t work in current version.
>
>
>
> I am using WebVelocity 1.1a.
>
>
>
> WARenderLoopMain has no “call:” method.
>
>
>
> What is a right implementation?
>
>
>
> I need to open separate window with print version of document.
>
>
>
> Best regards,
>
> Eduard Maydanik
>
>
>
> _______________________________________________
> seaside mailing list
> seaside <at> lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Levente Uzonyi | 1 Mar 13:21 2011
Picon
Picon

Re: Re: The Weekly Squeak Summary No. 23: Jan 31 - Feb 27, 2011

On Mon, 28 Feb 2011, Fritz Schenk wrote:

> Michael thanks,
> I am running Squea4.2 with the cog image from pharo. So far no problems.

This makes no sense. There are VMs and images, and they are very 
different.
Cog is a JIT VM. There's also SqueakVM which is an interpreter. Both VMs 
can run Squeak, Pharo, Cuis, etc images. Squeak 4.2 is an image, just like 
Pharo 1.1.
There are also distributions which contain VM(s) and an image, like the 
All-in-one Squeak 4.2, or the Pharo 1.1.1 one-click. The latter is called 
an image on the Pharo download page, but that's nonsense. Since Pharo 
people don't like the name "Squeak", therefore they call SqueakVM as 
"Standard VM".

Levente

>
> I am going to try Seaside next.
>
> _______________________________________________
> seaside mailing list
> seaside <at> lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
Sebastian Sastre | 1 Mar 14:02 2011

Re: Re: website maintenance/feedback

adding some to the list (plus annotations):

- anthropomorphic approach. Very human-like way to program makes easier to install an interesting company culture
- "extreme short development and deployment cycles" <-- (often a week, depending on the feature a couple of days) this is extremely valuable to test business plans tweaks and getting more traction and social proof faster
- extremely productive & small teams <-- a 'pizza' team (a team you can feed using only one pizza) can run a whole startup.

"...
- small time-to-market;
- complex functionality;
- extreme short development and deployment cycles.

It is not optimal for startups having:
- extreme scalability or (real time) performance requirements;  <-- unacceptable (deal breaker) 
- existing libraries already covering most needed functionality.
For those startups Seaside can be suitable for proof of concepts. <-- kind of nice but... (opportunity here if you fix the previous issue)"

Notes about scalability:
Investors will not tell you no, they will tell you that they will think about it. So, anything that isn't a hell yeah is a no. So we better have that point addressed in a smarter way.

Said so, I'd add:

1 dabbledb found a way to make it work for them, nothing is written in stone saying they had to be the only ones (and if so lets break that stone)
2 if twitter runs on ruby, arguably slower than smalltalk VM's, then I feel that the can't scale judgment focused on theory and details and assumptions too soon
3 the wrong architecture (one that allows points of contention) will make even assembler to have scalability problems (reinforcing point 2)

I feel we can think bigger guys, is just addressing one issue at the time




On Feb 28, 2011, at 9:41 PM, Stephan Eggermont wrote:

Sebastian wrote:
that list needs the profile that makes the whole difference:
- as investor

Yes of course. Something like:

The Seaside framework allows small teams to build (complex) web applications fast.
It is interesting for startups needing:
- small time-to-market;
- complex functionality;
- extreme short development and deployment cycles.
It is not optimal for startups having:
- extreme scalability or (real time) performance requirements;
- existing libraries already covering most needed functionality.
For those startups Seaside can be suitable for proof of concepts.

Stephan_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Sebastian Sastre | 1 Mar 16:05 2011

nesting #call: in a single request? possible? ideas?

Hi guys,

what if you need to have an initialRequest: making your app going to nest, say two, #call: 'd components at once?

typical situation when the session is expired but your app gets the right model from some URL parameter but the reaction is not the main component but some one deeper

right now I see that it kind of can't be done (raising a WATaskNotDelegated), but I could be missing something

not that there aren't workarounds but ...

ideas?


iv>
o/
_______________________________________________
seaside mailing list
seaside <at> lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Julian Fitzell | 1 Mar 18:01 2011
Picon

Re: nesting #call: in a single request? possible? ideas?

Mm... try #show: instead? (not sure if I'm understanding your problem correctly)

On Tue, Mar 1, 2011 at 3:05 PM, Sebastian Sastre
<sebastian <at> flowingconcept.com> wrote:
> Hi guys,
> what if you need to have an initialRequest: making your app going to nest,
> say two, #call: 'd components at once?
> typical situation when the session is expired but your app gets the right
> model from some URL parameter but the reaction is not the main component but
> some one deeper
> right now I see that it kind of can't be done (raising a
> WATaskNotDelegated), but I could be missing something
> not that there aren't workarounds but ...
> ideas?
> sebastian
> o/
> _______________________________________________
> seaside mailing list
> seaside <at> lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>

Gmane