In continuation of the previous blog post on the PHOOP framework's background, I present here my design goals as I started working on the framework.
I primarily wanted to enjoy the benefits of inline html/php mode of coding for a typical PHP web application, but still make it completely object-oriented. The high-level design goals for the framework were set as follows:
What, another PHP application framework... well yes... Let me give some background first.
This has been a feature request for Ext.Net too, i.e. to provide a configuration option somewhere that if true emits out properly formatted script generated for initial GET request and for subsequent Ajax responses (an implementation might require considerable server resources is an altogether different story, especially as the script size grows).
Microsoft Exchange allows a user to access another User's mailbox in 2 ways, Delegation and Impersonation (Check this for more details). If you have used Outlook or Outlook web Access (OWA) and shared mailboxes with other users, chances are that you used Exchange delegation for mailbox sharing.
In continuation of my last blog post for managing Calendars dynamically for the ExtJs Calendar component, I present in this blog post the logic behind parsing and serializing Recurrence rules for the Calendar component, if you have enabled recurrence for the Calendar (You get to specify Recurrence rules for an event in the Calendar component, only if you enable recurrence for it, i.e. enableRecurrence=true).
Performing database side paging has always been a headache in Sql Server (as opposed to MySql which provides a built-in LIMIT clause for easy paging). However, I recently found an easy, fast and intuitive way of paging the data on the database side in Sql Server 2005 and later.
This time I needed to provide a drop-down list with selectable options exactly as you see for an ExtJs combobox. However, my base field was a TextArea instead of a single-line TextField, and I needed to provide selectable items in a DropDownList as text is inputted to the TextArea.
By the time you read this blog entry, the issue might already be fixed by the Chrome Frame team. Anyways, here's what we faced:
We recently had a strange issue with some of our users using IE with Chrome Frame to access their intranet application (that was actually a front-end to different other web apps). Some of these apps support Chrome Frame, while others do not. The actual sequence of events happened like this:
I just had an immediate need for modifying the core Ext.Net scripts that are embedded into the toolkit assembly itself. Till now, I resisted all temptations for doing so earlier, instead choosing to override Ext.Net behavior when needed by including my own scripts after the Ext.Net scripts on the page.