Re: Mobile App STACK4 with a D backend
On Tuesday, 24 December 2013 at 22:52:15 UTC, Martin Krejcirik wrote: On 22.12.2013 14:38, extrawurst wrote: would ask everyone who has access to an android device to test the app and give me feedback about every kind of problem you may encounter! Doesn't work for me on Xperia L. Stuck on black screen with small purple logo in the top left corner. Does this maybe look like the problem you are having ? http://forum.xda-developers.com/showthread.php?t=2580084
Re: Mobile App STACK4 with a D backend
On 27.12.2013 12:33, extrawurst wrote: > Does this maybe look like the problem you are having ? > http://forum.xda-developers.com/showthread.php?t=2580084 Yes, just blank screen and nothing happens. -- mk
Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
Hi everyone, Despite I released the big completion engine refactoring half a week ago I'd still like to announce it over here as well. There's been a complete completion engine overhaul (i.e. the part that matches the currently selected code part against the abstract symbol node in the AST and furthermore prepares the resolution of that node) and several performance improvements concerning parsing code & code completion. The full release note: http://mono-d.alexanderbothe.com/huge-completion-engine-refactoring-less-internal-clutter-v0-5-5-5/ Completion bugs/issues/requests: https://github.com/aBothe/D_Parser/issues Non-completion related stuff: https://github.com/aBothe/Mono-D/issues Cheers, Alex
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 16:40:57 UTC, Alexander Bothe wrote: Hi everyone, Despite I released the big completion engine refactoring half a week ago I'd still like to announce it over here as well. There's been a complete completion engine overhaul (i.e. the part that matches the currently selected code part against the abstract symbol node in the AST and furthermore prepares the resolution of that node) and several performance improvements concerning parsing code & code completion. The full release note: http://mono-d.alexanderbothe.com/huge-completion-engine-refactoring-less-internal-clutter-v0-5-5-5/ Completion bugs/issues/requests: https://github.com/aBothe/D_Parser/issues Non-completion related stuff: https://github.com/aBothe/Mono-D/issues Cheers, Alex Excellent! Alex has been fixing a lot of bugs regarding DUB package support that I've reported recently. It's nice having an IDE that knows how to read and set up a project based on a package.json file. Regards, Kelet
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 16:40:57 UTC, Alexander Bothe wrote: There's been a complete completion engine overhaul (i.e. the part that matches the currently selected code part against the abstract symbol node in the AST and furthermore prepares the resolution of that node) and several performance improvements concerning parsing code & code completion. Thank you. I tried Mono Develop 4.2 and Mono-D 0.5.5.4, it was great. I have only one request: can you focus at the Mono-D stability? I saw a few errors last time (I'm not shure if it was Mono Develop errors or Mono-D errors). So, can you use only stable Mono Develop versions and print current required Mono Develop version? Also, can you create betta/rc versions of Mono-D and, maybe, create separate repro for it? In past I had very bad experience of work with Mono-D because any Mono Develop and/or Mono-D upgrade could break the IDE. So, it will be really great to see stable Mono-D.
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 17:52:22 UTC, ilya-stromberg wrote: I have only one request: can you focus at the Mono-D stability? I saw a few errors last time (I'm not shure if it was Mono Develop errors or Mono-D errors). Then please tell me as soon as they appear! Assuming that you've got a longer programming experience, you should know well that silent/destructive raging won't help anybody! :) So, can you use only stable Mono Develop versions and print current required Mono Develop version? That's one thing I did for the last bunch of years. I hated it, brought even more confusion and I had doubled circumstances to manage everything. Atm I'm very happy that I can even release Mono-D for all 3 major OS platforms exclusively via addins.monodevelop.com which is the built-in distribution platform of MD. Also, can you create betta/rc versions of Mono-D and, maybe, create separate repro for it? I'd rather recommend to downgrade if something is not working at all - or just skip versions (like the usual main release followed by several bug fix releases - It's always your choice not to update!) I know this implies some efforts (head to http://addins.monodevelop.com/Project/Index/27 and select an older release :-)) but ensures that quite everyone is using the very latest version. Only then I can locate bugs&issues most efficiently. In past I had very bad experience of work with Mono-D because any Mono Develop and/or Mono-D upgrade could break the IDE. So, it will be really great to see stable Mono-D. Lastly, please define 'stable'. I think you mean 'not crashing at every key stroke' - well, that can indeed happen from time to time. But still, it's continous partly test-driven rolling-released integration - what do you expect? :-D Furthermore, the guys from MonoDevelop seem to have taken a break from changing the APIs on every release plus if you use the dub architecture, Mono-D is a fully opt-in solution to develop your project. If it's just crashing, keep on developing with other tools and may return if it's working again. Or just keep filing issue reports, or try to fix it on your own - it's FOSS! :-)
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 19:09:28 UTC, Alexander Bothe wrote: On Friday, 27 December 2013 at 17:52:22 UTC, ilya-stromberg wrote: I have only one request: can you focus at the Mono-D stability? I saw a few errors last time (I'm not shure if it was Mono Develop errors or Mono-D errors). Then please tell me as soon as they appear! Assuming that you've got a longer programming experience, you should know well that silent/destructive raging won't help anybody! :) It was non-critical errors and thay appeared randomly. At least I can't reproduse it now. But OK, I'll try to send bug reports. So, can you use only stable Mono Develop versions and print current required Mono Develop version? That's one thing I did for the last bunch of years. I hated it, brought even more confusion and I had doubled circumstances to manage everything. Atm I'm very happy that I can even release Mono-D for all 3 major OS platforms exclusively via addins.monodevelop.com which is the built-in distribution platform of MD. I don't talk that you must support different Mono Develop versions for different OS. Current stable Mono Develop is 4.2.2, can you use it for all supported OS and specify recomended Mono Develop version ad the `http://mono-d.alexanderbothe.com/download/` page? I just want to say: "please, don't use Alpha/Betta Release of Mono Develop". I have a lot of problems with Betta Release of Mono Develop at Ubuntu ~2 years ago. Also, can you create betta/rc versions of Mono-D and, maybe, create separate repro for it? I'd rather recommend to downgrade if something is not working at all - or just skip versions (like the usual main release followed by several bug fix releases - It's always your choice not to update!) Not exactly. Actually, I decided do not to update, but one day I had to create a new MonoD installation after OS re-install, and it was complitly broken. I couldn't even open the project. It was terrible. After that I decided to use Eclipse/DDT, even it has less features. I know this implies some efforts (head to http://addins.monodevelop.com/Project/Index/27 and select an older release :-)) but ensures that quite everyone is using the very latest version. Only then I can locate bugs&issues most efficiently. OK. Can you add instruction how to do downgrade? In past I had very bad experience of work with Mono-D because any Mono Develop and/or Mono-D upgrade could break the IDE. So, it will be really great to see stable Mono-D. Lastly, please define 'stable'. I think you mean 'not crashing at every key stroke' - well, that can indeed happen from time to time. Yes, exactly. But I agree that Mono-D looks much better than before. But still, it's continous partly test-driven rolling-released integration - what do you expect? :-D Furthermore, the guys from MonoDevelop seem to have taken a break from changing the APIs on every release plus if you use the dub architecture, Mono-D is a fully opt-in solution to develop your project. If it's just crashing, keep on developing with other tools and may return if it's working again. Or just keep filing issue reports, or try to fix it on your own - it's FOSS! :-) Unfortunately, dub didn't exist at that days. But yes, today it's possible.
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 19:45:09 UTC, ilya-stromberg wrote: OK. Can you add instruction how to do downgrade? I believe the process is like this: 1. Close any D Language solutions you may have open. 2. Open the add-in manager (under tools menu), go to the "Gallery" tab, and under "Language bindings", uninstall the "D Language Binding". 3. Restart MonoDevelop/Xamarin Studio (you will be prompted to). 4. Download the version that you'd like to use from the aforementioned website. 5. Open the add-in manager, and on the bottom left there is "Install from file" - select the file you downloaded from the website. Regards, Kelet
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
Awesome. It seems to work fine so far. Since I started using dub I had to say goodbye to what working IDEs I had running, and when I tried Mono I was unlucky enough to do so right after an update that killed everything (mono crashed, plugins didn't work, couldn't find compiler, couldn't recognize d files, kept wanting to downgrade plugins once installed). It looks good now though. Integration with dub could be explained a tad better (hint: open the package.json file and done), but it's really easy. I realize this doesn't say much about Mono-D, but an IDE that hasn't crashed yet is better than no IDE. :P
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
I'll take it back. When writing a module specification, it kept
interrupting me with this error. Due to an annoying error in
Mono-Develop, I cannot change the language in the program without
changing it in my OS, which I don't bother this moment. I have
translated the first line, it's in {}. "ved" means "at".
{ System.NullReferenceException: The objekt reference is not
configured to an occurence of an object. }
System.NullReferenceException: Objektreferencen er ikke
indstillet til en forekomst af et objekt.
ved
D_Parser.Dom.DefaultDepthFirstVisitor.Visit(ArrayLiteralExpression
x)
ved
D_Parser.Dom.Expressions.ArrayLiteralExpression.Accept(ExpressionVisitor
vis)
ved
D_Parser.Completion.CompletionProviderVisitor.Visit(DVariable n)
ved D_Parser.Dom.DVariable.Accept(NodeVisitor vis)
ved
D_Parser.Dom.DefaultDepthFirstVisitor.VisitChildren(IBlockNode
block)
ved
D_Parser.Completion.CompletionProviderVisitor.VisitChildren(IBlockNode
block)
ved
D_Parser.Dom.DefaultDepthFirstVisitor.VisitBlock(DBlockNode block)
ved D_Parser.Dom.DefaultDepthFirstVisitor.Visit(DModule n)
ved D_Parser.Dom.DModule.Accept(NodeVisitor vis)
ved
D_Parser.Completion.CodeCompletion.GenerateCompletionData(IEditorData
editor, ICompletionDataGenerator completionDataGen, Char
triggerChar, Boolean alreadyCheckedCompletionContext)
ved
MonoDevelop.D.Completion.DCodeCompletionSupport.BuildCompletionData(Document
EditorDocument, DModule SyntaxTree, CodeCompletionContext ctx,
CompletionDataList l, Char triggerChar)
ved
MonoDevelop.D.DEditorCompletionExtension.HandleCodeCompletion(CodeCompletionContext
completionContext, Char triggerChar, Int32& triggerWordLength)
ved
MonoDevelop.Ide.Gui.Content.CompletionTextEditorExtension.KeyPress(Key
key, Char keyChar, ModifierType modifier)
ved MonoDevelop.D.DEditorCompletionExtension.KeyPress(Key key,
Char keyChar, ModifierType modifier)
ved
MonoDevelop.Ide.Gui.Content.TextEditorExtension.KeyPress(Key key,
Char keyChar, ModifierType modifier)
ved
MonoDevelop.D.Formatting.Indentation.DTextEditorIndentation.KeyPress(Key
key, Char keyChar, ModifierType modifier)
ved
MonoDevelop.Ide.Gui.Content.TextEditorExtension.KeyPress(Key key,
Char keyChar, ModifierType modifier)
ved
MonoDevelop.Ide.Gui.Content.TextEditorExtension.KeyPress(Key key,
Char keyChar, ModifierType modifier)
ved
MonoDevelop.Ide.Gui.Content.TextEditorExtension.KeyPress(Key key,
Char keyChar, ModifierType modifier)
ved
MonoDevelop.Ide.Gui.Content.TextEditorExtension.KeyPress(Key key,
Char keyChar, ModifierType modifier)
ved
MonoDevelop.Ide.Gui.Content.TextEditorExtension.KeyPress(Key key,
Char keyChar, ModifierType modifier)
ved
MonoDevelop.Debugger.ExceptionCaughtTextEditorExtension.KeyPress(Key
key, Char keyChar, ModifierType modifier)
ved
MonoDevelop.SourceEditor.ExtensibleTextEditor.ExtensionKeyPress(Key
key, UInt32 ch, ModifierType state)
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 19:45:09 UTC, ilya-stromberg wrote: It was non-critical errors and thay appeared randomly. At least I can't reproduse it now. But OK, I'll try to send bug reports. Please! Bug trackers, mails, blog comments, IRC, G+ - even via facebook :O There are so many ways to communicate! :-) I don't talk that you must support different Mono Develop versions for different OS. Current stable Mono Develop is 4.2.2, can you use it for all supported OS and specify recomended Mono Develop version ad the `http://mono-d.alexanderbothe.com/download/` page? I just want to say: "please, don't use Alpha/Betta Release of Mono Develop". I have a lot of problems with Betta Release of Mono Develop at Ubuntu ~2 years ago. This is why I decided to distribute my very own Linux x86/x64 version of MonoDevelop on simendsjo's server @ http://simendsjo.me/files/abothe in order to prevent exactly these kinds of circumstances - since that version is the version I'm using the most time on my machine. Not exactly. Actually, I decided do not to update, but one day I had to create a new MonoD installation after OS re-install, and it was complitly broken. I couldn't even open the project. It was terrible. After that I decided to use Eclipse/DDT, even it has less features. Sure, and then you'll have the chance to 'return' two years afterwards :) I know this implies some efforts (head to http://addins.monodevelop.com/Project/Index/27 and select an older release :-)) but ensures that quite everyone is using the very latest version. Only then I can locate bugs&issues most efficiently. OK. Can you add instruction how to do downgrade? See Kelet's instructions.
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 20:23:51 UTC, Casper Færgemand
wrote:
I'll take it back. When writing a module specification, it kept
interrupting me with this error. Due to an annoying error in
Mono-Develop, I cannot change the language in the program
without changing it in my OS, which I don't bother this moment.
I have translated the first line, it's in {}. "ved" means "at".
{ System.NullReferenceException: The objekt reference is not
configured to an occurence of an object. }
System.NullReferenceException: Objektreferencen er ikke
indstillet til en forekomst af et objekt.
ved
D_Parser.Dom.DefaultDepthFirstVisitor.Visit(ArrayLiteralExpression
x)
Makes me smile :-D
That's the usual stuff I'm talking about - those classical places
of null-ref exceptions where I simply couldn't imagine they could
occur at exactly that location.
Module specification - like module ABC; ? You'll laugh: It works
for me, no exception when trying to write such statement.
Furthermore I had to wonder why it's throwing at visiting
ArrayLiterals..anyway, thanks for the quick report.
Looking at the code, there's not even the possibility to have an
NRE occuring over there. Something weird happened again.
Cheers,
Alex
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 20:37:23 UTC, Alexander Bothe wrote: On Friday, 27 December 2013 at 19:45:09 UTC, ilya-stromberg wrote: I don't talk that you must support different Mono Develop versions for different OS. Current stable Mono Develop is 4.2.2, can you use it for all supported OS and specify recomended Mono Develop version ad the `http://mono-d.alexanderbothe.com/download/` page? I just want to say: "please, don't use Alpha/Betta Release of Mono Develop". I have a lot of problems with Betta Release of Mono Develop at Ubuntu ~2 years ago. This is why I decided to distribute my very own Linux x86/x64 version of MonoDevelop on simendsjo's server @ http://simendsjo.me/files/abothe in order to prevent exactly these kinds of circumstances - since that version is the version I'm using the most time on my machine. Great! In that case can you just print your MonoDevelop version to the download page. Now you have: Head to http://monodevelop.com/Download and install the latest release (it may even be an ‘Alpha’ version) of MonoDevelop It's exactly that I don't want to have (‘Alpha’ version). OK. Can you add instruction how to do downgrade? See Kelet's instructions. Can you add the instructions to the your site? I think it can help to many people if they'll see an errors.
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 20:53:26 UTC, ilya-stromberg wrote: Great! In that case can you just print your MonoDevelop version to the download page. Now you have: Head to http://monodevelop.com/Download and install the latest release (it may even be an ‘Alpha’ version) of MonoDevelop It's exactly that I don't want to have (‘Alpha’ version). This is the MonoDevelop magic (yes, next to the D magic there is some in MonoDevelop as well :-)) I had to understand in before either: There is no alpha, beta or stable version even if it's called that way. The only way those versions differ between each other are API changes and bug fixes/regressions. Currently, both stable and master-built (from the git master repo) versions feature the very similar API what makes Mono-D (currently!) running on all 4.2 releases. This might change again - but atm, it works. OK. Can you add instruction how to do downgrade? See Kelet's instructions. Can you add the instructions to the your site? I think it can help to many people if they'll see an errors. Sure.
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 20:47:07 UTC, Alexander Bothe wrote: snip Cheers, Alex Hmm, it's not just modules, I think I know what's wrong. I just wrote SysTime and stopped, realizing I wanted it in a function instead. As I started writing the new function, I was continuously interrupted with a similar null-pointer until I removed the original line just containing SysTime. It looks to me like it happens whenever there's incomplete code, so I'd think it related to the syntax checking or whatever magic. I can avoid it by just not leaving incomplete code, though my brain is going to complain =/. Perhaps it's a quirk of Mono-Develop rather than the plugin. Given the inability to change language, such a bug would not surprise me. :P
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 22:58:23 UTC, Casper Færgemand wrote: On Friday, 27 December 2013 at 20:47:07 UTC, Alexander Bothe wrote: snip Cheers, Alex Hmm, it's not just modules, I think I know what's wrong. I just wrote SysTime and stopped, realizing I wanted it in a function instead. As I started writing the new function, I was continuously interrupted with a similar null-pointer until I removed the original line just containing SysTime. It looks to me like it happens whenever there's incomplete code, so I'd think it related to the syntax checking or whatever magic. I can avoid it by just not leaving incomplete code, though my brain is going to complain =/. Perhaps it's a quirk of Mono-Develop rather than the plugin. Given the inability to change language, such a bug would not surprise me. :P May I have some code samples? Writing 'SysTime' may happen everywhere - as well as 'a similar null-pointer' .. I have no magic glass bowl to look in, you know. ;-) Cheers, Alex
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Saturday, 28 December 2013 at 02:02:44 UTC, Alexander Bothe wrote: May I have some code samples? Writing 'SysTime' may happen everywhere - as well as 'a similar null-pointer' .. I have no magic glass bowl to look in, you know. ;-) I can't reproduce it in a new file. I can, however, go to any line in my existing project, press a key on the keyboard, and the code completion window crashes with a null pointer. Not sure what you want aside from that. I don't see why it would have anything to do with what code I've written. My only import outside Phobos is Pegged. D_Parser.Dom.DefaultDepthFirstVisitor.Visit(ArrayLiteralExpression x)
Re: Mono-D v0.5.5.5 - Huge completion refactoring/v0.5.5.6 - Bug fixes
On Friday, 27 December 2013 at 21:59:12 UTC, Alexander Bothe wrote: On Friday, 27 December 2013 at 20:53:26 UTC, ilya-stromberg wrote: Great! In that case can you just print your MonoDevelop version to the download page. Now you have: Head to http://monodevelop.com/Download and install the latest release (it may even be an ‘Alpha’ version) of MonoDevelop It's exactly that I don't want to have (‘Alpha’ version). This is the MonoDevelop magic (yes, next to the D magic there is some in MonoDevelop as well :-)) I had to understand in before either: There is no alpha, beta or stable version even if it's called that way. The only way those versions differ between each other are API changes and bug fixes/regressions. Currently, both stable and master-built (from the git master repo) versions feature the very similar API what makes Mono-D (currently!) running on all 4.2 releases. This might change again - but atm, it works. When I used `ppa:keks9n/monodevelop-latest` repro, the MonoDevelop updated every day. So, it was alpha version. BTW, I had a lot of problems with it, new `ppa:ermshiperete/monodevelop` looks much better. I repeat, please write supported MonoDevelop version at the download page. You have too many opportunities for Ubuntu: we have 3 different repros and nobody knows the correct one. BTW, `ppa:ermshiperete/monodevelop` contains pre-installed Mono-D, so it looks like the maintainer wants to support correct MonoDevelop version for Mono-D. Additional request: please use more intuitive version number, see http://semver.org/ because current version scheme doesn't provide any additional information. Please use: 1) 1-st digit if you need to upgrade the MonoDevelop version with incompatible API changes 2) 2-nd digit if you have new features, code refactoring or any other big code change 3) 3-d digit if you have only bug fixes It can help a lot. For example, 2 last Mono-D versions should have 0.5.6.0 and 0.5.6.1 numbers.
