Aptana function definition popups - aptana

I've noticed that in Aptana 2.0 over 1.5.1 that when typing a php function, you no longer get the popup window showing the function description and it's parameters.
Does anyone know how to get this working again? As I relied on it quite heavily to remember which parameters went where. Open in PHP Manual shortcut Shift+F2 also doesn't work either, so all I can do is open my browser and keep php.net open all the time.
Are either of these features functional? I know that Open delcaration has never worked annoyingly, but I had the function popup in 1.5.1 perfectly.

I use this AutoHotKey script to get the PHP manual in a new browser tab for the selected text in any program:
;Windows+p for Google's I'm feeling lucky "php + selected text"
#p::
oCB := ClipboardAll ; old Clipboard
Sendinput, ^c
GoogleSearch:= "http://www.google.com/search?ie=UTF-8&oe=UTF-8&sourceid=navclient&gfns=1&q=php+" Clipboard
ClipBoard := oCB ; restore ClipBoard
Run, %GoogleSearch%
return
Not ideal, but will get you the PHP manual quickly.

First, go to Window -> Open Perspective -> Other and check you're in the PHP perspective and not the Aptana Web one. I'm not sure if this is necessary, but it can't hurt to try.
Secondly, try right clicking on a PHP file in Aptana's navigator / project explorer and go to Open With -> (Other ->) -> PHP Editor. This will open it with PDT, instead of Aptana's web editor (which has discontinued PHP support).

Related

How do I stop vs code terminal from opening while writing code

I installed live sass compiler in vs code. No matter what I write inside scss file, the terminal keeps opening (watch the attached video for better understanding of the problem) Please suggest a way of running the compiler in background "SILENTLY".. Ah looks like I cannot add video here so I'm adding an image
settings > extensions > live sass compiler > show output window on
Set setting to warning or error. You can also use none if you want.
In the case of Sass live compiler vscode extension
Open Preferences -> Settings
Search Sass live compiler extension from the left column under Extensions category.
Then search Settings: Show Output Window On setting and set it to none from the dropdown.
It will fix your problem.
if you meant to say that your terminal is frequently opening while your coding in your vs code because of live server
install nodejs and npm install -g live-server
then open the windows terminal and cd into the directory of your project files
and then type live-server and hit enter
ik this is not the best answer and there might be a setting on vscode that can help you but this should work too
That is not the terminal, that is the output window, it displays all the extensions and their live logs. See picture. You cannot disable the outputs of the extensions unless you uninstall that specific extension.
If you don't want constant parsing results select a different window like problems or the actual terminal
Actually this was output window which kept opening to log the errors. My problem was solved by unchecking an option which (I am not sure) was under SAAS settings (dont remember exactly and also cant find again but somehow it got solved >>> Sorry I have low memory :)
You can use this instruction:
"liveSassCompile.settings.showOutputWindowOn": "None"
Just copy it to settings.json file of your Extension Live SASS compiler

How to reduce source code modifications in Progress Developer Studio for OpenEdge?

I'm working with OpenEdge Progress-4GL, release 11.6.
As mentioned in this other question, working with the AppBuilder has the drawback that, when saving a *.w file, there are quite some source code modifications.
However, while taking my first steps in working with Progress Developer Studio for OpenEdge (version 4.3), this drawback seems to be there too (not so surprising, because opening the design of the *.w file says something like "launching/running/opening/... AppBuilder").
Is there a version of PDSOE which does not have this drawback? I would like to open a *.w file, save it (without any change) have a minimum amount of source code modifications.
Edit
Oops, I forgot the most important feature: is there a version of PDSOE which is not blocked by the 32K procedure size limit of AppBuilder?
Edit
How can I create/add a new window or smartwindow? When I try to create something new, I get the following menu:
Thanks in advance

Progress Developer Studio for OpenEdge issues syntax error but the same code will not get any syntax error when checking syntax from Progress Editor

