Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-15 Thread Araq
Hmmm I got summoned here. Libraries that don't follow Nim's conventions are bad but worse for Nim are non-existing libraries so go ahead and do what you consider the best solution. But fwiw, the reason why we make `foo_bar` the same as `fooBar` is that `foo_bar` shouldn't exist to begin with

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-14 Thread moerm
@dom96 is right. In a given language it's the _language 's_ rules that apply. And there are good reasons for that. To provide just one example: Syntax highlighting. We should also keep in mind that **readability** has been shown in multiple studies (which looked at _real world_ dev.

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-14 Thread cumulonimbus
> You should follow the language's conventions, not the libraries. Off topic for this thread, sorry, but ... I can't square this with Nim's liberal grouping of camelCaseWhichIHate and camel_case_which_I_hate. So far, I only use Nim on linux, interfacing with existing libraries all using

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-14 Thread miran
;)

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-14 Thread citycide
> it seems that there is no more users except me and Ward Hmm? I use it, and while I respect the author's choice to keep the current convention I do wish it would follow Nim's type vs value casing guidelines at the very least. It's not like it's a wild departure from the original lib and could

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-14 Thread oyster
I respect every contribution to Nim. But don't make conventions be a religion. ok maybe you can make it yourself's religion, but do not command all others do so. In fact, I use wxPython so I can learn wNim without too hard work. wNim is the first(and till now the only) library for me to make a

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-13 Thread SolitudeSF
> Name convention is not the faith or the absolute rule. they should be

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-13 Thread Ward
I don't agree. Name convention is not the faith or the absolute rule. The names I used are more convenient and more familiar to wxWidget users, at least, for me. If who don't like the name convention I used, he can choose not to use the library.

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-13 Thread dom96
You should follow the language's conventions, not the libraries.

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-11 Thread Ward
wNim's use the name convention according to wxWidgets. wCommandID is corresponding to wxWidgets' wxWindowID.

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-11 Thread dom96
Please consider calling these types `WCommandId` etc. Nim convention is to name types with an uppercase first letter.

Re: release: a current-runable, error-in-the-future msgbox for wNim

2018-11-11 Thread enthus1ast
if this is a package others should be able to install with nimble, you need to create a nimble file. So that one could do install https://github.com/retsyo/nim-myMsgBox Run see

release: a current-runable, error-in-the-future msgbox for wNim

2018-11-10 Thread oyster
I, a programming amateur and (always) newbie, released my msgbox control for [https://github.com/khchen/wNim](https://github.com/khchen/wNim), which can specify the font for message and buttons , at [https://github.com/retsyo/nim-myMsgBox](https://github.com/retsyo/nim-myMsgBox) I don't have