| Author |
Message |
|
codetale
Member
Joined: Fri Jun 22, 2007 11:07 am Posts: 150
|
 per project Plugin's settings
I have use many plug-ins (in-house), some of the plugin affect individual project, it save the settings in project folder with it name. When shared with team members, there have many "custom" files that not belong to project.
Is it possible to make the as3proj not to rewrite the xml tag/section its not belong to? then we can save our plugins per project settings into it. so that the settings are not visible and not affected the member who not using the plugin
Thank you very much
|
| Sat Apr 03, 2010 6:32 am |
|
 |
|
Philippe
Admin
Joined: Wed Aug 31, 2005 7:27 am Posts: 10746 Location: Paris, France
|
 Re: per project Plugin's settings
This is a request we already got in the past I think we could extend the Project object to allow plugins to store data in the proj file but we didn't look into implementing it.
|
| Sat Apr 03, 2010 4:46 pm |
|
 |
|
codetale
Member
Joined: Fri Jun 22, 2007 11:07 am Posts: 150
|
 Re: per project Plugin's settings
Really? no wonder me felt so familiar with my own question We already implement our own datafile container for this purpose, its was quite simple xml document. any suggestion for the file extension we should use? thank you very much
|
| Sat Apr 03, 2010 6:31 pm |
|
 |
|
iNils
Sponsor
Joined: Wed Oct 24, 2007 8:56 am Posts: 47 Location: Moscow, Russia
|
 Re: per project Plugin's settings
+1
|
| Fri Apr 16, 2010 8:25 am |
|
 |
|
Kulkoff
Member
Joined: Sat Nov 15, 2008 4:00 am Posts: 171
|
 Re: per project Plugin's settings
+1
|
| Fri Apr 16, 2010 8:39 am |
|
 |
|
Warappa
Member
Joined: Wed Jun 20, 2007 8:09 am Posts: 331
|
 Re: per project Plugin's settings
vote +1
_________________ Practice always defeats theory
|
| Fri Apr 16, 2010 10:26 am |
|
 |
|
Philippe
Admin
Joined: Wed Aug 31, 2005 7:27 am Posts: 10746 Location: Paris, France
|
 Re: per project Plugin's settings
Implemented in FD4 SVN. Code: Project p = (Project)PluginBase.CurrentProject; // requires ProjectManager reference p.Storage["foo"] = "bar"; // stored as: <entry key="foo"><![CDATA[bar]]></entry> p.Save(); // not automatic!
string value = p.Storage.ContainsKey("foo") ? p.Storage["foo"] : null; p.Storage["foo"] = null; // delete entry p.Save();
|
| Mon Nov 29, 2010 10:26 pm |
|
 |
|
Warappa
Member
Joined: Wed Jun 20, 2007 8:09 am Posts: 331
|
 Re: per project Plugin's settings
Niiiice! Is it planned to push this feature down to FD3?
_________________ Practice always defeats theory
|
| Tue Nov 30, 2010 7:58 am |
|
 |
|
codetale
Member
Joined: Fri Jun 22, 2007 11:07 am Posts: 150
|
 Re: per project Plugin's settings
Great Just download it from SVN But it seem the FD3 Plugin are not working in FD4, is there any changes? Thank you very much.
|
| Tue Nov 30, 2010 8:05 am |
|
 |
|
Mika
Admin
Joined: Tue Aug 30, 2005 6:14 pm Posts: 2543 Location: Finland
|
 Re: per project Plugin's settings
The 3rd party plugins might be binary incompatible, so republishing them against FD4 fixes the problems.
|
| Tue Nov 30, 2010 8:08 am |
|
 |
|
Philippe
Admin
Joined: Wed Aug 31, 2005 7:27 am Posts: 10746 Location: Paris, France
|
 Re: per project Plugin's settings
Warappa wrote: Niiiice! Is it planned to push this feature down to FD3? Now FD3 is now feature-freezed and should only receive maintenance updates.
|
| Tue Nov 30, 2010 9:03 am |
|
|