Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / GUI / July 2004

Tip: Looking for answers? Try searching our database.

A Look'n Feel for Prototypes?

Thread view: 
Shane Mingins - 26 Jul 2004 21:41 GMT
This is cool!

http://napkinlaf.sourceforge.net/

Signature

There are three kinds of untruths: Lies, Damn Lies, and Statistics. --
Attributed to Benjamin Disraeli by Mark Twain

Remi Bastide - 27 Jul 2004 11:20 GMT
>This is cool!
>
>http://napkinlaf.sourceforge.net/

Ok, but what is the point ? The use of low fidelity prototypes is a
very valuable tool in the requirements phase, but the point is
precisely to get rid of any software tools and use mainly pencil and
paper, so that several prototypes can be build at no cost in iterative
evaluation cycles.  I do not see any benefit in using such a software
tool (presumably with a gui builder) in this phase.

See :
http://portal.acm.org/citation.cfm?id=175288&coll=portal&dl=ACM&CFID=24775303&CF
TOKEN=21398962


or

http://portal.acm.org/citation.cfm?id=223514&coll=portal&dl=ACM&CFID=24775340&CF
TOKEN=59086947

Thomas Weidenfeller - 27 Jul 2004 12:17 GMT
> Ok, but what is the point ? The use of low fidelity prototypes is a
> very valuable tool in the requirements phase, but the point is
> precisely to get rid of any software tools and use mainly pencil and
> paper, so that several prototypes can be build at no cost in iterative
> evaluation cycles.  I do not see any benefit in using such a software
> tool (presumably with a gui builder) in this phase.

While I agree that index cards and board markers are maybe best in
design, I can follow the logic of that LnF author. There is more to
shipping working software than what you can find in research papers and
academic discussions.

If you have to hand out half-finished software, e.g. if you do a series
of early deliveries to QA, alpha and beta testers and the gold owners,
and if you want to indicate that the GUI implementation (not the design)
and/or the application logic isn't finished, then this LnF is a clear
statement.

I have been in the situation myself a few times, were people thought the
application was done at the very moment the main window popped up the
first time. I wouldn't have used this LnF, because the statement is IMHO
a little bit to strong, but I thing his idea is good.

/Thomas
Steven T Abell - 28 Jul 2004 15:56 GMT
> This is cool!
>
> http://napkinlaf.sourceforge.net/

I tried the Napkin L&F in the Slamdunk UI framework.
It's cute,
but when I switch to a different L&F after using Napkin,
screen drawing is all screwed up and stays screwed up,
even if I switch back to Napkin.
This doesn't happen with the standard JDK L&Fs.
Also, it slows things down a lot.
But, given its purpose, maybe that's a good thing.

Steve
Signature

Steven T Abell
Software Designer
http://www.brising.com

In software, nothing is more concrete than a good abstraction.



Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.