On Jan 2, 2007, at 7:26 PM, Norman Palardy wrote:
On Jan 02, 2007, at 6:13 PM, Brendan Murphy wrote:
There has been some grumbling on what RS has chosen to implement
as features. A lot of this grumbling is not justified because it
does not match the facts. In the release notes, there were
approximately 167 changes in r1 and there were approximately 13
items marked as "new". That makes for about 8% of the work as new
feature work and the new features for r1 could be categorized as
minor. So the reality of r1 is that about 92% of the work was for
bug fixes and bug fixes are what people have been clamoring for.
So I think you have to give RS some credit here for doing the
right thing in r1 and the quality is improving.
I'd quite agree.
2007r1 is much more usable than any 2006rX release for my purposes.
Having said that, we need to hold their feet to the fire going
forward.
[snipped]
Here is my list of nuts and bolts features...
- Libraries (source code and precompiled).
This would be useful and hopefully have some effect on compile
speed as well
Basically a "project of projects" so one project could be "build
this library" and the main project could use that library
- Plugins per project.
You have NO idea how much I'd LOVE this one and how much hassle it
would save me !
You could just create your own 'hassle' and save it... Okay, just
kidding! :)
- Creating plugins in RB.
Plugins for RB or plugins for other applications ?
RB plugins in RB seems nice but if you can make it in in RB then
why not just make a module/class and use it ?
Because, from what I can tell, plugin-based controls get a nice icon;
user created classes do not.
RB plugins are things that cannot be done in RB and so have to be
done in C/C++ etc.
And that list of "cannot be done in RB" is getting shorter over time
- Folders in the IDE to help organize our methods.
Ummm I use these all the time
Not sure what else you need
I think he means that - within an RB 'object' (a window, module, or
class) - there should be some folder (or other organizational aid)
that allows you to group methods together. Something like:
<top level of project window>
Menu1
/Classes <- a "folder" named classes
App
MyClass
/factory-methods
/drawing
Draw() : <insert the 'public badge' icon here>
/private-stuff
DrawHelper() As Boolean : <insert the 'protected badge' icon
here>
/Windows
/Modules
/Exceptions
/Graphics
...
so, in this example, he has a project that has a folder, "Classes"
that has 2 classes in it; "App" and "MyClass". Within the "MyClass"
class, there are subfolders called; "Factory-methods", "drawing" and
"private-stuff". Presumably, you could open one ("drawing", say) and
only the method(s) grouped there - "Draw()" in this case - would show
up in the code editor window (in more detail, of course!)
- Team development features (i.e., proper version control).
Just fixing the issues that exist in the current version control
format would make using SVN, CSV, RCS, etc MUCH better and that
would better enable team development
And an RB-specific 'diff' tool would be way cool!
I'd love to see the list of 500+ verified bug reports in RB grow a
LOT shorter in the next release
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
