PDA

View Full Version : Central ux repository



SamuraiJack1
6 Aug 2008, 3:03 PM
Central repository for user extensions.

Glad to announce about the initial alpha release of the central repository for Ext user extensions.

http://extjs-ux.org/

It is very feature-limited and minimalistic yet, but still useful, it solves the current problems with the user extensions, which are:
the dispersion of ux's through the forum (users have to bookmark every extension they use)
the different quality of documentation (up to general description only)
the complexity of updating the ux's for users (need to find bookmark, read the forum thread to find latest version, find download link, etc..)
the complexity of creating demos for authors (need to have own hosting)Below is the briefly description of the repository, intended for its users. For description, intended for authors, please take a look here (http://extjs-ux.org/twiki/bin/view/Main/UxRegistration).


The documentation.

All uxs are combined in the hierarchical tree, in a way, that was used for Ext library itself. The documentation is available here:
http://extjs-ux.org/ext-docs/
or here (in older format)
http://extjs-ux.org/docs

http://extjs-ux.org/ext21/images/uxdocs_header-new.png

The documentation of each ux contains the version information, information about the author of extension and the license under which it is published.
It also contains the links to extension's forum thread, to available demos, and to any other extension-related materials.


Downloading and updating of the ux's.

You can download a single extension via the link "Defined in" in its documentation. But for keeping all your ux's up to date, you should setup a local copy of the repository.

The repository is organized in the form of SVN. To access it, you'll need an svn client.
For Windows users the best choice will be the TortoiseSVN
http://tortoisesvn.tigris.org/

For Linux - there are several good enough clients, one of them - Subclipse plugin for Eclipse.
http://subclipse.tigris.org/

For downloading - create a local directory for your copy and checkout to it the following URL:
http://extjs-ux.org/repo/trunk
(this operation need to be performed only once)

For updating your local copy to the latest versions - use update command of your svn client.
(Please consult your svn clients documentation about details of performing these tasks)

Thats all - with couple of clicks, all ux's in your local copy will be synchronized with latest versions.

---------------------------------------------------------
Project summary:
Contributors (http://extjs-ux.org/twiki/bin/view/Main/Contributors)
Roadmap (http://extjs-ux.org/twiki/bin/view/Main/Roadmap)
Changelog (http://extjs-ux.org/twiki/bin/view/Main/ChangeLog)

saJoshua
7 Aug 2008, 5:59 AM
Thanks to mjlecomte for pointing this thread out to me. We've been discussing something like this for a while.

I have just registered the extjs4work.com domain for this purpose and am checking with the ISP if I can get SVN set on the windows web server. I'll post again here once I get a response.

Joshua

jsakalos
7 Aug 2008, 7:12 AM
I have such server [something].extjs.eu but I need to know more details. Contact me on skype nick=jsakalos.

saJoshua
7 Aug 2008, 7:17 AM
Hi Saki,

I'd just like to clarify purpose / intent at this stage. Are you willing to create an area where members can sign up and collaborate on extjs samples? You have an awesome site, but I'd like to get something on the go that users can change / play with extjs online.

@SamuraiJack1 : I haven't received a response from my ISP yet, but if they're not willing to make SVN available, I'm sure a couple of hooks could allow the site to use code.google.com / sourceforge to host the SVN.

Joshua

SamuraiJack1
7 Aug 2008, 7:43 AM
Hi Saki,

I'd just like to clarify purpose / intent at this stage. Are you willing to create an area where members can sign up and collaborate on extjs samples? You have an awesome site, but I'd like to get something on the go that users can change / play with extjs online.

@SamuraiJack1 : I haven't received a response from my ISP yet, but if they're not willing to make SVN available, I'm sure a couple of hooks could allow the site to use code.google.com / sourceforge to host the SVN.

Joshua

Both code.google.com and sourceforge are not suitable for this project - there will be no control on server-side software. Also setup the configuration that I mentioned on windows hosting could be tricky task, much easier on linux.

saJoshua
7 Aug 2008, 8:05 AM
Hi Jack,

what do you mean by "there will be no control on server-side software"?

Also, how far do you want to take the "central repository for ux'es"? It seems that you want to allow collaboration. Would this be available from within the website, or would each "author" need to access the SVN from their computer?

Joshua

SamuraiJack1
7 Aug 2008, 8:20 AM
Hi Jack,

what do you mean by "there will be no control on server-side software"?

Also, how far do you want to take the "central repository for ux'es"? It seems that you want to allow collaboration. Would this be available from within the website, or would each "author" need to access the SVN from their computer?

Joshua

Hi

Well, you'll not be able to upload doc-generating script and run it once per hour, for example. Svnforge and google.code are optimized for another tasks. If we'll need request tracking capabilities we can install bugzilla or trac, etc..

About collaboration - it is not the main purpose of this project. The main purpose is structurizing of the ux'es publishing policy.
The collaboration will be also naturally achieved due to SVN nature of repository - will be much easier to create patches, browser historical data, etc. But the main purpose again - is to concentrate all ux'es in 1 place and to gain their's code quality level.

saJoshua
7 Aug 2008, 8:29 AM
ok, I see what you're aiming towards. What I had in mind is specifically quite different.

I am keen to see what you make of it. Hopefully Saki can help you get it launched easily.

Cheers,
Joshua

ThorstenSuckow
7 Aug 2008, 9:16 AM
+1

And I strongly recommend a community process for voting extensions into the repository (such as PEAR does) and coding guidelines/styles for official ux. Otherwise, the repository will be quickly become pure chaos.

jsakalos
7 Aug 2008, 10:15 AM
Hi Saki,

I'd just like to clarify purpose / intent at this stage. Are you willing to create an area where members can sign up and collaborate on extjs samples? You have an awesome site, but I'd like to get something on the go that users can change / play with extjs online.

@SamuraiJack1 : I haven't received a response from my ISP yet, but if they're not willing to make SVN available, I'm sure a couple of hooks could allow the site to use code.google.com / sourceforge to host the SVN.

Joshua
It should be a svn repository for extensions/plugins, however, users can put samples there too. I'm testing it, stay tuned.

jsakalos
7 Aug 2008, 10:18 AM
Hi Jack,

what do you mean by "there will be no control on server-side software"?

Also, how far do you want to take the "central repository for ux'es"? It seems that you want to allow collaboration. Would this be available from within the website, or would each "author" need to access the SVN from their computer?

Joshua
I can answer this: The idea is to have users with their own passwords to access their repositories. Repositories would be publicly available read-only.

jsakalos
7 Aug 2008, 10:22 AM
+1

And I strongly recommend a community process for voting extensions into the repository (such as PEAR does) and coding guidelines/styles for official ux. Otherwise, the repository will be quickly become pure chaos.
I have no idea (yet?) of how to do this. Once I'll give a user an access he/she can put there whatever he/she wants. Sure, I can remove the access based on user votes.

jsakalos
7 Aug 2008, 10:26 AM
ok, I see what you're aiming towards. What I had in mind is specifically quite different.

I am keen to see what you make of it. Hopefully Saki can help you get it launched easily.

Cheers,
Joshua
No problem to participate on my site. Look how current examples are done, prepare files and send 'em to me - you can even put your own credits/ads there and I'll publish it on my site. I won't give write access for the time being.

marcov
8 Aug 2008, 7:33 AM
I am a newcomer to extJS and I am amazed at the wealth of contributions, especially yours.

Along the lines of a central repository, I think it would be of great benefit to the entire community to host the extJS library, similar to the way jQuery is hosted by Google; see http://code.google.com/apis/ajaxlibs/

Since getting Google to host extJS may be a bit of a challenge, maybe the library could be hosted on the extJS site?

tidal
8 Aug 2008, 10:15 AM
And I strongly recommend a community process for voting extensions into the repository (such as PEAR does) and coding guidelines/styles for official ux. Otherwise, the repository will be quickly become pure chaos.
Hhm, while this generally would make sense, it also would produce a
large overhead in organisation and for the contributor

tidal
8 Aug 2008, 10:15 AM
But I have another topic, I would like to mention.
This is licenses and escpecially commercial use of the ux

SamuraiJack1
8 Aug 2008, 11:51 AM
I'm not familiar with PEAR, but any publishing policy is better than no publishing policy and "extension hunting" on forum (for an example of successfull repository project take a look at CPAN)

Currently the only requirements for publishing will be:
- proper placing in repository
- proper documentation with ScriptDoc
thats all, not much at all

Since there is no widely accepted sane way for testing js GUI (or i just dont know about it?) proper test coverage as a requirement will be excluded for now

Guys, lets put our efforts not in speaking and flaming, but in coding. Basis of the project is already completed and will be deployed for testing in couple of days.

The areas where you may help:
-- JSDoc improvements (much work, but there is still the hope that ExtJs will release their's tool)
-- Test platform developing
-- Writting manual about publishing
etc, post your ideas

SamuraiJack1
8 Aug 2008, 12:03 PM
+1

And I strongly recommend a community process for voting extensions into the repository (such as PEAR does) and coding guidelines/styles for official ux. Otherwise, the repository will be quickly become pure chaos.

Yes, there will be "guidelines/styles for official ux", even requirements, but no voting, anyone will be able to submit extension he/she(?) developed. Good ux'es will found their's users and bad will be just ignored.

ThorstenSuckow
10 Aug 2008, 2:04 AM
Yes, there will be "guidelines/styles for official ux", even requirements, but no voting, anyone will be able to submit extension he/she(?) developed. Good ux'es will found their's users and bad will be just ignored.

Well, then there's still the problem with namespace clashes...

And how will you manage that someone who maintains a ux is the only one who can commit updates to this specific directory in the repository?

SamuraiJack1
10 Aug 2008, 3:21 AM
Well, then there's still the problem with namespace clashes...
Yea, I thought about this - every author will register his ux first, so clashes will be excluded.



And how will you manage that someone who maintains a ux is the only one who can commit updates to this specific directory in the repository?
mod_authz_svn allows per-directory access, more details here:
http://svnbook.red-bean.com/en/1.4/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir

I wrote a "working draft" of the publishing policy, its quite ugly document, but it clears project architecture, if you want, I can pm it you.

jsakalos
10 Aug 2008, 7:38 AM
We're thinking about creating a repository management system where it would work as follows:

1) an extension author would apply for a repositor[y/ies]
2) he/she would get an invitation mail to create the repositor[y/ies]
3) he/she would create the repositor[y/ies]
4) he/she would assign access rights to public (e.g. read only) and/or to other authors, possibly read/write.
5) he/she would have exclusive rights to his/her repository - if the author decides to remove it, revoke public access, or whatever else, it would be possible.

What do you think about this system?

mjlecomte
10 Aug 2008, 8:59 AM
sounds good. Basically give the initial author admin rights for their repository?

jsakalos
10 Aug 2008, 11:04 AM
Yes, for their own repository.

steffenk
10 Aug 2008, 3:18 PM
May be something like we did for TYPO3 would be great.
Have a look at
http://forge.typo3.org/projects/show/extensions

Sure all users have an account. They can register a project which has a bugtracker / news / repository a.s.o. Project leaders /members are allowed to commit to rep.

The system is a redmine

jay@moduscreate.com
11 Aug 2008, 2:42 AM
why not just use SourceForge?!

