| Summary: | Should really use GIO | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Anjuta Plugin | Reporter: | Joshua Lock - Disabled <josh> |
| Component: | anjuta-plugin | Assignee: | liping Ke <liping.ke> |
| Status: | VERIFIED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, sgw, yp.ap.watcher, yp.watcher |
| Version: | 0.9 | ||
| Target Milestone: | 1.0 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
|
Description
Joshua Lock - Disabled
2010-09-01 08:16:36 UTC
The GIO documentation includes a section on migrating form other API's: http://library.gnome.org/devel/gio/stable/migrating.html IMHO this change should be made before the next release is tagged. Hi, Josh Just checked the info! I just look through the below links, found the GIO will not be a very simple task, need to go through lots of API interfaces and extract what we need to replace and have some test. Since I am not sure whether it will be a high priority request compared with eclipse plugin. I will find spare time to look@GIO interface for knowlege preparation. If we can find time to finish the job, I will try to modify it. So I want to postpone this task to 1.0M. Thanks & Regards, criping We've made the decision to leave the Anjuta plugin as it and open it up for the community to continue the maintaince if there's such desire I can understand why this decision was made. |