Wigbi 1.0.2 release notes

Wigbi 1.0.2 was released yesterday. The new release features some handy additions and some important changes.

A change that is important to note is that the View class has been stripped. All View::add methods (except View::addView) have been removed, since they made the View class really messy and I regret adding them there in the first place. Due to this, all UI plugins have been changed to not use these methods. When upgrading to Wigbi 1.0.2, old UI plugins must be modified not to use the removed methods.

Another big change is that all of the view/edit UI plugins (e.g. NewsControl and NewsForm) have been merged into one single control. Furthermore, they do not add a serialized version of the object to a hidden textarea, but add the ID of the managed object into a hidden field instead. This makes them more secure and easier to manage.

The WigbiDataUiPlugin class has a really handy addition. The getSet() method will make he property section of all data plugins a lot smaller. Also, it is verified that the constructor can use parameters. See the MenuItem class for examples of these two changes.

Wigbi now embeds the startup JavaScript code in a CDATA comment, which means that the code no longer affects HTML validation.

Finally, the RuntimeBuild.obfuscate parameter can be removed from the config file. It is no longer used.

In all, the new release makes Wigbi even more light-weight. Let me know if you decide to try it out. I would love to hear what you think of it.

Wigbi 1.0.1 release notes

This release features major plugin adjustments. For instance, the two bundle files that were previously created by Wigbi are no longer generated. Instead, Wigbi creates one per data plugin and uses the .js file of each UI plugin. A Wigbi 1.0.0 app MUST remove these bundle files to ensure that no classes are conflicting.

The auto-generated data plugin class files are no longer commented, which is meant to make them easier to read. Future versions will probably feature far better compression as well. For instance, get/set props will probably have a convenient method that make each property into just one row.

Besides being able to specifiy additional CSS and JavaScript paths that will automatically be added when Wigbi is started, the Wigbi config file contains a key for PHP paths as well. This makes it even easier than before to extend Wigbi with your own functionality.

The 1.0.1 release also features two new UI plugins for working with the menu item data plugin. The list will probably be generalized in future versions.

From this version on, unit tests are not added to the release bundle. To get hold of the unit test bundle, fork the source code on GitHub.

Wigbi 1.0.0 release notes

Wigbi 1.0.0 is a complete rewrite of previous Wigbi versions. New developers are adviced to check out the documentation, demos and tutorials on wigbi.com. The release feature major changes, of which only some are listed down below.

The Wigbi configuration file has been completely rewritten and uses real ini sections. Older configuration files will not work with Wigbi 1.0.

Wigbi no longer features bundled classes. All the source code is provided as is, which simplifies modifications and bug fixes in an already running Wigbi instance. The two wigbi/php/wigbi and wigbi/js/wigbi folders are now removed as well. The Wigbi classes are added directly in wigbi/php and wigbi/js.

Wigbi no longer creates bundled JavaScript files for the data and UI plugins. UI plugins already have a JavaScript file, so generating file for them is no longer necessary. For data plugins, Wigbi now generates one file per plugin. The obfuscate option has been removed from the configuration file since it’s no longer used by Wigbi. For now, the JavaScriptPacker tool is still bundled with Wigbi, though. It may be removed in future versions.

It is now possible to change the value of the Wigbi::configFile(..) property to make Wigbi use another configuration file when starting up. However, note that the property is currently not set for the JS Wigbi class, since the PHP property is relative and the JavaScript property must be app relative. It is important that you change the Wigbi._ajaxConfigFile variable as well for now.

Some Wigbi classes that were previously static have now been made non-static to make it possible to create custom instances. However, the Wigbi class has default instances of these classes that are setup with the Wigbi config file.

All property methods have been modified. Instead of x()/setX(..), properties now take an optional set parameter if they are settabl…just like jQuery

Wigbi now features a quite basic MVC engine which is inspired by ASP.NET MVC. This makes it even easier to separate functionality from content.

The WigbiUIPlugin base class has been simplified compared to the old one. It contains a few help methods and must still be inherited.

Wigbi 0.99 is out!!!

After a loooong vacation and a lot of fiddling around with the limited time, I have finally managed to get a new Wigbi release out and a new site up and running. The new version is 0.99 and features a lot of improvements, new functionality, major bug fixes etc. Make sure to download it and have a look at the new tutorials and demos.

I have uploaded new Wigbi downloads, including Wigbi itself and its source code (optional). You can now also download the Wigbi Demos, which demonstrate Wigbi and its various classes and plugins.

