This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I just finished reading about EF Everywhere and it made me wonder what the lightspeed crew at mindscape is working on. One lightweight framework to rule them all sounds very appealing. Are you working on a mobile ORM. Basically... can you show us part/all/any of your roadmap and let us know where you are heading and some indication of when you will be heading there? One of the reasons I am asking is due to the frustrations with using lightspeed and breeze together. Which brings me to my next question... How are the Think Tank lightspeed suggestions handled? I read in an old forum post: changes are 75% based on user requests and suggestions and 25% things we think would make the product so much better Are there a lot of suggestions that are being communicated to you that don't make it into the think tank? I only see 2 out of 42 requests have been fulfilled. Thanks for your time! |
|
|
|
|
Hi, Over the past year we've been working a lot on the core engine of LightSpeed - improving the querying engine, removing bugs from the designer and just generally improving the foundations that LightSpeed is built on. This has been deliberate as LightSpeed is a fairly mature product now and closing some of the issues just helps make it a stronger platform going forward. It also means adding things later (e.g. capabilities on top of the core querying) is easier because the core is more stable. I've been watching the breeze.js thread a little, but with only a couple of our customers looking at it there's not a lot of return on investing our teams time in learning breeze.js and then making changes to LightSpeed to support it. Further to that, I haven't seen any concrete changes that we could add to LightSpeed to make interoping with breeze easier (please correct me if wrong, or provide some for the team to take a look at! :). Most of it seems like the challenges between a client side model and the server side model, which will always be a bit complicated. I'd personally like to hear if there are any particular pain points we could resolve there that don't make LightSpeed a more awkward product to use to help a small user base using Breeze (I don't mean that to sound condescending, more that we take a lot of care with the LightSpeed API to ensure we don't introduce breaking changes unless absolutely necessary or a major improvement! :-). We've been a little light on some of the change requests with LightSpeed with Version 6 due to the focus on repaying technical debt, strengthening the core and plugging bugs. We also do get a lot of feature requests outside the feature request mini site, although we do need to get more on top of that. I hope that helps explain what's been going on recently. Version 6 of LightSpeed will ship shortly and then we'll look more at some new features that help as many of our customers as possible :-) John-Daniel Trask P.S. I'm curious to see how EF7 turns out. Given it took them so long to get basics like enum support in there, I'm not confident that a rebuild from the ground up is going to be a win for users who stick with EF. In fact, almost any big-bang rewrite of a product typically fails. Losing six years worth of bug fixes and improvements puts the EF team in a big hole to climb out of to get back to where they are now. A good write up about this can be found here: http://www.joelonsoftware.com/articles/fog0000000069.html |
|
|
|
