* System.Web.UI/Page.cs:
* System.Web.UI.WebControls/LinkButton.cs: show the validation summary
when client validation and linkbuttons are used. Patch by Juraj
Skripsky.
svn path=/trunk/mcs/; revision=70294
* Page.cs: fixed and optimized ProcessPostData
The "second try" used for controls that created at OnLoad.
fixed for controls that use RgisterRequeresPostBack to handle post data.
svn path=/trunk/mcs/; revision=69301
* Page.cs: The specified theme must exist as either an application theme.
If the theme does not exist, an HttpException exception s thrown.
svn path=/trunk/mcs/; revision=69282
* Rationalize the user of MonoTODOs.
- Removed all the TODOs that were only overwritten methods
and had no further information.
- Methods that threw exceptions now have the message "Not
implemnted".
- Methods that return some constant are declared like
that.
- Removed a bunch of stale MonoTODOs that had not been
removed.
svn path=/trunk/mcs/; revision=68620
* Page.cs: fixed: PreviousPage property
when CrossPostBack is processed PreviousPage is initialized
only if PreviousPage property is called.
svn path=/trunk/mcs/; revision=68251
* Page.cs: fixed: for 2.0 only
When Page processes Callback IsPostBack = false, but it still needs
LoadViewState/ControlState and ProcessPostData
svn path=/trunk/mcs/; revision=66600
When page is invoked by cross-page posting, PreviousPage processed all live-cycle up to OnLoadComplite included.
IsPostBack, IsCallBack and IsCrossPagePostBack returns relevant values.
svn path=/trunk/mcs/; revision=65879
* Page.cs: use the new internal LosFormatter.SerializeToBase64.
* LosFormatter.cs: always work on base 64 strings even if the
input/output is on a Stream. Fixes bug #78640.
svn path=/trunk/mcs/; revision=61711
2006-03-07 Chris Toshok <[email protected]>
* Page.cs (InitializeStyleSheet): load the style sheet theme using
ThemeDirectoryCompiler.
(InitializeTheme): load the page's theme using
ThemeDirectoryCompiler.
(InternalProcessRequest): call InitializeTheme after OnPreInit.
(FrameworkInitialize): call InitializeStyleSheet.
(PageTheme,StyleSheetPageTheme): new properties to get the
respective themes.
* Control.cs (ApplyStyleSheetSkin): new method. Calls ApplySkin
on the ControlSkin (if there is one) for this control in the
page's StyleSheetSkin.
(ApplyThemeRecursively): applies the page's theme recursively to
the control hierarchy. Must be done this way because the control
tree is already present when we apply the theme (it has to be,
since theme's override settings).
* PageTheme.cs (GetControlSkin): add internal call to do the
lookup for us.
* PageThemeFileParser.cs: the parser object that represents each
individual skin file.
* PageThemeParser.cs: the parser object that represents the entire
theme directory.
* PageThemeBuilder.cs: this class generates the right exception on
the right event, but it's not hooked up yet.
In System.Web.UI.WebControls:
2006-03-07 Chris Toshok <[email protected]>
* WebControl.cs (EnableTheming): leave the MonoTODO, but implement
by chaining up to base.EnableTheming.
svn path=/trunk/mcs/; revision=57676
2006-03-02 Chris Toshok <[email protected]>
* Control.cs (ApplyStyleSheetTheme): remove the exception, and add
a MonoTODO.
* Page.cs (Theme): implement setter/getter.
(StyleSheetTheme): same.
* PageParser.cs (ProcessMainAttributes): parse the Theme and
StyleSheetTheme attributes.
In System.Web.UI.WebControls:
2006-03-02 Chris Toshok <[email protected]>
* WebControl.cs (SkinID): implement setter/getter, and have them
just chain up to base.SkinID.
In System.Web.Compilation:
2006-03-02 Chris Toshok <[email protected]>
* TemplateControlCompiler.cs (InitMethod): emit an assignment for
SkinID just after the creation of our object, and right after that
call "_ctrl.ApplyStyleSheetSkin (page)".
(CreateAssignStatementsFromAttributes): split out the majority of
this code to CreateAssignStatementFromAttribute, and change this
method to simply a loop over the attribute keys. In the 2.0 case,
skip the SkinID property, since that's handled explicitly in
InitMethod.
* PageCompiler.cs (AddStatementsToInitMethod): emit assignments
for Theme and StyleSheetTheme.
svn path=/trunk/mcs/; revision=57516
2006-02-23 Chris Toshok <[email protected]>
* Page.cs (ProcessCallbackData): track change to
ICallbackEventHandler iface.
* ICallbackEventHandler.cs: enable the proper members of this
interface.
* DataSourceSelectArguments.cs: reformat getter/setters.
In System.Web.UI.WebControls:
2006-02-23 Chris Toshok <[email protected]>
* BaseCompareValidator.cs, BaseValidator.cs, Button.cs,
DataControlField.cs, DetailsView.cs, FormView.cs, GridView.cs,
HotSpot.cs, LinkButton.cs, Login.cs, SiteMapDataSource.cs,
SqlDataSourceCommandType.cs, TableSectionStyle.cs,
TemplateField.cs, TreeNodeCollection.cs, TreeNode.cs, TreeView.cs,
ValidationSummary.cs, WizardStepBase.cs: fix tons of corcompare
errors. most were caused by a property/method being virtual when
it shouldn't be, or vice versa.
svn path=/trunk/mcs/; revision=57203
* MasterPage.cs (CreateMasterPage): don't nullref on null
contentTemplateCollection.
* ControlBuilder.cs: add a flushOutputStatements field.
* PageParser.cs (ProcessMainAttributes): handle Title attribute.
(Title): add getter.
* Page.cs (Title): implement getter/setter.
(InternalProcessRequest): after calling ApplyMasterPage, apply the
page's Title directive if there is one.
(AddContentTemplate): make the EditorBrowsable attribute apply to
the method, not the field.
svn path=/trunk/mcs/; revision=56634
* MasterPage.cs: rework this file, adding some static methods
gleaned from MS stack traces, and clear up the propogation of
content templates between nested master pages.
* Control.cs (TemplateControl): implement.
* TemplateControl.cs: re-indent some of the code.
(ReadStringRecource): according to msdn2, these throw
NotSupportedException.
* MasterPageParser.cs (HandleOption): implement. assign our
master page's MasterPageFile from the UserControl property.
* UserControl.cs (InitializeAsUserControlInternal): new method
that allows initialization without a page.
* UserControlParser.cs (ProcessMainAttributes): for 2.0 handle
MasterPageFile attributes, so we can have nested master pages.
(MasterPageFile): add a 2.0 specific property.
* TemplateControlParser.cs: in .net 2.0, our base class is
BaseTemplateParser.
(HandleOptions): be consistent and call base.HandleOptions.
* BaseTemplateParser.cs: new (stubbed) class.
* MasterPageControlBuilder.cs: new file, not filled in (and really
not used either.)
* Page.cs (InternalProcessRequest): call ApplyMasterPage.
(SaveExistingContentTemplates): nuke.
(ReapplyExistingContentTemplate): nuke.
(ApplyMasterPage): if we have a master page, call
MasterPage.ApplyMasterPageRecursive with it and add it to our
controls.
(set_MasterPageFile): remove call to SaveExistingContentTemplates.
(get_Master): call MasterPage.CreateMasterPage.
(AddContentTemplate): keep track of the page's content templates
in a local Hashtable - they aren't our master page's content
templates.
svn path=/trunk/mcs/; revision=56620