Community
Participate
Working Groups
Build Identifier: 20110218-0911 I would like to make some suggestions from the VB6 IDE Please add a Rapid Developer mode, that would be toggled (so people who don't like it, don't have to use it) and would change the behavior of the UI -When setting the event handlers (ie: OnClick) instead of bringing up a prompt to choose which string points to the event handler code: if the event handler has already been set: Go to the line where the code starts otherwise: Make the Activity_Objectname_Event string, set it to Objectname_Event, and create the first and last line of code for the event ( public void Objectname_Event(View view) { } ) then go to the line where it starts -When setting any property that uses an XML value, automatically create it for that property and just set the values. -Add 2 combo/dropdown boxes to the top of the class for an activity One lists all available widgets on the activity The other lists all available events triggered by the currently selected widget from the first combo box. Any event that has an event handler will be in bold text to differentiate them from the ones without handlers Upon selecting a widget from box #1, it automatically selects the first event with a handler from box #2 if one exists Upon selecting an event from box #2, if it has a handler it scrolls down to the line where it starts on, otherwise it would create the event handler automatically (like the first suggestion) This would be especially helpful for beginners or those used to Visual Studio Reproducible: Always
Created attachment 195424 [details] Here's how it looks in VB6's IDE
Please open bugs and enhancement requests with the Android plug-in with the Android developers.
That's not a good solution, as it ensures it'll probably never be implemented. They have a whole OS to worry about with millions of bugs/feature requests.
(In reply to comment #3) > That's not a good solution, as it ensures it'll probably never be implemented. Tanya, we don't work on the Android plug-in. You need to speak with the developers of the Android plug-in. I don't know what you want us (the Eclipse developers) to do here.
I had assumed you guys made Eclipse and thus had complete control over its code. Sorry for the mistake. I don't think a plugin could even give them the sort of control I'm asking for.
(In reply to comment #5) > I had assumed you guys made Eclipse and thus had complete control over its > code. We only do so much. There are thousands of Eclipse plug-ins out there and only a small fraction of those plug-ins are hosted on the repositories of Eclipse.org. > I don't think a plugin could even give them the sort of control I'm asking for. Well, won't know unless you ask. Ask the Android plug-in developers to implement what you want. If they can't do it and need APIs to achieve this that isn't currently supported by Eclipse, they can come here and open a bug and we can have a conversation on that specific API and feature then.