Another drop down terminal extension for GNOME Shell. With tabs. Works on Wayland natively
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 55 | Active |
| 54 | Active |
| 53 | Active |
| 52 | Active |
| 51 | Active |
| 50 | Active |
| 49 | Active |
| 48 | Active |
| 47 | Active |
| 46 | Active |
| 45 | Active |
| 44 | Rejected |
| 43 | Active |
| 42 | Active |
| 41 | Active |
| 40 | Active |
| 39 | Active |
| 38 | Active |
| 37 | Active |
| 36 | Active |
| 35 | Active |
| 34 | Active |
| 33 | Active |
| 32 | Active |
| 31 | Rejected |
| 30 | Inactive |
| 29 | Inactive |
| 28 | Inactive |
| 27 | Inactive |
| 26 | Inactive |
| 25 | Inactive |
| 24 | Inactive |
| 23 | Inactive |
| 22 | Rejected |
| 21 | Inactive |
| 20 | Inactive |
| 19 | Inactive |
| 18 | Inactive |
| 17 | Inactive |
| 16 | Inactive |
| 15 | Inactive |
| 14 | Inactive |
| 13 | Rejected |
| 12 | Inactive |
| 11 | Inactive |
| 10 | Inactive |
| 9 | Inactive |
| 8 | Inactive |
| 7 | Inactive |
| 6 | Rejected |
| 5 | Inactive |
| 4 | Inactive |
| 3 | Rejected |
| 2 | Inactive |
| 1 | Rejected |
Where do you use the application.js file? I'm asking that because you cannot import gtk and gdk in extension.js. and the line 307 (application.js) cannot create objects in global scope (if that's getting imported in extension.js).
application.js is a separate gjs process. Launched by spawn_app() in extension.js It's been this way since the 1st version.
So you should start that file with this: ```js #!/usr/bin/env gjs ``` and if that's a separate application why do you import `misc`to use `getCurrentExtension` (line 24 application.js)? why not getting `Me.path` value from argv?
Well.. Actually, subprocess's entry point is `com.github.amezin.ddterm` script. That one starts with `#!/usr/bin/env gjs` shebang, and imports `application.js`. It also sets up `Me.path`. If you look at `misc.js`, you'll see that it's a tiny "fake" getCurrentExtension() implementation, for the cases where the code is actually not running in extension context. Why do I need the trick with fake `misc.getCurrentExtension()`? Because I want to reuse some code in both application/subprocess and extension. Primarily, it's Preferences dialog, which can be used both by the extension API and loaded by the application directly.
Okay. Maybe moving those app related files to app sub folder can make it easier for the reviewers but you can also leave it like that.
We have a fork of this extension posted for review: https://extensions.gnome.org/review/44843 Seems they just added 44 and they mentioned this in the description: > I have no plans on add/removing features..just thought others may like it.. Are you going to move to 44?
That seems to be just my "master" branch (but a bit outdated). I stuck in an infinite "fix one small thing before release" (initially - because removal of rxjs turned to almost full rewrite, and I didn't want to upload code that will be completely replaced later again). I'm going to upload a release today/tonight.
Ok. Thank you for the clarification.
ddterm