|
|
| Re: Ideas from Grails dependency resolution [message #486673 is a reply to message #486649] |
Fri, 18 September 2009 14:57   |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
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 #571489 is a reply to message #486649] |
Fri, 18 September 2009 14:57 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
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
>
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05199 seconds
] 
Search
Help
Register
Login
Home
