Bug 254

Summary: Should really use GIO
Product: [Yocto Project Subprojects] Anjuta Plugin Reporter: Joshua Lock - Disabled <josh>
Component: anjuta-pluginAssignee: 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 Anjuta plugin currently uses a combination of GnomeVFS (src/plugin.c) and POSIX (src/beaver-utils.c) for file and directory handling.

We should really switch to using GIO because:
* GnomeVFS is in the process of being deprecated
* We should be consistent in our API usage for performing similar tasks
Comment 1 Joshua Lock - Disabled 2010-09-01 08:18:11 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.
Comment 2 liping Ke 2010-09-15 20:37:05 UTC
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
Comment 3 Jessica 2010-12-10 11:47:05 UTC
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
Comment 4 Joshua Lock - Disabled 2010-12-13 04:08:43 UTC
I can understand why this decision was made.