Answered Q2 2008 "Futures" Build

Feed from this thread

Answer Telerik Admin Master
Posted on Jul 8, 2008 (permalink)
We are very pleased to announce the availability of our new “Futures” build of RadControls for ASP.NET AJAX. This is a preview build for our Q2 2008 Release and includes latest developments on all controls in the suite. We are dedicated to involve the community with our progress and hear your feedback on the new features and improvements we have been working on.

The “Futures Build” (Telerik.Web.UI_2008_2_708) is now available for download in your Client.Net accounts. Please see attached screenshot.

See online demos at:
http://www.telerik.com/demos/aspnet/prometheus-futures

Documentation will be available at (within several hours):
http://www.telerik.com/help/aspnet-ajax-futures

Your feedback will be highly appreciated – please do not hesitate to share any suggestions or comments you might have.

Please note that this is a work-in-progress and some of the features are still in development and QA.

What’s New in RadControls for ASP.NET AJAX Q2 2008 Futures (Version Number 2008.2.708):

Common for all controls:

Removed the obsolete Default2006 and Mac skins. Added the new Gray skin and updated Telerik skin.
RadRotator – new control in the RadControls for ASP.NET AJAX suite
1. Slides any kind of content - able to operate with server controls as well in its template items
2. Declarative binding to a datasource
3. Ability to slide frames left, right, up and down
4. Ability to control the sliding speed
5. Built in-buttons mode to allow for manual sliding
6. Full-blown client-side API for programmatically manipulating items
Coming Soon
1. WebService support for dynamic loading of frame content
2. New rotator types to provide different user experience
3. 12 built-in skins
4. More visual scroll effects
RadAjax
What’s Fixed:
1. RadAjaxPanel is now rendered as SPAN if the UpdatePanel.RenderMode == Inline
2. Fixed scenario with validators inside ajaxpanel and radajaxmanager on the page
3. Width and Height are now applied to the outer DIV if set
RadChart

What’s Fixed:
1. Candlestick charts now respect XValue
2. Fixed issues with nullable data source
3. Fixed issues with DefaultLabelValue
4. Fixed OutOfMemoryException caused by certain gradient settings
5. Top left pixel is not grey anymore
6. Fixed issues with chart series item label margins
RadComboBox

What’s New:
1. Filtering functionality
2. Sorting functionality
3. show() and hide() client side methods of RadComboBoxItem
What’s Fixed:
1. Removing an item in OnClientItemsRequested event threw an error; Fixed
2. BackColor property of RadComboBoxItem didn't work if its value was unnamed color; Fixed
RadDock

What’s Fixed:
1. Fixed a problem with initially collapsed docks in Firefox
2. The content width of the dock was not set correctly during resize
3. Fixed a problem with the dock's state when left and top are not set
RadFormDecorator

What’s Fixed:
1. Fixed a problem when the page URL contains spaces.
2. Fixed compatibility with RadStyleSheetManager control
3. Fixed compatibility with RadGrid
4. Fixed a problem when the global font-size is set in percent
5. Fixed a problem with TEXTAREA elements in IE not being visible when a RadFormDecorator is on the page.
RadEditor
What’s New:
1. Added a new property - ToolsWidth, which is used to set the width of the editor toolbar
What’s Fixed:
1. Fixed a rendering issue - width/height values were rendered twice.
2. Fixed a problem when the editor is initially hidden and then made visible with client script.
3. Fixed a problem with fullscreen mode when the editor's parent has css position: fixed.
4. Fixed a problem with the ajax spellchecker and the ToolProviderID property
RadGrid

