Smalltalk › Cincom › VisualWorks

[vwnc] Seaside Tutorial

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 5 messages Options
Steffen Märcker
Reply | Threaded
Open this post in threaded view
♦
♦
|

[vwnc] Seaside Tutorial

Steffen Märcker
Hi,
 
I've followed the Seaside Tutorial on http://www.hpi.uni-potsdam.de/swa/seaside/ and have got some problems with the chapter "Persistence". I've tried to implement StImageDatabase as simplest solution but
 
        StImageDatabase>>saveImage
 
                SmalltalkImage current saveSession
 
does not work in VisualWorks. I've changed this to "ObjectMemory snapshot". But I am unsure if this is correct, because Seaside fails to call some components right after each saveImage call, e.g. in StRootTask>>go
 
        user ifNotNil: [self session login user.
                        self call: StLoggedInComponent] "Does not show the component, no Error Notification"
 
Same holds true for the StTaskEditor.
Has someone been worked with this tutorial to and got any ideas?
 
Greetings, Steffen
_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten!
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Victor-67
Reply | Threaded
Open this post in threaded view
♦
♦
|

[vwnc] Marketing Point?

Victor-67
With all the banks and other companies going bad, an interesting question
might be something like:

Of all the companies that use software,  and taking into account the
proportion of those that use Smalltalk,  What's the proportion of those that
are surviving (and of those that went bad) that use Smalltalk?

Let's assume for the sake of discussion that within those that are
surviving, the proportion that are using ST is large, while within those
that are failing use very little ST.

It may be difficult to demonstrate that the success stories are because of
the use of ST, but if somebody succeeds in demonstrating this, it would be
great.  On the other hand, the argument could be made that the organizations
that were tested by difficult times and survived, choose to use ST, and it
didn't get in the way.

Víctor

PS.  I am cross posting to cls.  Sorry for the redundancy.

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Mark Roberts
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: [vwnc] Seaside Tutorial

Mark Roberts
In reply to this post by Steffen Märcker
Steffen,

As you've found, there are some issues with the
HPI tutorial, which was written for Squeak, not
VisualWorks. I never got their tutorial application working myself.

Cincom has some Seaside tutorials, but I don't
believe they cover image-based persistence.
Somebody else might be able to advise you about
how to make it work with Seaside, but I'd suggest
trying some kind of database-based solution
instead. There are a few options available, the
main one being supported by Cincom now is Glorp
and ActiveRecord, and we do have some material on that to help you get started.

I should also mention that in Cincom's
WebVelocity (Seaside + Glorp IDE for web apps),
we are moving away from the general pattern of
using the image for code and definitely data
storage. WebVelocity comes with a SQLite
repository ready to go when you first start up,
so it's very easy to manage application code
without using snapshots. The idea now is to make
database and code repositories easier to use, so
you can get going with "real" persistence options.

Best regards,

M. Roberts
Cincom Systems, Inc.


At 10:26 PM 11/18/2008, Steffen Märcker wrote:

>Hi,
>
>I've followed the Seaside Tutorial on
>http://www.hpi.uni-potsdam.de/swa/seaside/ and
>have got some problems with the chapter
>"Persistence". I've tried to implement StImageDatabase as simplest solution but
>
>         StImageDatabase>>saveImage
>
>                 SmalltalkImage current saveSession
>
>does not work in VisualWorks. I've changed this
>to "ObjectMemory snapshot". But I am unsure if
>this is correct, because Seaside fails to call
>some components right after each saveImage call, e.g. in StRootTask>>go
>
>         user ifNotNil: [self session login user.
>                         self call:
> StLoggedInComponent] "Does not show the component, no Error Notification"
>
>Same holds true for the StTaskEditor.
>Has someone been worked with this tutorial to and got any ideas?
>
>Greetings, Steffen
>_________________________________________________________________________
>In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten!
>Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114
>
>_______________________________________________
>vwnc mailing list
>[hidden email]
>http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
cdavidshaffer
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: [vwnc] Seaside Tutorial

cdavidshaffer
Mark D. Roberts wrote:

