seaside February 2012

seaside@lists.squeakfoundation.org

38 participants
34 discussions

Start a nNew thread

(no subject)
by Robert Sirois 29 Feb '12

29 Feb '12

...Make alot of money using your computer http://ponto.kelly-systems.com.br/service.link.php?bolink_friend_id=83yt2

1 0

flyover popup content position
by bobn＠rogers.com 29 Feb '12

29 Feb '12

Hello, I'm trying to learn techniques for showing flyover content, where something pops up while your mouse moves over a component. A common approach seems to be to build a hidden component and then use javascript to make it visible. I've got that working, using code like this... onMouseOver: (html jQuery ajax script: [:s | s << (html jQuery id: flyoverId) cssAt: 'top' put: ((html jQuery id: cellId) positionTop). s << (html jQuery id: flyoverId) cssAt: 'left' put: ((html jQuery id: cellId) positionLeft). s << (html jQuery id: flyoverId) show]); onMouseOut: (html jQuery ajax script: [:s | s << (html jQuery id: flyoverId) hide]); ...where 'cellId' is the id of a table cell. But this example shows the popup content over the table cell. What I need next is to adjust the 'left' position by adding '(html jQuery id: cellId) width' to the positionLeft value. Easy enough to do with javascript, but how is this done with Seaside jQuery? Also, are there other examples of how to show flyover content using Seaside jQuery? And what about popup content that you can interact with? i.e. content that says rendered as you move your mouse over it. Thanks for any help, Bob

3 2

ESUG SummerTalk - Fuel, binary object serializer
by Martin Dias 28 Feb '12

28 Feb '12

Hi folks. I am really happy to announce that ESUG is sponsoring me for Fuel development through the ESUG SummerTalk. I am Martin Dias, a student at Buenos Aires, Argentina. The idea behind this SummerTalk is to implement Fuel, a binary, fast and general-purpose object graph serializer in Pharo<http://www.pharo-project.org/>. It is based on VisualWorks' Parcels ideas. Actually, the project has already started since several months. Tristan Bourgois and I started with the project while doing an internship with RMoD, INRIA <http://rmod.lille.inria.fr/web/pier>. Since a couple of months, Mariano Martinez Peck <http://marianopeck.wordpress.com/> joined the team, and now he is the official mentor in the SummerTalk. ESUG website for SummertTalk: http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011 The website with all the necessary information is here: http://rmod.lille.inria.fr/web/pier/software/Fuel It even includes slides explaining the algorithm. In addition, a paper is in progress. For the moment, Fuel already provides the following features: - Fast pickle format. It is much faster to materialize than to serialize. - Correctly support class reshape (when the class of serialized objects has changed). - Serialize ANY kind of object. For the moment there is no object to our knowledge that we cannot serialize and materialize. - Be able to completely serialize classes and traits (not just a global name). - Support cycles and avoid duplicates in the graph. - Integration to Moose <http://www.moosetechnology.org/> with an extension to export and import their models. - Detection of globals: for example if you serialize Transcript, it is not duplicated and instead managed as a global reference. - Solve common problems like Set rehash. - Buffered writing: we use a buffered write stream for the serialization part (thanks Sven!). - No need of special support from the VM. - Try to have a good object oriented design. - Well tested (about 120 tests, for the moment). - Large set of benchmarks (even benchmarks for Moose extension). And of course, there are a lot features for the future. You can see some of them in the website and some in the issue tracker: http://code.google.com/p/fuel/issues/list We really appreciate all kind of feedback and comments. If you want to try it, check in the website how to do it. It is extremely easy. Once again, I want to thank a lot to ESUG for sponsoring the project. I plan to create a "news" section in the website with some RSS. I will keep you informed. Best regards, Martin

5 12

(no subject)
by Robert Sirois 28 Feb '12

28 Feb '12

...Make serious money online http://rezocomproduction.fr/service.link.php?ofolucky=45h2

1 0

Re:0
by Robert Sirois 27 Feb '12

27 Feb '12

..Single mom makes real money working from home http://srouji-trading.com/service.link.php?wiyahoo_id=51qu4