SamuraiJack1
11 Aug 2008, 3:51 AM
why not just use SourceForge?!

Well, I'll try to describe what I have in mind.

Try to imagine that Ext library was written by many authors. And every author wrote a single source file. And after they combine these files into one library - the Ext library appear.

But the problem with documentation arised. Coz every author documented his file as he wants, and placed the documentation where he wants. Some authors doesnt documented theirs files at all.

So they all decided to create a central repository and to use one documenting/coding style. After that, when they placed all files into source/ directory (with sub-namespaces like data, util, etc), they were able to receive nice documentation, which centralized all library files in 1 place, and which can be found here: http://extjs.com/deploy/dev/docs/


So, the current purpose of the project - is to place all ux'es to one place and receive the same quality documentation on them, which will be available online

jay@moduscreate.com
11 Aug 2008, 5:23 AM
Per the license, you can't distribute/etc anything Ext that has the word 'library' in it.

SamuraiJack1
11 Aug 2008, 5:26 AM
Per the license, you can't distribute/etc anything Ext that has the word 'library' in it.

What do you mean and how it is related to ux repository?

jay@moduscreate.com
11 Aug 2008, 5:56 AM
Never mind,

I suppose if you don't distribute Ext WITH your proposed community framework, you should be OK.



4. PROHIBITED USES

You may not, without prior written consent of Ext JS, LLC, redistribute the Software or
Modifications other than by including the Software or a portion thereof within Your own product,
which must have substantially different functionality than the Software or Modifications and
must not allow any third party to use the Software or Modifications, or any portions thereof,
for software development purposes. You are explicitly not allowed to redistribute the Software
or Modifications as part of any product that can be described as a development toolkit or
library or is intended for use by software developers and not end-users. You are not allowed to
redistribute any part of the Software documentation.

You may not: a) use any part of the Software or Modifications or Your knowledge of the Software
(or any information that You learn as a result of Your use of the Software) to create a product
with the same or substantially the same functionality as the Software; b) transfer, rent, lease,
or sublicense the Software or Modifications, or any portions thereof; c) change or remove the
copyright notice from any of the files included in the Software or Modifications.

UNDER NO CIRCUMSTANCES MAY YOU USE THE SOFTWARE (INCLUDING WITHOUT LIMITATION THE SOURCE CODE
THEREOF) AS THE BASIS FOR OR IN CONNECTION WITH A PRODUCT THAT CONTAINS THE SAME, OR SUBSTANTIALLY
THE SAME, FUNCTIONALITY AS THE SOFTWARE.

SamuraiJack1
11 Aug 2008, 6:04 AM
Ah, yea, it will be separated from Ext library itself.

SamuraiJack1
14 Aug 2008, 11:35 AM
Glad to announce about the initial alpha release:

http://ux.samurai-jack.org/repo

It is very feature-limited and minimalistic yet, but still useful, take a look below for description.

1) Main repo is organized this way:
/authors - authors home directories
/trunk
/trunk/Ext
/trunk/Ext/ux - main trunk, all single ux'es are joining here

2) Each author's home directory is organized this way:
/authorName/tags
/authorName/branches
/authorName/trunk
/authorName/trunk/Ext
/authorName/trunk/Ext/ux - author's trunk, registered ux'es will be copied from here to main trunk

Authors can register here:
http://ux.samurai-jack.org/register

And later login here:
http://ux.samurai-jacl.org/login

After registration, the home directory of the author is created, and the author is the only who can write permissions for it.
(!) nothing will be copied from authors dir by default, see section 3)

3) Authors should register their's extension via additional form, available here:
http://ux.samurai-jack.org/uxregister
(should be done on early stage of ux development to reserve the name).

After registration, the extension (plus .css file) will be included to copy list and every hour these files will be copied from authors directory to main trunk.

Authors should place their's ux'es to proper directories in their's trunk, relative to namespace of the ux, for example:
extension Ext.ux.event.Broadcast (is under Ext.ux.events namespace)
should be named Broadcast.js and place like this:
/authorName/trunk/Ext/ux/event/Broadcast.js

So, these files will be copied every hour:
/authors/authorName/trunk/Ext/ux/event/Broadcast.js --> /trunk/Ext/ux/event/Broadcast.js
/authors/authorName/trunk/Ext/ux/event/Broadcast.css --> /trunk/Ext/ux/event/Broadcast.css


4) Every hour, after all files were copied from author's directories, JSDoc is starting against /trunk with recursion. It generate a directory of docs, which is available here:

http://ux.samurai-jack.org/docs


5) It is author's responsibility to properly place the file and document the code. If the file will be placed in another location it will not be copied to main trunk. If the JSDoc will fail on author's file, then his ux will be leaved undocumented and will not appear in main list.

------------------------------------------------------------------------------------------------------------
I'm inviting community members to participate.

devnull
14 Aug 2008, 11:59 AM
Very cool stuff, I like it alot.
It would be nice to have an easy package download link on each extension's main page too, as a zip file with js and css files included and with proper paths (maybe full filenames as in Ext.ux.event.Broadcast.js or as ux/event/Broadcast.js to work with your jScout setup).
Is there any consideration for extensions that do not fit the 1 js file and 1 css file model? Is there even a need for this consideration?

MaximGB
14 Aug 2008, 12:14 PM
From my POV it's a stillborn idea. What are the pros for me as an author of ExtJS extensions to commit my extensions to samurai-jack.org? As I can see this organization connected to perl Catalyst MVC framework. So my potential users can be misguided by that fact. They might think that my or any other ux require Catalyst or designed to work with it only. I also don't want my open source uxs to be associated with samurai-jack or any other ExtJS user ;). I don't mind against some ExtJS UX foundation or something like this. But it should be something neutral (ExtJS.org will be a good one). I think that creation of this kind of foundation should be guided by ExtJS LLC or by its volounteers or employes.

SamuraiJack1
14 Aug 2008, 12:16 PM
From my POV it's a stillborn idea. What are the pros for me as an author of ExtJS extensions to commit my extensions to samurai-jack.org? As I can see this organization connected to perl Catalyst MVC framework. So my potential users can be misguided by that fact. They might think that my or any other ux require Catalyst or designed to work with it only. I also don't want my open source uxs to be associated with samurai-jack or any other ExtJS user ;). I don't mind against some ExtJS UX foundation or something like this. But it should be something neutral (ExtJS.org will be a good one). I think that creation of this kind of foundation should be guided by ExtJS LLC or by its volounteers or employes.

Partially support this )

SamuraiJack1
14 Aug 2008, 12:27 PM
Very cool stuff, I like it alot.
It would be nice to have an easy package download link on each extension's main page too, as a zip file with js and css files included and with proper paths (maybe full filenames as in Ext.ux.event.Broadcast.js or as ux/event/Broadcast.js to work with your jScout setup).
Is there any consideration for extensions that do not fit the 1 js file and 1 css file model? Is there even a need for this consideration?

Thanks in general and for substantial comment in particular.
Actually exactly these (and another similar) questions I supposed to discuss in this thread.

Ideas about download link:
Think it should be included in a standard documentation template for UX. And either the author need to fill it, or it will be filled automatically. Actually, on this stage of the project the easiest way to download single ux - will be just to checkout the whole main trunk )

About ux'es that don't fit into 2 files - here is much to think about, we becoming to "distribution" concept (copyright by CPAN )) The distribution can contain several files, etc... For current stage of the JavaScript development it is not so important concept, because there is no native packaging mechanism (jScout is a good candidate for this role) and no testing mechanism. So, think 99% of all ux'es will fit 2 files for now, but its the 1st place for refactoring efforts in the nearest future.

SamuraiJack1
14 Aug 2008, 12:35 PM
From my POV it's a stillborn idea. What are the pros for me as an author of ExtJS extensions to commit my extensions to samurai-jack.org? As I can see this organization connected to perl Catalyst MVC framework. So my potential users can be misguided by that fact. They might think that my or any other ux require Catalyst or designed to work with it only. I also don't want my open source uxs to be associated with samurai-jack or any other ExtJS user ;). I don't mind against some ExtJS UX foundation or something like this. But it should be something neutral (ExtJS.org will be a good one). I think that creation of this kind of foundation should be guided by ExtJS LLC or by its volounteers or employes.

Well, I'm support this only in part about domain name )


From my POV it's a stillborn idea.
So, you are satisfied with "forum hunting" for each ux you are using?


What are the pros for me as an author of ExtJS extensions to commit my extensions to samurai-jack.org?
It is only the initial testing platform


As I can see this organization connected to perl Catalyst MVC framework.
It is wrote with it, but personally I'm not afilliated with them


I also don't want my open source uxs to be associated with samurai-jack or any other ExtJS user ;). I don't mind against some ExtJS UX foundation or something like this. But it should be something neutral (ExtJS.org will be a good one). I think that creation of this kind of foundation should be guided by ExtJS LLC or by its volounteers or employes.

I suggest to host it on extjs.com and ask the core team to allow to use their's documenting tool for this project.

