|
|
| Changed: |
< < |
%META:TOPICPARENT{name="Main.PhantomPlugins"}%
| > > |
%META:TOPICPARENT{name="Trash.PhantomPlugins"}%
|
| Changed: |
< < |
CurrentProjectComponent?
| > > |
|
| Changed: |
< < |
See Also: PhantomPlugins?
| > > |
See Also: PhantomPlugins
|
| Changed: |
< < |
It's very simple ApplicationComponent and ProjectManagerAdapter?. some times you needed to get current project, just call to this component. I think that in feature this class will depricate, but now API for this expected.
| > > |
It's very simple ApplicationComponent and ProjectManagerAdapter. some times you needed to get current project, just call to this component. I think that in feature this class will depricate, but now API for this expected.
|
| Changed: |
< < |
-
- If multi project has avaible then only one of projects may be current. Otherwise the project level components come to unstable, becose it's have a constructor with project parameter. I think that will be a workspace. In this workspace where are projects, but only one project may be selected at one time. I wrong? So ProjectManagerListener? has changes - add one new method
selectedProject. So, then it avaible i will rewrite the code and this new code will set current project in method selectedProject. I think that multi project support in IntelliJ be is a another gui for existing code - Recently Used Projects algoritm. But maybe i wrong. And i also guess, that currentProject must be geted via open API.
| > > |
-
- If multi project has avaible then only one of projects may be current. Otherwise the project level components come to unstable, becose it's have a constructor with project parameter. I think that will be a workspace. In this workspace where are projects, but only one project may be selected at one time. I wrong? So ProjectManagerListener has changes - add one new method
selectedProject. So, then it avaible i will rewrite the code and this new code will set current project in method selectedProject. I think that multi project support in IntelliJ be is a another gui for existing code - Recently Used Projects algoritm. But maybe i wrong. And i also guess, that currentProject must be geted via open API.
|
| Changed: |
< < |
%META:FILEATTACHMENT{name="Plugins.Main.CurrentProjectComponent.java" attr="h" comment="" date="1024407908" path="D:\TEMP\Plugins.Main.CurrentProjectComponent.java" size="1047" user="Main.AlexeyEfimov" version="1.1"}%
| > > |
%META:FILEATTACHMENT{name="Plugins.Main.Trash.CurrentProjectComponent.java" attr="h" comment="" date="1024407908" path="D:\TEMP\Plugins.Main.Trash.CurrentProjectComponent.java" size="1047" user="Main.AlexeyEfimov" version="1.1"}%
|
| Changed: |
< < |
%META:TOPICMOVED{by="AlexeyEfimov" date="1030368414" from="Plugins.CurrentProjectComponent" to="Main.CurrentProjectComponent"}%
| > > |
%META:TOPICMOVED{by="AlexeyEfimov" date="1039535969" from="Main.CurrentProjectComponent" to="Trash.CurrentProjectComponent"}% |
|
|
| Changed: |
< < |
%META:TOPICPARENT{name="Plugins.PhantomPlugins"}%
| > > |
%META:TOPICPARENT{name="Main.PhantomPlugins"}%
|
| Changed: |
< < |
| > > |
CurrentProjectComponent?
|
| Changed: |
< < |
See Also: PhantomPlugins?
| > > |
See Also: PhantomPlugins?
|
| Changed: |
< < |
%META:FILEATTACHMENT{name="Plugins.CurrentProjectComponent.java" attr="h" comment="" date="1024407908" path="D:\TEMP\Plugins.CurrentProjectComponent.java" size="1047" user="Main.AlexeyEfimov" version="1.1"}%
| > > |
%META:FILEATTACHMENT{name="Plugins.Main.CurrentProjectComponent.java" attr="h" comment="" date="1024407908" path="D:\TEMP\Plugins.Main.CurrentProjectComponent.java" size="1047" user="Main.AlexeyEfimov" version="1.1"}%
|
| Changed: |
< < |
%META:TOPICMOVED{by="AlexeyEfimov" date="1024577871" from="Main.CurrentProjectComponent" to="Plugins.CurrentProjectComponent"}%
| > > |
%META:TOPICMOVED{by="AlexeyEfimov" date="1030368414" from="Plugins.CurrentProjectComponent" to="Main.CurrentProjectComponent"}% |
|
|
| Changed: |
< < |
See Also: PhantomPlugins?, SystemPropertiesView?, OneInstance?
| > > |
See Also: PhantomPlugins? |
|
|
| Added: |
> > |
This plugin currently is depricated. This one have no good idea to track for "current project" now, becose build since #630 have a multiproject support by SDI notation. This plugin may used only in previos build #629. |
|
|
| Added: |
> > |
-
- If multi project has avaible then only one of projects may be current. Otherwise the project level components come to unstable, becose it's have a constructor with project parameter. I think that will be a workspace. In this workspace where are projects, but only one project may be selected at one time. I wrong? So ProjectManagerListener? has changes - add one new method
selectedProject. So, then it avaible i will rewrite the code and this new code will set current project in method selectedProject. I think that multi project support in IntelliJ be is a another gui for existing code - Recently Used Projects algoritm. But maybe i wrong. And i also guess, that currentProject must be geted via open API.
-- AlexeyEfimov - 27 Jun 2002
|
|
|
| Added: |
> > |
- How do you consider this to be working with multi project support?
-- MikeAizatsky - 27 Jun 2002
|
|
|
| Changed: |
< < |
Hmm, I would be carefull using this. Take a look at the PluginDocumentation -- Project-Singleton.
| > > |
Hmm, I would be carefull using this. Take a look at the Project Singleton. |
|
|
| Changed: |
< < |
Hmm, I would be carefull using this. Take a look at the PluginDocumentation? -- Project-Singleton.
| > > |
Hmm, I would be carefull using this. Take a look at the PluginDocumentation -- Project-Singleton. |
|
|
| Added: |
> > |
Hmm, I would be carefull using this. Take a look at the PluginDocumentation? -- Project-Singleton.
JohannesSchneider - 24 Jun 2002 |
|
|
| Changed: |
< < |
%META:TOPICPARENT{name="PhantomPlugins"}%
| > > |
%META:TOPICPARENT{name="Plugins.PhantomPlugins"}%
CurrentProjectComponent?
|
| Changed: |
< < |
It's very simple ApplicationComponent and ProjectManagerAdapter. some times you needed to get current project, just call to this component. I think that in feature this class will depricate, but now API for this expected.
| > > |
It's very simple ApplicationComponent and ProjectManagerAdapter?. some times you needed to get current project, just call to this component. I think that in feature this class will depricate, but now API for this expected.
|
| Changed: |
< < |
Back to PhantomPlugins
| > > |
Back to PhantomPlugins?
|
| Changed: |
< < |
%META:FILEATTACHMENT{name="CurrentProjectComponent.java" attr="h" comment="" date="1024407908" path="D:\TEMP\CurrentProjectComponent.java" size="1047" user="AlexeyEfimov" version="1.1"}%
%META:FILEATTACHMENT{name="currentProject.zip" attr="h" comment="currentProject.zip" date="1024559847" path="D:\TEMP\plugins\phantom-plugins\plugins\currentProject.zip" size="10099" user="AlexeyEfimov" version="1.1"}%
| > > |
%META:FILEATTACHMENT{name="Plugins.CurrentProjectComponent.java" attr="h" comment="" date="1024407908" path="D:\TEMP\Plugins.CurrentProjectComponent.java" size="1047" user="Main.AlexeyEfimov" version="1.1"}%
%META:FILEATTACHMENT{name="currentProject.zip" attr="h" comment="currentProject.zip" date="1024559847" path="D:\TEMP\plugins\phantom-plugins\plugins\currentProject.zip" size="10099" user="Main.AlexeyEfimov" version="1.1"}%
%META:TOPICMOVED{by="AlexeyEfimov" date="1024577871" from="Main.CurrentProjectComponent" to="Plugins.CurrentProjectComponent"}% |
|
|
| Changed: |
< < |
It's very simple ApplicationComponent and ProjectManagerAdapter. some times you needed to get current project, just call to this component.
| > > |
|
| Changed: |
< < |
I think that in feature this class will depricate, but now API for this expected.
| > > |
It's very simple ApplicationComponent and ProjectManagerAdapter. some times you needed to get current project, just call to this component. I think that in feature this class will depricate, but now API for this expected.
|
| Changed: |
< < |
CurrentProjectComponent cpc = (CurrentProjectComponent)ApplicationManager.getApplication().getComponent(CurrentProjectComponent);
<nop>
| > > |
Back to PhantomPlugins
|
| Changed: |
< < |
Project project = cpc.getCurrentProject();
| > > |
try {
Project project = CurrentProjectComponent.getCurrentProject();
<nop>
|
| Added: |
> > |
} catch (ComponentNotFoundException? ex) {
log.error(ex);
}
|
| Changed: |
< < |
-- AlexeyEfimov - 17 Jun 2002
| > > |
-- AlexeyEfimov - 20 Jun 2002
|
| Added: |
> > |
%META:FILEATTACHMENT{name="currentProject.zip" attr="h" comment="currentProject.zip" date="1024559847" path="D:\TEMP\plugins\phantom-plugins\plugins\currentProject.zip" size="10099" user="AlexeyEfimov" version="1.1"}% |
|
|
| Added: |
> > |
%META:FILEATTACHMENT{name="CurrentProjectComponent.java" attr="h" comment="" date="1024407908" path="D:\TEMP\CurrentProjectComponent.java" size="1047" user="AlexeyEfimov" version="1.1"}% |
|
|
| Added: |
> > |
%META:TOPICINFO{author="AlexeyEfimov" date="1024301531" format="1.0" version="1.1"}%
%META:TOPICPARENT{name="PhantomPlugins"}%
It's very simple ApplicationComponent and ProjectManagerAdapter. some times you needed to get current project, just call to this component.
I think that in feature this class will depricate, but now API for this expected.
CurrentProjectComponent cpc = (CurrentProjectComponent)ApplicationManager.getApplication().getComponent(CurrentProjectComponent);
Project project = cpc.getCurrentProject();
if (project == null) {
// No project opened
} else {
// Some operation with project
}
-- AlexeyEfimov - 17 Jun 2002 |
View
| Diffs | r1.16 | > | r1.15 | > | r1.14
| More
|
|