Tag Archives | FuseBox

Moving and throwing away

About two weeks ago my son, wife and myself moved into our new house. As everyone who is familiar with moving knows, the “how-to” move and getting “rid of stuff” is a very important process.

Up until now, I made it a habit that every time I had to move (up until now I moved approximately every one and a half years, don’t ask I just never felt “like home”) I will throw away stuff that I did not touch or used within the last six months.

So, today way one of these days again, where I went into our old apartment (especially the cellar) and moved “stuff” from one side to the other. On the left side, I put everything I wanted to throw away and on the right side I placed stuff I will move to our new house.

At the end of the day I had a lot of stuff to throw away and off it was to the recycling place. By now, you might be asking what this all has to do with SixSigns, this blog and software development.

During the process of throwing things away and getting rid of things that were left in the cellar, as some people refer to as “baggage in your consciousness/mind”, I felt a great relief and loss of mental weights.

I was thinking of how I could apply this feeling to software development. We as developers know and learn a certain way to code our applications. But what about if we “throw” away our habit, maybe a certain way of how to approach a coding challenge and start coding with a framework or even with a new tool?

Throw away; old habits and challenge yourself learning something new!

Maybe you have been thinking about to start learning Fusebox (as an example), then I suggest to “throw” away your old habits and start the next project with Fusebox or else you will never start!

Throw away; the mentality that you will do it it soon, do it now!

Speaking of throwing away. Don’t you think *your* application offers way to many options and confuses your users more then you thought? Maybe it is time to throw away the “this functionality has to be in the product or else…”mentality and start down the path of “Less is more”?

Throw away; complexity and simplify your application (life)!

Ok, on to moving those boxes now…

Comments { 16 }

Fusebox: xfa overwrite possible

Just a quick note that Fusebox 5.x allows to have also the XFA value set with “overwrite=false”.

With this you are able to use xfa like this:

<xfa name=”submitform” value=”c.add” overwrite=”false” />

I have not seen this in the documentation and thus mention it here.

Comments { 17 }

Fusebox 5.5.1 available and some things to know

Sean Corfield released Fusebox 5.5.1 the other day with a short blog post. Since we all love to read Release Notes (yes, you should read it) I thought I post some of the most important stuff here (for those who despite warnings still don’t want to read the Release Notes).

Implicit circuit does not allow multiple fuseactions!

Quote: If you had an XML circuit specification that used <do> to invoke multiple fuseactions in an undeclared (implicit) circuit, only the first <do> would succeed. Subsequent <do>s would fail to find the fuseaction. This has been corrected.

Model/View implicit circuit permissions should be internal

Quote: Fusebox 5.5 allowed you to invoke implicit model and view circuit fuseactions directly as part of a request because permissions were not checked. The implicit model and view circuits were intended to be internal rather than public. In Fusebox 5.5.1, permissions are correctly enforced. This may break your code if you were invoking model or view circuit fuseactions directly instead of using the controller circuit.

Reorganize repository to make future releases easier

Actually this is only needed if you are getting Fusebox with Subversion (which we highly recommend). Thus remember to change the call to Fusebox in your index.cfm (if you are getting the root directory of the Fusebox551 folder).

This is not technically a bug fix but it doesn’t add functionality either. Prior to Fusebox 5.5.1, the Subversion repository comprised a single directory that contained the core files, along with subdirectories containing the extensions, skeleton application and extensions.

The Subversion repository has now been reorganized to contain:

  • build/ – ant build.xml file to package / deploy Fusebox releases
  • corefiles/ – the core files, now in their own directory
  • docs/ – release notes for each release
  • extensions/ – lexicons and plugins
  • scaffolder/ – the beta application scaffold generator
  • skeleton/ – the traditional and no-XML skeleton applications

This was done to make life easier for the core file developers but if you’ve been downloading Fusebox from Subversion, you will notice this change (and, hopefully, the ant script will make your life easier too).

Thank you Sean for another great Fusebox patch/release.

Comments { 38 }

Fusebox 5.5 is golden

According to Sean Corfield Fusebox 5.5 has gone gold and is now available.

If you are into a Framework or already work with Fusebox then go and grab the latest version. We have been working with Version 5.5 since Beta 1 and just love it.

Comments { 18 }