Re: WYSIWYG-editor for mac
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 52576
interpreted = N
texte = >Virtually all of our customers want to be able to easily edit their >content in a browser [as opposed to having a classified add for >their intranet]. > >The Java-based solutions are far more feature-rich, but the Flash >solutions are looking very interesting for their cross-platform >compatibility. Aside from features, I think pricing and hassle-free >licensing is a big issue. There's a ton of solutions out there from >freeware to way overboard, overpriced, enterprise solutions. Is it >too much to ask for a cross-platform, webdna-compatible, server lic. >for under $500.-? Yes of course it is too much to ask! There are simply not enough webdna users out there who (1) need this capability and (2) are willing to pay for it ... to justify any webdna developer building a solution like this and then selling it for only $500 00 -- unless that developer has a way to recover his development costs other than just by selling his content management package. There's a big difference between building a tool for yourself and building it so that it can become a sellable product for others. If you build it for yourself, you obviously have other ways to recover your investment than by reselling it (and then supporting it for who knows how long). And you never have to document it because you're the one who built it. The sheer amount of time and effort required just to document a private solution (so that it can be used by others) is an investment that most webdna developers are not willing to make, and for good reason -- the market for webdna solutions is simply not that big. For example, I built a very good database management tool for myself. This tool does all kinds of tasks on the live server, so my sites can remain online and continue to be updated by visitors, at the same time that I am using my tool to perform tasks that I would otherwise have to do by importing the db file into a desktop database program, manipulating it there, then exporting and uploading it to replace the online db with the newly modified db. This tool is extremely useful to me, and I use it on a daily basis for one db management task or another. It is, in fact, a tool that nearly all webdna programmers would benefit from because it saves so much time when dealing with db's and the data they contain. But *if* I had to write documentation that would allow me to sell it, I could never sell enough copies to cover my investment in time to write the documentation alone -- much less the time it took me to actually write the tool itself. And my market for this tool is virtually all webdna programmers, not just the few who may desire a webdna-based content management system. So as you can see, it is unlikely that there will ever be a marketable content management system for webdna unless (1) SMSI builds it themselves and includes it in a future upgrade package, which probably means passing the cost on to all webdna users by increasing the upgrade price, or (2) a BIG company buys webdna from SMSI and markets webdna in a manner that causes it to become far more widely accepted in the industry ... so that enough people will be using webdna to justify an independent player's efforts to build and market such a system. Of course, all this is only my personal opinion ... -- Sincerely, Kenneth Grome ------------------------------------------------------------- Outsource your WebDNA programming for $18 an hour or less! ------------------------------------------------------------- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>Virtually all of our customers want to be able to easily edit their >content in a browser [as opposed to having a classified add for >their intranet]. > >The Java-based solutions are far more feature-rich, but the Flash >solutions are looking very interesting for their cross-platform >compatibility. Aside from features, I think pricing and hassle-free >licensing is a big issue. There's a ton of solutions out there from >freeware to way overboard, overpriced, enterprise solutions. Is it >too much to ask for a cross-platform, webdna-compatible, server lic. >for under $500.-? Yes of course it is too much to ask! There are simply not enough webdna users out there who (1) need this capability and (2) are willing to pay for it ... to justify any webdna developer building a solution like this and then selling it for only $500 00 -- unless that developer has a way to recover his development costs other than just by selling his content management package. There's a big difference between building a tool for yourself and building it so that it can become a sellable product for others. If you build it for yourself, you obviously have other ways to recover your investment than by reselling it (and then supporting it for who knows how long). And you never have to document it because you're the one who built it. The sheer amount of time and effort required just to document a private solution (so that it can be used by others) is an investment that most webdna developers are not willing to make, and for good reason -- the market for webdna solutions is simply not that big. For example, I built a very good database management tool for myself. This tool does all kinds of tasks on the live server, so my sites can remain online and continue to be updated by visitors, at the same time that I am using my tool to perform tasks that I would otherwise have to do by importing the db file into a desktop database program, manipulating it there, then exporting and uploading it to replace the online db with the newly modified db. This tool is extremely useful to me, and I use it on a daily basis for one db management task or another. It is, in fact, a tool that nearly all webdna programmers would benefit from because it saves so much time when dealing with db's and the data they contain. But *if* I had to write documentation that would allow me to sell it, I could never sell enough copies to cover my investment in time to write the documentation alone -- much less the time it took me to actually write the tool itself. And my market for this tool is virtually all webdna programmers, not just the few who may desire a webdna-based content management system. So as you can see, it is unlikely that there will ever be a marketable content management system for webdna unless (1) SMSI builds it themselves and includes it in a future upgrade package, which probably means passing the cost on to all webdna users by increasing the upgrade price, or (2) a BIG company buys webdna from SMSI and markets webdna in a manner that causes it to become far more widely accepted in the industry ... so that enough people will be using webdna to justify an independent player's efforts to build and market such a system. Of course, all this is only my personal opinion ... -- Sincerely, Kenneth Grome ------------------------------------------------------------- Outsource your WebDNA programming for $18 an hour or less! ------------------------------------------------------------- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Missing custom convert.db (1998)
WebCat2 as a chat server? (1997)
Triggers (2003)
[WebDNA] SiteBuilder Calendar (2008)
Mac: [ListFiles] bug alert (1997)
[PHP3] does QuickTime Movies? (2000)
Viewing Changes (1998)
Superfilous Characters (1998)
Re[2]: Enhancement Request for WebCatalog-NT (1996)
WebMerchant 1.6 and SHTML (1997)
Why this code works from some places and doesn't from others? (2000)
Search returns all, not 20 (1997)
users change an email address (2002)
[searchString] (1997)
[shownext max=?] armed (1997)
Progress !! WAS: Trouble with formula.db (1997)
More DateMath problems (1997)
old mail...problem with listserv? (1998)
Setting up shop (1997)
Price override - solved (2004)