Existing users, 
 GoodPage - 1.3.1graphical HTML/CSS authoring tool |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
Documentation!!!! 
- Version: 1.3.0, 3/4/2007 12:37PM PST
(1 of 1 users found this comment useful)
brunobfan
Really needs documentation. - Version: 1.3.0, 12/30/2006 03:17PM PST
alphamanque
The authors state at the beginning of their skimpy documentation: "We believe that applications should be designed for use without manuals." Maybe, but GoodPage doesn't appear to be designed that way at all. That statement presupposes an completely intuitive interface, users with similar intuition and a relatively simple program. In all fairness, these suppositions don't hold with any software that performs non-trivial tasks and comprehensive documentation significantly shorten learning curves.
That said, although difficult to use, GoodPage is a very interesting program with enough clever and unique features to warrant a look if you have the time. The only major problem I found was that the ftp service wouldn't generate a remote file listing.
My GoodPage license included a license (free) for FlyPath, a very nice, fast, small footprint file manager. It comes much closer to the intuitive ideal touted for GoodPage.
That said, although difficult to use, GoodPage is a very interesting program with enough clever and unique features to warrant a look if you have the time. The only major problem I found was that the ftp service wouldn't generate a remote file listing.
My GoodPage license included a license (free) for FlyPath, a very nice, fast, small footprint file manager. It comes much closer to the intuitive ideal touted for GoodPage.
Most Recent Replies: View All 1 Replies
- Really needs documentation.
couldn't resist trying this app. but... - Version: 1.2.2, 8/24/2005 02:28AM PST
(4 of 4 users found this comment useful)
ende
...so far i haven't been able to figure out, how to add site-wide css attributes to, say headers.
[QUESTIONS TO THE DEVELOPERS]
i had no problem finding out how to add inline-css-properties to a tag. then i can SEE in the info-panel that this property is an "inline style attribute", but i can not change this. i had expected that this would be a popup with all included css-files to choose from, but it isn't. is there a way to to this without adding the properties to the css-file in the oldfashined manner by hand?
why can i choose css-properties from a list of 120 properties, even if most of them are not allowed for this tag? it would be even nicer, if one could choose to filter the list for example to not show speech-related css-poperties.
why can't i choose (appropriate) html-attributes and their values from a list?
when entering values for css-poperties a popup with appropriate the values instead of a text-field would be nice. like p.e. font-weight with a [normal,bold,bolder,lighter,<value:100-900>]-popup.
there is MUCH potential in this app and the structured view is a great unique feature already.
i like the idea, that small software should work without documentation. BUT as a software gets more complex, a documentation is a necessity! what would you say, if p.e. illustrator would come without docu? and even more so, if a software uses a new approach and concept. you are denying the uniqueness of your new approach if don't make a documentation for goodpage.
i'm really loking forward to upcoming releases.
[QUESTIONS TO THE DEVELOPERS]
i had no problem finding out how to add inline-css-properties to a tag. then i can SEE in the info-panel that this property is an "inline style attribute", but i can not change this. i had expected that this would be a popup with all included css-files to choose from, but it isn't. is there a way to to this without adding the properties to the css-file in the oldfashined manner by hand?
why can i choose css-properties from a list of 120 properties, even if most of them are not allowed for this tag? it would be even nicer, if one could choose to filter the list for example to not show speech-related css-poperties.
why can't i choose (appropriate) html-attributes and their values from a list?
when entering values for css-poperties a popup with appropriate the values instead of a text-field would be nice. like p.e. font-weight with a [normal,bold,bolder,lighter,<value:100-900>]-popup.
there is MUCH potential in this app and the structured view is a great unique feature already.
i like the idea, that small software should work without documentation. BUT as a software gets more complex, a documentation is a necessity! what would you say, if p.e. illustrator would come without docu? and even more so, if a software uses a new approach and concept. you are denying the uniqueness of your new approach if don't make a documentation for goodpage.
i'm really loking forward to upcoming releases.
Most Recent Replies: View All 1 Replies
It creates a folder with two sample sited on the desktop. I wanted to see what they did so I doubleclicked the GoodPage file in the dynamic folder and was greeted with an inscrutable setup dialog.
It is a complete failure on the part of the developers to think this program is so COOL that people will fight for the privilege of spending more time than necessary to learn how to use it.