IconFactory - utility for creating icons in Pharo

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: IconFactory - utility for creating icons in Pharo

kilon.alios
"SVG is human readable (XML based), no ?"

yeap , XML format , nothing special. Athens has an importer for them.

"If they are not too large, it might even be quite useful to store them as strings in the image, although I do agree this is not scalable in the end. (But Seaside uses this mechanism to store real images in the image, and that works very well during development, in the sense that it is convenient)."

oh yes it suits me to keep them small so they can be more modular so as you said to compose and decompose them easily . And if it works well for you, should work well for me ;)
Reply | Threaded
Open this post in threaded view
|

Re: IconFactory - utility for creating icons in Pharo

Ben Coman
In reply to this post by kilon.alios


On Mon, Apr 6, 2015 at 2:16 AM, kilon alios <[hidden email]> wrote:

"Maybe we are not talking about the same thing ?"

We do I just brought an alternative. My initial question is why this data is not stored inside a Collection and instead individual methods are preferred. 

But now that I thought it through I understand in practice would not make much difference. And as you said methods are already browsable, Collections are not.


Also methods can be packaged and distributed using Monticello.  Live Collections can not.
cheers -ben 
Reply | Threaded
Open this post in threaded view
|

Re: IconFactory - utility for creating icons in Pharo

kilon.alios
yes exactly

On Mon, Apr 6, 2015 at 1:18 AM, Ben Coman <[hidden email]> wrote:


On Mon, Apr 6, 2015 at 2:16 AM, kilon alios <[hidden email]> wrote:

"Maybe we are not talking about the same thing ?"

We do I just brought an alternative. My initial question is why this data is not stored inside a Collection and instead individual methods are preferred. 

But now that I thought it through I understand in practice would not make much difference. And as you said methods are already browsable, Collections are not.


Also methods can be packaged and distributed using Monticello.  Live Collections can not.
cheers -ben 

12