What’s New:
1. Client-side data-binding
2. get_cell() method added for GridDataItem
3. rowDataBound added
4. virtualItemCount support for client-binding
5. ClientEvents.OnCommand + sortExpressions & filterExpressions on the client
6. File extention property for GridExcelExport added
7. Added new virtual method to copy column editors settings in orrder to workaround problem with shared column editors creation
8. Added autoscroll functionality when dragging items
9. Change: ChangePageSize will reset CurrentPageIndex
What’s Fixed:
1. Fixed exception thrown when exporting with objectdatasource with custom paging and no results are returned
2. Added a   to the table cell when the hyperlink is an empty string
3. _uniqueIDToClientID should replace ":" as well.
4. Fixed the column alignment in IE quirks mode
5. Fixed some scenarios, in which column did not align in IE (e.g. vertical scroll only)
6. Fixed a JavaScript error thrown in Mozilla when the grid is with frozen columns and ShowFooter=true
7. Fix for an IE issue related to "Submit Query" text insert inside the sort sprite buttons
8. Fixed all column editors to take up the correct skin when the grid's skin is set in web.config
9. Fixed the skin of the pager slider, when the grid skin is set in web.config
10. Fixed a header/data cell alignment issue in IE when the MasterTable is narrower than the Grid
11. Changed filtering menu design-time serialization and visibility
12. Fixed a JavaScript error when columns are resized with footers shown
13. Performance optimizations when scrolling in Safari
14. Dragged items in Safari 3 are now positioned correctly when page is scrolled.
15. Fixed an exception when font size is set.
16. URLs now work as expected when exported PDF
RadInput

What’s New:
1. Client-side initialization improvements - Fixed a problem with delay before the value of the text field to be filled on initial load
What’s Fixed:
1. RadNumericTextBox: Fixed a problem with "Esc" button
2. Fixed a problem with RadNumericTextBox and UpdatePanel
3. The ButtonCssClass is now applied as expected
RadMenu

What’s Fixed:
1. RadContextMenu did not honor the style z-index property, fixed;
RadPanelBar

What’s New:
1. show() and hide() client side methods of RadPanelItem
RadScriptManager and RadStyleSheetManager

What's New:
1. The controls now have an OutputCompression property to control the gzip/deflate compression of the combined output.
RadScheduler

What’s New:
1. The external edit example now uses RadDock instead of RadWindow. This approach achieves the same functionality with greatly simplified code.
2. New property - NumberOfHoveredRows that controls the row hover and initial appointment duration.
3. Improved client-side loading time by around 30%.
4. Exchange provider.
What’s Fixed:
1. Appointment start and end time are now accessible on the client side when the server is in different culture than en-US.
2. Appointments with zero duration are now rendered when they occupy the first visible slot in week view.
RadSlider

What’s Fixed:
1. The slider now supports two drag handles.
2. Added new server and client API to support the two handle mode.
What’s Fixed:
1. Fixed a problem with the ValueChanged server event - sometimes it was called twice
RadSpell

What’s Fixed:
1. Fixed spell dialog localization problems
RadSplitter

What’s Fixed:
1. Fixed a problem with the ContentUrl property not always resolving to the correct address.
2. Fixed a problem when the slider is initially hidden and then made visible with client script.
3. Fixed a problem when the splitter control is absolutely positioned
4. Fixed a small sliding pane positioning problem in Firefox
5. When you have HeightOffset>0, Height=100% the splitter takes 100% height of its parent.When the splitter is in a TABLE (width/height in percents), the splitter resizes to smaller size as expected, when you resize the browser.
RadToolBar

What’s Fixed:
1. The calling set_enabled on a split button, configured to use a DefaultButton did not change the enabled state of the default button. Fixed.
RadToolTip

What’s New:
1. Added a new method to the client API - updateLocation().
RadTreeView

What’s New:
1. Tri-state checkbox support
What’s Fixed:
1. On rare occasions OnClientMouseOut did not fire. Fixed.
2. OnClientNodeEditing and OnClientNodeEdited now fire even if the node’s text has not changed.
RadUpload

Breaking Changes:
1. Client-side localization does not respect the Telerik.Web.UI.RadUploadUtils.Localization object anymore. Instead, the client-side set_localization property is used.
2. RadProgressArea’s Localization property is not a dictionary anymore. Instead, the object contains strongly named properties (RadProgressArea1.Localization["Total"] = "out of "; is changed to RadProgressArea1.Localization.Total = "out of ";)
What’s New:
1. RadUpload’s HttpModule is reworked and now the control supports IIS7 integrated mode; Memory optimization relies on the default .NET Framework 2.0 engine.
2. Telerik.RadUpload.TempFolder application setting is deprecated, as the files are handled by the standard .NET Framework engine.
Attached files
- FuturesDownload.png
Reply
ewart Master

