|
|||||||
![]() |
|
|
Thread Tools |
|
#1
|
||||
|
||||
|
I haven't seen anything like this, does it exist?
Is there any chance of releasing the Extjs documentation app, or even turning the app into a community resource so we can easily provide consistent documentation for user extensions? I've got a handful of extensions I'd love to start sharing. I ported http://johndyer.name/post/2007/09/Ph...or-Picker.aspx to an Ext Panel. I've been working on a docking border layout(like IDE/photoshop) Yet another Ext page builder Database front-end configurator and some others It's a bit overwhelming to get all this into the community : / |
|
#2
|
||||
|
||||
|
We don't have any plans around this currently, although providing a way to generate API docs for user extensions is probably a good idea. You definitely can't go wrong following the same doc conventions that Ext uses regardless -- even if someone has to read them in the code, it will be consistent. We'll see if we can come up with a strategy for ux docs.
|
|
#3
|
||||
|
||||
|
Would following the documentation conventions in the base code be a good step to prepare ux code to get sucked into any ux documentation app?
Are there any internal documentation guidelines we users could have access to to meet halfway? |
|
#4
|
||||
|
||||
|
Quote:
![]() Quote:
|
|
#5
|
||||
|
||||
|
Just wanted to second this request.
![]()
__________________
Rich Waters |
|
#6
|
||||
|
||||
|
Collin,
Do you have demos for your extensions that we can view? Would be very appreciated. |
|
#7
|
||||
|
||||
|
I don't have any publicly hosted demos right now.
![]() This is something I'm working on this next week though. |
|
#8
|
|||
|
|||
|
I third this request.
I need to be able to document our internal app so that other developers can interact with it as easily as I am able to. |
|
#9
|
|||
|
|||
|
Fourth this request. ExtJS docs is jsdocs++.
|
|
#10
|
|||
|
|||
|
Quote:
![]() |
![]() |
| Thread Tools | |
|
|