hendricd
15 Aug 2008, 6:48 AM
All this appears a good start (and we've seen some momentum regarding this before, but crashed after the licensing change).

But, Jack has hinted (http://extjs.com/forum/showthread.php?p=160268#post160268) about plans as well (although to what end is not clear).
It also sounds as if the documentation syntax/API will likely remain proprietary for a while?All this spells 'continued-ambiguity'. It would seem the best we could hope for is a simple ux.Registry of some sort (which the Wiki already provides for those who really care about posting/supporting their stuff there)

mjlecomte
15 Aug 2008, 7:00 AM
I think a repository would more likely gain support if it offered:

an interface to search the extensions (tagging extensions as grid, form, store, or multiple, etc)
an area for demos to be loaded

Without those two items I don't see much added benefit compared to the current wiki or extensions forum.
For the interface I envisioned some sort of grouping grid with search and/or filter.

SamuraiJack1
15 Aug 2008, 7:47 AM
I think a repository would more likely gain support if it offered:
an interface to search the extensions (tagging extensions as grid, form, store, or multiple, etc)
an area for demos to be loadedWithout those two items I don't see much added benefit compared to the current wiki or extensions forum.
For the interface I envisioned some sort of grouping grid with search and/or filter.

Well, to understand the added benefit even in current state, please read this post: http://extjs.com/forum/showthread.php?p=207492#post207492
and imagine that every single file from Ext library is published in the form of forum topics, think it will be obviously after that. But you are right - features you mentioned should be really presented.

Still inviting community members, those who wants to participate, please pm me.

SamuraiJack1
15 Aug 2008, 8:42 AM
All this appears a good start (and we've seen some momentum regarding this before, but crashed after the licensing change).
But, Jack has hinted (http://extjs.com/forum/showthread.php?p=160268#post160268) about plans as well (although to what end is not clear).
It also sounds as if the documentation syntax/API will likely remain proprietary for a while?All this spells 'continued-ambiguity'. It would seem the best we could hope for is a simple ux.Registry of some sort (which the Wiki already provides for those who really care about posting/supporting their stuff there)

How about to participate in this, instead of JIT wars? )

mjlecomte
15 Aug 2008, 9:39 AM
Yes, this will or could be good. The thing I notice a lot though, as I'm sure you have, is people tend to ask "is there an online demo". Bad enough the freeloaders want the code, but they need to see a demo too. ;)

So support for demos, examples, etc. for the code would probably be just as essential as the API docs. Imagine if Ext didn't have the demos area!

Another item to chew on might be forum / discussion. If not in the repository, at least the ability to post a link back to the ext forums.

hendricd
15 Aug 2008, 9:47 AM
How about to participate in this, instead of JIT wars? )
I'd be happy to, if I understood exactly what the scope and feature-set of 'this' was going to be. ;)

SamuraiJack1
15 Aug 2008, 9:58 AM
Yes, this will or could be good. The thing I notice a lot though, as I'm sure you have, is people tend to ask "is there an online demo". Bad enough the freeloaders want the code, but they need to see a demo too. ;)

So support for demos, examples, etc. for the code would probably be just as essential as the API docs. Imagine if Ext didn't have the demos area!

Another item to chew on might be forum / discussion. If not in the repository, at least the ability to post a link back to the ext forums.

Actually, the problems you mentioned are already resolved. Since the svn is http-browsable, authors can upload the demos right inside their's home directories and put the links to it into the documentation. They also can put the links to forum thread, wiki page etc. Think the demos platform should be also systematized as it was done with Ext examples.

SamuraiJack1
15 Aug 2008, 10:09 AM
I'd be happy to, if I understood exactly what the scope and feature-set of 'this' was going to be. ;)

On this stage the purposes are
- improvements in documentation tool (several forum members are currently doing this: http://extjs.com/forum/showthread.php?t=43860)
- accounting system for authors
- List of all extensions, including tagging, searching, ranking, etc..
- documentation improvements

SamuraiJack1
21 Aug 2008, 11:51 AM
v0.1a released

Changelog:
------------------------------------------------------------------------------------------------------------
v0.1a - documentation system improvements:
http://ux.samurai-jack.org/docs
------------------------------------------------------------------------------------------------------------

SamuraiJack1
22 Aug 2008, 1:34 AM
Well, I'm going to register a "nickname-neutral" domen for this project and I'd like it to be accepted by most of community members. So, if you have your variant, feel free to post it here.

How about extjs-ux.org ? )

p.s. think variants with "forge" suffix are not suitable for this project, coz they resembles such projects as SourceFourge, RubyForge etc, which are intended for development support, whereas this repository is mostly intended for publishing support.

JorisA
22 Aug 2008, 1:36 AM
Awesome project, One thing that may be nice is the ability to have jsdoc parse the author name / thread url / source url from the source so it can be showed in the doc tree.

And is it also possible to run demo's on the server? Maybe it's an idea to host Ext 2.0/2.1/2.2 as well so all demos can link to it. And how should folder structure be then?

/authors/authorName/trunk/Ext/ux/event/Broadcast.js
/authors/authorName/trunk/Ext/ux/event/Broadcast.css
/authors/authorName/trunk/Ext/ux/event/SimpleDemo.html
/authors/authorName/trunk/Ext/ux/event/AdvancedDemo.html
/authors/authorName/trunk/Ext/ux/event/SampleData.xml

SamuraiJack1
22 Aug 2008, 1:50 AM
Awesome project, One thing that may be nice is the ability to have jsdoc parse the author name / thread url / source url from the source so it can be showed in the doc tree.

Good idea, I'm thinking exactly about something like this. Not sure yet how to implement it in the sane way, but it will appear in nearest releases.


And is it also possible to run demo's on the server? Maybe it's an idea to host Ext 2.0/2.1/2.2 as well so all demos can link to it. And how should folder structure be then?

/authors/authorName/trunk/Ext/ux/event/Broadcast.js
/authors/authorName/trunk/Ext/ux/event/Broadcast.css
/authors/authorName/trunk/Ext/ux/event/SimpleDemo.html
/authors/authorName/trunk/Ext/ux/event/AdvancedDemo.html
/authors/authorName/trunk/Ext/ux/event/SampleData.xml
Yea, its possible, since svn is http-browsable, so you can put links to demos inside the documentation like this:


/authors/authorName/trunk/Ext/ux/event/SimpleDemo.html -->
http://ux.samurai-jack.org/repo/authors/authorName/trunk/Ext/ux/event/SimpleDemo.html

/authors/authorName/trunk/Ext/ux/event/AdvancedDemo.html -->
http://ux.samurai-jack.org/repo/authors/authorName/trunk/Ext/ux/event/AdvancedDemo.html

/authors/authorName/trunk/Ext/ux/event/SampleData.xml -->
http://ux.samurai-jack.org/repo/authors/authorName/trunk/Ext/ux/event/SampleData.xml

SamuraiJack1
22 Aug 2008, 2:05 AM
You can also link ext files (currently 2.1) from here


http://ux.samurai-jack.org/ext21/ext-all.js
http://ux.samurai-jack.org/ext21/adapter/ext/ext-base.js
....etc, there is a whole Ext distribution there

mjlecomte
22 Aug 2008, 5:10 AM
Well, I'm going to register a "nickname-neutral" domen for this project and I'd like it to be accepted by most of community members. So, if you have your variant, feel free to post it here.

How about extjs-ux.org ? )

p.s. think variants with "forge" suffix are not suitable for this project, coz they resembles such projects as SourceFourge, RubyForge etc, which are intended for development support, whereas this repository is mostly intended for publishing support.

If you'll open this to more potential, I like the name ext-dojo.com (the name even goes with your username?). Anyway there might be:
ext.dojo.com/ux/
ext.dojo.com/blog/
ext.dojo.com/samples/
ext.dojo.com/learn/

This way people can collectively contribute to examples, people can post samples using their ux, etc. Probably use similar registration where people can post in blogs or post examples.

SamuraiJack1
22 Aug 2008, 5:32 AM
From Wikipedia:
------------------------------
A dojo (道場 (http://en.wiktionary.org/wiki/%E9%81%93%E5%A0%B4), dōjō? (http://en.wikipedia.org/wiki/Help:Japanese)) is a Japanese (http://en.wikipedia.org/wiki/Japanese_language) term which literally means "place of the Way". Initially, Dojo were adjunct to temples. The term can refer to a formal training place for any of the Japanese do arts but typically it is considered the formal gathering place for students of a martial arts (http://en.wikipedia.org/wiki/Martial_arts) style to conduct training, examinations and other related encounters.
The concept of a dojo as a martial arts training place is a Western (http://en.wikipedia.org/wiki/West) concept; in Japan (http://en.wikipedia.org/wiki/Japan), any physical training facility, including professional wrestling schools (http://en.wikipedia.org/wiki/Professional_wrestling_school) may be called dojos as well depending on the context.
------------------------------

Sounds cool, I like it )

The minuses are - association with Dojo toolkit and a bit fancy meaning. Good idea, anyway )

jay@moduscreate.com
22 Aug 2008, 5:57 AM
I would suggest no. I like the idea, other than another framework being named that.


also, have you gotten permission from the ext team to use the name extjs as part of a domain?

SamuraiJack1
22 Aug 2008, 6:09 AM
I would suggest no. I like the idea, other than another framework being named that.
Yea, if only there was no Dojo toolkit, this idea would be great.


also, have you gotten permission from the ext team to use the name extjs as part of a domain?

Well, Ext team does'nt made any comments yet. Though (in pm), Brian said: "Feel free to do so (we're all for it)" so, hope they support this effort in some form. Actually, I think that the best domain name is: ux.extjs.com

SamuraiJack1
25 Aug 2008, 7:03 AM
v0.11a released

Domain name changed to nickname neutral, if this was a blocker for someone - then it is removed.

Changelog:
------------------------------------------------------------------------------------------------------------
v0.11a - domain name changed:
http://extjs-ux.org/docs
http://extjs-ux.org/register
http://extjs-ux.org/uxregister
http://extjs-ux.org/login
------------------------------------------------------------------------------------------------------------
v0.10a - documentation system improvements:
http://ux.samurai-jack.org/docs
------------------------------------------------------------------------------------------------------------

jerrybrown5
25 Aug 2008, 9:09 PM
For obvious reasons we should agree on a licensing standard of all included UX components. I favor LGPL as expressed in everything Jsakalos writes.

* @license compcomm.js is licensed under the terms of the Open Source * LGPL 3.0 license. Commercial use is permitted to the extent that the * code/component(s) do NOT become part of another Open Source or Commercially * licensed development library or toolkit without explicit permission.

JorisA
26 Aug 2008, 4:52 AM
good one. I'll see if I've got some stuff to add.

SamuraiJack1
26 Aug 2008, 5:17 AM
For obvious reasons we should agree on a licensing standard of all included UX components. I favor LGPL as expressed in everything Jsakalos writes.

* @license compcomm.js is licensed under the terms of the Open Source * LGPL 3.0 license. Commercial use is permitted to the extent that the * code/component(s) do NOT become part of another Open Source or Commercially * licensed development library or toolkit without explicit permission.

I think the repository should not limit extension's authors to one particular license, coz it is only publishing area, no more than that.
But the default license should be mentioned, yes. What do you think about smth like: "If the license model is not explicitly mentioned in the description of the extension, then it is supposed to be licensed under the terms of the Open Source * LGPL 3.0 license"? And authors should agreed with this note before registration.

harley.333
26 Aug 2008, 5:58 AM
I've got a couple features I'd like to suggest. These features are for "users" of the site (not necessarily extension-developers):
1. Allows users of the site to keep a "briefcase" of extensions. When I log into the public site, I'm presented with my "briefcase" which contains extensions that I've placed there.

2. Create a "Build-Your-Own" feature for extensions. The site would package up selected extensions using Ext's JSBuilder. This gives users a single, minimized JS file which contains all of the selected extensions.


On a side note, I've written several extensions for myself, and I always use my initials as a namespace. For example:


Ext.ux.hhj.FormWindow

I did this to avoid naming collisions, and I'm curious what other developers think of this. I think this would avoid the potential 'first-come-first-registered' problem.

SamuraiJack1
26 Aug 2008, 7:58 AM
I've got a couple features I'd like to suggest. These features are for "users" of the site (not necessarily extension-developers):
1. Allows users of the site to keep a "briefcase" of extensions. When I log into the public site, I'm presented with my "briefcase" which contains extensions that I've placed there.

2. Create a "Build-Your-Own" feature for extensions. The site would package up selected extensions using Ext's JSBuilder. This gives users a single, minimized JS file which contains all of the selected extensions.


Reasonably good ideas, I placed them in my "features.txt" file. Though these features are for "users" and will be implemented I think in 2.0 release only (1.0 milestone will be accounting system for authors + sane navigation through ux'es)



On a side note, I've written several extensions for myself, and I always use my initials as a namespace. For example:


Ext.ux.hhj.FormWindow
I did this to avoid naming collisions, and I'm curious what other developers think of this. I think this would avoid the potential 'first-come-first-registered' problem.

Think using initials as high-level namespace for ux'es is not "best practice", coz it is less descriptive than another high-level namespace.
For example compare :
Ext.ux.panel.YouTubePanel and Ext.ux.sj.YouTubePanel
Ext.ux.panel.GMapPanel and Ext.ux.oa.GMapPanel
Users will intuitively expect all panel-like extensions in Ext.ux.panel namespace and they'll first check it and only after that will start search in another places.
But choosing the name is fully depends from author, anyway.

mjlecomte
26 Aug 2008, 8:06 AM
I use similar naming convention as
Ext.ux.panel.YouTubePanel
naming the extension override similar to package/class.

Prepending the author name earlier in the namespace only complicates it in my opinion. The location doesn't matter in that case but would always require the authors initials to keep track of.

If someone else comes up with another YouTubePanel then it can just go:
Ext.ux.panel.YouTubePanel (first author)
Ext.ux.panel.YouTubePanel.hhj (next author)

At least this way not all extensions would have to use the author initials. (Next) Author can inject their initials at end or name the extension differently.

harley.333
26 Aug 2008, 10:19 AM
I guess since the repositories are already broken down by author, adding the author to the namespace is totally unnecessary. I was really thinking of the case where a developer uses two "YouTubePanel" extensions. But then, why would any sane developer do that?!

Since the web site's going to require that all extension names be unique, you'll probably see alot of wacky naming conventions (DataStore, myDataStore, xDataStore, hhjDataSore, etc). I was suggesting a standard (albeit wacky) naming convention. Maybe you don't need entension names to be unique after all...?

SamuraiJack1
28 Aug 2008, 4:42 AM
Demonstration of the demo-hosting capabilities of the repo:

http://extjs.com/forum/showthread.php?t=45448

mjlecomte
28 Aug 2008, 7:39 AM
If the doc system is configurable by you I'm wondering if you need the following at the top along with the package, class info, etc.


Author
Version
License

Author may not be needed, but I think the other two should probably be prominently displayed? Not sure how appropriate Version would be since this is on svn, but would give an indication where you could see how old your copy is?

Coming along nicely... ;)

SamuraiJack1
28 Aug 2008, 8:46 AM
If the doc system is configurable by you I'm wondering if you need the following at the top along with the package, class info, etc.
Author
Version
LicenseAuthor may not be needed, but I think the other two should probably be prominently displayed? Not sure how appropriate Version would be since this is on svn, but would give an indication where you could see how old your copy is?

Coming along nicely... ;)

