| Version 6 (modified by pav, 16 years ago) (diff) |
|---|
Discussions
In this video are explained our goals, what we strive to achieve, our challenges and how we shall proceed in order to create a product with high quality. It is recommended everyone to be familiar with this discussion.
Detailed log of the discussion is included below.
Topics:
= pro_lib = - designed to help people! If they are not helping, either something should be fixed or people do not understand how to use it.
* attibute - self responsible.
* do not care about initializing order.
* good practices:
* defaulty constructors.
* avoid final properties.
* push updates - instead of updating things manually, provide these things the ability to auto-update.
* avoid trying to use unconventionally the pro_lib since this is error prone.
* Property improper use cases:
* accessing an AutoProperty WILL NOT invoke its compute() method!
* resource properties:
* create method should depend on NOTHING => it is invoked once and will not update things.
* setup methods are designed to keep things synchronized for people. @Setup may be put to split setup things in different methods, so that they are updated in groups.
* destroy methods are not working.
* List properties.
= core_modularity =
* extensions are now sortable by comparator.
= base_visual =
== layout ==
== menus ==
* this is a new module to split the layout and menus from the main.view things.
= base_skins =
* provides things to simplify things that are registered for a single skin => currently a map with (id, value) entries.
= global things =
* few people have a global vision about things.
* people should get a better overall idea.
* supercool model.
* not only implement a great library but find a task to actually use it and also do that task.
* this will improve the library.
* things that are error prone will appear.
* the "not my task/class" problem (people tend to do only things that are tracked and planned):
* the code is owned by everyone!
* fix things that need to fixed in order to implement you things, otherwise the next revision of the task will fail.
* if the things are complicated to be fixed, ask the others, make discussions about it.
- AsteaCon 2008
During the three days of discussions at Sheraton Hotel between Astea Team and some of our oversea partners detailed information about all aspects of the project was given.
- Branding discussions with Robert Abbott from Shift Global
Project overview of Sophie 2.0 by the team leader which aims to introduce the product to Robert Abbott from Shift Global.
Discussion between Robert Abbott and Astea Team on which they discussed Sophie 2.0 logo drafts and basic visual wireframes of the future product.
Discussion about Sophie 2.0 user interface and some internal aspects of the project.
Discussion between Astea team and Robert Abbott about the vision and functionality of Sophie 2 website.
Milo gives details about the modules that he refactored, and explains his vision about improvement of the code quality.
