On 15.01.2008, at 22:43, Hanno Schlichting wrote:
Raphael Ritz wrote:
Wichert Akkerman wrote:
2. Not sure it's the best possible UI to completely hide a
product if a dependency is missing.
[...]
I'ld like some input from Hanno on that. What I did was update the
isInstallable method in the quickinstaller tool, which seemed the
logical place to put it and makes sure all the standard APIs and
code paths do the right thing. QI has never had a user interface
or API that communicates why a product is not installable and I'm
not sure what the best way to add this is.
Well, for testing purposes I just deliberately introduced a typo
in the PloneLanguageTool (of Plone 2.5.4 to demonstrate that
this is not new; removed a colon in line 60) and in
'prefs_install_products_form'
I get:
Broken products
Some products were found to have errors when compiling the install
file.
* PloneLanguageTool
Error Type
exceptions.SyntaxError
Error Value
invalid syntax (Install.py, line 60)
That's what I meant.
Along the same line we could just list products with broken
dependencies
here as well as they are checked anyway.
This seems like a good approach for me right now. I do have some
plans to do a major update to the installation logic for Plone 3.2
so a better UI can probably wait until then. Right now the
dependency support is the most frequently asked for feature, so lets
get that out to people :)
amen, brother ;-)
cheers,
tom
Hanno
_______________________________________________
Framework-Team mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/framework-team
_______________________________________________
Framework-Team mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/framework-team