> Steffen,
>
> As you've found, there are some issues with the
> HPI tutorial, which was written for Squeak, not
> VisualWorks. I never got their tutorial application working myself.
>
> Cincom has some Seaside tutorials, but I don't
> believe they cover image-based persistence.
> Somebody else might be able to advise you about
> how to make it work with Seaside, but I'd suggest
> trying some kind of database-based solution
> instead. There are a few options available, the
> main one being supported by Cincom now is Glorp
> and ActiveRecord, and we do have some material on that to help you get started.
>
> I should also mention that in Cincom's
> WebVelocity (Seaside + Glorp IDE for web apps),
> we are moving away from the general pattern of
> using the image for code and definitely data
> storage. WebVelocity comes with a SQLite
> repository ready to go when you first start up,
> so it's very easy to manage application code
> without using snapshots. The idea now is to make
> database and code repositories easier to use, so
> you can get going with "real" persistence options.
>
>  
I'd like to add GOODS (an OODB) to this list as well.  Give it a
try...usually pretty simple to make an object graph persistent.  Latest
client is in the public repository with links to the DB server code and
information.

David

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
James Robertson-7
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: [vwnc] Seaside Tutorial

James Robertson-7
In reply to this post by Mark Roberts
The Seaside tutorial here:

http://www.cincomsmalltalk.com/userblogs/cincom/blogView?content=smalltalk_daily_seaside_intro

is roughly based on that tutorial, with a domain change.  For  
persistence, it simply uses a singleton to save data into instance  
variables.  As Mark points out, using the Active Record pattern (as we  
do in Web Velocity) is preferable.



James Robertson
Cincom Smalltalk Product Evangelist
http://www.cincomsmalltalk.com/blog/blogView
Talk Small and Carry a Big Class Library




On Nov 19, 2008, at 10:22 PM, Mark D. Roberts wrote:

> Steffen,
>
> As you've found, there are some issues with the
> HPI tutorial, which was written for Squeak, not
> VisualWorks. I never got their tutorial application working myself.
>
> Cincom has some Seaside tutorials, but I don't
> believe they cover image-based persistence.
> Somebody else might be able to advise you about
> how to make it work with Seaside, but I'd suggest
> trying some kind of database-based solution
> instead. There are a few options available, the
> main one being supported by Cincom now is Glorp
> and ActiveRecord, and we do have some material on that to help you  
> get started.
>
> I should also mention that in Cincom's
> WebVelocity (Seaside + Glorp IDE for web apps),
> we are moving away from the general pattern of
> using the image for code and definitely data
> storage. WebVelocity comes with a SQLite
> repository ready to go when you first start up,
> so it's very easy to manage application code
> without using snapshots. The idea now is to make
> database and code repositories easier to use, so
> you can get going with "real" persistence options.
>
> Best regards,
>
> M. Roberts
> Cincom Systems, Inc.
>
>
> At 10:26 PM 11/18/2008, Steffen Märcker wrote:
>> Hi,
>>
>> I've followed the Seaside Tutorial on
>> http://www.hpi.uni-potsdam.de/swa/seaside/ and
>> have got some problems with the chapter
>> "Persistence". I've tried to implement StImageDatabase as simplest  
>> solution but
>>
>>        StImageDatabase>>saveImage
>>
>>                SmalltalkImage current saveSession
>>
>> does not work in VisualWorks. I've changed this
>> to "ObjectMemory snapshot". But I am unsure if
>> this is correct, because Seaside fails to call
>> some components right after each saveImage call, e.g. in  
>> StRootTask>>go
>>
>>        user ifNotNil: [self session login user.
>>                        self call:
>> StLoggedInComponent] "Does not show the component, no Error  
>> Notification"
>>
>> Same holds true for the StTaskEditor.
>> Has someone been worked with this tutorial to and got any ideas?
>>
>> Greetings, Steffen
>> _________________________________________________________________________
>> In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und  
>> gestalten!
>> Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114
>>
>> _______________________________________________
>> vwnc mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Free forum by Nabble Edit this page