Posted on Jul 9, 2008 (permalink)

Good stuff!

Exploring the RadComboBox Office2007 skin.. feedback is it would benefit from some padding in the skin so that the text is not hard up against the input - hopefully this can be the default for the final release as it makes a big improvement to the look:

<style type="text/css">
.rcbInput
{
padding-left: 3px !important;
}
</style>

My personal preference is also that the font looks better 1px larger, perhaps consider that too:
font-size:12px !important;

Final comment is in IE6 the dropdown on this skin does not line up vertically wit the input box as it does in FF2

regards
ewart

Reply
Nigel

Posted on Jul 9, 2008 (permalink)

Excellent work. It's funny, I actually spent TODAY trying to get something like a client side OnCommand for the RadGrid working, and what do I read in the release notes. There is is. Nice work Telerik. I have trialed both yours and Component Arts components and I must say that yours are not even in the same ball park. Very profession, well maintained controls..

Thanks heaps, keep up the great work

Reply
Shaun Peet MVP

Posted on Jul 9, 2008 (permalink)

I understand that this is a Futures release and that what we're seeing isn't completed but the rotator in its current form has got me worried. I usually try to kick the tires of a new control in a semi-live environment but there's no way this can happen with the rotator in its current state. Is there any chance somebody can answer these questions for me?

1) Is there going to be a way to advance frames without sliding? The old rotator had a transition effect property that allowed frames to be faded in and out rather than sliding in a particular direction.

2) Is there going to be a way to toggle the border from showing? IMO, this should be OFF by default. I'm guessing setting the BorderStyle / BorderWidth would have a similar effect; in which case it makes even more sense to have the border off by default with an easy mechanism for turning it on.

2b) Buttons off by default as well? Or, is there any way there could be configurable areas for "navigating" the rotator that could be placed on any of the four sides. I'm thinking something like an "<AdvanceUpTemplate />", "<AdvanceLeftTemplate />", <AdvanceBottomTemplate />, etc. By default, the contents of these would be the buttons (if set to visible), but it would also allow us to create custom buttons / html on any of the four sides.

3) What the heck is the RotatorType "FromCode" and when / where / why / how is it used?

4) Will there be a property similar to the PauseOnMouseOver from the old version?

Thanks in advance,

Shaun.

Reply
bemara57

Posted on Jul 9, 2008 (permalink)

Yes you fixed RadUpload working with IIS7!!!! It's working great, even on a IIS7 shared hosted server. This is great!

Some aesthetic feedback about the skins.. What did you do with the Telerik skin?!?? If it was ugly that would be okay since it's a matter of taste.. but it's a plain old white. If I wanted a plain white skin, I would of just made a skin with no colors. I liked the old Telerik cause it had green highlights, making it look like it's glowing. This is going to make me change all my skins from the Telerik one, unless this is convincing enough. It's almost like the new "Gray" skin you introduced, so I don't get why you changed the Telerik skin like that.

Reply
bemara57

Posted on Jul 9, 2008 (permalink)

One thing I noticed about the RadEditor is that the Style Builder icon in the toolbar doesn't show up anymore when displayed. I'm using the Outlook skin by the way.

Reply
Telerik Admin

Posted on Jul 10, 2008 (permalink)

Hello bemara57,

@ewart maclucas:
Thank you for your feedback. We've adjusted the Office2007 skin accordingly. The font size, however, will continue to be 11px, in order to preserve consistency between RadComboBox and the Office2007 skin for all other RadControls.

