Gene Amtower wrote:
> Thomas,
>
> I'm willing to perform updates to the wiki, if I can. I'm coming
> across a significant number of purely grammatical errors in the
> documentaiton that I'm willing to correct.
Great.
> However, I'm not sure how to update the wiki myself. Is this related
> to the "Login" link at the bottom of each doc page?
Indeed, yes. (The link is also in the green side-box on every page).
> If so, how do I know if I have a login for this area? I tried my
> sourceforge login - didn't work.
No, you have to set up an account for this. When you follow the login
link, on the login form there is also a link saying "Register". The
registration should be easy and straight-forward. Get back to us if
you're running into any trouble.
> Is this going to require me to be setup as a documentation provider
> for Qooxdoo? I'd like to help out that way, and I sent an email to
> Andreas a couple of days ago about contributing to documentation, but
> I saw in another post today that he's off on a vacation.
Yes, he is, but I think it is just going through the little registration
procedure.
>
>
> If that's what it will take, I don't mind waiting for him to return,
> but I would like to help out as best I can. I don't really want to
> clutter up bugzilla if I can straighten out minor errors myself.
>
> I think the issue about adding file locations and filenames to the
> examples in the documentation is worth adding to bugzilla. I've added
> Bug #2449 for it.
Thanks.
T.
>
> Thanks,
>
> Gene
>
> On Tue, 2009-06-02 at 15:53 +0200, thron7 wrote:
>> Gene Amtower wrote:
>> > Qooxdoo Team,
>> >
>> > One thing that occurs to me is that the embedded example code within
>> > the online docs could be more helpful if it described a typical file
>> > name/location that would include the example code. This way, readers
>> > of the documentation would understand where in their project folders
>> > that particular example file would be added or modified. This could
>> > apply to the config files, theme files, image files, and code files
>> > throughout the documentation.
>> >
>> > It appears that you've already adopted a consistent example project
>> > name 'myApplication' in these examples. This would suggest adding a
>> > notation for the filename in the example on "Extending Themes" in
>> > "Custom Themes" [1] as
>> > "/myApplication/source/class/myApplication/theme/Appearance.js", so
>> > that the reader would have a better understanding on how to start
>> > implementing custom themes in their own project.
>> >
>> > Of course, we could leave it to the reader to try to figure it out,
>> > but I think we should make it easier to adopt these powerful features
>> > of Qooxdoo.
>>
>> Good point. Could you put this into a bug (product category "website")?!
>> Thanks.
>>
>> >
>> > One concern I noticed in this particular example is that it includes
>> > the line
>> >
>> >> qx.Theme.define("myApplication.Appearance",
>> >>
>> >
>> > If this is supposed to be the file
>> > /myApplication/source/class/myApplication/theme/Appearance.js, then my
>> > project created from a recent Qooxdoo trunk doesn't have the same
>> > line. My Appearance.js file for this project was generated instead
>> > with this line
>> >
>> >
>> >> qx.Theme.define("myApplication.theme.Appearance",
>> >>
>> >
>> > This line is consistently different in the all of the theme files in
>> > my project. Was the structure of the theme files changed at some
>> > point after the documentation on theming was created, by moving them
>> > to the "theme" subfolder of the class files? Or does it work fine
>> > either way? If not, then we should clean up the doc examples in this
>> > area.
>>
>> No, for all I can say class and theme names have to reflect the
>> directory structure. Please open another doc bug for it - or put it
>> straight in the wiki right away.
>>
>> T.
>>
>> >
>> > Thanks,
>> >
>> > Gene
>> >
>> > [1] http://qooxdoo.org/documentation/0.8/ui_custom_themes
>> > ------------------------------------------------------------------------
>> >
>> > ------------------------------------------------------------------------------
>> > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
>> > is a gathering of tech-side developers & brand creativity professionals.
>> > Meet
>> > the minds behind Google Creative Lab, Visual Complexity, Processing, &
>> > iPhoneDevCamp as they present alongside digital heavyweights like
>> > Barbarian
>> > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
>> > ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > qooxdoo-devel mailing list
>> > [email protected]
>> > <mailto:[email protected]>
>> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>> >
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [email protected]
>> <mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
