Hello Guys!
Can somebody explain me how to load monticello in gemstone/s through topaz? As i can understand after that step you can download other packages via monticello. Oleg |
Oleg,
What version of GemStone are you looking at? Since about version 2.2.2 of the 64 bit product (June or July of this year), we have been shipping a seaside directory that contains a readme which has instructions for taking a virgin GemStone repository and loading Monticello and Seaside into it. If you have downloaded a copy of GemStone from our website, it is likely to be version 6.x, which is our 32 bit product for which we do not have Monticello/Seaside support. If you have 64 bit hardware and are interested in trying our GLASS beta, send mail to gssbeta at gemstone.com with a request. The GLASS VMWare appliance has GemStone pre-installed (including Monticello and Seaside), so it's by far the easiest way to come up to speed. Hope this helps, Dale Oleg Richards wrote: >Hello Guys! > >Can somebody explain me how to load monticello in gemstone/s through topaz? >As i can understand after that step you can download other packages via >monticello. > >Oleg > > _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hello Dale!
I'm using MacBook with Intel Core Duo. So i think it's 32-bit. Can i install a virtual machine with 64-bit to experement? As for production environment i have a 64-bit environment. But i want to try before go to production. What will you recommend me? And one specific question: I've read many articles about GLASS. But how will persistence work? For example if i want to store data in Magma or GOODS i just need to store a dictionary which is root for all my data. Where should i store my root in GemStone. I've read a documentation but can't find place. Can you give me an example. Oleg
|
In reply to this post by Oleg Richards
Oleg, _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
I have only Core Duo, not Core 2 Duo :(. So i am afraid that i can't try GLASS..
Can i run through emulation in VMWare?
|
>>>>> "Oleg" == Oleg Richards <[hidden email]> writes:
Oleg> I have only Core Duo, not Core 2 Duo :(. So i am afraid that i can't try Oleg> GLASS.. Can i run through emulation in VMWare? GLASS is *only* a VMWare Appliance already. You need VMWare Fusion to even try it. There's no Gemstone for native OSX anyway, even though all the other parts would have OSX equivalents. Well, "Linux" doesn't have an OSX equivalent, except for OSX. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[hidden email]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
I know it... I wanted to ask: Can i run 64bit linux in VMWare Fusion on my mac?
|
In reply to this post by Oleg Richards
I guess not, older core duo is not 64 bit and there's no software simulation for it. Newer core 2 duo is fine though. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Understand.. But thats very bad. Why should i have 64-bit environment just to develop my application. In production - sure.. But for development.. I also have 2 latest toshiba qosmio notebooks. They are 1.5 year old. I even can play crysis.. But can't run a smalltalk program. I understand that i can develop in squeak. But here i can see problem again: I can write neither russian nor spanish characters under my mac.. If i close my eyes on it and will use english - how can understand how to install my application under gemstone and how to apply it to its specifics. How can i such expensive thing without understanding what it it?
|
In reply to this post by Oleg Richards
Oleg,
As others have mentioned you need to have the 64bit hardware to run GemStone. There would be a significant amount of work for us to port our 64bit product to run on 32 bit architectures, so we won't be heading in that directions. We have recently announced a non-commercial version of GemStone 6.2 is available for the Mac (Tiger on x86). GemStone 6.x is the 32 bit line of our server. This is an option that could be followed. On the other hand, if you are developing an application (with plans to deploy on GemStone), then it is actually a very good strategy to develop in Squeak and deploy in GemStone. Our first GLASS customer to go into production did just that. They started developing their application in Squeak long before we even a beta ready for GemStone (in fact they did their development using Seaside2.7), then when we had our beta ready they ported their application from Squeak to GemStone (using Seaside2.8). As Boris has mentioned, taking advantage of GemStone persistence is as simple as storing things in class variables. Anything that is kept alive in your Squeak image will be kept alive (and persisted) in GemStone. In a Seaside application, the framework does the commits, so there is literally no need to change you application when you move it to GemStone. A good set of unit tests is recommended, but then thats a good idea no matter what your deployment plans are. You _do_ have to be more aware of concurrency issues in a GemStone application than you do in an image-based application. Intra-session data structure access is protected by object locking in the framework, but for data structures that may be updated by multiple sessions (places where you would be using Semaphores to protect data access in a Squeak Seaside application) you will likely need to use some GemStone-specific reduced conflict classes. I have plans to write a blog post to cover the options in more detail - after today's discussion, I will probably write it sooner rather than later. In general, you will be doing very little GemStone/persistence-specific code in a Seaside application that is targeted to be deployed in GemStone. In the end, I think it is very possible (and even desirable) to develop your Seaside app in Squeak with plans to deploy in GemStone. I would think that you can get away with doing quite a bit of development, before really needing to get access to GemStone and 64 bit hardware. Dale _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Yeah, you know a little article on developing for Gemstone without
Gemstone would be really useful for people considering making the jump. At least folks could be getting ready to adopt. -Todd Blanchard On Dec 14, 2007, at 10:41 AM, Dale Henrichs wrote: > Oleg, > > As others have mentioned you need to have the 64bit hardware to run > GemStone. There would be a significant amount of work for us to port > our 64bit product to run on 32 bit architectures, so we won't be > heading in that directions. > > We have recently announced a non-commercial version of GemStone 6.2 > is available for the Mac (Tiger on x86). GemStone 6.x is the 32 bit > line of our server. This is an option that could be followed. > > On the other hand, if you are developing an application (with plans > to deploy on GemStone), then it is actually a very good strategy to > develop in Squeak and deploy in GemStone. Our first GLASS customer > to go into production did just that. They started developing their > application in Squeak long before we even a beta ready for GemStone > (in fact they did their development using Seaside2.7), then when we > had our beta ready they ported their application from Squeak to > GemStone (using Seaside2.8). > > As Boris has mentioned, taking advantage of GemStone persistence is > as simple as storing things in class variables. Anything that is > kept alive in your Squeak image will be kept alive (and persisted) > in GemStone. In a Seaside application, the framework does the > commits, so there is literally no need to change you application > when you move it to GemStone. A good set of unit tests is > recommended, but then thats a good idea no matter what your > deployment plans are. > > You _do_ have to be more aware of concurrency issues in a GemStone > application than you do in an image-based application. Intra-session > data structure access is protected by object locking in the > framework, but for data structures that may be updated by multiple > sessions (places where you would be using Semaphores to protect data > access in a Squeak Seaside application) you will likely need to use > some GemStone-specific reduced conflict classes. I have plans to > write a blog post to cover the options in more detail - after > today's discussion, I will probably write it sooner rather than later. > > In general, you will be doing very little GemStone/persistence- > specific code in a Seaside application that is targeted to be > deployed in GemStone. > > In the end, I think it is very possible (and even desirable) to > develop your Seaside app in Squeak with plans to deploy in GemStone. > I would think that you can get away with doing quite a bit of > development, before really needing to get access to GemStone and 64 > bit hardware. > > Dale > > > _______________________________________________ > 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 |
In reply to this post by Dale
Dale! Thank you for the time for explain. Currently i am developing using visual works in parallels. First version of my application has been already in production windows server 64bit for 2 months. In vw again. I like squeak development, especially Ramons image. But i cant use it. I need to type unicode characters using keyboard, or even be sure that i can load them. My financial reporting system works in huge corporation and i have many requests from others to show it. I need persistence. Now i have my homegrown system, but i think that if there is something better i can recommend customers to buy it. There is another problem - i did not heard about gemstone specialists here. So what will you recommend? |
Oleg,
I am not too familiar with character encoding issues with GemStone ... I think that we are probably pretty close to Squeak in that regard for the moment (i.e., we can handle storing anything in the byte arrays, but when it comes to intelligent manipulation of characters ByteArray and String don't cut it). We have DoubleByteString classes that I think would help here , but I haven't worked with integrating them into Seaside. It is something that we planned to provide for in the future, but haven't spent much time on up to now. Using GBS and VW just might be the best combo for the near term ... Why don't you contact Monty Williams at GemStone, I'm sure that something can be worked out. Dale Oleg Richards wrote: > Dale! Thank you for the time for explain. Currently i am developing using > visual works in parallels. First version of my application has been already > in production windows server 64bit for 2 months. In vw again. I like squeak > development, especially Ramons image. But i cant use it. I need to type > unicode characters using keyboard, or even be sure that i can load them. My > financial reporting system works in huge corporation and i have many > requests from others to show it. I need persistence. Now i have my homegrown > system, but i think that if there is something better i can recommend > customers to buy it. There is another problem - i did not heard about > gemstone specialists here. So what will you recommend? > _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |