#61 Notes/Diary re Tasks

[Anonymous]

Originally created by: jon.nor...@fin-plus.co.uk
Originally owned by: jon.nor...@fin-plus.co.uk

Onging notes via Task, going back to JIRA/Task based dev as move to Beta, regimented approach.

Tasks need to be kept minimal at this stage and focus is currently on IOC which is now DI, QLNet and Clean Components (less Naive!!!!!!).

Favour ongoing tasks as solution is an continual evolving product.

Avoid renaming common classes as product settles.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Finish [https://code.google.com/p/fpmessaging/issues/detail?id=54 54 {}{,} etc]

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Look at QLNet again complete change over

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Defer QLNet till next week column helpers re client component not best model need to be able to add new column types from config will start changing this today.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Renamed .clients as .views in keeping with aspects of templates
Renamed FinPlusWPFClient as FinPlusClientShell
Renamed connection components change component FinPlusApp to FinPlusView

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Columns have been bugging me I do not want the requirment for evey datacolumn to be individualy defined in the template this will make for length complex templates.

What I have decided is to introduce columns re create instance of re DI re templates you effectibvely registering col types, makes sense since 10 columns could be of the same type tell helper {{colType, {col1, col2, col3, col4 etc}} then have xml to define type. Plus new types can be introduced without code breaks to existing components eg Grid or ColHelper components.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

effectively colType are collection of col builders

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Split grid controls but can only use programatic need to use DI get instance first sample of none constructor/method param sololving.

Also changed component base classes to none abstract to clean code base 

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Productionise Components  : change FinPlusColHelper to FinPlusGridColHelper

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

It might be better to have seperate teMplates for registered types, for example a RegisteredCol template that you reference within the view templates. Reigistered types a static resource.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Going to add templates for .regtypes each .view and .service can link to a number of .regtypes these can be share or not depending on use case and risk re shring flexible.

First .regtypes will be for grid columns and it will be shared buy clients

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Yesterday first use if get registered type re grid coluns this will evolve

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Look at Command Routing, move the events to functions into a single point

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Need to think about event routing need to be simple but bespoke re KVP universal model and audits. Spent some time today on website, website almost Phase 3 some code moving to Phase 2 connectivity stuck in reverse gear at the moment hardly Phase re POC.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Added commad parsers code cleaner, looked at further decoupling of UI components

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Added FinPlusExceptions and decided component routing should have varied choices for cleaner code will clean WPF controls also permissions to be brought into line.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

yesterday did a lot of renaming for transparency

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Core classes re KVP solution Functions->Function->Item

Consider suggestions eg Pods->Pod->Seed?

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Back to QLNet today

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Did some work on QLNet sticking with this name handle solution for now as I port my wrap of QuantLib C++ to QLNet. The name handle solution works well for Excel addins and might hav some advantages with the query driven enterprise solutions this will evolve.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Issue 43 has been merged into this issue.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Issue 64 has been merged into this issue.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

We now have all major tasks to move from Naive POC to Beta, QLNet today also keep in back of mind should FinPlusAnalytics be a component assembly

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

QLProxy was a v nasty rap to get some data to play with, QLNet can see B sensitivities can do something v nice with this.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Tomorrow will start to scrap business components that depend on QLProxy, I want QLNet to be from config via DI to object less naive v nice and one less layer

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

Project renames and comp proj break down add transparency