24 Jun
2008
24 Jun
'08
10:35 p.m.
Hi,
I would know if there is a mean to only import in a MooseModel the selected
packages in the MooseBrowser?
For example, when I import the bundle Moose in Moose Browser, I would only
have in the MooseModel the packages of the bundle.
I hope it was clear.
Romain
24 Jun
24 Jun
11:07 p.m.
On Jun 24, 2008, at 10:35 PM, Romain PEIRS wrote:
Hi,
I would know if there is a mean to only import in a MooseModel the
selected packages in the MooseBrowser?
For example, when I import the bundle Moose in Moose Browser, I
would only have in the MooseModel the packages of the bundle.
You have to do a filter at the end because a model has to create stub
and the stub are often in other packages.
I hope it was clear.
somehow :)
Romain
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
17 Jul
17 Jul
3:14 p.m.
do not forget that the importer will import also all the parent
packages/bundles/namespaces of the imported package/bundle/namespace.
for example when you import Moose bundle which is packaged in
MooseDevelopment bundle and this last is packaged in Smalltalk bundle,
MooseDevelopment and Smalltalk bundles will be imported also. They
will not be stubs because they dont contain stub classes. In this case
they will be empty (each definedClasses isEmpty), so you can remove
such packages/bundles.
hani
On 24 juin 08, at 23:07, Stéphane Ducasse wrote:
On Jun 24, 2008, at 10:35 PM, Romain PEIRS wrote:
Hi,
I would know if there is a mean to only import in a MooseModel the
selected packages in the MooseBrowser?
For example, when I import the bundle Moose in Moose Browser, I
would only have in the MooseModel the packages of the bundle.
You have to do a filter at the end because a model has to create stub
and the stub are often in other packages.
I hope it was clear.
somehow :)
Romain
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3:46 p.m.
On Jul 17, 2008, at 3:14 PM, Univ-SAVOIE wrote:
do not forget that the importer will import also all
the parent
packages/bundles/namespaces of the imported package/bundle/namespace.
for example when you import Moose bundle which is packaged in
MooseDevelopment bundle and this last is packaged in Smalltalk bundle,
MooseDevelopment and Smalltalk bundles will be imported also. They
will not be stubs because they dont contain stub classes.
may be we should have a good example and see if how we can mark such
packages as stub.
In this case
they will be empty (each definedClasses isEmpty), so you can remove
such packages/bundles.
hani
On 24 juin 08, at 23:07, Stéphane Ducasse wrote:
On Jun 24, 2008, at 10:35 PM, Romain PEIRS wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
I would know if there is a mean to only import in a MooseModel the
selected packages in the MooseBrowser?
For example, when I import the bundle Moose in Moose Browser, I
would only have in the MooseModel the packages of the bundle.
You have to do a filter at the end because a model has to create stub
and the stub are often in other packages.
I hope it was clear.
somehow :)
Romain
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
4:31 p.m.
On 17 juil. 08, at 15:46, Stéphane Ducasse wrote:
On Jul 17, 2008, at 3:14 PM, Univ-SAVOIE wrote:
no I do not think that it is we need to mark such packages as stub:
- a stub package is package that contains at less one stub class, or
any of its sub-packages containes at less one stub class.
- a package that has no defined classes nor extended classes is an
empty package (nt that i use actually the term empty package for a
package that its allClasses is empty).
this way we have 2 different filters that you use as together or not
(That depends on what you want to do/have).
hani
do not forget that the importer will import also
all the parent
packages/bundles/namespaces of the imported package/bundle/
namespace.
for example when you import Moose bundle which is packaged in
MooseDevelopment bundle and this last is packaged in Smalltalk
bundle,
MooseDevelopment and Smalltalk bundles will be imported also. They
will not be stubs because they dont contain stub classes.
may be we should have a good example and see if how we can mark such
packages as stub. In this case
they will be empty (each definedClasses isEmpty), so you can remove
such packages/bundles.
hani
On 24 juin 08, at 23:07, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Jun 24, 2008, at 10:35 PM, Romain PEIRS wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
I would know if there is a mean to only import in a MooseModel the
selected packages in the MooseBrowser?
For example, when I import the bundle Moose in Moose Browser, I
would only have in the MooseModel the packages of the bundle.
You have to do a filter at the end because a model has to create
stub
and the stub are often in other packages.
I hope it was clear.
somehow :)
Romain
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5:16 p.m.
I see but an empty should be really really rare to have.
Stef
On Jul 17, 2008, at 4:31 PM, Hani Abdeen wrote:
On 17 juil. 08, at 15:46, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Jul 17, 2008, at 3:14 PM, Univ-SAVOIE wrote:
no I do not think that it is we need to mark such packages as stub:
- a stub package is package that contains at less one stub class, or
any of its sub-packages containes at less one stub class.
- a package that has no defined classes nor extended classes is an
empty package (nt that i use actually the term empty package for a
package that its allClasses is empty).
this way we have 2 different filters that you use as together or not
(That depends on what you want to do/have).
hani
do not forget that the importer will import also
all the parent
packages/bundles/namespaces of the imported package/bundle/
namespace.
for example when you import Moose bundle which is packaged in
MooseDevelopment bundle and this last is packaged in Smalltalk
bundle,
MooseDevelopment and Smalltalk bundles will be imported also. They
will not be stubs because they dont contain stub classes.
may be we should have a good example and see if how we can mark such
packages as stub. In this case
they will be empty (each definedClasses isEmpty), so you can remove
such packages/bundles.
hani
On 24 juin 08, at 23:07, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Jun 24, 2008, at 10:35 PM, Romain PEIRS wrote:
> Hi,
>
> I would know if there is a mean to only import in a MooseModel the
> selected packages in the MooseBrowser?
> For example, when I import the bundle Moose in Moose Browser, I
> would only have in the MooseModel the packages of the bundle.
You have to do a filter at the end because a model has to create
stub
and the stub are often in other packages.
>
> I hope it was clear.
somehow :)
>
> Romain
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
6001
days inactive
6024
days old
5 comments
4 participants
participants (4)
-
Hani Abdeen -
Romain PEIRS -
Stéphane Ducasse -
Univ-SAVOIE