Currently, I recommend to explicitly include all publishing information in the description of your main class, inside the JSDoc comments, like this:


/**
* A persistent menu, rendered on panel. This menu can be rendered like any other panel, there is no need in additional <b>show()</b> call.
* This menu is not closed when its child element is clicked or child menu is hidden.
* <br>Based on Animal's code : <a href="http://extjs.com/forum/showthread.php?t=26395">http://extjs.com/forum/showthread.php?t=26395</a>
* <br><br>Demo link: <a href="http://extjs-ux.org/repo/authors/SamuraiJack/trunk/Ext/ux/panel/MenuPanel/menus.html">http://extjs-ux.org/repo/authors/SamuraiJack/trunk/Ext/ux/panel/MenuPanel/menus.html</a>
* <br><br>Forum thread: <a href="http://extjs.com/forum/showthread.php?t=45448">http://extjs.com/forum/showthread.php?t=45448</a>
* @class Ext.ux.panel.MenuPanel
* @extends Ext.Panel
*/
You can use html markup here.
Note that the description of the class should be place before the @class tag.

Take a look here for an example of JSDoc markup:
http://extjs-ux.org/repo/trunk/Ext/ux/panel/MenuPanel.js

Also the version information should be included, coz SVN revision number is constantly increasing, while others are commiting (each commit create a new revision of the whole repo).

jerrybrown5
28 Aug 2008, 9:44 PM
Author
Version (+ date)
License

Everything is progressing nicely. I also like the header idea but I agree that these three fields should be broken out--if possible. From a developer perspective I would need to know this info before I could even think about implementing anything.

Best regards,
Jerry

SamuraiJack1
29 Aug 2008, 7:49 AM
v0.12a Released

Changes:
fixed several bugs, thanks to mjlecomte
minor documentation improvments :
following tags added: @author, @license, @version
partially {@link href} construction support adde for following cases:
link to another class, like {@link Ext.ux.another.ux}
link to the symbol in the current class, should be used like {@link #Ext.ux.current.class-method_name} Example: http://extjs-ux.org/docs/
(look on Ext.ux.panel.MenuPanel documentation)

mjlecomte
29 Aug 2008, 7:22 PM
Can overrides be included in the repository also? Not sure how the naming would work in that situation since there could be multiple overrides of the same class.

hendricd
30 Aug 2008, 8:43 AM
@(SamuraiJack1, et all) -- Great work/collaboration effort on this project ! Good to finally see some action on this issue.

How might we address the issue of namespace registration of established ux's that leverage multiple inheritance to deliver multiple classes (eg.
ux.Media[Component/Panel/Window] (base classes) ->
ux.MediaFlash[Component/Panel/Window] ->
ux.Chart[OFC2/Fusion/......][Component/Panel/Window]
)
and often with multiple source files involved?

MI (from a proposed documentation perspective) doesn't really fit the notion of the ux.panel.Something, ux.window.Something, .....
Not even sure jsDoc was designed to handle such a scenario in the first place. :s

Because of the current documentation/namespace-registration structure, a re-organization of existing ux namespaces would quickly litter the doc site and break everyone's code if such a namespace change were required. Or, in the end, are we really talking about (virtual) documentation namespaces that may have little to do with the actual namespace implementation? :-?

Second,
What's the final concensus on what licenses are 'permitted' to participate in this? Some extensions will clearly require GPL treatment because of their potential conflicts with the FLOSS Exception restrictions, while others could easily qualify with even 'lesser' (yet FLOSS-compatible) status than LGPL.

Third,
Does a ux.plugins namespace fit in here too?

mjlecomte
30 Aug 2008, 8:58 AM
I was thinking about plugins along with the overrides as a matter of fact.

Plugins would basically be same as extensions wouldn't it? I would NOT want to see an entire separate directory for plugins and overrides though...
not this:


L ux
L extensions
L grid
L filter
L plugins
L grid
L filter

That would be pain to manage looking around. I would simply want it arranged by closest class match then maybe the ux author will have to append as they see fit:


L ux
L grid
L filter
Ext.ux.grid.Filter.js (an extension)
Ext.ux.grid.Filter.plugin.js (a plugin)
L store
L JsonStore
Ext.ux.store.JsonStore.js (a plugin)
Ext.ux.store.JsonStore.extension.js (an extension created later)
Ext.ux.store.JsonStore.authorName.extension.js (an extension created even later)

Not sure does every dot "." create another leaf in the doc tree?

For the more complicated extensions like MIF wouldn't this be similar to a grid which relies on several classes put together (column model, grid, grid view, etc. etc.). I would guess for each file in the extension library you'd probably need to register a separate ux for it though? If that's the case I guess an enhancement to the ux registration form might be to permit specifying more than 1 name (and maybe show a preview of the directory, etc. the new ux would be stored in prior to hitting "save" to help with editing, etc.).

hendricd
30 Aug 2008, 11:53 AM
For the more complicated extensions like ux.Media, wouldn't this be similar to a grid which relies on several classes put together (column model, grid, grid view, etc. etc.).

Those are class members(properties), not super-classes.

The issue stems from the fact that higher level media/flash classes inherit from multiple base classes (namespaces), and I'm just wondering how jsDoc could handle those while still keeping the documentation/namespace heirarchy managable.

SamuraiJack1
31 Aug 2008, 7:42 AM
@(SamuraiJack1, et all) -- Great work/collaboration effort on this project ! Good to finally see some action on this issue.

How might we address the issue of namespace registration of established ux's that leverage multiple inheritance to deliver multiple classes (eg.
ux.Media[Component/Panel/Window] (base classes) ->
ux.MediaFlash[Component/Panel/Window] ->
ux.Chart[OFC2/Fusion/......][Component/Panel/Window]
)
and often with multiple source files involved?

MI (from a proposed documentation perspective) doesn't really fit the notion of the ux.panel.Something, ux.window.Something, .....
Not even sure jsDoc was designed to handle such a scenario in the first place. :s

Because of the current documentation/namespace-registration structure, a re-organization of existing ux namespaces would quickly litter the doc site and break everyone's code if such a namespace change were required. Or, in the end, are we really talking about (virtual) documentation namespaces that may have little to do with the actual namespace implementation? :-?


Glad to see the constructive discussion started.

Actually, when we are talking about the "ux'es" (both extensions and plugins) we are talking about "packages".

Lets take for example Ext.ux.panel.MenuPanel. During publishing, the javascript class "Ext.ux.panel.MenuPanel" is placed into "Ext.ux.panel.MenuPanel" package. And this package is placed under URL like: /Ext/ux/panel/MenuPanel.js.

This "directory per each namespace" principle strictly binds the URL of the package with its name. This will allow to create references to this package from another packages. This is the only "strictness" in this scheme - the actual name choosing for extension and for the package is fully at the discretion of the author.

The notion "Ext.ux.panel.something" is good for specialized extensions, which features are good described with two words - panel and "something". More complex extensions are just not falled under a two simple tags, so there is no ideal single naming scheme for them, which is based on hierarchy. So, the authors are free to choose a good descriptive name )

Thats the general consideration about the choosing namespace. And I think for established ux's will be the best to publish them with current name, and may be switch to another in next major release.



Second,
What's the final concensus on what licenses are 'permitted' to participate in this? Some extensions will clearly require GPL treatment because of their potential conflicts with the FLOSS Exception restrictions, while others could easily qualify with even 'lesser' (yet FLOSS-compatible) status than LGPL.

Third,
Does a ux.plugins namespace fit in here too?

Why should repository limit the authors to any set of licenses? Think we should talk only about the "default license" and some kind of "user agreement" with authors, which should relive any legal responsibilities from the repository project itself.

SamuraiJack1
31 Aug 2008, 7:52 AM
I was thinking about plugins along with the overrides as a matter of fact.

Plugins would basically be same as extensions wouldn't it? I would NOT want to see an entire separate directory for plugins and overrides though...
not this:


L ux
L extensions
L grid
L filter
L plugins
L grid
L filter
That would be pain to manage looking around. I would simply want it arranged by closest class match then maybe the ux author will have to append as they see fit:


L ux
L grid
L filter
Ext.ux.grid.Filter.js (an extension)
Ext.ux.grid.Filter.plugin.js (a plugin)
L store
L JsonStore
Ext.ux.store.JsonStore.js (a plugin)
Ext.ux.store.JsonStore.extension.js (an extension created later)
Ext.ux.store.JsonStore.authorName.extension.js (an extension created even later)
Not sure does every dot "." create another leaf in the doc tree?

For the more complicated extensions like MIF wouldn't this be similar to a grid which relies on several classes put together (column model, grid, grid view, etc. etc.). I would guess for each file in the extension library you'd probably need to register a separate ux for it though? If that's the case I guess an enhancement to the ux registration form might be to permit specifying more than 1 name (and maybe show a preview of the directory, etc. the new ux would be stored in prior to hitting "save" to help with editing, etc.).

About the 1st part - actually the answer is "Plugins would basically be same as extensions wouldn't it?"

About the 2nd part - thats the nearest refactoring case, currently thinking how to implement this with minimal efforts required from authors.

