Hi,
I think we should standardize on one or the other syntax.
I like the simplicity of using $() but it would be clearer to always use jQuery(), as many other libraries are using the dollar sign and someone looking at a fragment of our code needs to know immediately which lib is used.
2010/4/10 Marc Delisle marc@infomarc.info:
Hi,
I think we should standardize on one or the other syntax.
I like the simplicity of using $() but it would be clearer to always use jQuery(), as many other libraries are using the dollar sign and someone looking at a fragment of our code needs to know immediately which lib is used.
I believe $() is better - there is no point in using two libraries, so there is no risk of name conflicts. Also, it is easy to check that jQuery is used.
Hi Marc,
to use jQuery() instead of $() may be ok, but you must know, that in jQuery UI and other plug-ins for jQuery there is always used the $(). My personal opinion is to use the $(), cause it's the jQuery default. Perhaps it would help to leave comment before function / jQuery call?
Which other libraries are still used, which are using the $()? I think, other libraries should be ported to jQuery.
Michael.
Am 10.04.2010 13:01, schrieb Marc Delisle:
Hi,
I think we should standardize on one or the other syntax.
I like the simplicity of using $() but it would be clearer to always use jQuery(), as many other libraries are using the dollar sign and someone looking at a fragment of our code needs to know immediately which lib is used.
Michael Keck a écrit :
Hi Marc,
to use jQuery() instead of $() may be ok, but you must know, that in jQuery UI and other plug-ins for jQuery there is always used the $(). My personal opinion is to use the $(), cause it's the jQuery default. Perhaps it would help to leave comment before function / jQuery call?
Hi Michael, yes it would help (if everyone accepts to do it, which I doubt).
Which other libraries are still used, which are using the $()? I think, other libraries should be ported to jQuery.
Porting Mootools calls to jQuery is almost done, I think that only the import progress bar remains to be done. Any volunteer? :)
Michael.
Am 10.04.2010 13:01, schrieb Marc Delisle:
Hi,
I think we should standardize on one or the other syntax.
I like the simplicity of using $() but it would be clearer to always use jQuery(), as many other libraries are using the dollar sign and someone looking at a fragment of our code needs to know immediately which lib is used.
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Marc Delisle a écrit :
Porting Mootools calls to jQuery is almost done, I think that only the import progress bar remains to be done. Any volunteer? :)
See libraries/display_import.lib.php.
Hi Marc,
I'll have a look at this and submit a patch, hopefully tomorrow.
Philip
2010/4/10 Marc Delisle marc@infomarc.info:
Marc Delisle a écrit :
Porting Mootools calls to jQuery is almost done, I think that only the import progress bar remains to be done. Any volunteer? :)
See libraries/display_import.lib.php.
-- Marc Delisle http://infomarc.info
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi,
in jQuery UI there's a widget progressbar ;) Docu: http://docs.jquery.com/UI/Progressbar
Please notice to avoid problems on update progressbar please use follow code (that problem I've with my uploader): $('#your_element .ui-progressbar-value').css({ 'width' : your_progress_var + '%' }); instead of $('#your_element').progressbar( "value" , you_progress ).
Explained: $('your_element').progressbar( "value" , you_progress ) takes to long time and hangs up after to much calls.
I'm writing on an uploader now ... the first test can be seen here: http://michaelkeck.de/projects/jquery/#demo-uploader
Michael
Am 10.04.2010 14:02, schrieb Philip Frank:
Hi Marc,
I'll have a look at this and submit a patch, hopefully tomorrow.
Philip
2010/4/10 Marc Delisle marc@infomarc.info:
Marc Delisle a écrit :
Porting Mootools calls to jQuery is almost done, I think that only the import progress bar remains to be done. Any volunteer? :)
See libraries/display_import.lib.php.
-- Marc Delisle http://infomarc.info
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Michael Keck a écrit :
Hi,
in jQuery UI there's a widget progressbar ;) Docu: http://docs.jquery.com/UI/Progressbar
Please notice to avoid problems on update progressbar please use follow code (that problem I've with my uploader): $('#your_element .ui-progressbar-value').css({ 'width' : your_progress_var + '%' }); instead of $('#your_element').progressbar( "value" , you_progress ).
Explained: $('your_element').progressbar( "value" , you_progress ) takes to long time and hangs up after to much calls.
I'm writing on an uploader now ... the first test can be seen here: http://michaelkeck.de/projects/jquery/#demo-uploader
Michael
Thanks Michael about the jQuery UI progress bar. Please note however that the phpMyAdmin implementation should not depend on Flash to obtain the values. We currently use the PHP extensions APC or uploadprogress.
Hi Marc,
the progress bar is not programmed in flash, it's jQuery ;) But of course it's updated from Flash with an external call.
The Flash is only used as front-end to select and upload files and is only used (displayed) if Flash is installed. If not, the normal file input is used, but without upload progress. This is the point why I'm searching for other alternatives too, but without patching or installing software in php environment. You must know, not all peoples own a root server. And not all ISP give support to do such things ;(
How does the PHP extensions (APC or uploadprogress) work, I've read that PHP must be patched?
PS: I've a root server.
Michael
Am 10.04.2010 14:51, schrieb Marc Delisle:
Michael Keck a écrit :
Hi,
in jQuery UI there's a widget progressbar ;) Docu: http://docs.jquery.com/UI/Progressbar
Please notice to avoid problems on update progressbar please use follow code (that problem I've with my uploader): $('#your_element .ui-progressbar-value').css({ 'width' : your_progress_var + '%' }); instead of $('#your_element').progressbar( "value" , you_progress ).
Explained: $('your_element').progressbar( "value" , you_progress ) takes to long time and hangs up after to much calls.
I'm writing on an uploader now ... the first test can be seen here: http://michaelkeck.de/projects/jquery/#demo-uploader
Michael
Thanks Michael about the jQuery UI progress bar. Please note however that the phpMyAdmin implementation should not depend on Flash to obtain the values. We currently use the PHP extensions APC or uploadprogress.
Hi,
both APC and uploadprogress extensions are available via PECL, so you can install them by simply running "pecl install apc/uploadprogress".
The current solution sends form to an invisible iframe and periodical AJAX request gets current size of uploading file. The information about size and progress of the upload is handled by either APC or uploadprogress. If non of them is available, then there is no progress bar displayed.
Tomas
On Sat, Apr 10, 2010 at 3:21 PM, Michael Keck sfnet@michaelkeck.de wrote:
Hi Marc,
the progress bar is not programmed in flash, it's jQuery ;) But of course it's updated from Flash with an external call.
The Flash is only used as front-end to select and upload files and is only used (displayed) if Flash is installed. If not, the normal file input is used, but without upload progress. This is the point why I'm searching for other alternatives too, but without patching or installing software in php environment. You must know, not all peoples own a root server. And not all ISP give support to do such things ;(
How does the PHP extensions (APC or uploadprogress) work, I've read that PHP must be patched?
PS: I've a root server.
Michael
Am 10.04.2010 14:51, schrieb Marc Delisle:
Michael Keck a écrit :
Hi,
in jQuery UI there's a widget progressbar ;) Docu: http://docs.jquery.com/UI/Progressbar
Please notice to avoid problems on update progressbar please use follow code (that problem I've with my uploader): $('#your_element .ui-progressbar-value').css({ 'width' : your_progress_var + '%' }); instead of $('#your_element').progressbar( "value" , you_progress ).
Explained: $('your_element').progressbar( "value" , you_progress ) takes to long time and hangs up after to much calls.
I'm writing on an uploader now ... the first test can be seen here: http://michaelkeck.de/projects/jquery/#demo-uploader
Michael
Thanks Michael about the jQuery UI progress bar. Please note however that the phpMyAdmin implementation should not depend on Flash to obtain the values. We currently use the PHP extensions APC or uploadprogress.
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Michael Keck a écrit :
Hi Marc,
the progress bar is not programmed in flash, it's jQuery ;) But of course it's updated from Flash with an external call.
The Flash is only used as front-end to select and upload files and is only used (displayed) if Flash is installed. If not, the normal file input is used, but without upload progress. This is the point why I'm searching for other alternatives too, but without patching or installing software in php environment. You must know, not all peoples own a root server. And not all ISP give support to do such things ;(
How does the PHP extensions (APC or uploadprogress) work, I've read that PHP must be patched?
It must not be patched, it just has to have one of these extensions installed. Anyway, the APC extension is very common for opcode caching.
See http://www.phpmyadmin.net/documentation/#faq2_9
PS: I've a root server.
Michael
Okay,
I've noticed. But what is with peoples which can't run / install
APC and uploadprogress extensions are available via PECL, so you can install them by simply running "pecl install apc/uploadprogress".
because they are using a "hosted domain" only or do not have rights to install the above described? Wouldn't it be nice to enable for such people an alternative?
Am 10.04.2010 15:28, schrieb Marc Delisle:
Michael Keck a écrit :
Hi Marc,
the progress bar is not programmed in flash, it's jQuery ;) But of course it's updated from Flash with an external call.
The Flash is only used as front-end to select and upload files and is only used (displayed) if Flash is installed. If not, the normal file input is used, but without upload progress. This is the point why I'm searching for other alternatives too, but without patching or installing software in php environment. You must know, not all peoples own a root server. And not all ISP give support to do such things ;(
How does the PHP extensions (APC or uploadprogress) work, I've read that PHP must be patched?
It must not be patched, it just has to have one of these extensions installed. Anyway, the APC extension is very common for opcode caching.
See http://www.phpmyadmin.net/documentation/#faq2_9
PS: I've a root server.
Michael
Michael Keck a écrit :
Okay,
I've noticed. But what is with peoples which can't run / install
APC and uploadprogress extensions are available via PECL, so you can install them by simply running "pecl install apc/uploadprogress".because they are using a "hosted domain" only or do not have rights to install the above described? Wouldn't it be nice to enable for such people an alternative?
An open source one, yes :)
Am 10.04.2010 16:01, schrieb Marc Delisle:
Michael Keck a écrit :
Okay,
I've noticed. But what is with peoples which can't run / install
APC and uploadprogress extensions are available via PECL, so you can install them by simply running "pecl install apc/uploadprogress".because they are using a "hosted domain" only or do not have rights to install the above described? Wouldn't it be nice to enable for such people an alternative?
An open source one, yes :)
It is programmed as open source. I will contribute the fla-file with all included libraries (as .tgz) and the compiled swf-file. But it's not really finished, why there's no source download at the moment.
Michael Keck a écrit :
Am 10.04.2010 16:01, schrieb Marc Delisle:
Michael Keck a écrit :
Okay,
I've noticed. But what is with peoples which can't run / install
APC and uploadprogress extensions are available via PECL, so you can install them by simply running "pecl install apc/uploadprogress".because they are using a "hosted domain" only or do not have rights to install the above described? Wouldn't it be nice to enable for such people an alternative?
An open source one, yes :)
It is programmed as open source. I will contribute the fla-file with all included libraries (as .tgz) and the compiled swf-file. But it's not really finished, why there's no source download at the moment.
I meant this: if it requires non-open source components, we should discuss it as a team first, as IMO we never took this approach.
Personnally I think that as an open source project, we should set an example by not requiring non-open source elements like Flash.
Am 10.04.2010 16:36, schrieb Marc Delisle:
Michael Keck a écrit :
An open source one, yes :)
It is programmed as open source. I will contribute the fla-file with all included libraries (as .tgz) and the compiled swf-file. But it's not really finished, why there's no source download at the moment.
I meant this: if it requires non-open source components, we should discuss it as a team first, as IMO we never took this approach.
Personnally I think that as an open source project, we should set an example by not requiring non-open source elements like Flash.
okay ;)
2010/4/10 Michael Keck sfnet@michaelkeck.de:
Am 10.04.2010 16:36, schrieb Marc Delisle:
Michael Keck a écrit :
An open source one, yes :)
It is programmed as open source. I will contribute the fla-file with all included libraries (as .tgz) and the compiled swf-file. But it's not really finished, why there's no source download at the moment.
I meant this: if it requires non-open source components, we should discuss it as a team first, as IMO we never took this approach.
Personnally I think that as an open source project, we should set an example by not requiring non-open source elements like Flash.
okay ;)
I don't quite get it... Is the "upload progress bar" the same as the "import progress bar"? I'm willing to spend some time on porting mootools code to jQuery today, but wouldn't want get in the way of what Michael is working on. So, what exactly do these progress bars show?
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Philip Frank a écrit :
I don't quite get it... Is the "upload progress bar" the same as the "import progress bar"? I'm willing to spend some time on porting mootools code to jQuery today, but wouldn't want get in the way of what Michael is working on. So, what exactly do these progress bars show?
Currently it's only used for import progress bar. It's true that we can import directly from the server with some config which is not there by default, but the usual case is importing via upload.
Am 11.04.2010 14:53, schrieb Philip Frank:
I don't quite get it... Is the "upload progress bar" the same as the "import progress bar"? I'm willing to spend some time on porting mootools code to jQuery today, but wouldn't want get in the way of what Michael is working on. So, what exactly do these progress bars show?
Philip,
my explained progressbar was an idea for uploading. I've not done anything for the import progressbar.
If you want porting mootools code to jQuery please still go on.
One tip I've for you with jQuery UI Progressbar: Update the progressbar with $('#your_element').progessbar("value", your_value + "%"); would make problems, cause this call would take to much time. Please use this: $('#your_element .ui-progress-bar-vakue').css({ 'width' : your_value + '%' }); This sets the new width of the progressbar directly and is faster.
Michael
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
2010/4/11 Michael Keck sfnet@michaelkeck.de:
Am 11.04.2010 14:53, schrieb Philip Frank:
I don't quite get it... Is the "upload progress bar" the same as the "import progress bar"? I'm willing to spend some time on porting mootools code to jQuery today, but wouldn't want get in the way of what Michael is working on. So, what exactly do these progress bars show?
Philip,
my explained progressbar was an idea for uploading. I've not done anything for the import progressbar.
If you want porting mootools code to jQuery please still go on.
One tip I've for you with jQuery UI Progressbar: Update the progressbar with $('#your_element').progessbar("value", your_value + "%"); would make problems, cause this call would take to much time. Please use this: $('#your_element .ui-progress-bar-vakue').css({ 'width' : your_value
- '%' });
This sets the new width of the progressbar directly and is faster.
Michael
I dug through the related code, display_import.lib.php, import_status.php and import.php. I'm not sure if I overlooked it, but there is no tracking of progress while running an import. I couldn't get the ajax import to work on the current master, it just silently falls back to an ordinary post.
From looking at the code and porting some to jQuery I figured the
following: A progress bar is displayed if the php extension apc or uploadprogress is installed, but it shows the progress of the file upload, not that of the import, which just happens without intermediate output. So, Michael, what you are doing with Flash is already there, only working when certain server extensions are available.
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Am 11.04.2010 19:42, schrieb Philip Frank:
2010/4/11 Michael Keck sfnet@michaelkeck.de:
Am 11.04.2010 14:53, schrieb Philip Frank:
I don't quite get it... Is the "upload progress bar" the same as the "import progress bar"? I'm willing to spend some time on porting mootools code to jQuery today, but wouldn't want get in the way of what Michael is working on. So, what exactly do these progress bars show?
Philip,
my explained progressbar was an idea for uploading. I've not done anything for the import progressbar.
If you want porting mootools code to jQuery please still go on.
One tip I've for you with jQuery UI Progressbar: Update the progressbar with $('#your_element').progessbar("value", your_value + "%"); would make problems, cause this call would take to much time. Please use this: $('#your_element .ui-progress-bar-vakue').css({ 'width' : your_value
- '%' });
This sets the new width of the progressbar directly and is faster.
Michael
I dug through the related code, display_import.lib.php, import_status.php and import.php. I'm not sure if I overlooked it, but there is no tracking of progress while running an import. I couldn't get the ajax import to work on the current master, it just silently falls back to an ordinary post.
From looking at the code and porting some to jQuery I figured the following: A progress bar is displayed if the php extension apc or uploadprogress is installed, but it shows the progress of the file upload, not that of the import, which just happens without intermediate output.
Okay, I've misunderstood. Cause I was thinking some one has done such thing for importing.
So, Michael, what you are doing with Flash is already there, only working when certain server extensions are available.
The Flash was planned as an alternative uploader if server *has not* apc or uploadprogress installed and was only for uploads. But some peoples don't like flash (not really open source), so I've canceled this idea.
Philip Frank a écrit :
2010/4/11 Michael Keck sfnet@michaelkeck.de:
Am 11.04.2010 14:53, schrieb Philip Frank:
I don't quite get it... Is the "upload progress bar" the same as the "import progress bar"? I'm willing to spend some time on porting mootools code to jQuery today, but wouldn't want get in the way of what Michael is working on. So, what exactly do these progress bars show?
Philip,
my explained progressbar was an idea for uploading. I've not done anything for the import progressbar.
If you want porting mootools code to jQuery please still go on.
One tip I've for you with jQuery UI Progressbar: Update the progressbar with $('#your_element').progessbar("value", your_value + "%"); would make problems, cause this call would take to much time. Please use this: $('#your_element .ui-progress-bar-vakue').css({ 'width' : your_value
- '%' });
This sets the new width of the progressbar directly and is faster.
Michael
I dug through the related code, display_import.lib.php, import_status.php and import.php. I'm not sure if I overlooked it, but there is no tracking of progress while running an import. I couldn't get the ajax import to work on the current master, it just silently falls back to an ordinary post.
Philip, I think it's broken in the current master. If you checkout the QA_3_3 branch you'll see it work.
Breakage might be because of the ongoing conversion to jQuery.
And it's supposed to be a progress bar just for the uploading part of the import.
From looking at the code and porting some to jQuery I figured the
following: A progress bar is displayed if the php extension apc or uploadprogress is installed, but it shows the progress of the file upload, not that of the import, which just happens without intermediate output. So, Michael, what you are doing with Flash is already there, only working when certain server extensions are available.
2010/4/11 Marc Delisle marc@infomarc.info:
Philip Frank a écrit :
2010/4/11 Michael Keck sfnet@michaelkeck.de:
Am 11.04.2010 14:53, schrieb Philip Frank:
I don't quite get it... Is the "upload progress bar" the same as the "import progress bar"? I'm willing to spend some time on porting mootools code to jQuery today, but wouldn't want get in the way of what Michael is working on. So, what exactly do these progress bars show?
Philip,
my explained progressbar was an idea for uploading. I've not done anything for the import progressbar.
If you want porting mootools code to jQuery please still go on.
One tip I've for you with jQuery UI Progressbar: Update the progressbar with $('#your_element').progessbar("value", your_value + "%"); would make problems, cause this call would take to much time. Please use this: $('#your_element .ui-progress-bar-vakue').css({ 'width' : your_value
- '%' });
This sets the new width of the progressbar directly and is faster.
Michael
I dug through the related code, display_import.lib.php, import_status.php and import.php. I'm not sure if I overlooked it, but there is no tracking of progress while running an import. I couldn't get the ajax import to work on the current master, it just silently falls back to an ordinary post.
Philip, I think it's broken in the current master. If you checkout the QA_3_3 branch you'll see it work.
Breakage might be because of the ongoing conversion to jQuery.
And it's supposed to be a progress bar just for the uploading part of the import.
I just submitted a patch for this: https://sourceforge.net/tracker/?func=detail&aid=2986073&group_id=23...
From looking at the code and porting some to jQuery I figured the
following: A progress bar is displayed if the php extension apc or uploadprogress is installed, but it shows the progress of the file upload, not that of the import, which just happens without intermediate output. So, Michael, what you are doing with Flash is already there, only working when certain server extensions are available.
-- Marc Delisle http://infomarc.info
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Marc Delisle a écrit :
Hi,
I think we should standardize on one or the other syntax.
I like the simplicity of using $() but it would be clearer to always use jQuery(), as many other libraries are using the dollar sign and someone looking at a fragment of our code needs to know immediately which lib is used.
So to summarize, Piotr and Michael prefer $(). Someone else wants to voice their preference or arguments?
Le 11 avr. 2010 à 12:12, Marc Delisle a écrit :
Hi,
I think we should standardize on one or the other syntax.
I like the simplicity of using $() but it would be clearer to always use jQuery(), as many other libraries are using the dollar sign and someone looking at a fragment of our code needs to know immediately which lib is used.
So to summarize, Piotr and Michael prefer $(). Someone else wants to voice their preference or arguments?
My voice doesn't count a lot for now, but my opinion would be for $(). It's not like you change your Javascript framework every month, and JQuery is self-sufficient and very-complete (plugins, functions) so I don't see a reason for cumulating different frameworks.
Regards, Edouard.
Edouard SWIAC a écrit :
My voice doesn't count a lot for now, but my opinion would be for $(). It's not like you change your Javascript framework every month, and JQuery is self-sufficient and very-complete (plugins, functions) so I don't see a reason for cumulating different frameworks.
Hi Edouard, every voice counts :)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2010/4/11 Marc Delisle :
Edouard SWIAC a écrit :
My voice doesn't count a lot for now, but my opinion would be for $(). It's not like you change your Javascript framework every month, and JQuery is self-sufficient and very-complete (plugins, functions) so I don't see a reason for cumulating different frameworks.
Hi Edouard, every voice counts :)
I'm undecided on the matter, because I don't know enough about Javascript frameworks and their implementation. But I read some good arguments to go for $() : - - only one framework is (or will be) used (i.e. JQuery) within PMA, so there is no reason for confusion - - it's a common practice to use $().
My 2 cents.
Greets,
Dieter
-- Marc Delisle http://infomarc.info
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
- -- Groetjes,
Dieter Adriaenssens
Le 11 avr. 2010 à 20:23, Dieter Adriaenssens a écrit :
2010/4/11 Marc Delisle :
Edouard SWIAC a écrit :
My voice doesn't count a lot for now, but my opinion would be for $(). It's not like you change your Javascript framework every month, and JQuery is self-sufficient and very-complete (plugins, functions) so I don't see a reason for cumulating different frameworks.
Hi Edouard, every voice counts :)
I'm undecided on the matter, because I don't know enough about Javascript frameworks and their implementation. But I read some good arguments to go for $() :
- only one framework is (or will be) used (i.e. JQuery) within PMA, so
there is no reason for confusion
- it's a common practice to use $().
My 2 cents.
Greets,
Dieter
I know that Prototype and JQuery share the $() notation (had the chance of doing a migration from Prototype to JQuery and well, it hurts). I have a good insight of YUI, and YUI doesn't use (natively) this notation. It's all I know, so I add my 2 cents to yours ;)
Cheers, Edouard
HI, I'm just a new comer to this mail list. Until now i have used $() notation throughout my programs using jQuery. One of the reason for that is, the jQuery plugins for the web editors uses $() notation(Dream weaver) in the codes and therefore its better for me to use the same notation as well. thank you.
On Mon, Apr 12, 2010 at 12:33 AM, Edouard SWIAC edouard.swiac@gmail.comwrote:
Le 11 avr. 2010 à 20:23, Dieter Adriaenssens a écrit :
2010/4/11 Marc Delisle :
Edouard SWIAC a écrit :
My voice doesn't count a lot for now, but my opinion would be for $(). It's not like you change your Javascript framework every month, and JQuery is self-sufficient and very-complete (plugins, functions) so I don't see a reason for cumulating different frameworks.
Hi Edouard, every voice counts :)
I'm undecided on the matter, because I don't know enough about Javascript frameworks and their implementation. But I read some good arguments to go for $() :
- only one framework is (or will be) used (i.e. JQuery) within PMA, so
there is no reason for confusion
- it's a common practice to use $().
My 2 cents.
Greets,
Dieter
I know that Prototype and JQuery share the $() notation (had the chance of doing a migration from Prototype to JQuery and well, it hurts). I have a good insight of YUI, and YUI doesn't use (natively) this notation. It's all I know, so I add my 2 cents to yours ;)
Cheers, Edouard
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Am 11.04.2010 12:12, schrieb Marc Delisle:
Marc Delisle a écrit :
Hi,
I think we should standardize on one or the other syntax.
I like the simplicity of using $() but it would be clearer to always use jQuery(), as many other libraries are using the dollar sign and someone looking at a fragment of our code needs to know immediately which lib is used.
So to summarize, Piotr and Michael prefer $(). Someone else wants to voice their preference or arguments?
+1 $()
Hi
Dne Sun, 11 Apr 2010 06:12:35 -0400 Marc Delisle marc@infomarc.info napsal(a):
Marc Delisle a écrit :
Hi,
I think we should standardize on one or the other syntax.
I like the simplicity of using $() but it would be clearer to always use jQuery(), as many other libraries are using the dollar sign and someone looking at a fragment of our code needs to know immediately which lib is used.
So to summarize, Piotr and Michael prefer $(). Someone else wants to voice their preference or arguments?
I don't have any preference, so $() is fine for me.
-
Dieter Adriaenssens -
Edouard SWIAC -
Marc Delisle -
Michael Keck -
Michal Čihař -
Philip Frank -
Piotr Przybylski -
Sebastian Mendel -
sutharshan balachandren -
Tomas Srnka