| Ideas from Grails dependency resolution [message #486586] |
Fri, 18 September 2009 06:37  |
Eclipse User |
|
|
|
In a tweat, Oisin mentioned that something like the grails dependency
management http://tr.im/z1Y9 should be considered for b3.
Not knowing what Oisin liked in particular, I think these two features
are important, and should be handled by b3:
- injection of dependencies
- ability to have different dependencies injected (or removed) for
different actions
Maybe there were some more features...
Regards
- henrik
|
|
|
|
| Re: Ideas from Grails dependency resolution [message #486673 is a reply to message #486649] |
Fri, 18 September 2009 10:57  |
| Eclipse User |
|
|
|
Oisin Hurley wrote:
> Henrik Lindberg wrote on Fri, 18 September 2009 06:37
>> Not knowing what Oisin liked in particular, I think these two features
>> are important, and should be handled by b3:
>>
>> - injection of dependencies
>> - ability to have different dependencies injected (or removed) for
>> different actions
>
>
> The first thing that struck me was the syntax - editable without any XML
> and without any need for the simplifying influence of
> an IDE. It's very important to me that I can describe all of the
> metadata I need to describe in a way that is compact and can
> be simply edited as necessary from a ssh connection.
>
Yes, I thought that looked nice too. In b3, the idea is to separate the
resulting model from the artifacts - although it would certainly be
possible to save Ecore instances of the b3 models, these are not
suitable for human editing :)
The idea is to invent compact and easy to use syntax with XText as an
alternative to some GUI based editor. The nice thing being that there
can be different formats/editors etc. suitable for different situations,
and that specifications may "add up" - i.e. that a full gui based editor
could be used to create some overall model, and that additional
"stuff/advice" can be provided in a compact format.
> So that's more of a 'user' requirement than a core function requirement,
> i.e. that there must be a way to conveniently
> update build files through a remote terminal access provided
> as part of the basic b3 package - not as an extension.
>
> Does that make sense?
>
Yes, that makes a lot of sense.
> cheers
> --oh
>
|
|
|
|
|
| Re: Ideas from Grails dependency resolution [message #527343 is a reply to message #527252] |
Wed, 14 April 2010 16:59 |
| Eclipse User |
|
|
|
Hi,
I guess the result is the implementation of the b3 model and concrete
text representation (language) as described in the first draft of the b3
book.
I am very interested in feedback on b3, comparision to grails, etc.
Regards
- henrik
On 4/14/10 5:05 PM, Werner Keil wrote:
> Has there been any result from this discussion?`
>
> I'm working heavily with Grails right now, so in this area I'd also be
> happy to contribute to.
>
> Werner
|
|
|
| Re: Ideas from Grails dependency resolution [message #571382 is a reply to message #486586] |
Fri, 18 September 2009 10:08 |
| Eclipse User |
|
|
|
Henrik Lindberg wrote on Fri, 18 September 2009 06:37
> Not knowing what Oisin liked in particular, I think these two features
> are important, and should be handled by b3:
>
> - injection of dependencies
> - ability to have different dependencies injected (or removed) for
> different actions
The first thing that struck me was the syntax - editable without
any XML and without any need for the simplifying influence of
an IDE. It's very important to me that I can describe all of the
metadata I need to describe in a way that is compact and can
be simply edited as necessary from a ssh connection.
So that's more of a 'user' requirement than a core function
requirement, i.e. that there must be a way to conveniently
update build files through a remote terminal access provided
as part of the basic b3 package - not as an extension.
Does that make sense?
cheers
--oh
|
|
|
| Re: Ideas from Grails dependency resolution [message #571489 is a reply to message #486649] |
Fri, 18 September 2009 10:57 |
| Eclipse User |
|
|
|
Oisin Hurley wrote:
> Henrik Lindberg wrote on Fri, 18 September 2009 06:37
>> Not knowing what Oisin liked in particular, I think these two features
>> are important, and should be handled by b3:
>>
>> - injection of dependencies
>> - ability to have different dependencies injected (or removed) for
>> different actions
>
>
> The first thing that struck me was the syntax - editable without any XML
> and without any need for the simplifying influence of
> an IDE. It's very important to me that I can describe all of the
> metadata I need to describe in a way that is compact and can
> be simply edited as necessary from a ssh connection.
>
Yes, I thought that looked nice too. In b3, the idea is to separate the
resulting model from the artifacts - although it would certainly be
possible to save Ecore instances of the b3 models, these are not
suitable for human editing :)
The idea is to invent compact and easy to use syntax with XText as an
alternative to some GUI based editor. The nice thing being that there
can be different formats/editors etc. suitable for different situations,
and that specifications may "add up" - i.e. that a full gui based editor
could be used to create some overall model, and that additional
"stuff/advice" can be provided in a compact format.
> So that's more of a 'user' requirement than a core function requirement,
> i.e. that there must be a way to conveniently
> update build files through a remote terminal access provided
> as part of the basic b3 package - not as an extension.
>
> Does that make sense?
>
Yes, that makes a lot of sense.
> cheers
> --oh
>
|
|
|
| Re: Ideas from Grails dependency resolution [message #571580 is a reply to message #486673] |
Fri, 18 September 2009 11:12 |
| Eclipse User |
|
|
|
Henrik Lindberg wrote on Fri, 18 September 2009 10:57
> The idea is to invent compact and easy to use syntax with XText as an
> alternative to some GUI based editor.
Sounds cool - this is something that I would like to
contribute to.
--oh
|
|
|
|
| Re: Ideas from Grails dependency resolution [message #603729 is a reply to message #527252] |
Wed, 14 April 2010 16:59 |
| Eclipse User |
|
|
|
Hi,
I guess the result is the implementation of the b3 model and concrete
text representation (language) as described in the first draft of the b3
book.
I am very interested in feedback on b3, comparision to grails, etc.
Regards
- henrik
On 4/14/10 5:05 PM, Werner Keil wrote:
> Has there been any result from this discussion?`
>
> I'm working heavily with Grails right now, so in this area I'd also be
> happy to contribute to.
>
> Werner
|
|
|
Powered by
FUDForum. Page generated in 0.25236 seconds
Home