unknownworlds / decoda Goto Github PK

View Code? Open in Web Editor NEW

892.0 127.0 265.0 113.79 MB

Decoda Lua IDE and debugger

License: GNU General Public License v3.0

Shell 0.55% TeX 0.11% C 27.70% C++ 71.22% Python 0.06% Objective-C 0.25% CSS 0.01% Slash 0.11% Lua 0.01%

decoda's Introduction

Decoda Source Code
==================================

BUILDING
========

Decoda is built from premake4 project files. premake4 can be downloaded from
http://industriousone.com/premake/download

Decoda has only been tested with the vs2013 target, however it may be possible
to compile Decoda with older versions. It is not currently possible to build
Decoda as a 64-bit executable or a non-Windows application.

LICENSE
=======

See COPYING.txt for the GNU GENERAL PUBLIC LICENSE

EXCLUDED CODE: The code described below and contained in the Decoda Source Code
release is not part of the Program covered by the GPL and is expressly excluded
from its terms. You are solely responsible for obtaining from the copyright
holder a license for such code and complying with the applicable license terms.

Lua library
---------------------------------------------------------------------------
libs/lua/*

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

wxWidgets and wxScintilla libraries
---------------------------------------------------------------------------
libs/wxWidgets/*
libs/wxScintilla/*

WXWINDOWS LIBRARY LICENCE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

This library is free software; you can redistribute it and/or modify it
under the terms of the GNU Library General Public Licence as published by
the Free Software Foundation; either version 2 of the Licence, or (at
your option) any later version.

This library is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library
General Public Licence for more details.

You should have received a copy of the GNU Library General Public Licence
along with this software, usually in a file named COPYING.LIB. If not,
write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330,
Boston, MA 02111-1307 USA.

EXCEPTION NOTICE

1. As a special exception, the copyright holders of this library give
permission for additional uses of the text contained in this release of
the library as licenced under the wxWindows Library Licence, applying
either version 3.1 of the Licence, or (at your option) any later version of
the Licence as published by the copyright holders of version
3.1 of the Licence document.

2. The exception is that you may use, copy, link, modify and distribute
under your own terms, binary object code versions of works based
on the Library.

3. If you copy code from files distributed under the terms of the GNU
General Public Licence or the GNU Library General Public Licence into a
copy of this library, as this licence permits, the exception does not
apply to the code that you add in this way. To avoid misleading anyone as
to the status of such modified files, you must delete this exception
notice from such code and/or adjust the licensing conditions notice
accordingly.

4. If you write modifications of your own for this library, it is your
choice whether to permit this exception to apply to your modifications.
If you do not wish that, you must delete the exception notice from such
code and/or adjust the licensing conditions notice accordingly.

tinyxml library
---------------------------------------------------------------------------
libs/tinyxml/*

www.sourceforge.net/projects/tinyxml
Original code (2.0 and earlier )copyright (c) 2000-2006 Lee Thomason (www.grinninglizard.com)

This software is provided 'as-is', without any express or implied
warranty. In no event will the authors be held liable for any
damages arising from the use of this software.

Permission is granted to anyone to use this software for any
purpose, including commercial applications, and to alter it and
redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must
not claim that you wrote the original software. If you use this
software in a product, an acknowledgment in the product documentation
would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and
must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source
distribution.

TreeListCtrl
---------------------------------------------------------------------------
src/Frontend/treelistctrl.h
src/Frontend/treelistctrl.cpp

WXWINDOWS LIBRARY LICENCE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

EXCEPTION NOTICE

2. The exception is that you may use, copy, link, modify and distribute
under your own terms, binary object code versions of works based
on the Library.

decoda's People

Contributors

Stargazers

Watchers

Forkers

losinggeneration seemsindie camron asraniel bussiere gnucode2012 luadist cgiogkarakis gitlisted fsfod eisbaer66 sulmone wangray86 syntheticpp ipublue babyphenix kerlw akof1314 alexhayton jakerr dev-life dreamfrog ohkuy xuxiandi ronald132 sharpglasses chinshou wtmmac academician guolisen dantheman1 fluffyfreak joeriedel whoo24 kmry hellodudu radent odie jimmeny sanaahamel myownclone pakoito madmaxoft rawbug teile longloo kerasking x-strong zhangxinnan imakid qyqx umisama lxjames groov0v mattholley lucifer1989 tsingpan jmcdermo mooosu stlnkm smallkot autious alexkordic shooker2012 blueantst ag0ran cdrr useada qq260327056 mihaisebea benoit-germain tgame rastline littlesome glycerine qiuleiwang ttg-bherrera sxzhou isin yamomota cubemoon aesteris lowsar aressky gezidan daweibalong dcourtois sundiyone ihad xiedantibu fastbird zgpxgame xubingyue kerogi zhuzhonghua bysea51 viruscamp somasekhar44 luiseduardohdbackup mettra

decoda's Issues

Decoda does not handle Lua files encoding UTF-8 or UTF-16 properly

There are no option for changing the Lua files encoding. Decoda does not handle UTF-8 or UTF-16. It only supports the locale in non-Unicode characters only.

Decoda should handle the UTF-8 or UTF-16 properly.

Version 1.17 (Build 1035) Beta 1 Crash

Last beta crashes on any Windows without Visual Studio 2013.
(checked on Windows 7 and 8. After click on the link Decoda crashes).

Problem resolved after replacing msvcp120.dll and msvcr120.dll from redist VS2013 folder.

premake4 failed on Linux

premake4.lua:9: attempt to call global 'vpaths' (a nil value)

using http://software.opensuse.org/package/premake4

and

Lua 5.1.5  Copyright (C) 1994-2012 Lua.org, PUC-Rio

the debug version of Decoda can't be launched.

the debug version of Decoda can't be launched in my computer,my os is windows 7, IDE is vc++2005.
I used the permake4 ,version 4.4-beta5 and the following commands to make the project:

premake4 --os=windows --platform=x32,vs2005

then used the VC++2005 open the project, build the solution and start the debugging,
the release is ok for launching. but the debug is not.

the message as below:
Unable to start program
'e:\xxx\bin\debug\Decoda.exe'
this application has failed to start because the application configuration is incorrect .review the manifest file for possible errors,reinstalling the application may fix this problem, for more details ,please see the application event log'

Does anybody know what is wrong in it ?

Cannot open two different lua files of the same name in Decoda

So we have two files called Constructor.lua in two different directories. They are both different files but they're named the same. I opened one and it shows up fine in Decoda, I try to open the other and it doesn't open. It just goes to the currently opened file of the same name.

Why the software history was not kept?

Hi there,

I'm a researcher studying software evolution. As part of my current research, I'm studying the implications of open-sourcing a proprietary software, for instance, if the project succeed in attracting newcomers. However, I observed that some projects, like decoda, deleted their software history.

5eb2b94

Knowing that software history is indispensable for developers (e.g., developers need to refer to history several times a day), I would like to ask decoda developers the following four brief questions:

Why did you decide to not keep the software history?
Do the core developers faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
Do the newcomers faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
How does the lack of history impacted on software evolution? Does it placed any burden in understanding and evolving the software?

Thanks in advance for your collaboration,

Gustavo Pinto, PhD
http://www.gustavopinto.org

Crash when symbol name length from C stack > 256

in DebugBackend.cpp line 3161:

sprintf(stack[i].name, "%s", symbol->Name);

should changed to:

_snprintf(stack[i].name, 256, "%s", symbol->Name);

When Lua 5.2 support?

When Lua 5.2 support?
I think many people want this.

CRLF vs LF in .deproj files

When checking project files in to git, the git on windows expects all text files to have CRLF line ends; the .deproj files break this, causing weird git behavior for these files.

Decoda should either use CRLF on windows, or provide an option to set whether to use CRLF or LF.

Compilation fails on Linux

premake4 --version
premake4 (Premake Build Script Generator) 4.4-beta4
premake4 gmake
cd build
make

==== Building Shared (debug) ====
Creating ../bin/debug
Creating obj/Debug/Shared
StlUtility.cpp
CriticalSection.cpp
In file included from ../src/Shared/CriticalSection.cpp:23:0:
../src/Shared/CriticalSection.h:26:21: fatal error: windows.h: file not found
compilation terminated.
make[1]: *** [obj/Debug/Shared/CriticalSection.o] Fehler 1
make: *** [Shared] Fehler 2

installers?

anyone thinking about Linux or Mac installers for the future?

MacOS X port?

Dear unknownworlds' devs

I'm drooling over decoda -- I'm using lua quite a bit, and the lack of real-life dev tools is a major pain.

Do you know how hard it would be to port Decoda to OS X, please?
Cheers.

Focus lost when switching tabs

When switching between tabs, either by using Ctrl+Tab, or by mouse, the editor window loses focus, making it necessary to click inside the editor with the mouse. This is especially bothersome when there's text selected in the window and I want to interact with it, because clicking to gain focus will cancel the selection. Also, middle-click doesn't make the editor gain focus, if it is lost in this way.

application crash when using luajit

Hi,
I found that when the application built by luajit is always crash when I get the information of some variable in Decoda. But when I replace luajit back to lua to build the application, it never happen.
It also happened when I set jit.off().
Could you help me on this?
Thanks a lot

Regards,
Cong Ling

No activity from project owner for several months

Hi,

It's been several months now that bugfixes and other improvements have been proposed, without anything done about them.

I can understand that you may not have the time to manage Decoda maintenance, but in that case maybe it would be a good idea to open commit rights to other people if another maintainer manifests him/her-self?

If the official branch if left unattended for too long, I fear it will simply die. It would be better if a single endorsed version could be the reference instead of having everyone fork his own.

64-bit build

I've been using Decoda for a while, and one issue has been that debugging will not work for 64-bit processes, requiring me to switch to the 32-bit build of my binary in order to debug Lua code. Now that Decoda is open source, it seems like this should possible to change. I would do it myself, but I'd like to find out what the stumbling blocks are to doing so.

The first road block appears to be that there are several static libraries in the repository, which I presume are built in 32-bit. Presumably, these need to be rebuilt in 64-bit as well - meaning that at the very least, 64-bit builds should be generated and imported. I know what most of them are, so I might be able to do that myself, but not all of them.

Update - What is this? I have no idea.
dbghelp - Microsoft's DbgHelp library. Static 64-bit libs are included with "Debugging Tools for Windows". I noticed though that the size of the 32-bit libs are not the same as the ones I have, so I'm not sure what version they're from.
lua - Obviously Lua 5.1, should be easy - though I imagine it should be upgraded to Lua 5.2.1 at some point.
tinyxml - The only one with a readme, stating it's available here. Again, though, I don't know what version it is.
wxScintilla - Presumably this, but happily sources are included. I noticed that the included version of Scintilla is 1.62 which is very old (from 2004!)
wxWidgets - Also includes source...with a million build targets, all set up for 32-bit. Hopefully it will work as 64-bit, though. Appears to be version 2.8.something?

Now, aside from all that, it's likely there are things in the debugger itself (LuaInject?) that need to change. I haven't delved into the code at all, so I don't know what awaits me.

Thoughts? Is anyone else interested in this who might want to collaborate?

Step by step debugging fails after pcall

Given the following snippet:

local string = require "string"

pcall(error, "some error")

print("hello world")
print("bar")

If I set a breakpoint on line 1, and then go step by step with F10 (Step Over), it works until I try to step over the line with pcall. At that point it just runs until the end.

However, if I step with F11 (Step Into), I can step on each line with no problem.

Tested this with Decoda 1.16 and 1.17 (build 1035 beta 1), it behaves the same in both.