Your comments
Disclaimer: I like the fact that additional features for GLPI are possible via plugins: this makes the GLPI core less bloated.
Why integrate a plugin into the GLPI Core? If the plugin does the job there is no need to make it part of GLPI.
If you think the plugin's features should be integrated into GLPI's core: please explain why it should be, which advantages it would brings, why the plugin-solution is not working (or badly).
Having the object's name in the <title> page would help when dealing with many browser tabs.
Disclaimer: I like the fact that additional features for GLPI are possible via plugins: this makes the GLPI core less bloated.
Why integrate a plugin into the GLPI Core? If the plugin does the job there is no need to make it part of GLPI.
If you think the plugin's features should be integrated into GLPI's core: please explain why it should be, which advantages it would brings, why the plugin-solution is not working (or badly).
Please see CALDAV server support which is a more generic way of doing the same thing (and thus profit to more setups).
I don't think integrating this feature into GLPI Core is a good idea: or it should also work with any objects (eg. with users, to map their belongings).
On the other side, having a v0.90 compliant archires plugin would be great :) (but it might not be the right place to ask for this).
What are projects?
-1
Disclaimer: I like the fact that additional features for GLPI are possible via plugins: this makes the GLPI core less bloated.
Why integrate a plugin into the GLPI Core? If the plugin does the job there is no need to make it part of GLPI.
If you think the plugin's features should be integrated into GLPI's core: please explain why it should be, which advantages it would brings, why the plugin-solution is not working (or badly).
I like the fact that additional features for GLPI are possible via plugins: this makes the GLPI core less bloated.
But I think adding "Generic object" and "Custom fields" features in GLPI core could improve integration.
This integration would require plugins to support theses objects: this is good for user experience but require more work for plugin's developers.
Please take this into account when choosing to implement this idea.
Creating an "external" KB entry (that points to a given URL) is a good and easy-to-implement solution.
Customer support service by UserEcho
Since the dropdowns are now (since v0.85 I believe) searchable, If you want to set the location to "Room 3" you can type "Room 3", the dropdown would then filter out locations whose name does not contains "Room 3" while keeping the intermediates/parents of locations whose name contains "Room 3" also keeping the hierarchy.
I find a single input easier to use than a succession of inputs.