Question on Priorities

A very valid question Peter - although I guess the availability of the COM APi allows developers to integrate Logos with other pieces of software for the benefit of the whole community. Admiittedly this is probably of more use for developer innovation than your average user however your average user will ultimately benefit!

Bradley Grainger said:

To avoid future disappointment, I'll let you know now that 4.0d will not have a major new user-visible feature; this is by design.

Bradley, thank you very much for this information! One of my biggest frustrations is when Logos is silent, I would rather be told up front, to sit and chill (except by M.J.) concerning an issue rather than to feel like my concerns/requests are being ignored. 

Terry

Bradley Grainger said:

To avoid future disappointment, I'll let you know now that 4.0d will not have a major new user-visible feature; this is by design. The purpose for 4.0d is to keep the Development team shipping code, and to get the minor fixes and improvements that have been made into your hands without undue delay. We'd rather ship small, incremental updates on a regular schedule than hold back 4.0d until there is a major feature ready to ship

Bradley, in this case then I think you made a mistake making it 4.0d.

4.0c SR2...x would be nearer the point (and more accurate) as its bug fixes

I will try and contain my disapointment and try to hibernate until 4.0e comes out.

Bradley Grainger said:

To avoid future disappointment, I'll
let you know now that 4.0d will not have a major new user-visible
feature; this is by design.

Having "merging reintegrated" is pretty big improvement too.   I would considered that "user facing", even if the users don't recognize it.

Bradley Grainger said:

Our beta testers are very important to us, so I'm open to changing the beta programme to a slower release schedule if the community consensus is that beta testers would be more interested, happier, etc. with that model.

I like little-and-often, rather than long waits with nothing. The last week or so before 4.0d was very slow in the Beta forum, so it was clearly time for the next round.

I see the COM API as a big deal, and opens up new options (L3 has a very rich API / Object Model). And yes, COM API was on User Voice (twice)!!!

The new URI formats (Logos and Logosref) are powerful and clean. Nice work.

The new exports are useful and important. More of those please.

Index merge is important.

Ongoing bug fixes and stable code is important. Thanks.

The way I see it, 4.0d B1 already does many things we need and want. I'm not disapointed by it.

Thanks Logos Team!

JimT said:

The way I see it, 4.0d B1 already does many things we need and want.

I agree with Jim. If publishers and hobbyists can do useful things with the API that we can benefit from, then it's worth having, and other features are worth waiting for. The URI feature is definitely very useful for those using Logos to teach. I'm sure that during the entire 4.0 development, lots of development time was 'wasted' building better tools that we'll never see for creating resources for publishers and Logos staffers to use. Except, of course that it wasn't wasted time. It's just that the benefits are indirect, not direct.

I guess I'm a dissenting voice here...I did see some welcome fixes and improvements, some mentioned here in this thread.

If i had my way; EVERYTHING I want would be out next week...but sadly, I don't run the dev's..

Thank you Bradley and company for a job well done, over a long period of time..it probably can get to be hard mentally and physically to put in so much time under such pressing conditions, and we certainly appreciate it.  [Y]

God bless you all.

bob

Dave Hooton said:

Bradley Grainger said:

Our beta testers are very important to us

Bradley

I'd like a fix for Collections (long outstanding) so that it keeps its View setting between restarts when part of a layout. This is so annoying.

Thanks,

YES!