PDSOE version 4.5.2, OE 11.7.1 - 64-bit - Win 10 64
I have an Webspeed (.w) opened in my PSDOE.
If I simply right click over this code and choose Check Syntax in the context menu (Ctrl+Shift+C)
it will return me an error from an include file used by this .w regarding the get-cookie():
Syntax Check:
** Unable to understand after -- "GET-COOKIE". (247)
In my .w, I have all the necessary Webspeed include files - including proto.i that will have the forward get-cookie function signature and all that.
So far so good, I could have thought of Propath and all that, but two things make things more complicated now:
If I choose to compile the code instead of checking syntax, it will compile just fine - which tells me that all my include files and propath are correctly configured and all set, a .r is produced
If from PDSOE, with my code still opened, I go in Eclipse \ OpenEdge \ Tool \ Procedure Editor , it will open a Progress Editor with the same code in place right, and from this procedure editor, if I simply right click and check syntax, it will return no errors at all.
I downloaded OE 12.3 and tried the same thing, got the same behavior.
I checked all the propath and it was right (code compiles)
I tried restarting the AVM, no difference
I tried a shared AVM, no difference
I am running out of ideas specially after I got the same issue on 12.3.
Would you happen to have any other idea or could thing of anything else that could explain the check syntax behavior in PDSOE?
Thanks!
So your project configuration sounds o.k.. You should open a call with Progress tech support IMHO.
If your .w file is a mapped web object and not a CGI wrapper, you might have little luck with support for those on OpenEdge 12.3 - as PASOE does not support running them. There's an enhancement request open for votes: https://openedge.ideas.aha.io/ideas/OPENEDGE-I-753?utm_source=idea_comment_mailer&utm_medium=email&utm_campaign=subscribers
On OpenEdge 11.7.1 this should still be supported though.
CGI wrappers should work fine on OpenEdge 12.3 though.

Console isn't showing up when running print() using LOVE2d with atom-editor

Using atom-editor 1.13 with the love-ide package installed to run LOVE2d 10.2 games (windows 7)
Apparently if you create a conf.lua file in the same folder as your main.lua file you can add some configuations to main.lua. So, I've got these lines of code in my conf.lua to show console.
function love.conf(t)
t.console = true
end
But when I go back to my main.lua and type print("ballz"), all I see is a blank LOVE2d game screen with no extra console window. Not really sure if this is because I'm using atom editor or not. Everything seems to be PATH'ed correctly.
On a side note, whenever I run atom using the love-ide package it always tries to install some "dependecy files" like the hyperclick-love package, and the auto-complete-love package. These fail to install because I don't have git installed.. honestly I really don't know what git is, but neither it, hyperclick, or auto-complete seemed like requirements to run my game, so in the spirit of not installing unnecessary things onto my computer I never installed these things... annoying as it is to see this notification always pop up when I start atom. Anyone know if this is contributing to the issue, or know a way to remove these notifications or auto-download-attempts? My LOVE2d code still seems to run without these packages.
Have you set up the terminal emulator in your configuration?
(Windows only) Try using the lovec.exe executable instead of the normal love.exe. The first one attaches to the console that executed the game, the second one ignores it.
Lua has a buffered output, try adding io.stdout:setvbuf('no') to the top of main.lua

Freopen() not working in SDL

I tried using freopen() to redirect the "cout" function to the console, but it doesn't produce the desired effect. Instead of just double clicking on the executable and having the console show it's message, I need to use a command prompt or a batch file, and that's a problem, because I want the user to be able to close the console after the message has been displayed without closing the SDL window. This is supposed to be a console application. I apologize if I am not clear enough.
If using freopen() doesn't work the SDL Console FAQ gives a tutorial on recompiling the SDLmain library that is relatively easy to understand, especially if you already have MSYS and MinGW installed. You can use the resulting SDLmain library instead of your current one and it should work (It did for my project).

Resources