Recent activity
Subscribe to this feed
Jim replied on September 13, 2009 18:16 to the problem "DiffPops crashes a lot" in Elegant Technologies:
Jim replied on September 04, 2009 01:57 to the problem "DiffPops crashes a lot" in Elegant Technologies:
Hmm - well that sucks. It obviously isn't suppose to do this. I'm not sure that i've tested this on 3.0 yet (oops) and literally just moved from Boston to DC this week. I'll be back working for real starting next Tuesday - so I'll tackle this as soon as I can. Thank you very much for reporting the problem.
JJ
Jim replied on September 03, 2009 21:12 to the problem "DiffPops crashes a lot" in Elegant Technologies:
Jim replied on September 03, 2009 20:38 to the problem "DiffPops crashes a lot" in Elegant Technologies:
Jim replied on August 13, 2009 21:51 to the idea "Filling the gap between out-of-box export and production ready code." in Napkee:
Jim marked one of Enrico Berti's replies in Napkee as useful. Enrico Berti replied to the idea "Filling the gap between out-of-box export and production ready code.".
-
Jim started following the idea "Detach UI Library to second monitor" in Balsamiq.
-
Jim started following the idea "Allow one mockup to serve as a background layer for other mockups." in Balsamiq.
-
Jim started following the question "BlackBerry Balsamiq Stencils" in Balsamiq.
-
Jim started following the idea "Enhanced paragraph widget for bullet lists and numbered lists" in Balsamiq.
-
Jim started following the question "Insert a mockup by reference instead of copy..." in Balsamiq.
-
Jim started following the idea "Version Update Notification" in Balsamiq.
Jim replied on August 13, 2009 21:27 to the idea "Multiple JS Libraries support" in Napkee:
Jim replied on August 13, 2009 21:22 to the idea "Filling the gap between out-of-box export and production ready code." in Napkee:
Maybe this actually needs cooperation with balsamiq - or maybe i just want too much! I'm trying to get closer to a workflow where I can play in the mockup world, add finished design, add mockup components that migrate to finished code, and finally, any custom code is highly insulated and segregate so that round trip iterations are possible and realistic.
That isn't asking much, is it?
Jim shared an idea in Napkee on August 13, 2009 21:09:
Filling the gap between out-of-box export and production ready code.Napkee could become a powerful piece of my production pipeline if I could build in my own hooks or make a plugin so I would work with my own components.
Let's say that I have some fancy balsamiq component, say, the Yahoo calendar component for balsamiq seen here: http://mockupstogo.net/yui-calendars
It isn't realistic for you to write the balsamiq to html code for every possible component, but until I have some way to fill in the gaps between what you've already written and what I need, then Napkee, by definition, isn't meeting my needs.
I don't if plugins are the right answers.
If, for example, you could somehow identify the yahoo component in the export (a beginning and end), then I could at least scan the generated code and replace it with my own code.
Not sure if any of this is possible, but I'm interested in how you and others expect/plan to fill-the-gap between the nominal out-of-the-box export and what's required for production code.
Thanks - keep up the good work. Napkee is a cool concept!
Jim replied on August 13, 2009 20:22 to the problem "Napkee web>preview drops BMML elements in iphone mockup" in Napkee:
I thought I had this problem, too, but that isn't quite right. Most of my mockups, lately, are for iphone mobile safari web apps. In preview, I expected to see the iphone image, even though I would obviously not expect to see it once I actually looked at the app on the iPhone.
I think the confusion comes from the term 'preview'. For whatever reason, when people write for mobile devices, they want to see an image of the device while still in simulator / preview mode. It would be good to show the skin if I'm publishing to the web to share the mockup, but I don't want to see the skin if I'm publishing as a final mobile web app.
So, bottom line:
* Show the iphone skin in the preview
* Make it an option as to whether or not to show the skin upon export.-
Jim started following the problem "Napkee web>preview drops BMML elements in iphone mockup" in Napkee.
Jim replied on August 04, 2009 02:40 to the problem ""Took too much time" is too short!" in FairSoftware:
Jim reported a problem in FairSoftware on August 03, 2009 12:35:
Can't re-submit an edit w/o changing Project NameIt seems that whenever I edit a project description, I see an error ProjectName already in use. Which causes me to have to create a name, like "Project Name 2".
Work-around: Create a new name. Re-edit and reset the new name back to the original name
Jim reported a problem in FairSoftware on August 03, 2009 12:29:
"Took too much time" is too short!The edit pages for product description time out way before I get a chance to finish my edits, and so i MUST edit offline and then copy-and-paste - bummer.
| next » « previous |
Loading Profile...










