Closed GoogleCodeExporter closed 8 years ago
[deleted comment]
Btw. there's a similar issue with inlineeditor.js which is part of the standard
'ajax' Prado script package required by all active controls - but is actually
used by only one control, by TInPlaceTextBox.
Both ratings.js and inlineeditor.js should be moved to a separate Prado package
- like is the case the slider, tabpanel, and accordion scripts and controls.
Removing 'effects.js' from the standard 'prado' package might be also worth a
try, as obviously that script file is also not actually needed by most
controls, and is included only for convenience there. This change, however,
would require a more thorough check of all controls, as some of them might rely
on 'effects.js' always being included, even though they don't specify that
requirement exactly by a call to
TClientScriptManager::registerPradoScript('effects'). Which should be the
proper way to signal the requirement of inclusion said file in the page.
So controls needing the effects library (like the TAccordion control) should
either have the latter call added to their onPreRender/registerAssets methods,
or 'effects' should be added as a dependency to their appropriate script
package list in packages.php.
Original comment by google...@pcforum.hu
on 8 May 2012 at 8:02
ratings.js and inlineeditor.js have been fixed in r3137; i'll keep this ticket
open to investigate the removal of effects.js from the base scripts
Original comment by ctrlal...@gmail.com
on 10 May 2012 at 9:13
Original comment by ctrlal...@gmail.com
on 25 Jun 2012 at 1:56
It seems like in scriptaculous-adapter.js there's a backward compatibility
Prado.Effect class that relies on scriptaculous' effects class in order to
provide an highlight() function. I'll be glad to trash this entire class and
the dependency at once, but this would be an incompatible change that's not so
good for a 3.2.1 release.
Currently we work on trunk/ for every change, so the better idea would be to
branch off 3.2 and making such changes to trunk/. Anyway, i'm unsure if this
would be a good idea, since we're just a bunch of devs and work on multiple
branches would lead to some overhead work.
So i'm closing this for now, since i'm quite sure that any future work will
need a lot of restructuring and documentation of the javascripts anyway.
Of course if you'd like to join and give an hand..
Original comment by ctrlal...@gmail.com
on 6 Aug 2012 at 5:00
Original issue reported on code.google.com by
google...@pcforum.hu
on 8 May 2012 at 7:09