[Gambas-user] a gambas3 component does not provide underlying components

[Charlie Reinl]

Am Samstag, den 16.07.2011, 00:40 +0200 schrieb Benoît Minisini:
> > Salut Benoit,
> > 
> > I'm porting actually a gambas2 application to gambas3.
> > 
> > The application consists of several parts. These parts can be ran as
> > executable, or used as component (now Library) in other applications.
> > 
> > Now I remarked that while gambas2, when using a component, which it self
> > uses a component, provides/know this underlying component.
> > 
> > gambas3 doesn't, you have to declare in every applications.
> > 
> > Here a small example :
> > 
> > application	| App_5	| App_4	| App_3	| App_2	| App_1
> > ----------------|-------|-------|-------|-------|------
> > component	| App_4	| App_3	| App_2	| App_1	|
> > gambas2		|	| App_2	| App_1	|	|
> > ----------------|-------|-------|-------|-------|------
> > libraries 	| App_4	| App_3	| App_2 | App_1	|
> > gambas3 	| App_3	| App_2	| App_1	|	|
> > 
> > 		| App_2	| App_1	|	|	|
> > 		| App_1	|	|	|	|
> > 
> > ----------------|-------|-------|-------|-------|------
> 
> I confirm the design problem.
> 
> As for native components, their dependencies is managed by the IDE, not at 
> runtime. As for libraries, nothing is done
> 
> This is not a good idea: if it is not really a problem for native components 
> (they are somewhat under my control), libraries are done by users, and so you 
> get the problem you described.
> 
> I must think to find a good solution...
> 

Salut,

may be I missed it, but how can I (we users) continue to use components
in gambas3 ?

  

-- 
Amicalement
Charlie