On Thu, Mar 11, 2010 at 10:47 AM, Igor Stasenko
<siguctua@gmail.com> wrote:
2010/3/11 Mariano Martinez Peck <marianopeck@gmail.com>:
> Hi folks. I was playing a bit with the ClassOrganizer stuff. I thought that
> class comments were in the image, but it seems they are kept in the
> .source.� Is this correct ?
>
> They are ALWAYS kept in the .sources?
>
> I know that the class of the instancia variable "classComment" in the
> ClassOrganizer can be Text, ByteString or even RemoteString. I though that
> only those who have RemoteString were in .sources� but it seems all are
> there. I am correct ? is this the desired behavior ?
>
The state of these things are bunch of hacks, added over a years and
really, really messy.
OK...thanks for the warning.
�
I presented some ideas about it in the past, but since it requires a
substantial efforts to make it done,
they weren't get past much the state of an ideas. :)
I would like to hear those ideas. What I want to do right now, is to be able to remove a lot of memory consumption that maybe they are not used under certain circumstances like embedded devices. For example, I would like to remove all the method categories or put a blank space. Or to remove the class comments (I though they were in the image). In summary, for those applications that can live with that, I would like to remove unnecessary data from ClassOrganization so that to low memory footprint.
�What do you think?
Cheers
Mariano
> Thanks!
>
> Mariano
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
--
Best regards,
Igor Stasenko AKA sig.
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project