Regarding RadRotator
Shaun, we plan to have the *new* RadRotator support all the capabilities of the RadRotator Classic.
In addition to that, we plan to add more functionality to it, than was possible before. This is why the RadRotator is being implement on a entirely different logic from before - so that it is possible to integrate new functionality naturally into its architecture. The way the *old* Rotator was implemented it basically could not be further enhanced due to its lack of inner integrity. There are a number of properties designed to work with one rotator "mode", and yet another pack designed to support another "mode". Just reading through the names of the properties often got people confused when to use what. In addition to this the *old* Rotator binding had some limitations, and support for WebServices (load on demand) was severely lacking.

Now, up to your questions:

1) Yes, there will be a mode that allows change of frames without sliding. However, we are working on providing cross-browser effects, rather than the IE specific ones. Non-IE browsers, especially FireFox are taking greater share each month, and it is of top importance to provide all features to be cross-browser where possible. Thus, having a set of effects might not make it to the original RadRotator release. In case this is the type of Rotator you commonly use, the RadRotator Classic should be fine to use for some more time.

2) We are currently working on RadRotator skins. It will feature a full set of 12 skins, as in all other RadControls. We will consider providing skins without borders. In all cases, it is easy to override the border by providing CSS on the page that does so - and we will show you how to do it, should you need it after the official release.

3) Currently the default for RadRotator is to show buttons. Integrated buttons are a feature that did not exist in *old* RadRotator - yet it is a commonly requested one. You can easily start the rotator in automatic mode by setting RotatorType="AutomaticAdvance". This is clearly demonstrated at the default example, as well as at the DeclarativeDataSource example.
On a side note - yes, there will be properties that will allow the developer to specify button IDs. In this way a developer will be possible to place buttons of their choice and look anywhere on the page to control the RadRotator.

3) We plan to introduce a number of rotator *types* - that will get the rotator provide different user experience. For the time being there are two types - Buttons and AutomaticAdvance - but we eventually plan to bring those to 5 or 6. As for the FromCode type - it just means that the rotator will not have any ways for the user to interact with it directly, rather it will be through some other means that the developer has provided - that is the rotator's API methods will need to be explicitly invoked for the rotator to do something.

4) At present, if the RotatorType="AutomaticAdvance", the rotator will pause if the user hovers with the mouse (you can test that on the demos).

Regards,
Tervel
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Reply
Nigel

Posted on Jul 10, 2008 (permalink)

Hi, I purchased the toolkit yesterday, and am currently working on a site that could really make use of a fully functional rotator tool. Is there anyway I can get access to the RadRotator Clasic?

Reply
Telerik Admin

Posted on Jul 10, 2008 (permalink)

Hello Nigel,

You can request the classic version of RadRotator through our support ticketing system and we will gladly provide it for you (since the old Classic versions of our controls are not present under the Client.NET account for new customers). Thus you will be able to test the product following the instructions from this KB article.

Best regards,
Stephen
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Reply
bemara57

Posted on Jul 10, 2008 (permalink)

This is one last attempt to salvage the old Telerik skin. It would be great if you kept the original skin and just named the new one "White Dove" or something. You can never have enough skins. And I know it's your skin and all, but you can't be completely changing the color scheme of a skin (not just a little, but radically) and expect no one's going to care. There are websites out there that have a branded look already. Not cool..

Reply
Telerik Admin

Posted on Jul 10, 2008 (permalink)

Hello Basem,

According to the skinning survey we carried out, the Telerik skin was not very used, because of its bright light green color. That is why we decided to modify and facelift it, in order to make it more attractive. Of course, we are aware that some people like the older version more, that is why the controls offer the opportunity to use non-embedded skins. On the other hand, we must do our best to offer skins, which suit the majority of customers.

Regards,
Dimo
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Reply
AK

Posted on Jul 10, 2008 (permalink)

Am I assuming correctly, once the "obsolete" skins are removed, I'll have to re-code them back in as a custom skin? I do use the MAC radtabstrip skin as I find it's one of the best when having a secondary level of tabs. It would be nice to see a few others skins look better when using a second level.

Reply
Telerik Admin

Posted on Jul 10, 2008 (permalink)

Hi Andrew,

