jObjective is currently undergoing some refactoring. It shouldn't break any compatibility, but the inheritance mechanism is being enhanced so the base class constructors don't have to be rewritten when inheriting. A side benefit is that my compiler/minimizer of choice, Google Closure, should be able to achieve better results. I am also going to use apply to facilitate any overridden base functions, rather than the current slightly tacky approach that's in development.
Once this is complete work shall start on Tutorial #2 which is going to be a mini project in it's self. The website is also going to implement some better HTML code formatting, so it should be easier to read.
jObjective aims to create a custom object orientated layer for HTML Javascript DOM elements. It simplifies access to data contained in various elements, allowing for single get and set methods to generate JSON objects of complex form layouts particularly, but not exclusively, for transmission via AJAX.
Showing posts with label jObjectve. Show all posts
Showing posts with label jObjectve. Show all posts
Thursday, 10 February 2011
Thursday, 27 January 2011
jObjectiveDotNET v1.0.1 Released
The first release of the jObjectiveDotNET Framework has been uploaded.
jObjectiveDotNET is a .NET framework which provides web controls which bind directly to the jObjective objects.
The compiled DLL of the framework may be downloaded at Google Projects. The DLL requires .NET 3.5 and includes the jObjective javascript files as embedded resources, so nothing else is required.
The first example web page may also be downloaded here. This example simply allows a set of input elements to post their data to a server side web service using jObjective. Simply download the web project, create a new IIS application and add a reference to the latest jObjectiveDotNET DLL. (Requires .NET 3.5)
Enjoy.
jObjectiveDotNET is a .NET framework which provides web controls which bind directly to the jObjective objects.
The compiled DLL of the framework may be downloaded at Google Projects. The DLL requires .NET 3.5 and includes the jObjective javascript files as embedded resources, so nothing else is required.
The first example web page may also be downloaded here. This example simply allows a set of input elements to post their data to a server side web service using jObjective. Simply download the web project, create a new IIS application and add a reference to the latest jObjectiveDotNET DLL. (Requires .NET 3.5)
Enjoy.
Introduction to jObjective
jObjective aims to create a custom object orientated layer for HTML Javascript DOM elements. The layer simplifies access to data contained in various elements, allowing for single get and set methods to generate JSON objects of complex form layouts particularly, but not exclusively, for transmission via AJAX.
This blog aims to examine the usage of jObjective and how it can benefit web development.
All files and examples are available to download on Google Project: jObjective downloads
A little bit of a prologue: I am currently an ASP.NET developer, some of the problems faced might be different to that of a PHP developer, but I believe the problems still exist in some form regardless of the higher level language. The jObjective Library aims to be independent of the language used to write the pages, although the examples on it's use that I will include will be written in ASP.NET. Hopefully this shouldn't be much of a problem as once the page is rendered to the browser there will be no ambiguity.
This blog aims to examine the usage of jObjective and how it can benefit web development.
All files and examples are available to download on Google Project: jObjective downloads
A little bit of a prologue: I am currently an ASP.NET developer, some of the problems faced might be different to that of a PHP developer, but I believe the problems still exist in some form regardless of the higher level language. The jObjective Library aims to be independent of the language used to write the pages, although the examples on it's use that I will include will be written in ASP.NET. Hopefully this shouldn't be much of a problem as once the page is rendered to the browser there will be no ambiguity.
Subscribe to:
Posts (Atom)