mjlecomte
31 Aug 2008, 8:15 AM
I'd say the page where the author registers the extension should just have some verbage that indicates that anyone that registers a ux is assumed by default to be using license XXXX and if they want a different license then the author is responsible to explicitly list said license(s) with @license tag(s) in the source code.

jelt
2 Sep 2008, 6:30 AM
how to add an ux to the repository ?

i've created an account. And now ?

"Create New Topic" on the left menu ? (network error)
description for authors which perhaps provide help about that ? (network error).

So please explain here how to do that...

PS : and the user registration is the crappiest i've never seen ! Why, by the hell, the user must be capitalized firstname last name ? my user name is Jelt, but it's not possible to set it... so Jelt Jelt is born... to stupid interface

SamuraiJack1
2 Sep 2008, 6:46 AM
how to add an ux to the repository ?

i've created an account. And now ?

"Create New Topic" on the left menu ? (network error)
description for authors which perhaps provide help about that ? (network error).

So please explain here how to do that...

PS : and the user registration is the crappiest i've never seen ! Why, by the hell, the user must be capitalized firstname last name ? my user name is Jelt, but it's not possible to set it... so Jelt Jelt is born... to stupid interface


There were problems with server, now they are fixed and all links should work.

Seems you have registered in the wiki of the project - not in the repo.

Author registration is here:
http://extjs-ux.org/register

After registration as an author you should register your extension here:
http://extjs-ux.org/uxregister

More details here:
http://extjs-ux.org/twiki/bin/view/Main/RepositoryDesign

jelt
2 Sep 2008, 10:41 PM
thanks for your help :)

jerrybrown5
4 Sep 2008, 11:05 PM
All,
I received the go-ahead from Animal to put a couple of the components in this repository that started life on the forum. Furthermore, I am willing to put a few more custom components that he developed on my request (and expense) here. All would be released for the common good of the Ext community under LGPL.

CarouselLayout -- still the best carousel implementation (even better than the one I wrote :-)
PanPanel--pans (instead of scrolling) a container that contains a large image or other
TemplateLayout -- Use an arbitrary html template to control field placements in a layout
RowBlinds--window blinds that elegantly come down from a database grid row--can be tied to mouse events eg click or mouse over
MultSelectPopup-- a popup to multiple select an item that can "snake" into multiple columns (eg Windows XP start menu)

However, this is a lot to document. Anybody willing to help here?

Cheers,
Jerry

galdaka
6 Sep 2008, 2:32 AM
I

SamuraiJack1
6 Sep 2008, 5:30 AM
[quote=galdaka;219922]I

SamuraiJack1
8 Sep 2008, 12:17 PM
The problem with svn (409 conflict) seems persist and appears after certain amount of new revisions. It looks like bug in the latest svn version.

I'm going to setup another svn version - this will take time, meanwhile if someone will encountered this problem - please PM me.

SamuraiJack1
9 Sep 2008, 1:47 AM
Fixed bug in jsdoc_ext, that prevented updating of the documentation tree. Also fixed properties documentation (added expanding capabilities). If you are using jsdoc_ext locally, you can update it from svn.

SamuraiJack1
9 Sep 2008, 5:40 AM
All,
I received the go-ahead from Animal to put a couple of the components in this repository that started life on the forum. Furthermore, I am willing to put a few more custom components that he developed on my request (and expense) here. All would be released for the common good of the Ext community under LGPL.

CarouselLayout -- still the best carousel implementation (even better than the one I wrote :-)
PanPanel--pans (instead of scrolling) a container that contains a large image or other
TemplateLayout -- Use an arbitrary html template to control field placements in a layout
RowBlinds--window blinds that elegantly come down from a database grid row--can be tied to mouse events eg click or mouse over
MultSelectPopup-- a popup to multiple select an item that can "snake" into multiple columns (eg Windows XP start menu)

However, this is a lot to document. Anybody willing to help here?

Cheers,
Jerry

Have you changed your mind about publishing these ux's? (pm'ed to you couple of days ago).

jerrybrown5
9 Sep 2008, 6:30 AM
Have you changed your mind about publishing these ux's? (pm'ed to you couple of days ago).

No, not at all. I think the UX is a great idea and I want to help support it. However, I am presently overbooked at work, which is why I can't document them faster.

BTW I didn't receive your PM. ??

SamuraiJack1
9 Sep 2008, 6:56 AM
No, not at all. I think the UX is a great idea and I want to help support it. However, I am presently overbooked at work, which is why I can't document them faster.

BTW I didn't receive your PM. ??

Cool ) I'm in for one of the ux's, preferably CarouselLayout (coz I had plans to develop my own). Going to send pm again - check your inbox please.

SamuraiJack1
9 Sep 2008, 7:53 AM
2 jerrybrown5:

Got your pm (please send me your any another contact)

jerrybrown5
9 Sep 2008, 8:22 AM
I uploaded Ext.Layout.Carousel. However, it gives me a bad un/pw when I tried to register it. I will send my email via pm.

jerrybrown5
11 Sep 2008, 9:33 AM
With the help of SamuraiJack1 and of course Animal for orginally writing it and giving me the go ahead to post it, the high quality carousel ux component is up including a demo. Take a look at it when you have a chance. (1 down 4 to go)
http://extjs-ux.org/docs/
Ext.ux.Layout.Carousel

mjlecomte
11 Sep 2008, 10:28 AM
Any ideas for registering css themes?

SamuraiJack1
12 Sep 2008, 12:54 AM
Following scheme could work:

- themes registers under Ext.ux.theme or Ext.ux.theme.authorName namespace (to naturally separates all themes of specific author)
- themes can be uploaded to author's home directory (full size + zipped package)
- the author creates a "placeholder" *.js file with name like: Ext.ux.theme.Slate.js and place in its description links to download and demo as usual

ZooKeeper
14 Sep 2008, 9:28 AM
I think the community descperatly needs a theme repository. Thanks for the effort of providing one!

mystix
16 Sep 2008, 10:08 PM
just visited the repo's docs browser and encountered this:

http://img301.imageshack.us/img301/9385/200809171406in0.png

jerrybrown5
16 Sep 2008, 10:39 PM
fyi http://www.extjs.com/forum/showthread.php?t=47375

SamuraiJack1
17 Sep 2008, 1:19 AM
just visited the repo's docs browser and encountered this:



2Doug
Think this glitch was caused by this line:

Ext.extend(Ext.ux.ManagedIFrame , Ext.util.Observable,It creates 2nd copy of class definition (1st was created by @class)
try to make it @private

SamuraiJack1
17 Sep 2008, 2:18 AM
SVN version of repository updated to 1.5.2.
It announce about memory leak fixing, so I hope that insane "409 Confilct" error is gone.

mjlecomte
17 Sep 2008, 5:10 AM
just visited the repo's docs browser and encountered this:

To clarify Jack's response. This is a problem to be corrected by the author of that extension. The doc system expects certain formatting and this shows what could happen if you stray from it's expectations. In this particular case Doug has a complicated extension that is abnormal, and is more difficult to figure out how to make it behave in the doc system (multiple files / classes for one package).

hendricd
17 Sep 2008, 10:39 AM
Ah, you noticed that too. /:)

t34
17 Sep 2008, 12:15 PM
..., the high quality carousel ux component is up including a demo. Take a look at it when you have a chance.
http://extjs-ux.org/repo/authors/jerrybrown5/trunk/Ext/ux/layout/Carousel/Demo.html is broken.

SamuraiJack1
17 Sep 2008, 12:32 PM
Thanks for pointing, fixed

jerrybrown5
17 Sep 2008, 1:27 PM
The template layout is now posted with a demo. This is my favorite layout because there have been so many uxs created to place fields side by side or up and down, when all you "really" needed was arbitrary html access to place any field wherever you darn well pleased. This is the only place that this code has been published so take a look and let me know what you think.

PS It does have one minor known issue that I can't get on top of yet. It will render each member component twice. Since this didn't cause any problem with all of the components that I use, I don't think it will be much of an issue to most of you as well.

** Two down and three to go.

mjlecomte
17 Sep 2008, 1:41 PM
Can you post forum threads for the ux's so there's a designated place to post for each ux? Carousel Layout doesn't have one at moment.

The demo is currently broken for IE7.

jerrybrown5
17 Sep 2008, 1:48 PM
The demo will be fixed on the next doc build. SamuraiJack moved it from Ext.ux.Layout to Ext.ux.layout and then we had an SVN conflict. In the meantime you can view it here

http://extjs-ux.org/repo/authors/jerrybrown5/trunk/Ext/ux/layout/Carousel/Demo.html

Also, feel free to create a thread for any UX that I post.

SamuraiJack1
19 Sep 2008, 4:01 AM
jsdoc_ext updates:

- added support for default value in the format

* @param {String} [accessLevel="author"] The user accessLevel is optional.(thanks to azbok)

- added @example tag, recognized in methods declaration, it wraps its content in <pre><code> tags and place it before parameters description
(thanks to azbok)

You can check the declare method documentation of jScout class in ux repository for examples:
http://extjs-ux.org/docs/

-fixed bug: last defined event lost in the case, when @class definition and Ext.extend definition are divided

DigitalSkyline
20 Sep 2008, 8:15 AM
I was just wondering what the status of this site is... right now it seems to be down:
Internal Server Error

...and when I tried to register the other day I got some other error.

mjlecomte
20 Sep 2008, 8:19 AM
I just tested and it works for me. I know there have been some svn issues and it will go offline sporadically.

DigitalSkyline
20 Sep 2008, 8:34 AM
http://extjs-ux.org/ forwards to ->
http://extjs-ux.org/twiki/bin/view/Main/ExtUxRepository

I'm getting the error on this page but not the docs page...

mjlecomte
20 Sep 2008, 9:19 AM
Yeah, the root forwards to the wiki for whatever reason. You're probably not too interested in the wiki anyway.

DigitalSkyline
20 Sep 2008, 10:07 AM
No you're right ... but still can't register :((

http://DigitalSkyline.com/media/images/captures/2008-09-20_1401.png

mjlecomte
20 Sep 2008, 10:16 AM
Server may be down. But FYI you do not need to register to browse/download. I only mention this because there have been several people who have registered and who have not posted anything. THere's no reason to register until you're ready to post an ux.

DigitalSkyline
20 Sep 2008, 10:34 AM
:) yeah I'm aware ... but I'm an eager beaver - I'm sure I can find plenty to commit...

SamuraiJack1
20 Sep 2008, 11:12 AM
server is on VPS, sometimes it goes to very low free memory, fixing..

SamuraiJack1
20 Sep 2008, 11:32 AM
rebooted server, registration works

You are welcome )