Using a removed skin is quite easy - you have to copy the CSS files and images from your RadControls for ASP.NET AJAX installation folder (Skins subfolder), place it anywhere in your web application, where you find it convenient, register the CSS file using a <link> tag and set EnableEmbeddedSkins="false" to the respective control.

As for the second level of tabs - thank you for the recommendation, I will pass it to our designers.

Sincerely yours,
Dimo
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Reply

ewart Master avatar

Posted on Jul 10, 2008 (permalink)

Another easy to fix skin issue wth the RadCalendar

TableLayout_Web20
{
width: 100%;
}

The issue and solution is also documented here..
http://www.telerik.com/community/forums/thread/b311D-meehh.aspx

paste a standard calendar in with Web20 to illustrate the problem:

    
             <telerik:RadCalendar ID="rdHolidays" runat="server" AutoPostBack="True" CultureID="5129" 
        
                                          CultureInfo="English (New Zealand)" EnableMultiSelect="True" Font-Names="Arial,Verdana,Tahoma" 
        
                                          ForeColor="Black" Height="162px" SelectedDate="" Style="border-left-color: #ececec;  
        
                                          border-bottom-color: #ececec; border-top-color: #ececec; border-right-color: #ececec"   
        
                                          ShowRowHeaders="False" UseColumnHeadersAsSelectors="False"   
        
                                          Skin="Web20">  
        
                                       </telerik:RadCalendar>

I really hope this can also make the new builld.

Telerik Admin

Posted on Jul 11, 2008 (permalink)

Hello Ewart,

Actually a better fix for this issue is to remove the defualt width from the skin, which has now been done. Thank you.

Regards,
Dimo
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Reply
Raynald

Posted on Jul 11, 2008 (permalink)

Hi,

Have you an idea of delivery date of final version ?

Thanks

Reply
Telerik Admin

Posted on Jul 11, 2008 (permalink)

Hello,

The official Q2 2008 release is scheduled for July 22, 2008.

All the best,
Dimo
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Reply
Shaun Peet MVP

Posted on Jul 12, 2008 (permalink)

Any chance there will be an interim build with a more production-ready rotator prior to July 22?

Everything else in the futures release looks great, btw.

Reply

ewart Master avatar

Posted on Jul 13, 2008 (permalink)

The default skin for the timepicker could benefit from a similar padding-left as the text is also fairly hard up on the left side:

    
            <telerik:RadTimePicker ID="rdtStart" runat="server" Width="110px" AutoPostBack="true">  
        
            <TimeView Culture="en-US" StartTime="5:00:0" EndTime="22:30:0" Interval="0:30:0" 
        
            Columns="5" TimeFormat="h:mm tt" Skin="Default">  
        
            </TimeView> 
        
            <DateInput MinDate="1-Jan-1985" Skin="Default" MaxDate="31-Dec-2010"   
        
            Width="120px" DateFormat="HH:mm" Culture="en-US" /> 
        
            </telerik:RadTimePicker>

The below snippet almost does the job for you, looks great in the text position, except now the right hand side of the control then looses it's border :( well, I tried anyway!

.radEnabledCss_Default,
.radEmptyMessageCss_Default,
.radHoverCss_Default,
.radFocusedCss_Default,
.radReadOnlyCss_Default,
.radDisabledCss_Default,
.radNegativeCss_Default,
.radInvalidCss_Default
{
padding-left: 3px !important;
}

cheers
ewart

Telerik Admin

Posted on Jul 14, 2008 (permalink)

Hello,

Shaun, we do not plan to officially release another build before Q2, however, you may open a separate support ticket and explain what exactly do you need.

Ewart, the right border disappears exactly because of the larger left padding. That's why the left padding can be 1px at most and that's the way it is in all skins.

All the best,
Dimo
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Reply
ewart Master

Posted on Jul 14, 2008 (permalink)

>>That's why the left padding can be 1px at most and that's the way it is in all skins

Yep well my feedback is it look pretty average when not squished up against the border, and I guess it will be like that in all skins, as you say.

Some more feedback - the Office2007 combo has a new yellow/orange bar showing the hilighted option. This looks truely excellent, and is much better than the previous version.

