Is there something I have to enable?Does it require the latest ODS?
Or did it simply not make it into this release (if so, please, please tell me it just missed this beta but will the next) 
…
I like the new javascript editor (i’ve only had a very brief look), but why the same tired old Java editor? If you can’t even get the Java editor updated when you move to Eclipse, how can you expect Notes developers to adopt Java?
Subject: the LS editor won’t make 8.5
this was announced at Admin 2008. It just did not make it it in time. It will come in a future release after 8.5 … not sure which they have targeted
Subject: Seriously? Wow, that’s a downer…
Without a doubt a LotusScript class browser is long overdue. If it wasn’t prioritized, then someone has clearly misplaced them and their grasp of reality. Utterly disappointing. Bitterly so. I’m beginning to understand a couple things:- Andrew’s blog post the other week
Subject: its not about prioritization, its about what can get done in the timeframe
they have some issues that won’t get done in the timeframe for 8.5 … if you think they should hold back, make a stink 
Subject: Agreed… maybe 2009 is the year for a class browser. 10 years late is better than never.
I’m not sure if I’d classify it as a ship-stopper due to the fact that the server should get into as many hands as possible for testing purposes… what a mess.
Subject: What about a Java editor?
Subject: Surely that is an absolute show stopper for most professional developers
My initial impressions were wow and then this post totally dismayed me - I cannot believe that IBM would seriously roll out a “Design Client” without at least the same level of Lotusscript functionality as the existing client
There have been strong rumours that there will be no LS debugger - how can you write LS without a debugger or is it just me that makes mistakes ?
On a positive note I like the idea of the search in designer and seeing the fields at view level without having to open the form.
Also like the much more accessible docment IDs and the ability to copy these to clipboard but some labels would be useful
Coming back to the LS bit, personally i would rather IBM didn’t deliver and IDE at all and focused on doing a complete job rather than deliver half a job
Oh and the concept of X pages looks awsome
thanks, Sean
Subject: if you think it is a show stopper …
than make your voice heard. There has been significant discussion about this in the Design Partner forum and meetings … all I can say is I agree with you
Subject: I have now asked
I have formally asked for an IBM view via the BP Forum
Subject: LS Class Browser
I’m a bit underwhelmed too.
The LS and Java editors seem to be exactly the same as Designer 6 or 7.
The new icons are nice though…
Mr Frunobulax
Subject: Why not?
I’m little bit disappointed about the priority of lotus script. This is the core language in lotus notes. Why XPages and not an Eclipse-like editor for lotus script. This was the only think i’m intrested on this release.
Subject: Please IBM, give us a Class Browser for LotusScript!
Hi IBM
We have been waiting for a LotusScript Class Browser since R5. Why don’t you just talk to the guys from TeamStudio who provide a class browser as freeware? In my opinion, this should be built in as standard into a proper IDE!
I appreciate new features like X-pages or DB2 access, but you should not forget to enhance the core features of lotus notes. I have got the impression, that the notes client has changed a lot, but the developers still have to suffer from a very poor IDE.
In case of java development, we can switch to pure Eclipse IDE, but in case of LotusScript, we depend on the Lotus Notes Designer, so please IBM, put a higher prioritiy on that part of LN/LD.
Subject: LS Editor
As John indicated, the LS Editor won’t make 8.5. Just a note here to say we understand how important this is and it was tough to make the decision to delay it.
We will deliver the LS Editor as soon as possible. At present, we have not set the maintenance release schedule for deliveries past 8.5, so I can’t say for sure, but we are thinking that 8.5.1 would be the likely delivery vehicle, and if its possible to provide it earlier, depending on how localized we can keep the capability, we may do that as well. As I said, we intend to deliver it as soon as possible.