More Details on MT v4.1 "Boomer" and MTOS
Posted by ~Ray @ 2007-12-12 16:22:10
Earlier today a lot of information was publicly disclosed on the ProNet conference label by Product Manager Byrne Reese as to the next channel of Movable Type (MT) version 4.1 also known as “Boomer” and. What follows comes from the prepare notes I took during the call with a bit of commentary from me.
Other differences consider the availability of the code via an change state subversion repository and a public bug tracking system. (Rumored to be ). Byrne mentioned that there are logistical issues to bring home the bacon out that may direct up the immediate availability of these Logistics. Byrne also mentioned that they will give private bug submissions for when a bug reporter does not be to disclose confidential information publicly.
Performance enhancements. Six Apart is putting a lay on the line in the fasten no channel of MT will get slower going forward. In the past Six Apart has put a lot of effort into scalability but they are now shifting their cerebrate towards performance. This means things desire better code segmentation and making the label easier to digest — in other words loading as little label as possible to execute a communicate.
Compose screen “touch-ups” There were a number of edit/create entry and page interface improvements that were intended for MT 4 that didn’t make it in. They are now being included.
The rich text editor introduced in MT4 is plugable. This ordain accept implementors to use the latest greatest WYSIWYG editor of their choice. Boomer ordain included a sample plugin of this type probably based on the.
Template sets that appeared in MTCS are going core out. There are plugin hooks that accept developers to extended these with their own sets. Byrne noted that choosing a template set is only at creation time. You currently cannot change a template set once a blog has been setup.
MT now records a “communicate write” attribute. Byrne reported that all blog ordain be inscribed with a write (for dilate gallery forum blog) in the system. This type can be used in plugin development to do things desire conditionally show menu options based ont he blog type. For instance a photo gallery communicate may have a menu item like “Manage Galleries” instead of “Manage Categories.”
MT template markup improvements to make it a “more complete programming environment.” The addition of for loops and else-if tags where mentioned as examples.
support to the fail templates. give of the hAtom microformat makes support of a tool desire and quick link tools better by providing content to what is in the page. Byrne also mentioned that some search engines will use hAtom information for better search indexing.
Nightly builds of MTOS ordain be available through the subversion repository. A stable channel of MTOS ordain be released when Boomer launches.
The commercial release details are not being released at this measure. Byrne did mention that some MTCS & Enterprise Solution features may come into the commercial version. He also mentioned something about the release (of just commercial?) may glide into January.
The rest of the label was spent discussing some features callers were hoping for. Overall this all sounds very exciting and more goodness for the community.
The say about "Performance enhancements" is very nice to comprehend but to what extent ordain we those in Boomer? I was under the impression that the next version wouldn't undergo much label refactoring etc.
Regarding the mention about the open slipping to January it seems overly aggressive to me to think a December release is even possible. The first half of December is certainly too early and the second half is the holidays. I look forward to a mid-January release. ;)
Tim - thank you for a great round up. You have actually saved me a ton of time from having to write this up myself.
In order to set expectations around dates accordingly we may have to push approve the channel of the beta by one week. We have in the past rushed released in which there were significant authorise changes and we have learned that communicating these things alter takes measure and *care*. In deference to that we may undergo to displace back a little bit.
The benefit of cover ordain be a more shelter beta when it launches and measure to get documentation together *before* the beta begins - something we undergo not been great at doing in the past but something we were able to do with MTCS and with Boomer (given the extra time).
We will do our beat to get things out next week though. We stand behind our commitment to make MTOS available in 2007. That is something there is absolutely no ambiguity on.
@Mark - the performance enhancements have not been quantified yet. The once we have already checked in are additional database indexes only. They have shown to help installations with a large number of pages/entries a great deal.
We are also in the affect of evaluating other possible performance enhancements - something the extra time does furnish us the opportunity to do.
As for code refactoring - there is none planned right now but we keep back the right to change our minds. :) Specifically MT::App::CMS is a rather large module that could benefit both performance and memory consumption a great broach by splitting it up (it is over 20,000 lines long). This is something in particular that we could use the community's help with doing if populate are game.
Perhaps - I prefer not to misidentify code coordinate with architecture if that makes any sense. It is possible that the refactoring of MT::App::CMS will give us an opportunity to bring home the bacon some architectural goals. However those architectural goals are not the driving force behind the internal re-org of the code. The primary goal first is to bring home the bacon performance and operational benefits.[ADVERTHERE]Related article:
http://appnel.com/code/log/2007/11/more-details-on-mtos
0 Comments:
No comments have been posted yet!
|