I note though in combo's with small widths (e.g. a list of state codes, "CA, "OR", "DC" or mins "1, 2, 3 .. 59, 60") in IE6 that you end up with a horizontal scroll bar within the dropdown, I suspect because of the width of the orange bar.. I suspect also this is an IE6 special that is not worth addressing.

cheers
ewart

Reply
Christian Surieux Master

Posted on Jul 16, 2008 (permalink)

Hello,

For me jumping from 1.610 to 2.708 broke all the RadComboBox ?
I have removed the previous patch to display selected item and multiline textboxes, thinking pb with RadFormDecorator is solved but it is worse : nothing is displayed in radComboBox and if I try to display the list clicking on expand button I get a javascript error saying 'this object can receive focus because it is hidden or could not receive focus'....

I get back to 1.619 with temp fixes if I don't finds something soon.

Regards
CS

Reply
Telerik Admin

Posted on Jul 17, 2008 (permalink)

Hello,

@ewart maclucas:
Thank you for your feedback. We've added the changes that you request to our schedule. Your Telerik points have been updated.

@Christian Surieux:
Please await your answer in the second forum thread that you have opened specifically for this problem.

Best wishes,
Alex
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Reply
David

Posted on Jul 22, 2008 (permalink)

Dimo mentioned back on the 11th that the release was scheduled for today (July 22, 2008).

Is the release still on schedule?

Thanks,
David

Reply
Telerik Admin

Posted on Jul 22, 2008 (permalink)

Hello David,

We are making final adjustments before the release and it will be available tomorrow.

Sincerely yours,
Svetlina
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Reply
ewart Master
Posted on Jul 22, 2008 (permalink)
I've just finished converting my entire website from the old asp.net radcontrols to this future build version of Promethesus. The process took a week for about 40 pages containing pretty much everything (window, tabs, splitters, graphs, grids, calendar, ajax, comboboxes, editors, inputs, menus, panelbar, sliders, the new formdecorator and upload) Did I mss anything? ;)

The site is in beta and is hosted http://trial.fitnessmentor.co.nz; people are feel to play with the trial, to see the new radcontrols in action, you'll have to use a test credit card 4111 1111 1111 1111 to join. if that site no longer exists then try www.fitnessmentor.net , that will be the live site. I'll be happy to give free accounts for people wanting just to checkout the controls in a real world scenario.

Anyway, my experience with the new framework was some highs and lows, a summary:
- using ajax on a user control that has been dynamically loaded now requires some extra effort. I could not figure this out on my own but Telerik sorted it for me. most of my week was stuck here so it your not doing this or know the magic 5 lines of code you need this will be much quicker!
- graphs converted without a hitch; just make sure you have cleaned out the old dll's first from all referenced projects, not just your main project, otherwise you'll have duplicate dll messages up the wazoo.
- I was able to ditch my entire customised skin pack and efforts. which is great. I had lots of little tinkerings to make the skins look better, using themes. I miss the glassy electric tabstrip but on the whole the new skins range from ok to excellent in my book, most at the latter end of the scale. There are maybe a handful of tweaks I could apply still but on the whole the skins look good in my website.
- from a manageability perspective, I love everything being wrapped up in one dll, it's simply fantastic. I'm using the embedded scripts/css approach too, although I may revert that once I've tested the prformance.
Reply
Hessner MVP

Posted on Jul 23, 2008 (permalink)

The provided links are invalid?

Reply
Jeremy Coenen

Posted on Jul 23, 2008 (permalink)

When is the Q2 release coming out?

Reply
Stratos Karimbakas

Posted on Jul 23, 2008 (permalink)

the Q2 release is now used for their online demos. Im guessing it will be available for download within a few hours.

Reply
Telerik Admin

Posted on Jul 23, 2008 (permalink)

You're right, Stratos. All Client.NET accounts will be updated in a couple of hours.

Thanks for your patience,
Paul
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.

Reply

Answered Q2 2008 "Futures" Build

Products

Consulting

Purchase

Support

Community

Company