A good example of the types of enhancements I am considering, which I
actually just ran into again and need to implement sooner than later is:

1 - Data Model Relationships
    defining foreign-key-like relationships in the object model that are
    not existant or created in the database. What I want is for the OM
    access methods to be generated for this type of access, even if it
    does not explicitly exist in the database as a fk.
    
2 - "javaName" attribute for relationships (FK and above)
    providing a "javaName" attribute to foreign-key (and the above
    mentioned relationships) to allow control of the generated accessor
    method names:
    
    <table name=USERS javaName="user">
    ....
    <foreign-key foreignTable="Book" javaName="FavoriteBook">
        <reference foreign="bookId" local="favoriteBookId">
    </foreign-key>
    </table>
    
    This would cause the generation of a getFavoriteBook method, rather
    than getBook, as would be generated now.
    
One of our major goals is to have Torque (or other tools) generate as
much of the definable code as possible, leaving us to build only the
real business logic.

Thanks
Russell

On Mon, 2002-09-09 at 11:13, J. Russell Smyth wrote:
> Thanks for the response. For #4&5, I am hoping for some reasonbaly quick
> discussion, as if my project takes off, I will need to plow into these
> for our uses, and knowing if they will be of value to the torque
> community as a whole, and how to integrate, would really help me plan
> out how we will approach this.
> 
> I also suspect some of my ideas/suggestions may need some discussion
> before becoming part of the plan. Will placing these ideas in Scarab
> generate email discussions?
> 
> thanks
> Russell
> 
> On Mon, 2002-09-09 at 10:48, John McNally wrote:
> > On Mon, 2002-09-09 at 10:17, J. Russell Smyth wrote:
> > > Torque Team,
> > > 
> > >   Before I start this I should introduce myself. My name is Russell
> > > Smyth, seen here with emails of both [EMAIL PROTECTED] (work)
> > > and [EMAIL PROTECTED] (home).
> > > 
> > >   My current project is seriously considering building around torque -
> > > in fact, all of our prototyping is currently being performed with
> > > torque, and we intend to stick with it for the foreseeable future. This
> > > means that I will be intimately involved with torque, at least as a
> > > user.
> > > 
> > >   We have a few improvements/changes we would like to see in torque,
> > > some of which I will be developing because we need them, even if the
> > > rest of the torque comunity does not. What I would like to know is:
> > > 
> > >  1 - what is the release schedule for v3? is v3 dev basically frozen?
> > 
> > Unless the enhancement is minor, yes.  
> > 
> > >  2 - when will v4 dev start?
> > 
> > I would prefer to wait as close to 3.0 release as possible.  The release
> > is still be handled in an integrated fashion with the rest of the
> > turbine projects.  And is being handled by Martin, I think it will be
> > RSN, but depends on his schedule.
> > 
> > >  3 - is there a list of v4 plans?
> > 
> > No.  Stephen has described some interest in refactoring the logic
> > between the java classes and templates.  Though I think he is leaning
> > towards leaving things more as they are.  And then v4 will likely
> > involve more minor changes, but they have not been determined.
> > 
> > >  4 - how does one submit suggestions/requests for v4?
> > 
> > I have setup scarab at 
> > 
> > http://scarab.werken.com:8080/issues
> > 
> > Please use this for both bugs and enhancements.
> > 
> > >  5 - I have several improvements/added features which I may try to
> > > implement if noone else is doing something similar - I would like to
> > > submit a list and get feedback, as well as where it would fit into the
> > > current development plans.. how/where should I do this.
> > 
> > same as above.
> > 
> > john mcnally
> > 
> > 
> > --
> > To unsubscribe, e-mail:   
><mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail: 
><mailto:[EMAIL PROTECTED]>
> > 
> 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to