The addition of a fuseaction field into the wireframe bothers me a little, in the same way that adding in table/field names and hyperlinks for HTML pages does.
I.e. anthing relating to a fuseaction, belongs in the architecture phase, not the wireframing one.
None the less I am aware that people like to reverse engineer and ensure that their wireframe is updated as they proceed through the FLiP process with their application. Just because I don't like it... well... I can simply choose not to use it.
How would you lie to join the project and assist, by providing some ideas on how to implement your requirement or perhaps even check out the source code and share your outcomes with the whole project?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would be more than happy to join but I have to warn you, I am a newbie at both FB and FLiP. My only experience with FB design tools are Addalon and very recently this project.
The reason I came up with this suggestion is my experience with Addalon. With it, you can wireframe and then continue on with the life-cycle and hopefully, in the end, have an all encompassing design (and at this point, without "too" much work, be able to add tools to generate the circuit xml files directly from the design -- assuming I know what I am talking about and this is just not my newbieness talking!).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1479959
Originator: NO
The addition of a fuseaction field into the wireframe bothers me a little, in the same way that adding in table/field names and hyperlinks for HTML pages does.
I.e. anthing relating to a fuseaction, belongs in the architecture phase, not the wireframing one.
None the less I am aware that people like to reverse engineer and ensure that their wireframe is updated as they proceed through the FLiP process with their application. Just because I don't like it... well... I can simply choose not to use it.
How would you lie to join the project and assist, by providing some ideas on how to implement your requirement or perhaps even check out the source code and share your outcomes with the whole project?
Logged In: YES
user_id=1800975
Originator: YES
I would be more than happy to join but I have to warn you, I am a newbie at both FB and FLiP. My only experience with FB design tools are Addalon and very recently this project.
The reason I came up with this suggestion is my experience with Addalon. With it, you can wireframe and then continue on with the life-cycle and hopefully, in the end, have an all encompassing design (and at this point, without "too" much work, be able to add tools to generate the circuit xml files directly from the design -- assuming I know what I am talking about and this is just not my newbieness talking!).
Logged In: YES
user_id=1479959
Originator: NO
Well,
I would swear that I have never read this message before, despite the fact the I visit nearly daily and it's nearly 4 months old.
As far as being a newbie goes... well don;t sweat it.
At some time we were all newbies!
And as they say - there is no better teacher than experience.
Just in case you have missed it there has been some renewed life breathed into the project too.
The current focus is on changing the text based "WIR" data file into XML.
In case you missed it, you've already been added to the project!