3 3

Is the community repository dead?
by Sebastian Sastre 25 Feb '12

25 Feb '12

Hi guys, I was about to commit some packages under MIT in squeaksource but it seems that squeaksource.com is not allowing people to add projects anymore. When you click on "Register Project" instead of the usual form, it says "On this server, only the administrator can create new projects!" Is that expected now? If so, we did that not even telling people about that in a blog post suggesting what to do? Some told me to stop using it and start using ss3.gemstone.com instead. So I've registered my user and created a repo there but my commits are failing (timeout when trying to write) Struggling with this will kill this community please help sebastian o/

3 6

Magritte 3
by Nick Ager 24 Feb '12

24 Feb '12

Hi, I'm pleased to announce a new version of Magritte - Magritte 3. The rational for Magritte 3 is eloquently described by Lukas in his mail below. The work on Magritte 3 was started by Esteban and completed by myself. I've created a screen-cast which describes: - the rational for Magritte 3 - the refactorings available to ease the transition from Magritte 1 or 2 to Magritte 3 - A walk-through of updating a sample from Magritte 2 to Magritte 3. The screen-cast is on vimeo at: http://vimeo.com/37032840 The sample used in screen-cast can be downloaded as: Gofer it > url: 'http://ss3.gemstone.com/ss/MagritteMagic'; > package: 'ConfigurationOfMagritteMagic'; > load. > > (Smalltalk at: #ConfigurationOfMagritteMagic) load. The slides used in the screen-case can be viewed on slideshare at: http://www.slideshare.net/nickager/magritte3 Enjoy Nick ---------- Forwarded message ---------- From: Lukas Renggli <renggli(a)gmail.com> Date: 17 November 2010 17:21 Subject: Re: Providing lookup environment for descriptions To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch> The way Magritte builds descriptions by default has become quite a nuisance. I think that at some point Magritte should be improved in that regard. I wrote a proposal this summer for how to proceed, but of course I had to finish my writing and never actually found the time to implement it: -------------------- I propose to perform the following (non-backward compatible) changes in the Magritte 2 code-base to resolve some major annoyances and issues that keep on reoccurring: - Move descriptions from class-side to instance-side. This resolves various issues such as cache-invalidation, instance specific descriptions, dynamic descriptions, context dependent descriptions, etc. Furthermore the descriptions will be closer to the code they describe and it will be possible to describe class- and instance-side of an object, not just the instance-side. - Rename the method #description as the default entry point into Magritte to #magritteDescription. This avoids common problems where the domain model already defines such a method. - Instead of using a naming convention for description methods, use a pragma called <magritteDescription> to annotate the methods. And to extend and change existing descriptions use <magritteDescription: aSelector>. Finally all Smalltalk implementation reached a consensus of pragmas that can be safely used cross-platform. All in all the "new" Magritte would look like in the following example. Imagine a shop item with the accessor #place: Item>>place ^ place Item>>place: aString place := aString The meta-description is defined on the instance-side and annotated. It can refer to itself for the possible places: Item>>placeDescription <magritteDescription> ^ MASingleOptionDescription new options: self possiblePlaces; label: 'Place of Item'; accessor: #place; yourself Class extensions can modify a description using: Item>>placeDescriptionXmlStorage: aDescription <magritteDescription: #placeDescription> ^ placeDescription xmlTag: 'xname' Since these changes are not backward compatible I'll try to provide automatic refactorings for most parts. Moving existing code to the new codebase will certainly cause some problems, but in the long run I believe this to be a much better approach than the current one. If people have any feedback, concerns or other changes that would be important in the same run I am happy to hear them.

9 14

re: Enterprise Software V Ecommerce [in smalltalk/seaside/cincom]
by Stephan Eggermont 23 Feb '12

23 Feb '12

