Re: [Pharo-project] about creating a task for the next milestone
Stef, I am very interested in serializers, but I (right or wrong) do not have good feeling about ReferenceStream and friends. When I last tested them (a while back), the output was BIG, and I was not comfortable about the location[*] of the conversion methods, nor with the timing: as usual, if I goof, please raise an error, don't put browsers in front of my end users =:0 That said, I am expecting to port some of my code, and completely rewrite other parts using things like Magritte. A variation on ReferenceStream might turn out to be of use to me. However, I am also considering something, again along the lines of Magritte (if not part or an extension thereof) to make my persistence independent of the internal representation of objects. With extensive unit testing, I think I could make that work, and should at least investigate it. Dolphin's STB and in particular its handling of layout changes is pretty good. I also found some things to like about SIXX and might try to blend the two. However clunky, I want to get my BibTeX system up and running, and then I will probably turn attention to an out-filer that writes code that Pharo can read. Some gnashing of teeth later, I will start to port sub-systems, redesigning some as I go. Bill [*] IIRC, they end up in ReferenceStream itself, rather than in the class that "needs help." It struck me as asking for trouble. Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab@anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029
stephane.ducasse@inria.fr 07/11/08 3:34 AM >>> Hello guys
I was reading the class ReferenceStream and sisters/mother. The ones that are in System-Object Storage. I think that these classes are important. They have a good class comments, even if we could improve. I would really like to use them as a test-bed for a canonical documentation effort: - unit tests - simple how to use I would also like to see if they can be rebuild on top of Nile. So I would like to know if some of you are interested working on this task. stef _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Jul 12, 2008, at 6:11 AM, Bill Schwab wrote:
Stef,
I am very interested in serializers, but I (right or wrong) do not have good feeling about ReferenceStream and friends. When I last tested them (a while back), the output was BIG, and I was not comfortable about the location[*] of the conversion methods, nor with the timing: as usual, if I goof, please raise an error, don't put browsers in front of my end users =:0
Indeed :)
That said, I am expecting to port some of my code, and completely rewrite other parts using things like Magritte. A variation on ReferenceStream might turn out to be of use to me. However, I am also considering something, again along the lines of Magritte (if not part or an extension thereof) to make my persistence independent of the internal representation of objects. With extensive unit testing, I think I could make that work, and should at least investigate it.
Dolphin's STB and in particular its handling of layout changes is pretty good. I also found some things to like about SIXX and might try to blend the two.
However clunky, I want to get my BibTeX system up and running, and then I will probably turn attention to an out-filer that writes code that Pharo can read. Some gnashing of teeth later, I will start to port sub-systems, redesigning some as I go.
I used SIXX (in fact Smallwiki had an implementation using SIXX). But I still would like to have some other nice solution like ImageSegments and smartRefStream
Bill
[*] IIRC, they end up in ReferenceStream itself, rather than in the class that "needs help." It struck me as asking for trouble.
Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254
Email: bschwab@anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029
stephane.ducasse@inria.fr 07/11/08 3:34 AM >>> Hello guys
I was reading the class ReferenceStream and sisters/mother. The ones that are in System-Object Storage.
I think that these classes are important. They have a good class comments, even if we could improve. I would really like to use them as a test-bed for a canonical documentation effort: - unit tests - simple how to use
I would also like to see if they can be rebuild on top of Nile. So I would like to know if some of you are interested working on this task.
stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I used SIXX (in fact Smallwiki had an implementation using SIXX). But I still would like to have some other nice solution like ImageSegments and smartRefStream
I have as well and still do for some things, but sixx files are huge compared to ReferenceStreams or SmartRefStreams and much more expensive generate so as far as I can see there's currently nothing able to compete with ReferenceStreams. SmartRefStream probably does need rewritten a bit to throw exceptions instead of prompting the user, but otherwise it seems to work rather well. Ramon Leon http://onsmalltalk.com
participants (3)
-
Bill Schwab -
Ramon Leon -
Stéphane Ducasse