Download Wigbi 0.99

Wigbi and the Wigbi Demos are easily downloaded from the web site:

Download Wigbi here

Release notes

Wigbi 0.99 features several MAJOR modifications and structure changes. It is the biggest release so far and will require major changes to your apps if you replace an old Wigbi version with this one.

The release also features major see and control changes. New features have been added and a couple of bugs have been discovered and fixed during the work with the Wigbi Demos, where much functionality is tested.

• The release bundle still includes the same folders as before – wigbi, wigbi_controls and wigbi_seeds. However, a new page has been added to make it even easier to get started with Wigbi – wigbi_test.phpThis file contains code that verifies if Wigbi is correctly configured. It uses the WigbiWizard control, and thus, the control is now added to the Wigbi controls folder by default. If you do not need it, feel free to remove it.
• Previously, the Wigbi include page added white space, which caused doctype tags to not be detected by the browser. This has been fixed. Make sure to include Wigbi BEFORE the document type – at the very first line, before defining any document types.
• The Wigbi start function no longer has any parameters. Instead, use the following properties BEFORE calling start, if you want them to apply:- Wigbi::setTheme
  • Wigbi::setGenerateHtml
• Seeds are now to be added to the wigbi/seeds folder instead of the old wigbi/php/seeds folder. This removes an unnecessary folder level.
• Controls are now to be added to the wigbi/controls folder instead of the old wigbi/php/controls folder. This removes an unnecessary folder level.
• I have decided to not use __get/__set properties in any Wigbi PHP system classes in order to make all classes behave in the same way, no matter if they are static or not or in PHP or JavaScript.Static classes cannot use __get/__set and Seeds cannot either (since they are regarded as public variables and thus get included in the database). So from now on, Wigbi will only use the property()/setProperty() standard. This change affects the following classes:

  -    PHP.System.Core.BaseControl
  -    PHP.System.Core.SeedFunction
  -    PHP.System.Core.SeedList
  -    PHP.System.MasterPage
  -    PHP.System.SearchFilter
  -    PHP.System.MasterPage

  The old properties are NOT supported, since they would conflict with the method name of the property functions.

• The Wigbi start function no longer has any parameters. Instead, use the following properties BEFORE calling start, if you want them to apply:- Wigbi::setTheme
  • Wigbi::setGenerateHtml
• The PHP versions of LanguageHandler and Configuration have been extended with a parameters property, which returns a list of all loaded parameters.The PHP IniReader class had a file parse bug that caused Windows not to interpret all line breaks correctly. This caused some empty configuration parameters to still be detected as set. This has now been fixed.

  The new IniReader class also only has a parseFile function – the string parse function has been removed.

• It is now possible to send variables to a master page. Just use the new method setVariable() in your page, and access the variable as normal in the master page. For instance:$master->setVariable(“foo”, “bar”)    // In the page
  print $foo      // In the master page
• Wigbi 0.99 now uses PHP explode instead of the deprecated PHP split.
• The PHP.SessionHandler class has been modified so that it stores data for each application separately. Previously, session data would “bleed” into all Wigbi applications that were running on a certain server, but this is now taken care of by this class. This update has been reflected in the LanguageHandler system class and the User seed class, which now uses SessionHandler instead of SESSION.
• In earlier versions, the database handler tried to connect even if nodatabase host was specified in the config file. This has been solved.
• The content of the system class wigbi/php/tools has been moved to the system folder wigbi/php/system.
• Some Wigbi controls have been renamed so that their name reflect their purpose better:LoginForm            ->    UserLoginForm
  LoginValidator        ->    UserLoginValidator
  LogoutForm            ->    UserLogoutForm
  PasswordResetForm    ->    UserPasswordResetForm
  PasswordUpdateForm    ->    UserPasswordUpdateForm
• Wigbi Control changes:FileUploadForm:
  The numUploads and setNumUploads properties are now implemented
  The fileFilter parseInt bug has been fixed
  The concurring file upload bug has been fixed

Wigbi 0.99 is released together with the Wigbi System Classes Demos and a brand new Wigbi web site. The documentation has also been looked over and a lot of unnecessary content has been removed.

Wigbi 0.99 has the WigbiWizard control added to the control collection by default, and will redirect the user to the wigbi/wizard.php page if application.runtimeBuild is set to 1 and something is incorrectly set. If the WigbiWizard control is removed from the control collection, this behavior will be disabled.