jerrybrown5
21 Sep 2008, 4:42 PM
For the one other person that cares (for info see polling http://extjs.com/forum/showthread.php?p=227240) , I just released and posted Ext.ux.Sound.

Cheers,
Jerry

jay@moduscreate.com
23 Sep 2008, 4:27 AM
http://tdg-i.com/img/screencasts/2008-09-23_0827.png

mjlecomte
23 Sep 2008, 4:34 AM
To clarify Jack's response. This is a problem to be corrected by the author of that extension. The doc system expects certain formatting and this shows what could happen if you stray from it's expectations. In this particular case Doug has a complicated extension that is abnormal, and is more difficult to figure out how to make it behave in the doc system (multiple files / classes for one package).


http://tdg-i.com/img/screencasts/2008-09-23_0827.png

ie, previously posted.

hendricd
23 Sep 2008, 7:48 AM
Yeah, yeah, I'm working on it. Once every hour. (:|

mjlecomte
23 Sep 2008, 7:50 AM
Yeah, yeah, I'm working on it. Once every hour. (:|

LOL. My problem too.

SamuraiJack1
23 Sep 2008, 9:24 AM
Will be more convenient to setup local copy of jsdoc_ext:

- install JavaVM
- checkout the jsdoc_ext project from:
https://jsdoc-tk-ext.svn.sourceforge.net/svnroot/jsdoc-tk-ext
(for example to c:\app\jsdoc)

and if your ux's are placed into c:\repos\ExtUx you can generate docs for them with the command line like:



cd c:\app\jsdoc
java -jar jsrun.jar app\main.js -r -H="UX Repository" c:\repos\ExtUxsee also readme.txt in jsdoc distribution for details

SamuraiJack1
23 Sep 2008, 9:26 AM
forget to mentioned - docs will appear in

c:\app\jsdoc\out\jsdox

hendricd
23 Sep 2008, 9:56 AM
whats the recommended build? trunk or branch ?

SamuraiJack1
23 Sep 2008, 10:01 AM
trunk contains all latest patches, its recommended

SamuraiJack1
3 Oct 2008, 12:43 AM
Now its possible to create direct links to classes in repository like this:
http://extjs-ux.org/docs/?class=Ext.ux.event.Broadcast

hendricd
5 Nov 2008, 7:30 PM
Are docs being generated from the Repo any more? I'm having no luck at all. :-?

SamuraiJack1
6 Nov 2008, 1:42 AM
Sorry, I just turn off my home computer for night (docs are generated on it). Now its on.

SAnDAnGE
11 Nov 2008, 1:32 AM
Does that website work anymore ?

SamuraiJack1
11 Nov 2008, 6:23 AM
Hosting problems, currently solving.

SamuraiJack1
11 Nov 2008, 6:34 AM
Server is up.

SamuraiJack1
22 Nov 2008, 4:07 AM
Project is moving to another hosting, service may be down till Monday.

albeva
4 Dec 2008, 12:01 PM
it seems still to be down...

SamuraiJack1
4 Dec 2008, 1:21 PM
It seems working for me - I've just tested all main links

http://extjs-ux.org/repo/
http://extjs-ux.org/docs/
http://extjs-ux.org/login

also login itself works..

albeva
10 Dec 2008, 7:22 PM
Nope.

Address Not Found

I'm in UK...

drew
12 Jan 2009, 9:58 PM
I'm also having problems accessing http://extjs-ux.org (I'm from Aus).

Although http://downforeveryoneorjustme.com seems to think it's really up. Odd?

SamuraiJack1
13 Jan 2009, 4:07 AM
Server was moved to dedicated hosting in Germany - its really up..

drew
13 Jan 2009, 3:11 PM
Works for me now. Go Germany!! :)

johnsbrn
2 Feb 2009, 10:41 AM
Github is a fantastic source code management system that has great collaborative features. ux namespace could be determined by github usernames, similar to how they manage gems. If you are not familiar with git and Github, check it out because it is really great. Rails and the Linux kernel are both using git source code management.

SamuraiJack1
2 Feb 2009, 11:00 AM
Sure, git is very advanced vcs. Though goals of ux repo are somewhat different - they are about to establish an "ux publishing standard". SVN was just used as convienient uploading and authorization platform.

johnsbrn
6 Feb 2009, 4:30 PM
Yes, but I think some kind of integration with github would be really helpful. The ability to easily fork a project and then submit your changes back to the source really promote community development in a way that I have never seen any other system do.


Sure, git is very advanced vcs. Though goals of ux repo are somewhat different - they are about to establish an "ux publishing standard". SVN was just used as convienient uploading and authorization platform.

mjlecomte
6 Feb 2009, 4:48 PM
It doesn't really matter if a repo at A (github) is better than a repo at B (current repo) if people only put code at C (the forums) or don't put it in at all.

chalu
18 Feb 2009, 4:47 AM
I have to set the mime-type for the html file for the demo of an extension so that it can get executed by the server instead of returning plain text, but the demo page send requests to some PHP files. I keep getting 404 (Not Found) errors when the PHP requests are made by the demo page. Copying the same link reported by firebug as 404, into a new tab takes me to the PHP file, but it is sent to the browser as plain text (displayed).

I am sure I'll have to set a mime-type property on it, but I don't know what it is. I checked my (local) Apache config file and found this : application/x-httpd-php

I'll try it and see what happens.

Regards.

SamuraiJack1
18 Feb 2009, 5:13 AM
May be php execution is disabled, what is your extension?

chalu
18 Feb 2009, 7:43 AM
May be php execution is disabled, what is your extension?

Yeah, something is wrong with PHP execution (maybe), first I get a 401 error (even after entering my credentials) and the a 404 (Not Found). copying the same URL and pasting in a new browser tab now presents the file for download :-/:-/. I have set the mime-type so they no longer just sent to the browser as text :-/:-/

I was trying to make a demo for Ext.ux.form.ScreenshotField.

Thanks.

SamuraiJack1
18 Feb 2009, 8:58 AM
Unfortunately, php files are served from svn repository, which is not a part of file system and is available via mod_dav. Thats why Apache 1st asks for password (401 Authorization Required) and then - gives 404 (because its a POST request). Opening the same URL in browser returns the content of the file (GET request).

May be its possible to somehow configure Apache that way, that it will post-process the content of file, received from repository, but I dont know how..

chalu
19 Feb 2009, 12:22 AM
Unfortunately, php files are served from svn repository, which is not a part of file system and is available via mod_dav. Thats why Apache 1st asks for password (401 Authorization Required) and then - gives 404 (because its a POST request). Opening the same URL in browser returns the content of the file (GET request).

May be its possible to somehow configure Apache that way, that it will post-process the content of file, received from repository, but I dont know how..

I am also very new to SVN, which is why my extensions are coming this late, I'd check with other SVN forums to see how this should work. However, I test my applications locally from working copies and they work well, that is :

My Repository : D:\repo\svn

Apache Webroot : D:\htdocs

Development Working Copy : D:\htdocs\workspaces\aptana\screenshotfield
So to test I'd go to : http://localhost/workspaces/aptana/screenshotfield/

For my full / real applications (that may use one or two projects like screenshotfield), I made another working copy that always points to trunk (unlike my development working copy that may be switched to a branch), and this is at :
D:\htdocs\apps\ all I need to get it up do date is run svn update on the application in question

Mybe I never have these problems because I am running things from working copies, all under my apache webroot, and not from the SVN virtual file system itself.

Regards.

SamuraiJack1
19 Feb 2009, 12:35 AM
Mybe I never have these problems because I am running things from working copies, all under my apache webroot, and not from the SVN virtual file system itself.


Thats it - your files are served from usual file system.

moegal
28 Feb 2009, 11:24 AM
http://extjs-ux.org does not seem to work.

Thanks, Marty

SamuraiJack1
1 Mar 2009, 12:56 AM
DNS problem, will be resolved soon

jfvwi
14 Mar 2009, 2:08 AM
DNS problem, will be resolved soon

I had been discussing this on another thread and didn't realize this one existed... what do you think is needed to get all of the UX threads under one roof, is it an incentive to put them there, or an active process with a code librarian to comb through the posts and add the code as necessary to the repository and document the stage, the use, and current status?

I looked at your setup - definitely a laudable effort!

SamuraiJack1
14 Mar 2009, 2:42 AM
Hi


... what do you think is needed to get all of the UX threads under one roof

