• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Why WebObjects / Results / Part 2-2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why WebObjects / Results / Part 2-2


  • Subject: Re: Why WebObjects / Results / Part 2-2
  • From: Dov Rosenberg <email@hidden>
  • Date: Sun, 04 Jul 2004 21:40:13 -0400

Those are some good guidelines and feature lists. I think it would be cool
to be able to compare and contrast some of the various technologies such as
.Net and Struts in an "objective fashion".

Dov

On 7/4/04 10:32 AM, "Lotsa Cabo" <email@hidden> wrote:

> (CONTINUED FROM PART ONE)
>
> #10: Glossary
> As with any new technology, there are many new terms that a "newbie"
> may not be familiar with.  For example, a M$ guy may no nothing of Java
> or UNIX (or vice versa).  There should be some place where no
> assumptions are made and any terms that may be foreign would be
> defined; regardless of how simple the pros may think it is.
>
> #11: Example Applications
> There should be simple and quick applications that a visitor to the
> site would be able to build, download, or maybe even use on the site..
> something where they can see it in use.  It would be great to have a
> summary of the application at the beginning or end to explain how or
> why it works.  This would NOT be a tutorial (that comes later) but
> instead something that quickly demonstrates how the technology would be
> used.  (One person used the analogy of the guy selling knives on TV...
> he quickly conveys the gist while you watch.)
>
> #12: Tutorials
> Similar to the example applications, however it would have step-by-step
> instructions on how to build the application or use the technology.
> Each step should offer an optional explanation of how or why something
> works so that the reader understands WHY they just performed a certain
> step.
>
> #13: When NOT to use the technology
> Several people mentioned that it would be wise to know when to opt for
> something else.  Just as it is useful to know how great the technology
> may be, it will be equally useful, and refreshing, to know when it is
> appropriate to select something else for the task at hand.  As one
> person so elegantly put it, "Any developer worth his salt can make
> almost any technology do something however a wise developer knows when
> he should refrain from doing so."
>
> The next two I am including here because of the large number of people
> that mentioned them, however they are [obviously] not "features," per
> se...
>
> #14: No Marketing
> Tons of people replied that the more commercial a site appears, the
> less likely they are to trust the content.
>
> #14: Developer-To-Developer
> Above all, the site should be honest and open information from one
> developer to another (the reader).  The site should show an open and
> honest look at the technology without sounding as if one is simply
> defending the technology.  Also, while every person contributing to the
> site may have a biased opinion, they must be able to state the facts
> without ranting.  No soap boxes.
>
> #15: Professional Cosmetics
> Countless people stressed that, while it is great to have a
> community-run site, people put weight in the professionalism of a site.
> There are far too many companies offering professional templates, and
> far too many designers available, to not have a site that equals a
> major company's level of professionalism.  Even if it is a
> community-run, or developer-supported, site, if you really take pride
> in your technology, then that pride should show through in the site's
> appearence.  If the site looks as if a developer threw it together in
> VI or FrontPage, then they will probably go somewhere else.  Likewise,
> while it may not seem fair, the more professional and cosmetically
> pleasing a site is, the more the many visitors will [unfortunately]
> trust the site.
>
> I hope this helps somewhat.  Just please don't shoot the messenger.  ;-)
>
> As I mentioned to Dov, I am working on a project scope for this.  Once
> it's ready, I would like to get it out to everyone, get some additional
> feedback, and maybe see some hand in the air from people willing to
> bite off a specific chunk of it.
>
> Have a happy and safe 4th!
>
> R/S
> Ryan
>
> _________________________
> Tired of spam?  Signup for a FREE SpamJammer.Com account and say
> goodbye to junk email forever!
> _______________________________________________
> webobjects-dev mailing list | email@hidden
> Help/Unsubscribe/Archives:
> http://www.lists.apple.com/mailman/listinfo/webobjects-dev
> Do not post admin requests to the list. They will be ignored.
>

--
Dov Rosenberg
Conviveon Corporation
370 Centerpointe Circle, suite 1178
Altamonte Springs, FL 32701
http://www.conviveon.com
email@hidden
AOL IM: dovrosenberg
(407) 339-1177 x102
(407) 339-6704 (fax)
(800) 475-9890
(407) 310-8316 (cell)
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Why WebObjects / Results / Part 2-2 (From: Lotsa Cabo <email@hidden>)

  • Prev by Date: Re: WO 5.2 on 10.3.4 - Project Builder Problem
  • Next by Date: Re: Any WWDC News
  • Previous by thread: Why WebObjects / Results / Part 2-2
  • Next by thread: Re: Why WebObjects / Results / Part 2-2
  • Index(es):
    • Date
    • Thread