On 23/07/2012 13:18, Fabio Martelli wrote:
> Hi All,
> as you can see from [1] several tasks regarding the administration console
> refactoring have been scheduled from the next major release onwards.
> At the moment, the Apache Syncope console seems to work quite fine but, from
> my PPOV, a complete code refactoring needs to be done ASAP according to the
> roadmap.
>
> As you can imagine, this task cannot be done one-shot but should be done step
> by step, crossing some releases.
>
> For this reason, I'd like to suggest to create a new console module to
> coexist with the current one.
> in this way we can develop the new console with calm, without creating
> troubles to the current end users.
>
> Please, let me know what you think about.
Fabio,
I do think that handling the admin console refactoring task as a
"rewrite from scratch" separate module is indeed a good idea.
Some reasons coming to my mind:
* the current console was originally architected with some now outdated
user interface patterns
* the current console source code would need some deep refactoring to
benefit from newest Wicket features
* we could empower some widespread adopted UI libraries and Wicket add-ons
* sometimes rewriting things from scratch - by always keeping an eye to
old implementation - is better than trying to impose a different order
* having two separate console modules can free us from the hassle of
giving not-enough-tested stuff to end users
We will need, of course, to replicate any relevant fix to both console
modules until we'll decide to completely switch to the new one.
One question though: what would be the best way to handle such
development at SVN level: a separate module ('newconsole'?) next to
current modules, a separate branch, ...?
Regards.
> [1] https://cwiki.apache.org/confluence/display/SYNCOPE/Roadmap
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
