[ANN][Squeak-dev Beta Image] Version 107

2007/4/16, Tim Johnson <[hidden email]>:
The message you get is not due to the universe system and we can't
change it. However, you point a problem with the VMMaker package: a
dependency is missing. Can somebody help me here? What is
KlattResonatorIndices and where do we find it?

--
Damien Cassou

On Apr 16, 2007, at 18:14 , Damien Cassou wrote:

It's for speech synthesis. There must be a Speech package somewhere.

- Bert -

El 4/16/07 12:52 PM, "Tim Johnson" <[hidden email]> escribió:

3.10 is the first "reduced" official image , following Pavel and my own
previous works.

One of the goal is easier the transition to smaller images as MinimalMorphic
or what comes in 3.11, that is more modular "base" .image what people grows
to what he / she wish using mechanism like Lex Universes.

At this moment, 3.10 base don't have some packages what once was part of
Squeak like Speech.

All Klatt classes was in Speech package, so you need load Speech first for
no complaints or contact VMMaker  owner for a new version what don't need
Klatt (wonder me why VMMaker need this ).

Edgar

 

On Apr 16, 2007, at 18:52 , Edgar J. De Cleene wrote:

Because some constants must be shared between the image and the plugin.

I suggested splitting up VMMaker into multiple packages before.  
However, in extreme, we would have one package per plugin, which  
would be cumbersome. No conclusion has been reached on this, so the  
status quo that VMMaker basically needs a Full Image remains.

- Bert -

Bert Freudenberg wrote:
> Because some constants must be shared between the image and the plugin.
>
> I suggested splitting up VMMaker into multiple packages before. However,
> in extreme, we would have one package per plugin, which would be
> cumbersome. No conclusion has been reached on this, so the status quo
> that VMMaker basically needs a Full Image remains.

A better answer is to factor the shared pools into their own packages
and have both, VMMaker as well as the actual package (Speech) depend on
the pools only.

Cheers,
   - Andreas

On 16-Apr-07, at 10:01 AM, Bert Freudenberg wrote:

To be picky/precise about this, VMMaker doesn't need Klatt installed  
UNLESS you are actually building the Klatt plugin. In general I guess  
we have to draw the line somewhere in our attempts to make everything  
happen magically and I stopped before working out a way of checking  
every dependency for each individual plugin.

>
> Because some constants must be shared between the image and the  
> plugin.

Exactly. The Balloon3D stuff was one example that caused much  
confusion some time ago.

>
> I suggested splitting up VMMaker into multiple packages before.  
> However, in extreme, we would have one package per plugin, which  
> would be cumbersome. No conclusion has been reached on this, so the  
> status quo that VMMaker basically needs a Full Image remains.

OK; we could break up VMMaker into many packages and try to make  
dependencies between them all. I guarantee that we would then get  
constant complaints about how complicated it is to load.

Although VMMaker usually gets included in a 'Full' image I would in  
general recommend starting from a basic image and loading the latest  
version of VMMaker; it's what I do and it's then only process I can  
possibly make time to evaluate. Any other way of doing things is at  
your own risk.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: PO: Punch Operator

2007/4/16, Edgar J. De Cleene <[hidden email]>:
> or contact VMMaker  owner for a new version what don't need
> Klatt (wonder me why VMMaker need this ).

+1. I really don't understand the link.

--
Damien Cassou

On 16-Apr-07, at 11:26 AM, Damien Cassou wrote:

> 2007/4/16, Edgar J. De Cleene <[hidden email]>:
>> or contact VMMaker  owner for a new version what don't need
>> Klatt (wonder me why VMMaker need this ).
>
> +1. I really don't understand the link.
The plugin code in VMMaker needs the constants relating to speech  
generation in order to generate the correct code. The Klatt class  
also needs those same constants. The constants are in a ClassPool.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Money can't buy love. But it CAN rent a very close imitation.

El 4/16/07 3:26 PM, "Damien Cassou" <[hidden email]> escribió:

> +1. I really don't understand the link.
>
> --
> Damien Cassou
>
I have one VMmaker and AppleScript weird package what don't need Speech.
Of course is for SqueakLight and I don't claim  what any could use it.
I see Bert and Andreas are talking about a partition, this sure become some
for learn of it.

Edgar

Damien Cassou wrote:
> 2007/4/16, Edgar J. De Cleene <[hidden email]>:
>> or contact VMMaker  owner for a new version what don't need
>> Klatt (wonder me why VMMaker need this ).
>
> +1. I really don't understand the link.
>
I think that this is a common packaging problem, for example Magma adds
methods to lots of classes but some images do not have all of those
classes. In most cases the error can simply be ignored. Basically it is
difficult to make a single package that automatically loads in 3.7, 3.8,
3.9 etc.

Keith

2007/4/16, Tim Johnson <[hidden email]>:
> Hello,
>
> I'll add one :)
>
> Trying to load VMMaker version 3.8b6 results in the following message
> (after FFI is loaded):

Corrected. Update your universe. Thank you for the report.

--
Damien Cassou

2007/4/12, Andreas Raab <[hidden email]>:
I sent a mail to Diego Gomez Deck for Video and Image Processing.
Markus Denker corrected Units. It should work now. Update your Universe.

Thank you for the reports.

--
Damien Cassou

tim Rowledge <[hidden email]> writes:
> To be picky/precise about this, VMMaker doesn't need Klatt installed
> UNLESS you are actually building the Klatt plugin. In general I guess
> we have to draw the line somewhere in our attempts to make everything
> happen magically and I stopped before working out a way of checking
> every dependency for each individual plugin.

It sounds like we want another package floating around, something like
"Full VM", which depends on VMMaker plus a plethora of standard
plugins.  VMMaker can then be minimal and not depend on anything but
the most core of packages.

Regarding how finely to divide the plugins, it is helpful to consider
the way the developers are organized, and to mirror that in the
division into packages.  For plugins that get a lot of attention and
maintenance from one particular person, it makes sense to put them in
their own packages.  For plugins that are basically finished and are
seeing very little maintenance, it makes sense to glop them into one
big package of standard plugins.


-Lex