Package blueprint: your advice

I am in the process (that is, when my mind is not full with the 1000 things to do when moving to a new city) of refactoring package blueprints, with multiple objectives in mind:

- make package blueprints work with namespaces
- a testbed for Chef queries
- rewriting the code to make it a bit more object-oriented
- add tests

There is one loophole I would like to expose and get your opinion about. Package blueprints shows references between classes across packages. Unfortunately nothing has been planned to handle class extensions. Right now there are just ignored so the picture given by package blueprints might be incomplete (but not false).

I don't plan for now to do something about this but if some people want to give a thought about this and later add their idea, they are welcome.

--
Simon Denier




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi Simon,

> - make package blueprints work with namespaces
> - a testbed for Chef queries
> - rewriting the code to make it a bit more object-oriented
> - add tests

I would like you to enhance your test. Hapao is mature enough for this.
How do you want to proceed?

Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On Mar 7, 2011, at 9:32 AM, Simon Denier wrote:

indeed. we ignore them because a reference made in an extension does not really belongs to the package class but
package extension.

Stef
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On 7 mars 2011, at 16:04, Alexandre Bergel wrote:

> Hi Simon,
>
>> - make package blueprints work with namespaces
>> - a testbed for Chef queries
>> - rewriting the code to make it a bit more object-oriented
>> - add tests
>
> I would like you to enhance your test. Hapao is mature enough for this.
> How do you want to proceed?


I don't really know :)

Right now it is two steps reverse-engineering, one step reengineering. The code is rather procedural-oriented with place for improvement with objects. How do you think Hapao could help?

--
Simon Denier




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

I just put online packages Moose-Blueprints and Moose-Tests-Blueprints. Not much more than a work in progress.

On 7 mars 2011, at 19:59, Simon Denier wrote:

--
Simon Denier




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> Right now it is two steps reverse-engineering, one step reengineering. The code is rather procedural-oriented with place for improvement with objects. How do you think Hapao could help?


Hapao help you to quickly increase the coverage of your tests by suggesting which methods you should focus on.

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On 9 mars 2011, at 20:21, Alexandre Bergel wrote:

>> Right now it is two steps reverse-engineering, one step reengineering. The code is rather procedural-oriented with place for improvement with objects. How do you think Hapao could help?
>
>
> Hapao help you to quickly increase the coverage of your tests by suggesting which methods you should focus on.

Ok I will try to see how it helps next time I go to Lille by train (last time! next friday)

--
Simon Denier




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On 9 mars 2011, at 20:21, Alexandre Bergel wrote:

>> Right now it is two steps reverse-engineering, one step reengineering. The code is rather procedural-oriented with place for improvement with objects. How do you think Hapao could help?
>
>
> Hapao help you to quickly increase the coverage of your tests by suggesting which methods you should focus on.
>

Thinking more about this, what I need to do is to reengineer and cut new perimeters inside the package blueprint blob. More precisely, I would like to define testable perimeters like:
- querying the model
- building the model beneath the visualization (surfaces + cells)
- describing the visualization with Mondrian
- and describing the browser around with Glamour

That's actually more complicated than I thought originally: there is a strong flavour of procedural implementation (inherited from the first version in VW), dead code, data structure which are centralized in the blob and should be put into objects, etc.

So that's what I'm trying to do: read code, what does it do and is it good or bad, write tests, rewrite if necessary. Since I start from nothing, I don't much test to guide me but it could be interesting to see these new 'perimeters' evolve through testing in Hapao.

--
Simon Denier




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Currently, I cannot afford dispersing myself. I would really like that we seat down together and look at the tests of Chef.

Alexandre


On 9 Mar 2011, at 16:44, Simon Denier wrote:

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> Thinking more about this, what I need to do is to reengineer and cut new perimeters inside the package blueprint blob. More precisely, I would like to define testable perimeters like:
> - querying the model
> - building the model beneath the visualization (surfaces + cells)
> - describing the visualization with Mondrian
> - and describing the browser around with Glamour
>
> That's actually more complicated than I thought originally: there is a strong flavour of procedural implementation (inherited from the first version in VW), dead code, data structure which are centralized in the blob and should be put into objects, etc.
>
> So that's what I'm trying to do: read code, what does it do and is it good or bad, write tests, rewrite if necessary. Since I start from nothing, I don't much test to guide me but it could be interesting to see these new 'perimeters' evolve through testing in Hapao.


Hapao is made to help you focus on the interesting methods when writing tests.

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev