I haven't had a chance to yet, but I'm going to take a look this weekend.
I'll try to take a look asap.

Thanks for all the work and rework after discussing it.

On Sat, Jan 17, 2009 at 7:21 PM, Krzysztof Koźmic <
[email protected]> wrote:

>
> Jonathon,
>
> Have you had the time to review the patch for InterceptorSelector? If
> you have any feedback on the implementation, since it's weekend I could
> work on it a little.
>
> cheers
> Krzysztof
>
> Jonathon Rossi pisze:
> > *DynamicProxy2* is fairly stable. I was planning to wait until the
> > Silverlight and Interceptor Selector work has been finished and
> > settled for a bit before making a release. There are 13 unresolved
> > issues which I need to have a good look at. I have been writing some
> > documentation, but haven't got back to finishing off the initial work
> > to get some feedback. If no show stoppers arise, I'd expect sometime
> > in March.
> >
> > *NVelocity* is stable, and has been for quite some time. There are 14
> > unresolved issues with several of them being enhancements. To be
> > honest, I haven't done anything to resolve the open issues, but I plan
> > to soon. Since Ken has suggested that MonoRail would be released
> > March-ish, and since NVelocity is mainly used as a MonoRail view
> > engine (however I know others including myself use it for non-MonoRail
> > things) it should be released before MonoRail. I expect by the end of
> > February would be an appropriate time. At this stage I haven't updated
> > the documentation, but I plan to write some basic documentation on how
> > to use it without MonoRail and update what we have at the moment,
> > which may include some repetition of what the Velocity pages contain,
> > but this isn't a big deal since the projects are no longer so similar.
> >
> > *VS Wizards/Integration* are out of date (both with Castle and with
> > VS2008 support) and to be honest again, I haven't done anything to get
> > them usable. Personally, I don't know if a ActiveRecord project
> > template is very useful because you can use ActiveRecord in different
> > ways (ActiveRecordBase or not), while the current wizards might be
> > promoting ActiveRecordBase when most of us don't use it. I know this
> > is off topic but there is also quite a few ways to set up MonoRail so
> > do we want a fairly basic template just to get devs started or
> > something much more? I have never used the wizards for anything real
> > because I just look at another project to set up a new project. Maybe
> > all we need is to make better sample projects and keep them up to date
> > since most of our users should be fairly comfortable with building a
> > project from a sample (or just renaming a sample project). I also
> > don't know if we want to integrate Castle Visual Studio Integration
> > from the contrib with the new project wizards. With that said there
> > are quite a few blocking issues before this can be released.
> >
> > On Sat, Jan 17, 2009 at 4:23 AM, hammett <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >
> >     Guys, it's been two months and a half since the project was split and
> >     new leaders stepped in. In the name of transparency I'd like to ask
> >     each of the new leaders the following questions:
> >
> >
> >     - Your project name:
> >
> >     - What's its status (Stable, unstable)
> >
> >     - What have you done towards releasing it? What's the stopper?
> >
> >     - Any ETA for the release?
> >
> >
> >     Thanks
> >
> >     --
> >     Cheers,
> >     hammett
> >     http://hammett.castleproject.org/
> >
> >
> >
> >
> >
> > --
> > Jonathon Rossi
> >
> > >
>
>
> >
>


-- 
Jonathon Rossi

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Development List" 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/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to