Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Show Posts

| * |

  Show Posts
Pages: [1]
1  Announcements and General Discussion / Fabrication / Issues with Fabrication, please help on: March 18, 2009, 03:27:05
Hi Darshan

I have had the pleasure of introducing my fabricator gem to two teams at where I work and thus also introducing the Fabrication framework. The primary goal of this is to get feedback to be able to improve the fabricator gem but also improve team development speed.

It seems that we have run into some issues / bugs with the framework and hope that You can help:

1. Release 0.6 of fabrication do not include AirApplication, as workaround we got the source code from subversion and this helped us create an Fabrication AirApplication.

2. ReactTo do not seam to work when you have a non referred component which uses ReactTo. Example we have a module1 that requests an ui component from module2. Module1 has no explicit reference to the ui component from module2, it just add it using Addchild. When module1 requests the component from module2, module2 creates the component and it's mediator, and sends the component to module1. Only addEventListener seems to work in the component for this scenario, reactTo methods leads to Nullpointer exception.

3. onRegister never executes when using Reflexive mediators with mx states. We have downloaded your demo Using Reflexive mediators with Application states and extracted the states-code to a component referenced in the application mxml file. Thus we use <mx:states instead of <fab:states in the component but this results in broken functionality(states), since the code never calls the onRegister method on the mediator of the deferred sub-component. We use this code to register the mediator (new ConfirmMediator(resolve(testView)..confirm).

Last I would love to know what the intentions are with Fabrication. Is it going to be further improved/developed on or is left for others to pick up? The reason I ask is, that we would really like to use Fabrication in production.

Thanx in advance
Steffen
2  Announcements and General Discussion / Fabrication / First release of fabricator gem, feedback please! (new version/update) on: March 03, 2009, 04:34:26
Hi Darshan et all

I have been working on and off on the fabrication generator last week and is now able to generate the first scaffold fabrication app with two modules. As mentioned most of the code is based on the simple routing demo. The generator creates two modules: an authentication module and a dashboard module both compiled as swfs and loaded when needed.

It is still in a rather early state but I thought it would be a good idea to release it now so that I can avoid moving in a wrong direction.

As a remark I have solved the problems with custom proxy, command, mediator, package etc that Jason suggested. But this feature will first be included in a future release.

The source is hosted at github -> http://github.com/sejensen/fabricator/tree/master
And the ruby gem is released at rubyforge -> http://rubyforge.org/projects/pure-fab-gen/
(It took some time to get the project approved, but by using rubyforge everyone can easily install the gem)

Usage instructions: (this is on mac with osx 10.5, assumes that ruby and rubygems are installed)
install gem: sudo gem install fabricator (currently version 0.0.5)
generate app: pureapp  AppName org.my.custom.package 'app title'
import project in flex builder as flex project: run AppNameShell.mxml

To create module codestructure
cd AppName
Run ruby script/generate pure_module ModuleName

example ruby script/generate pure_module Address -> results in AddressModule.mxml plus generated code for the new module. You have to overwrite the files when asked this is required to be able to genrate all the modules you want and still get all of them build etc.

Disclaimer for now the module is not included in the app, Since I am currently refactoring mediator and container code. but I thought being able to generate the skeleton and classes was a good start and the new module gets compiled as seperate swf.

That should be it! Hope to get some feedback, also on the currently generated code which is a little sparse. And if anyone have an idea of a more complex general app to generate that would be great?.

Enjoy  ;)
/Steffen
P.S. I hope the name fabricator is okay?



3  Announcements and General Discussion / Fabrication / Starting on a PureMVC multicore Fabrication generator gem on: February 18, 2009, 05:02:21
Hi everybody, especially Darshan.

I have been using puremvc for a while and got a little tired by the boilerplate startupcode needed for a new application. But still thinks that the whole idea ROCKS!!!! I know that copy paste helps a lot but found fabrication and saw that as the solution to my problems.

Still I would love to be able to only write the essential code of an app and at the company I work for, we could really benefit from a tool that could create app skeleton, moduleskeleton etc. etc.

Therefore I looked in to Dr. Nics Rubigen gem and has started on creating a gem that can do the above. I haven't really created an app based on fabrication yet, but wants the gem to create fabrication code. I have used the simple routing example as inspiration and for now it works quite okay. Have completed the first app skeleton with a single shell, mediator etc.

My question is whether someone has requests, ideas, template-code etc for such a gem?

I have convinced my management that it is okay for me to use workhours on this gem. So if anyone can help with ideas, code etc, that would be great and of course the gem will be publicly available if it results in anything useful.

Looking forward to hear from You.

Thank you in advance
Steffen Egelund Jensen
Pages: [1]