>
> It must make use and adoption simple, not more complex !
+1
2012/1/11 <edgar.sol...@web.de>
> the trunk is very reliable these days. i want to keep it that way.
>
> can you explain what has to be refactored to what degree? changes to core
> are especially delicate because we can easily break compatibility with
> plugins around.
>
I would start Top-down. First write tests for the components with the least
dependencies (i.e. PlugIns in the tools menu). Then refactor the hell out
of the Plugins (it won't break anything, because there are no
dependencies). If we evolved some best practices for the stucture of these
plugins, we could look into more dependent components and think about what
is worth refactoring and what could possibly break compatibility. So there
is no need to change the core right now.
> until now i understood the testing framework as an addition, isn't it?
>
The testing framework is just an additional package, yes. In order to run
and write tests on/for the plugins in the tools menu we don't need any
refactorings.
--Benjamin
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
