gemstone tutorial..

i am currently working on the gemstone tutorial, and am having a  
problem figure out how to get the code into the repository.. i think  
that step may be missing from the tutorial:

http://seaside.gemstone.com/tutorial/chapter14.pdf

i made a repository..

gave it a name, and a place to live..

but i don't see how my classes get into that repository..

am i totally missing it?

thanks!


___________
sergio t. ruiz
network analyst
red red design
419.281.8483

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi Sergio,

Nice to hear that someone is trying out my tutorial! Step #3 in that  
PDF is "Save your code to the new repository." Did you have any  
trouble with steps 1 & 2? The instructions are quite detailed.

James

On May 15, 2009, at 2:09 PM, sergio_101 wrote:

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On Fri, May 15, 2009 at 2:44 PM, James Foster <[hidden email]> wrote:
> Nice to hear that someone is trying out my tutorial!

It's by far the best tutorial I've come across.  Got me pretty
comfortable with Seaside in a day, I feel like it gave me enough
understanding of the core concepts that I've been able to write some
decent Seaside code.  So, thanks :)

Two gripes about it. First one is minor, it would be nice if you had
it in a single PDF so we don't have to download 16 separate chapters.
I actually did download all 16 and combined them into one PDF to make
it easier for me.

I had hoped to learn more about Gemstone and how to use it within
Seaside, since I've never used Gemstone (or anything like it) before.
That may have been out of the scope of what you were doing with the
tutorial though.  I'm wading through the Gemstone programming guide
now so hopefully I'll figure it out soon.

As a Seaside tutorial, it kicks ass.  As a Seaside on Gemstone
tutorial, it's very good as well - I got the Los Boquitas app running
on Gemstone, although I was not able to use the version of Gemtools
you did.  I think you used 2.4 and the only version I could find was
2.3.1.  As a Seaside *with* Gemstone tutorial I found it lacking.

Just a little constructive (I hope!) feedback.  Again, thank you for
the excellent tutorial.

Pat
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

For a long time I've been using submitFormNamed: with anchors using  
Seaside 2.6.  This has worked well for me but now that I've switched  
to Seaside 2.8 it doesn't work reliably.  I tried this with both IE  
and Safari and neither works.

Am I supposed to do something different with 2.8?  The funny thing is  
that sometimes it works, but other times not.  For example I'll put a  
breakpoint in a callback for one or more widgets on the page.  Then  
I'll interact with some widgets on the page and click on the anchor.  
Sometimes the callback will get called, but most of the time not.

Trying the WALinkSubmitTest by typing a new value into the field works  
with 2.6, but not with 2.8.  Is this a known bug, and is there a fix?

Of course if I use submit button it always works, but I need to be  
able to support anchors.

Thanks,

-Carl Gundel
http://www.runbasic.com
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On May 15, 2009, at 3:08 PM, Pat Maddox wrote:

> I had hoped to learn more about Gemstone and how to use it within
> Seaside, since I've never used Gemstone (or anything like it) before.
> That may have been out of the scope of what you were doing with the
> tutorial though.  I'm wading through the Gemstone programming guide
> now so hopefully I'll figure it out soon.

In a sense, if you can port a Seaside application from Squeak to  
GemStone and have it run with minimal changes, then the complexity and  
sophistication of GemStone has been effectively masked. On the other  
hand, there are some things like indexes that are new and  need  
explanation. Nothing is really "out of scope," so much as out of time.  
I figured I'd make what I have available and see what feedback comes.

What would you like to know about GemStone? What should the next  
chapter include?

James Foster
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On Fri, May 15, 2009 at 3:40 PM, James Foster <[hidden email]> wrote:
The big question I had at the end was, "so are my objects being saved
in gemstone now?"  As far as I know, gemstone persists global objects,
so the list of events stored in LBEvents class ought to be
persisted...I think.  As someone coming from a completely different
environment (Rails), and VERY excited/interested in gemstone, it was
hard to believe that I deployed it on gemstone and got all the magic
that goes along with it.

In addition to answering that question, I'd like to see two things in
the next chapter.  The first is running multiple images off the same
gemstone data store.  If gemstone provides distributed object
persistence, I want to see it in action!  The second is gemstone
usage, such as sessions and indexes.  Now that I've got my app running
on gemstone, I want to understand how to make best use of the
platform.

How does that sound?

Pat
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On May 15, 2009, at 3:46 PM, Pat Maddox wrote:

Yes, that is all there is to it. Transparent persistence with GLASS!

> As someone coming from a completely different
> environment (Rails), and VERY excited/interested in gemstone, it was
> hard to believe that I deployed it on gemstone and got all the magic
> that goes along with it.

I actually have had similar reactions from others. One long-time  
Smalltalker at a recent workshop finished the exercises and then just  
asked in passing, "So when do we get to persistence?" When I  
reiterated that objects saved in a class instance variable are  
persistent he finally got it. There isn't any mapping of objects to  
the database; they just are persistent.

> In addition to answering that question, I'd like to see two things in
> the next chapter.  The first is running multiple images off the same
> gemstone data store.  If gemstone provides distributed object
> persistence, I want to see it in action!  The second is gemstone
> usage, such as sessions and indexes.  Now that I've got my app running
> on gemstone, I want to understand how to make best use of the
> platform.
>
> How does that sound?

Those are good topics. I'll work on that. What platform/configuration  
are you using? Are you running GemStone in the VMware virtual  
appliance or native on Linux/Mac? If you are running in VMware, then  
the default configuration includes three VMs providing FastCGI with  
Apache doing round-robin load balancing. Each request goes to a  
different VM, so the persistence is demonstrated.

James

> Pat
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On May 15, 2009, at 5:44 PM, James Foster wrote:

> repository." Did you have any trouble with steps 1 & 2? The  
> instructions are quite detailed.


doh!

i called them "LasBoquitas"..

probably my Socal roots are showing.


___________
sergio t. ruiz
network analyst
red red design
419.281.8483

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On Sat, May 16, 2009 at 12:15 AM, Carl Gundel <[hidden email]> wrote:
> For a long time I've been using submitFormNamed: with anchors using Seaside
> 2.6.  This has worked well for me but now that I've switched to Seaside 2.8
> it doesn't work reliably.  I tried this with both IE and Safari and neither
> works.

That should work, but requires that you include WAStandardFiles with
your application. If this is not the problem, then FireBug should be
able to tell you more.

> Am I supposed to do something different with 2.8?  The funny thing is that
> sometimes it works, but other times not.  For example I'll put a breakpoint
> in a callback for one or more widgets on the page.  Then I'll interact with
> some widgets on the page and click on the anchor.  Sometimes the callback
> will get called, but most of the time not.

Is the form id unique? Also the comment of the method says that it
breaks if you introduce custom URL parameters, but I guess you are not
doing that?

> Trying the WALinkSubmitTest by typing a new value into the field works with
> 2.6, but not with 2.8.  Is this a known bug, and is there a fix?

I cannot reproduce the problem in 2.8. WALinkSubmitTest works for me.

Please note, that the Javascript hacks like #submitFormNamed:,
#submitFormNamed:, #setFocus, #setSelectionFrom:to:, ... won't be
supported anymore in upcoming versions of Seaside. Instead use a
supported Javascript library like Scriptaculous.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside