Javascript in Weblocks

[Daniel Borchmann]

Hi,

I am currently trying to understand the Javascript code that comes
bundled with weblocks. I have some questions on this (but please keep
in mind that I don't know much about javascript):

- What exactly is scriptaculous good for? Can't we remove at least
unittest.js?
- What is the purpose of dialog.js? I can't find any use in the source
code.
- Can't we remove shortcut.js (as described in
doc/js-backend-abstraction.txt)? It is only used in datagrid.js to
define three keyboard shortcuts which do not seem essential to me (at
least not to make shortcut.js a default dependency).
- Can we upgrade prototype.js to its most recent version?

There is also github.com/html/weblocks-jquery. Would it be a good idea
to integrate that into weblocks proper?

Best,

Daniel

--
Daniel Borchmann http://daniel.kxpq.de
GPG (Mail) 0849 473E 6BF0 B504 DF0B D640 455E 3610 01FF 778F

[o_z]

воскресенье, 4 января 2015 г., 13:11:53 UTC+2 пользователь Daniel Borchmann написал:

Hi,

I am currently trying to understand the Javascript code that comes
bundled with weblocks.  I have some questions on this (but please keep
in mind that I don't know much about javascript):

- What exactly is scriptaculous good for?  Can't we remove at least
  unittest.js?

We should move out all javascript files from Weblocks repository. 

- What is the purpose of dialog.js?  I can't find any use in the source
  code.

Search "show-dialog" through Weblocks code

- Can't we remove shortcut.js (as described in
  doc/js-backend-abstraction.txt)?  It is only used in datagrid.js to
  define three keyboard shortcuts which do not seem essential to me (at
  least not to make shortcut.js a default dependency).

I've removed shortcut.js 

- Can we upgrade prototype.js to its most recent version?

Prototype/Scriptaculous javascript backend should be separated from Weblocks.

It would be better to update prototype.js version then.

There is also github.com/html/weblocks-jquery.  Would it be a good idea
to integrate that into weblocks proper?

Yes, it should be integrated but as backend, without moving to Weblocks repository. 

[Daniel Borchmann]

ghItlhpu' o_z <olex...@gmail.com>:

> We should move out all javascript files from Weblocks repository.

This I hear with joy.

> I've removed shortcut.js

Yay, thanks!

>> There is also github.com/html/weblocks-jquery. Would it be a good idea
>> to integrate that into weblocks proper?
>>
> Yes, it should be integrated but as backend, without moving to Weblocks
> repository.

Do you have any concrete plans on implementing this javascript backend
in weblocks? How do you want to implement the custom javascript
functions weblocks in currently using (like the ones in weblocks.js)?
Are you planning to use parenscript for this, our do you just delegate
to the corresponding functions in the backend then?

I would really love to see javascript backends in weblocks. After all,
using weblocks means to not have to worry about all this webstuff, but
instead write nice websites in Common Lisp directly.