Think we need to close the Ext: User Extensions and Plugins (http://extjs.com/forum/forumdisplay.php?f=21) forum )

And if seriously, we need to establish UX publishing standard, which will include a certain amount of documentation (in jsdoc format), a test suite (or sample page) + an automatically created forum thread.

This will lower the number of extensions, but increase their's quality. This will also stimulate collaboration between authors, because it will be faster to improve already existed extension than write "yet another, already 15th, but still very cool Ext.ux.myCoolWizard".

Though imho, Ext community isnt mature enough yet for this.

mjlecomte
14 Mar 2009, 4:02 AM
My rambling thoughts...

My guess is that creating a ux in the repository is too much effort. People want to just make a post and leave it at that. Some people go through the extra effort of get a ux properly listed, but definitely the minority.

I'd say there needs to be a way for someone to add a ux to the "repository" at different levels.

Level 1 is what it is now. Properly adding the ux to svn, documenting etc.

Level 2 is what needs to be added. Some way for there to be a list of ux's that can be categorized. This level would be something where anyone can add the ux to the list so it can be cataloged, I guess like what you're saying a "librarian". But it shouldn't be put upon one user. Perhaps anyone can be a librarian, like a wiki. If there are problems later, then access can be changed to project members, moderators, or whatever.

A few people have essentially taken a level 2 ux and upgraded it to a level 1 ux by "publishing it". This takes some time because the publisher doesn't know the ux as well as the author of course.

The list I'm talking about is missing anyway. I'd like to be able to go to the ux repository and filter a grid view of uxs by component for example.

If you're coming into this with some energy, that would be my suggestion for re-energizing the ux repository. Having everything in js doc is kind of nice, but I think what is really needed is a list of uxs. There may be multiple uxs for a grid, so trying to fit them all into one tree view is difficult. Even navigating the tree now is problematic with the few ux's there are. You'd have to know to look to find a grid filter ux, as an example.

Really, my vision would be to have the "master list" as the ux repository home page. The list would show all extensions and have it be in a filterable view. Once you find a ux you want you should be able to click a link to go to the examples/code/docs/forum thread for that ux...so essentially separate docs for every ux, not one master ux doc.


name author component description code demo docs status

Those are some of the headings I can think of that would be of interest off top of my head. I can see use for other headings to rate the ux, etc. Another field for type (plugin or extension). Another field for license.

Of course add a search field also, so someone can type in a keyword to filter all fields.

This doesn't seem to complex, one grid on the client, a couple database tables on the backend? I'd say restrict delete rights to a moderator.

jerrybrown5
14 Mar 2009, 4:04 AM
Hi

Think we need to close the Ext: User Extensions and Plugins (http://extjs.com/forum/forumdisplay.php?f=21) forum )

And if seriously, we need to establish UX publishing standard, which will include a certain amount of documentation (in jsdoc format), a test suite (or sample page) + an automatically created forum thread.

This will lower the number of extensions, but increase their's quality. This will also stimulate collaboration between authors, because it will be faster to improve already existed extension than write "yet another, already 15th, but still very cool Ext.ux.myCoolWizard".



I hate to be party ruiner but this would also involve:
* Standardizing licenses
* Removing individual ownership of modules, which would facilitate module improvement
* Complete support of the Ext management which is unlikely
* Standard of test case creation which can be run through Selenium
* Creation and Maintenance of Automatic testing through a continuous integration server and Selenium
* And, nearly a full time effort just to moderate the submissions.

Translation: it is not going to happen. However, I like mjlecomte's grid idea.

Regards,
Jerry

mjlecomte
14 Mar 2009, 4:14 AM
Yeah, to me, it's painfully obvious that making it more difficult to publish is not what's needed right now. Once you get a decent code base then you can filter out the weeds. But those weeds would be self filtering I think via a "rating" or "downloads" (count) etc.

In the spirit of this idea: http://extjs.com/forum/showthread.php?p=302782#post302782
I'd say the "type" column would be plugin/extension/example

People could just post some examples if they want.

Saki's initiative has merit but I think that approach is also too difficult to publish.

SamuraiJack1
14 Mar 2009, 4:28 AM
* Standardizing licenses
* Removing individual ownership of modules, which would facilitate module improvement
* Complete support of the Ext management which is unlikely
* Standard of test case creation which can be run through Selenium
* Creation and Maintenance of Automatic testing through a continuous integration server and Selenium
* And, nearly a full time effort just to moderate the submissions.


Fully agreed:

Though imho, Ext community isnt mature enough yet for this.

SamuraiJack1
14 Mar 2009, 4:46 AM
I'll specify a bit, that under "maturity" I mean the ability to collaborate.

The whole current implementation of "central ux repo" took just 2 days of coding from me.

Another couple of days took deployment (I was newbie with Linux)

If someone agreed to host and deploy the application I'd be able to devote 4 days of coding for the system.

Meanwhile everyone can only speak, noone wants to contribute.

So the problem is not in the complexity of all those problems:

* Standardizing licenses
* Removing individual ownership of modules, which would facilitate module improvement
* Complete support of the Ext management which is unlikely
* Standard of test case creation which can be run through Selenium
* Creation and Maintenance of Automatic testing through a continuous integration server and Selenium
* And, nearly a full time effort just to moderate the submissions. but in the community

@mjlecomte
Think your idea can be implemented as another "displaying mode" for the current system.

It will be a flat list instead of tree or another type of tree. This mode will display all ux's in the system and the "docs" view - only ux's with proper jsdoc documentation.

jsakalos
14 Mar 2009, 5:19 AM
Saki's initiative has merit but I think that approach is also too difficult to publish.

Yes and it is intentional. See: http://extjs.com/forum/showthread.php?p=303132#post303132

mjlecomte
14 Mar 2009, 5:50 AM
IMHO:

The random Freddy Freeloader user will come looking for some free code. Freddy Freeloader is thinking, I want to do X, I wonder if someone has an example or extension for it. I don't think Sammy Freeloader requires the free code they are looking for have proper documentation.

Freddy Freeloader currently has to sift through an extension thread, examples thread, Saki's site, the ux site, the extensions section of the wiki, etc.

Dudley has put together an example/extension. Dudley figures he'll share it, why not. The typical Dudley will come to the forums and post a thread and attach the code.

Then enter Libby Librarian. Libby sees the mess, thinks there's a better way. If there were a list somewhere Libby might add to the list an extension/example Libby came across. That's not possible right now.

At the moment only Dudley can go through a registration / moderation process to get found/legacy code added to one of these systems. Saki's site and the current repository impose requirements for code format, etc.

Is there merit to the requirements? Sure. Is it necessary? I'd say no. The grid filter extension ambience put together is proof of this. It is hugely popular and had no documentation whatsoever. Was there an example? no.

The ux repository has been in existence long enough to show that the procedure to get code listed in the system is too difficult. IMHO, it's not just creating a different 'view' of what's there. There needs to be an easier way to add to the system.

The grid view I indicated had a column / field for "docs". If people require docs they just need to filter the view for those that don't have docs.

The grid view can have a field for "moderated" or "approved". A moderator can check if the submitted example/extension meets whatever criteria and "approve" it. People can choose to filter the grid to show only "approved" stuff.

Sorry to ramble, to me it just seems painfully obvious where the immediate shortcoming is.

jsakalos
14 Mar 2009, 5:58 AM
Libby sees the messWouldn't simple "Extensions Directory" with ranking system and with pointers to sources do? I could even envision a grid with name, download, rank, docs, etc. where authors would "publish" only pointers in a couple of seconds.

If such existed I would be first who would list extensions there.

jfvwi
14 Mar 2009, 6:44 AM
If someone agreed to host and deploy the application I'd be able to devote 4 days of coding for the system.



SamuraiJack - I'll host and deploy it - no problem... I think we really need to do this since I'm sure we all spend hours searching through the forum only to come up with examples or code that works in 1.0...

Let me know - I have an open server ready to roll - just have to re-init it.

As far as coding it, it sounds simple enough, I can do it if you don't have the time - but I have some stuff in front of it that I need to get done first...

jsakalos
14 Mar 2009, 6:57 AM
This coin has 2 sides: extensions users and extensions authors. For the whole project to be successful both sides must be considered. I'm on the authors side and publishing my extensions here would only add maintenance time to my already crazy schedule.

jfvwi
14 Mar 2009, 6:59 AM
This coin has 2 sides: extensions users and extensions authors. For the whole project to be successful both sides must be considered. I'm on the authors side and publishing my extensions here would only add maintenance time to my already crazy schedule.

What if you only had to register it - and add the pointer to the site?

We can always have a code librarian as well comb the forum and email the authors to get the latest code, I could always construct an automated system where you would email the latest code and it would post it automatically?

jsakalos
14 Mar 2009, 7:05 AM
I've already posted (http://extjs.com/forum/showthread.php?p=303138#post303138) what's my idea.

Most advanced developers already have their servers, sites, svn repositories, deployment systems, documentation, maybe also bug tracking systems. If you want them to drop all this and use another there must be very, very, very good reason to do that.

On the other hand, if you tell them: "Please, post pointers, links to your site, download, docs, etc" that is no problem. Filling one form? Peanuts...

jfvwi
14 Mar 2009, 7:13 AM
I've already posted (http://extjs.com/forum/showthread.php?p=303138#post303138) what's my idea.

Most advanced developers already have their servers, sites, svn repositories, deployment systems, documentation, maybe also bug tracking systems. If you want them to drop all this and use another there must be very, very, very good reason to do that.

On the other hand, if you tell them: "Please, post pointers, links to your site, download, docs, etc" that is no problem. Filling one form? Peanuts...

Yes, that's exactly what I mean...

jsakalos
14 Mar 2009, 7:17 AM
OK, where is the link to list my extensions at? ;)

... kidding, I know it doesn't exist yet but you have my full agreement on creating one ...

SamuraiJack1
14 Mar 2009, 8:28 AM
@jfvwi (http://extjs.com/forum/member.php?u=45581) - well, I already moved it to separate server, thanks for suggestion anyway.

Well, how about to start a development of a new specification for repository?

Let me summarize the currently available ideas of a workflow:


UXRepo spec draft

1) Author registers in the system
Imho its a must - anonymous ux submitting is evil.
Author will receive the svn account - but he can just ignore it if he wants.


2) Author register the extension
After registering the author will receive a fixed namespace for his ux - no one will be able to register the ux with the same name.

During registration, author can choose - how he would like to specify the metadata for his ux

2.1) "Take from jsdoc tags" - the system will look for ux sources in the author's svn account, process it via jsdoc-tk-ext (or probably ext-doc) and will extract all the needed info like, license, example link, forum thread link etc

2.2) Author can fill in all the info manually, via the big form with fields:


name author component description code demo docs status

Plus

I could even envision a grid with name, download, rank, docs, etc. where authors would "publish" only pointers in a couple of seconds.

In the both 2.1) and 2.2) the info will be stored in the same database


3) User can search the full repo.

Probably here should be implemented the tags cloud system - it works better than directory based system.

4) User can view the repo in the "jsdoc view mode" - will be shown the ux's with proper docs (even if they are not stored in the author's svn account - system will download the ux from "download link")

5) User can rank the ux.

Wouldn't simple "Extensions Directory" with ranking system and with pointers to sources do?

Correct me if I've missed something.

P.S. Complex ux can consists from several files - so imho, we need to agreed to a packaging standard somehow - surely it will be optional for simple 1-file ux's

jfvwi
14 Mar 2009, 9:02 AM
@jfvwi (http://extjs.com/forum/member.php?u=45581) - well, I already moved it to separate server, thanks for suggestion anyway.



Ok, I'm thinking you asked for someone to host the application in the last post. I init'd the server and have it ready if you need it.

As far as coding, I'm not going to duplicate effort, but if there's something I can do to help let me know, I'd definitely like to see this get done, and am more than happy to help.

On single versus multiple files, I would assume that the release would be a zip or some other compressed archive anyway so that shouldn't be an issue.

SamuraiJack1
14 Mar 2009, 9:38 AM
As far as coding, I'm not going to duplicate effort, but if there's something I can do to help let me know, I'd definitely like to see this get done, and am more than happy to help.

Thats great! Actually the server side of the system is quite simple - the most of work needs to be done on client, so there will be many chances to contribute, if the project will be "resurrected".

But to "resurrect" it, we need to reach the consensus on how it should work - so the authors will actually use it (notably established Ext persons, like Saki)

jsakalos
14 Mar 2009, 1:04 PM
If we really want success we need to do it this way:

1. Clearly formulate purpose of the project for both users and authors.
2. Repeat point 1 until we get agreement of many users and key authors.
3. Write specification of functionality and look.
4. Code it.
5. Get feedback from users and authors and improve it.

SamuraiJack1
14 Mar 2009, 1:28 PM
Well, we are already on the 5fth step and starting a new iteration.

The feedback from authors:
- difficult to publish

The feedback from users:
- great thing

The purposes are still the same:


it solves the current problems with the user extensions, which are:
the dispersion of ux's through the forum (users have to bookmark every extension they use)
the different quality of documentation (up to general description only)
the complexity of updating the ux's for users (need to find bookmark, read the forum thread to find latest version, find download link, etc..)
the complexity of creating demos for authors (need to have own hosting)

jsakalos
14 Mar 2009, 1:42 PM
Are you sure the purpose should stay same? Have you got full support of that purpose from both sides?

jsakalos
14 Mar 2009, 1:47 PM
As a side note: The purpose cannot be formulated as "it solves the current problems..." Whose problems?

The formulation must give it life, a long standing goal that both users and authors want.

SamuraiJack1
14 Mar 2009, 2:11 PM
@Saki As I understand, you support the idea in general, though you have a somewhat different vision on it. Can you please formulate the purposes how you see them?

jsakalos
14 Mar 2009, 2:21 PM
Purpose: To provide reliable database of Ext extensions and plugins with nice, easy to use and user friendly interface where authors can easily publish pointers to their works, users can easily find them and rank (thumb up or down) them.

jerrybrown5
14 Mar 2009, 6:41 PM
Until we have the 'perfect' solution, lets be happy with the best solution which (up until this point) IMHO is Saki's examples. The Ext-ux docs has become a bit disorganized with more submissions and as all know usability is king.

Saki, if you want, you can place the controls/examples that I released in the ext-ux repository also in your examples so long as you don't put a donate button on those pages. I'm still hoping for something better but... you know how that goes.

That includes:
Ext.ux.Sound
Ext.ux.layout.Carousel
Ext.ux.layout.Template

Regards,
Jerry

jsakalos
14 Mar 2009, 6:50 PM
Hmmm, the examples are mainly meant to show good coding practices and examples of usage of core Ext, however, I have put some of my extensions there myself for the purpose of demonstrating their usage.

I think that we should wait a couple of days to see where this new initiative will lead us (my vision is quite clear, I believe it could work and I'd like to have it) and if we're getting nowhere then we'll chat (skype is best) the possibilities. OK?

jsakalos
14 Mar 2009, 6:59 PM
Oh, I've almost forgotten to thank you for your high opinion of my examples.

So, thank you, Jerry.

:) :) :)

