Tagged: BDD RSS Toggle Comment Threads | Keyboard Shortcuts

  • danielsaidi 9:24 pm on April 28, 2010 Permalink | Reply
    Tags: BDD, , , , , SessionHandler, SimpleTest,   

    The work with Wigbi 1.0 proceeds 

    I am currently working with the Wigbi 1.0 release, which I wrote about earlier. I have now finished writing new versions for the following classes:

    • CacheHandler
    • IniReader
    • JavaScript
    • LogHandler
    • SessionHandler
    • Wigbi (part done)

    Working with SimpleTest has simplified development a lot, which is why the pace is so good ;)

    In Wigbi 1.0, all system classes will be independent of the Wigbi class (except—the Wigbi class), which means that you will be able to use them for other purposes as well, without having to rely on Wigbi. The only static classes (so far) are JavaScript and Wigbi. All other system classes now have default handlers that are initialized by Wigbi and accessed as properties of the Wigbi class.

    Several classes remain,  as well as data and UI plugin classes…but I’m getting there.

     
  • danielsaidi 2:05 pm on April 23, 2010 Permalink | Reply
    Tags: BDD, Data plugins, Data_plugins, , UI plugins, UI_Plugins   

    Development of Wigbi 1.0 has begun 

    After a while away from Wigbi, I have finally decided to start with the development of Wigbi 1.0, which will be a complete rewrite of the Wigi 0.99.x source code. Although the functionality will remain, some classes may be removed while others will be entirely rewritten.

    In Wigbi 1.0, seeds and controls will be renamed to the more intuitive data and UI plugins. I will also rewrite all plugins in a way that makes them even easier to use and manage.

    For instance, data plugins will be even easier to create and will require a minimum of code, since I have decided to remove the requirement for property methods. Wigbi will affect the variables and will not require that they are handled by properties or property methods.

    UI plugins (User Interface) will also be even easier to use, since I will reduce the JavaScript code of each plugin to a minimum. To affect the elements of each plugin, developers may use jQuery instead of using JavaScript properties for each plugin. Why reinvent the wheel?

    Also, Wigbi 1.0 will be fully test-driven, which is why I have started to look at various PHP TDD/BDD alternatives. If you have any suggestions, please let me know.

    I expect Wigbi 1.0 to be released at the end of May. If you feel like contributing, please let me know.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Follow

Get every new post delivered to your Inbox.