Hi list,
I've been following symfony here for about a year (would like to move a
large-ish project of ours to s), and am also an Eclipse user, so a
plug-in would be great.
Your plans for an initial release sound very good to me.
I think it's a smart idea to keep the amount of functionality to a
minimum for the first version, and concentrate on basic plug-in issues,
like getting it to install & update properly. More features can be added
later.
Just my 2 cents :-) . Looking forward to giving both the Plug-in and S
v2.0 a whirl soon!
-Chris
As for the plugin, I think it's good, although I'm not sure I get the
rationale behind having framework-specific IDEs, but if you can make it
helpful then great.
I was discussing this with another developer of the old plugin a
couple of days ago,
and i have the opinion that the new plugin should mainly focus on
leveraging
the workflow with the framework by adding features that do not exist
in the
framework itself, instead of pulling existing stuff into the ide,
like running symfony tasks.
Therefore, i will put my effort in adding symfony related information
to the
PDT code completion engine, adding error reporting with quickfixes
wherever
possible, and probably add refactoring features.
I'll add an example which will probably make things clearer:
class HelloController extends Controller
{
public function indexAction($name)
{
$someForm = new SomeForm();
return $this->render('HelloBundle:Hello:index', array('form' =>
$someForm));
}
public function anotherAction()
{
return $this->redirect('@logout');
}
}
Here i would like to add the following IDE features:
1. Add code assistance in the $this->render() call, for each part of
the viewpath (<Bundle>:<Controller>:<View>)
2. In the index template itself, tell the code completion engine that
$form is of type SomeForm(), so you'll get assistance for view
variables
3. Report an error if the index template does not exist, and add a
quickfix to create the template.
4. Enable to switch directly to the index template, by ctrl-clicking
on the word "index" in the $this->render() call
5. Add code assistance in the call to $this->redirect() after the @
sign, and show all available routes in a code-assist popup.
6. Create a tooltip, when hovering over '@logout', which shows the
definition of the route (either from the yaml or xml configuration)
7. Report an inline error, if the route @logout does not exist, and
also add a quickfix to directly create the route.
There's much more we can implement, like yml editor/ yml code
assistance, but to stay in a realistic estimate what
can be done until the release, i think we should focus on basic
features like this.
Please let me know if this stuff makes sense to you.
regards
-robert
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