I've had a stressfull day, so would you mind if I put this a bit provocative? The providers of the .NET and java infrastructure are in the business of selling databases. That is why their programming environments are not updated to perform well on modern systems with lots of memory and cores, unlike their database systems. Garbage collectors and collection libraries are not suitable for modern machines. The assumption that all objects are in memory is not very scalable. But Moore's law makes it more and more scalable. Stevens assumptions are very outdated. A mid-end database machine now has 48 cores and 512 GB of ram and costs about 25K (e.g. Dell Poweredge r815). If you take a look at the architecture used by Facebook, Twitter etc. for their non-analytical systems it is obvious that they are using very inefficient workarounds for not being able to work ram-based (memcached). If you cannot keep all objects in ram, it might make sense to have placeholders for large ones. In the Outlook example, keeping the attachments on disk is likely to solve the space problem. If those placeholders provide enough information for searching, sorting and matching, your only problem is getting the attachments from disk fast enough. SSD provides an answer there (or a NoSQL document store) Gemstone looks like an obvious match for this. 64 bit support of the other smalltalks is less well developed. If you need to scale beyond one machine/vm you have to think on how to partition your object space. Look for aggregates in the domain driven design literature. And you might be interested in command-query separation. Real scalability of course comes with a p2p architecture instead of a centralized model. The nice thing about building the UI first is that you then know what your architecture should support. Database first is unlikely to achieve innovative results. And relational database first is going to lead to lots of duplication because of the bad performance of relational databases in actually using relations. Stephan

1 0

Enterprise Software V Ecommerce [in smalltalk/seaside/cincom]
by dirk newbold 23 Feb '12

23 Feb '12

Hi all, I’m a relative newbie (4 years) to programming and seaside, who partnered up with some “old hands” (smalltalk/seaside is my first and only language). Initially we developed an Ecommerce (Istazaar) fashion platform for designers to maintain their collections. We stagnated last year due to the time restraints on the “old hands” and I then began developing a web based Enterprise Software (Vivport) platform for document-management/knowledge-management/emails/tasks. We now have two ventures at relatively equal stages of development. I believe the Enterprise Software (Vivport) platform is the more innovative however, now that Steve (one of the “old hands”) has some time again he has been able to review its development (which unfortunately I built unsupervised) and has major concerns in relation to deploying this venture. Instead of building the database; then building middleware, then UI; I’ve basically just built a UI, Steve’s concerns with the outcomes of this development process are outlined in his email to me below. We were wondering if the smalltalk/seaside community has any views on Steve’s concerns below that may influence our decision on which venture to proceed with. The platform has been developed to freely change between the user’s personal account and their company(ies) account. The personal accounts are free so we would be attempting to server many users. Any advice in relation to users/image, persistence, database, general deployment etc for this type of venture (essentially a beefed up gmail/cloud environment) would be greatly appreciated. Thanks for your time. Cheers, Dirk ---------- Forwarded message ---------- From: Steven Berryman <Steven(a)berrymanelectrical.co.uk> Date: Sat, Feb 18, 2012 at 6:07 AM Subject: RE: Vivport V Istazaar To: dirk newbold <dirkdirk(a)gmail.com> Dirk, As mentioned I’m concerned with the approach you have taken with Vivport and in one way this technology can lead you into a false sense of how easy things are (trust me you couldn’t have done it in .NET or java without infrastructure). The difference with the ecommerce site is that there is little shared data and I knew that the only real issue was storing users but that would be a simple mapping issue to a table. Even the registered objects were designed to make storing in the database easier so objects didn’t directly hold onto a registered object. What you have built is a very complicated network of objects for the benefit of the UI which for a prototype is great but would never work in the real world. The type of project you are building with Vivport is infrastructure and in one way the last thing you should have done is the UI. One system I worked on had 3-4 months of designing the infrastructure before a line of code was written. The problem you have is that you have assumed that all objects would be in memory and are accessible via threads and this just isn’t possible. If I look at my local Microsoft exchange server it’s currently 50GB for 5 users and the machine only has 4GB of ram so not only do you need to deal with large amounts of data but you have not addressed any multi-threading issues. For example Smalltalk provides structures such as SharedQueue to deal with any shared data in the memory and I’m guessing you didn’t use these? When everything is in memory the world is very easy but for a system like yours you would need to start with the database and design the schema. Most searches would be done directly in sql (assuming you are using a relational database) so that way you reduce the amount of data going to the client. So when you open up Microsoft Outlook it will run a query on the database to get your inbox and the email headers so you don’t pull large amounts of data across the network. As you start to click on emails it will pull the data over as required. So here is an example to show multi-threading issues (I have not used your code but I’m sure you get the point) Lets’ assume you have a folder with 10 items Dirk - actions Danny - actions folder items do: [ :item “goes through this loop twice” delete the last item in the folder “code falls over because the last element in the collection does not exist.” ] I’m sure you could try something like the above but you would need to put in a break point in the Dirk loop so you could then go in and to the removal from a different session. Now imagine the same thing with 5,000 users logged into your server all running threads across your code. Your code would have to be thread safe and this is not a simple task especially trying to do it on code not designed that way from the beginning. You could end up locking up all the other sessions if you don’t carefully design and keep your critical sections to a minimum. If you are using collections that are hashed they will fail in very strange ways if you have other threads removing or adding items as you are iterating through the collection. Basically in the ecommerce site we could sort of ignore the shared data issue as we shared very little data between sessions. Also you have added features that would be very expensive when using databases. For example the running man relies on the status of some piece of data and of course when everything is in the same memory space this is easy. In a database you would have to cross a transaction boundary and even the fastest database servers we have (costing 200k per server) you would be lucky for a single transaction to take between 1-10 milliseconds (costly when you scale up users and make too many database calls). This is why Microsoft exchange works the way it does as you can imagine how slow it would be if 5000 people logged into the server at the same time. So for most document management systems they would have a large database at the back end and all the searches would be done as stored procedures that could be based on some proprietary algorithm and none of this would be done in the language itself such as Smalltalk. Until you have a database schema designed you can’t even think about the UI. If you want to prove to yourself then try and create 100,000 users all with about 10MB of data and test to see if it works. See if you can log in a few sessions and send emails around. With the ecommerce site I could imagine how to add a database at the backend because it would be very simple. I would have no idea how you get this into a database even if you used an object database you would still need a defined object model. It’s also the reason why I liked the ecommerce site as it would be simple from the database end as it would only contain users, basic static data and designer’s data. Also I can see how we could have multiple servers to handler more traffic with the ecommerce site but would have no idea how we could do the same with your design. Hope this makes sense. Let’s catch up next week. Steve