jerrybrown5
14 Mar 2009, 7:29 PM
Oh, I've almost forgotten to thank you for your high opinion of my examples.

So, thank you, Jerry.

:) :) :)

Saki,
They speak for themselves. They are clear, concise and informative. Your site is reliable plus with very little effort any programmer can quickly drill down to the meat and potatoes. Any other Ux solution needs to be at least as usable. This will be the challenge.

Personally, I think the grid with feedback/commenting system holds the most promise but I also think that it will require a lot of work to make it where it will need to be from the component programmer and user perspectives. If this can't happen, then I think Saki's simple but very workable solution is the way to go.

Regards,
Jerry

mjlecomte
15 Mar 2009, 3:46 AM
Assuming the grid / list is agreeable to those that are going to contribute...

For this to go anywhere the entry into the list needs to be open, not just limited to the author. This is obvious based on what has happened to date with ux repo.

I suggest whomever is behind this effort PM me with your email address so we can take this discussion offline. If you have skype include that also, but I doubt we'd get a consensus on shared time.

jsakalos
15 Mar 2009, 4:01 AM
If we really want success we need to do it this way:

1. Clearly formulate purpose of the project for both users and authors.
2. Repeat point 1 until we get agreement of many users and key authors.
3. Write specification of functionality and look.
4. Code it.
5. Get feedback from users and authors and improve it.

I still think that we should do it the above way. I have done 1., now we should start new votable thread and get agreement of users and key authors on the purpose. Team can work toward a common goal only if 1. team knows the goal and 2. team agrees with the goal.

SamuraiJack1
15 Mar 2009, 6:13 AM
I suggest whomever is behind this effort PM me with your email address so we can take this discussion offline. If you have skype include that also, but I doubt we'd get a consensus on shared time.

+1
PM'ed to you.

Joe
24 Mar 2009, 5:17 AM
Thank you for this ux repository. I registered as an author and uploaded / registered a new component along with some demos. How easy to keep up to date! Was a bit hard to get started but once I figured out how it all worked and got the registration of the ux done - everything else was a cake walk.

Really nice to see a place where ux components can be loaded, documented and kept up to date by the authors. The way the system automatically updates your docs based on your comments (like ExtJS does) is just plain killer. The site is light years away from posting a forum entry and keeping it up to date.

I think a rating system sounds good - or even some type of process to pass in order to make it to "semi-official" or "solid" status. A link from the code back to a forum thread where comments can be posted works pretty good now as a "rating system" if nothing else can be provided in that respect.

The ux control names seems to be all over the map. I had a time trying to figure out the best name for my control. Even though it is not "Tree-Like", it is based on the tree, so I put it into the Ext.ux.tree area - maybe not the best but no real direction here.

BTW: My component is the Ext.ux.tree.SelectionList. Please let me know if there are any issues with my first contribution to the ux world. I'll remove it .. if it is noise .. let me know.

Mainly, just wanted to say thank you for putting the great ux site together and provide some input from a first time author into the repository.

SamuraiJack1
24 Mar 2009, 7:58 AM
Thank you for this ux repository. I registered as an author and uploaded / registered a new component along with some demos. How easy to keep up to date! Was a bit hard to get started but once I figured out how it all worked and got the registration of the ux done - everything else was a cake walk.

Really nice to see a place where ux components can be loaded, documented and kept up to date by the authors. The way the system automatically updates your docs based on your comments (like ExtJS does) is just plain killer. The site is light years away from posting a forum entry and keeping it up to date.

I think a rating system sounds good - or even some type of process to pass in order to make it to "semi-official" or "solid" status. A link from the code back to a forum thread where comments can be posted works pretty good now as a "rating system" if nothing else can be provided in that respect.

The ux control names seems to be all over the map. I had a time trying to figure out the best name for my control. Even though it is not "Tree-Like", it is based on the tree, so I put it into the Ext.ux.tree area - maybe not the best but no real direction here.

BTW: My component is the Ext.ux.tree.SelectionList. Please let me know if there are any issues with my first contribution to the ux world. I'll remove it .. if it is noise .. let me know.

Mainly, just wanted to say thank you for putting the great ux site together and provide some input from a first time author into the repository.

Hey,

My congratulations with 1st published ux! Its not a noise (don't remove it!) - its your contribution to the community and I'm really glad to see it published properly - with respect to the user. Hope the community in turn will provide many ready-to-use components for you.

Thanks for overall positive feedback - the project is still in the 'early alpha' stage, almost without any user interface. I have plans to resurrect it soon - if the authors will show the demand for that. For now you are the notable exception..

Regards, Nickolay

p.s. The only small issue with contribution is that you need to add mime-type to html files (the 5th section in manual (http://extjs-ux.org/twiki/bin/view/Main/UxRegistration))

Joe
24 Mar 2009, 9:25 AM
The html files mime-types are updated -thanks.

Again - thanks for a killer site. Doing this helped me finally see how the SVN client really works and how to update the code comments for auto-docs. I am still working on updating the docs to have better details, etc. Just wanted to get the post / link up.

This project was of GREAT benefit to learning SVN and commenting for javadoc - on top of being a great tool.

lkasdorf
24 Mar 2009, 7:31 PM
I'm off in the weeds here. I have been trying for the last hour to figure out how to get Ext.ux.MessageWindow so I can play with it.

I have tortoiseSVN installed. Now what do I enter for the repository URL? If I have to check out the entire ux repository, that would be ok too.

And if this info is somewhere I should have seen it, please let me know that as well.

And I agree that this looks like an excellent way to organize user extensions, and I love the docs done in the same manner as the extjs docs.

Thanks!

lkasdorf
24 Mar 2009, 7:35 PM
I missed the wording at the bottom of the first post- sorry.

Joe
25 Mar 2009, 7:29 AM
My test system has the ExtJS 2.2.1 "out of box" loaded in the ext21 directory. I use this version to test my ux controls and examples before pushing them up.

Yesterday I pushed up a new example for the Ext.ux.tree.SelectionList widget and hit an error that did not surface in the test system. I debugged and found that using the combo.getStore() method was not working but when I changed to combo.store it all worked fine on the server as well.

Should I be using another version of ExtJS in my test system for ux components being pushed to the UX Repository?

Here is a link to example in question (now using store, so no error)
http://extjs-ux.org/repo/authors/JosephFrancis/trunk/Ext/ux/tree/examples/SelectionListDemoInWindow.html

SamuraiJack1
25 Mar 2009, 8:25 AM
Just uploaded 2.2.1 version as /ext221, so you can switch to it

Joe
25 Mar 2009, 9:56 AM
I updated my local environment to /ext221 and pushed up the changes - all works fine.

I kept the code in the example as it was, so it will work for developers that are still on that version. That code is just in the demo anyway, not part of the control.

Thanks for adding the library so that 221 can be used in the demos :).

Joe
25 Mar 2009, 5:57 PM
I updated some files and examples and when I clicked the link for the .js file - it looked like it was an HTML file - even though there was no mime-type specified.

I updated the mime-type to plain/text and it started acting normal.

Is this the correction action?

Have you seen this / do you want an example (I can try to recreate).

dawesi
6 Apr 2009, 8:31 PM
I've already posted (http://extjs.com/forum/showthread.php?p=303138#post303138) what's my idea.

How about an air app that lists the extensions and docs wherever they are? Saki's idea... I'm whipping up an air app to do such. (extforge.org)

jsakalos
7 Apr 2009, 1:37 AM
Would it be multiplatform then? Linux, Mac, Win?

Arno.Nyhm
7 Apr 2009, 6:05 AM
How about an air app

-1

i think a ext "application" would be better then an special application where you need to download air is not good. i think all can be done as a webpage so we dont need it to be as air

dawesi
9 Apr 2009, 3:53 AM
How about like the docs:

1) Website that uses extjs
2) Air app so you can sync and go (win/osx/linux)

All built with the same extjs-based engine.

dawesi
9 Apr 2009, 3:56 AM
also then if you want to roll your own you can get an api-key and roll your own...

also you could have a flag that marks the ux or theme as 'certified' by one of a group of repository moderators.. and then the moderators could give a ranking based on personal oppinion.

mjlecomte
20 Apr 2009, 2:51 PM
If it's not up already, could you post Ext 3 for the repo? Maybe you could update the first post this thread with the links to various Ext versions?

SamuraiJack1
21 Apr 2009, 12:37 AM
Sure, uploaded to /ext3rc1

Also some updates in 1st post and ux registration manual:
http://extjs-ux.org/twiki/bin/view/Main/UxRegistration

SamuraiJack1
11 May 2009, 7:56 AM
Update:

Was added an alternative documentation view - generated with ext-doc (http://ext-doc.org/) tool.
Its available under:

http://extjs-ux.org/ext-docs/

New view also contain docs for Ext itself (3rc1.1), so you can insert links to native Ext classes, properties, events etc.

Please refer to official Ext3 sources for markup examples - they are slightly different from jsdoc-tk-ext format. Notably, @class and @extends tags are always expected first, followed with the general description of the class.

For more info about ext-doc, please refer this thread (http://extjs.com/forum/showthread.php?t=55214).

jsdoc-tk-ext documentation is still available under:
http://extjs-ux.org/docs

Stripeman
7 Jun 2009, 11:13 PM
Down again ?

SamuraiJack1
8 Jun 2009, 3:47 AM
Nope, works for me.

zombeerose
14 Aug 2009, 8:08 AM
Is the site down?

SamuraiJack1
14 Aug 2009, 8:26 AM
Seems so.. Can't access even my hosting account, looks like my hosting provider have connectivity issues..

tarini
21 Aug 2009, 6:58 AM
server is up :)

SamuraiJack1
21 Aug 2009, 7:07 AM
Yea, sorry for the inconvenience )

renku
17 Feb 2010, 7:39 AM
Apparently the registration and login doesn't work with Opera.

Well, the registration actually works, but it just didn't gave any feedback that it succeeded, so I managed to register several accounts :(

SamuraiJack1
17 Feb 2010, 7:54 AM
This project will not receive any updates, because it seems it will be superseded by ExtJS Marketplace (whatever it will be).

You may take a look at http://openjsan.org

Introductional materials:
http://openjsan.org/documentation/dists.html
http://search.cpan.org/dist/Module-JSAN/lib/Module/JSAN.pm

renku
17 Feb 2010, 12:18 PM
Damn! And I thought I had finally found a definitive source for ExtJS extensions.

So, do I understand correctly, that currently there is no central ux repository? (This JSAN-thing contained only few ext-related things, and "ExtJS Marketplace" is just an idea.)

Or is there anything that's better than digging in the forums?

SamuraiJack1
17 Feb 2010, 11:45 PM
Well, this project is a central ux repository (alpha version :) ). It works well (till the certain degree), but the development was stalled..

Yes, seems the only way will be to dig the forum..