<br><br><div class="gmail_quote">On Jan 24, 2008 7:02 PM, Jason Johnson <<a href="mailto:jason.johnson.081@gmail.com">jason.johnson.081@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Jan 23, 2008 11:50 PM, Michael van der Gulik <<a href="mailto:mikevdg@gmail.com">mikevdg@gmail.com</a>> wrote:<br>> <a href="http://gulik.pbwiki.com/Namespaces" target="_blank">http://gulik.pbwiki.com/Namespaces
</a><br>><br>> There is code available on the 3.10 Package Universes that I'm currently<br>> using to varying degrees of success.<br>><br>> Gulik.<br><br></div>Well, this isn't what I had in mind [1], but it looks quite good I
<br>must say. Are you planning to keep this namespace system as a<br>separate entity from "User" and the other concepts you mentioned? </blockquote><div><br><br>Yes. Namespaces are just another component of my Unnamed Grand Project[1][2].
<br><br>[1] <a href="http://gulik.pbwiki.com/Unnamed+Grand+Project">http://gulik.pbwiki.com/Unnamed+Grand+Project</a><br>[2] Naming suggestions welcome.<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The<br>namespace part seems like potentially a good candidate for adoption to<br>me. Do you have any pointers to projects using it, to get a feel for<br>how well it's working in practice?</blockquote><div><br><br>It won't be a candidate for adoption until the implementation is stable and widely used.
<br><br>As of yet, I'm only beginning to use my own tools to make actual namespaced projects. If you load the namespace tools from the 3.10 package universe, it automatically generates some demo namespaces (Kernel, Collection), but I wouldn't recommend using these in your own projects except for playing around. I'm currently porting Kernel and Collection to namespaces now.
<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">[1] It's actually not so far away though. What I was envisioning was<br>
a system that behaves mostly like now, but "module classes" or<br>"component classes" (classes that are made up of *classes* and methods<br>instead of just methods) would be visible in the main dictionary and
<br>none of the classes that make one up would be visible. The only way<br>one could be referenced outside is if the "module class" returned on<br>from a method. There would probably be on the code browser when
<br>looking at such a class that lets one "zoom in" to see inside it and<br>make changes.</blockquote><div><br><br>This sounds like a facade pattern to me.<br></div></div><br>I'm considering making namespaces able to be "private". You could then make a facade object which was the only class that has access to that namespace.
<br><br>Gulik.<br clear="all"><br>-- <br><a href="http://people.squeakfoundation.org/person/mikevdg">http://people.squeakfoundation.org/person/mikevdg</a><br><a href="http://gulik.pbwiki.com/">http://gulik.pbwiki.com/</a>