4 4

Incorrect position en JQDialog
by Gastón Dall' Oglio 21 Feb '12

21 Feb '12

Hi all. I guess that the JQWDialog is inconsistent informing the position of dialog in position: and onDragStop: methods. I check in Seaside-3.0.6-OneClick and http://jenkins.lukas-renggli.ch/job/Seaside%203.0/lastSuccessfulBuild/artif… To reproduce the problem: 1) Add position instance variable to JQUiFunctionalTest and modify >>renderWindowOn: to look like this : script: (html jQuery new dialog position: position; "line added" onDragStop: (html jQuery ajax callbackDraggable: [ :event | " line added" position := (event at: #position). position inspect ]); "line added" title: 'Vegetables'; autoOpen: false; addButton: 'Close' do: html jQuery new dialog close); with: [ html unorderedList list: self vegetables ]. 2) Go to http://localhost:8080/javascript/jquery-ui/dialogwidget 3) Press button Open Window and move de Dialog to bottom-left corner. 4) Refresh the page and press again button Open Window The dialog show with de left-top attributes changed each other. If you see the position in inspector that is opened when drag stop, the callbackDraggable: inform top@left, but in the comment of JQDialog>>position: method say that left@top are expected as parameter: " 2) an array containing an x,y coordinate pair in pixel offset from left, top corner of viewport (e.g. [350,100]) " The fact, if you change the coordinates of position with transposed the problem is solved: onDragStop: (html jQuery ajax callbackDraggable: [ :event | position := (event at: #position) transposed. position inspect ]); And the same problema in onResizeStop with the position (I have split the coordinates for size). Add width and height ivars and next code for reproduce problem: onResizeStop: (html jQuery ajax callbackResizable: [ :event | position := event at: #position. width := (event at: #size) x. height := (event at: #size) y ]); Regards.

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside February 2012