Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Mike Wright
    @itsxallwater
    I also added a .vscodeignore file, @dthiot, which should keep the Word doc out among other unnecessary files
    MVDBMS Solutions
    @MVDBMS-Solutions
    Installed 2.0.1. Looks good. Checked license and changelog pages - they're updating as well.
    About platform-specific syntax, for whomever is working on that (myself for D3), the page I created for AccuTerm might help : https://www.pickwiki.com/index.php/AccuTermKeywords
    I'm also going to try to get code folding to use the start/end markers that I use in AccuTerm WED, and allow these to be configurable.
    Mike Wright
    @itsxallwater
    Solid
    MVDBMS Solutions
    @MVDBMS-Solutions
    Gonna break from this for the day. Got a good start but this is a long term project and there are other daily priorities. But thanks again to each person involved for kicking this out. It's going to be fun.
    Mike Wright
    @itsxallwater
    Likewise, the paid work needs attention :P
    Dick Thiot
    @dthiot
    @itsxallwater, I am in 100% agreement with VuePress. I spent a little time looking at it but determined to get the release out and not hold things up with a conversion to VuePress. I'm happy to let Jeff T or Tony G or whomever make the conversion but my plan was to start spending some time on that later this week.
    MVDBMS Solutions
    @MVDBMS-Solutions
    If the source is Markdown, doesn't that leave the final deployment open to VuePress, GitHub Wiki, and other tools as well? If so then perhaps that should be the near-term target.
    MVDBMS Solutions
    @MVDBMS-Solutions
    Would I be too anal to suggest that BASIC is and should be a capitalized acronym, where Basic is a Microsoft-originated abomination?
    Dick Thiot
    @dthiot
    YES.
    Charles Barouch
    @CharlesBarouch
    mvBASIC works for me.
    Dick Thiot
    @dthiot
    J/K... That is a good suggestion.
    MVDBMS Solutions
    @MVDBMS-Solutions
    LOL. I think it's anal but I'm OK with that too. :)
    Dick Thiot
    @dthiot
    I have tried in the documentation to be very consistent but have not had anyone act as a proof reader or editor.
    Not anal, just OCD.
    Charles Barouch
    @CharlesBarouch
    CDO, put the letters in the right order!
    Dick Thiot
    @dthiot
    Thanks to a nifty little tool, I have a version of the documentation in Markdown. I am now working on a little cleanup before jumping back to real work.
    Mike Wright
    @itsxallwater
    That's exciting, Dick!
    MVDBMS Solutions
    @MVDBMS-Solutions
    To help with Markdown, there is a VSCode extension : Markdown Preview Enhanced. You can look at your markdown in (example) the left pane and the rendered result in the right.
    Interesting bug ... when I'm editing using the "Markdown" language server, I still get MVON# syntax checking. I think it's using the "*" activation but it's interesting that it's "bleeding trough". It's like polyglot coding, where we have HTML embedded in PHP, or JavaScript embedded in HTML. Since this is MVON# doing this and not the MVBASIC extension, I've disabled MVON# and will ignore the anomaly ... but will keep an eye open for it in case it pops up again.
    Dick Thiot
    @dthiot
    I already have the Markdown extension. Is the extension of your Markdown file ".md"? Does the file type at the bottom show Markdown?
    Are we using Gitter instead of Slack for a really good reason? Can we have multiple channels on Gitter?
    MVDBMS Solutions
    @MVDBMS-Solutions
    File type does show Markdown on a .md file. I've disabled it. May come back to triage later.
    MVDBMS Solutions
    @MVDBMS-Solutions
    Yes, we can have multiple gitter channels. The first channel comes with a "Community" room. More rooms can be created and then linked to a repo. For an example, see the link at the bottom of the repo a new project I've created: https://github.com/MVDBMS-Solutions/Adventure/ There is a channel for MVDBMS-Solutions, and a separate room for "Adventure".
    MVDBMS Solutions
    @MVDBMS-Solutions
    As to using Gitter or Slack. I've said a few times that there is no either/or/preference. Post where you want. Read where you want. It's up to you where you want to be and up to others where they want to be. Does that mean we will lose messages if "I" am not where "you" are? Yes, certainly. If we make any one place "official" then people who are not there will miss anything official. That's not cool. So we chat wherever we wish, and if there is anything "official" it should get posted wherever people are watching for notices. Forget Slack and Gitter. Think about people who have Facebook and/or Twitter. Think about newspaper vs radio vs TV. Think about email vs SMS. Think about a Yahoo Group vs Google Group. People are where they want to be. Limitations mean losses. I see no good reason to isolate or lose anyone in a community where we're struggling to engage as many people as we can.
    Dick Thiot
    @dthiot
    While I see and agree with your point I think that there are discussions that can be limited to a certain audience. All communications shouldn't necessarily be open to everyone. All communications don't need to be public. If the discussion is specific to this project and for the maintainers then there should be a way to communicate or even person to person communication that doesn't need to be public and therefore bordering on SPAM for those that the discussion is not meant for. I don't believe that a person should have to filter what they want. I go to the sports page because I don't want to read the other news and the sports are all that interest me. This doesn't mean that we exclude any one.
    MVDBMS Solutions
    @MVDBMS-Solutions

    Well, the only thing we should be talking about here is this one extension. So anyone who subscribes their interest in this extension should only be getting info about this one extension, not about anything that doesn't interest them.

    "All communications shouldn't necessarily be open to everyone. All communications don't need to be public."
    I don't see a need for non-public channels for a FOSS project. That's not the way it's done. Individuals can certainly choose to talk with one another about details that don't involve others. For example : "Did you leave off that semicolon for a reason?" But more general topics should be open for anyone to consider and voice an opinion. That's how "open" software development works ... and yes, it is rather chatty but democracy is a rather sloppy process in general.

    That said, if there are going to be other mvextensions, other than mvbasic, I would agree that a new room should be created to avoid polluting this more general room - but with a luxury of only 5 people having interest so far, I don't think that's a problem that needs to be solved yet.

    My intent is to communicate how the rest of the world uses the technology. I'm getting a bit frustrated with going back and forth on this single concept of choice, with human communications and with client/server connectivity. I don't think you'll find a single person saying they do not want choices. You'll only find people asking for more options. (I stopped short of recommending Discord as yet another option, which is wildly popular in software development (as is Slack) but unheard-of in the MV world.) I recommended Gitter for people who already have GitHub accounts - and Slack for those who do not.

    Again, choose your option but please don't try to restrict others based on your choices. If that is not something that the originators of this extension wanted or imagined then perhaps this shouldn't be a free=liberty and open (public discussions) package. And that said ... it's completely valid to simply reject suggestions. I volunteer that some of my suggestions might be invalid or simply undesirable, and I'm really OK with any suggestion getting rejected. So please don't feel like I'm trying to be forceful about anything either ... except about not being forceful. :)

    Best to ya bud!

    Dick Thiot
    @dthiot
    I am not sure my comments were clear, especially "All communications shouldn't necessarily be open to everyone." I understand FOSS and I don't think that discussions shouldn't be open to anyone, my point that I am trying to make is that there is sometimes "chatter" that is between two or more that is just interruptive of the group as a whole. If the group wants all discussions to invade everyone's time then who am I to disagree. Funny that you should mention Discord as Charles Barouch initially setup discord if I remember correctly. I will say that my biggest opposition to Gitter and Discord is that I already have 8+ chat type clients that I have to deal with. Adding 1 or 2 more is only adding to the pain.
    MVDBMS Solutions
    @MVDBMS-Solutions
    Thanks for the exchanges. There are private chats here and in Slack for those who want to take discussions off-list. In the browser UI, mouse-over the icon of individuals.
    Mike Wright
    @itsxallwater
    Chuck went the Discourse route not Discord, FWIW. Similar but different :)
    Dick Thiot
    @dthiot
    It was Discourse. There are too many chat platforms! :D BTW, I am using the Chrome extension All-In-One Messenger for all but Slack. All-In-One does Slack too but I have too many Workspaces that the actual client just works better. At least most of the chat platforms are in one place.
    MVDBMS Solutions
    @MVDBMS-Solutions
    I totally hear ya man. For years I was using Trillian to help with the IM chats of the day: IRC, ICQ, Yahoo, MSN, AIM, XMPP/Jabber... Perhaps that's confirmation of my mantra - I don't ask people to go to specific places. I don't want to deal with the "but I like Foo" rebuttal. I try to accommodate wherever people want to hang out, especially clients. Today that also means a bunch of different screenshares and remoting tools, portals, etc. Whatever they have, I just say "yes". And for this project and anything else I'm in, I don't care where someone wants to report an issue or discuss a feature. I want it to be easy for them so that we don't lose those voices. So I try to reduce that barrier by offering options. Yes, that makes it more difficult on those of us who want to hear all of those voices. For that, we have the all-in-one tools and other tricks of the trade to keep informed. This is the deck of cards that we have to play with in today's world.
    And that dove-tails with the DBMS connectivity challenge : Whatever DBMS connectivity people want to use, whatever they already have and love, I just want to say "yes" so that more people feel like they're in their comfort zone and we can remove impediments to using this and other software. With connectivity this is important, because some sites want to purchase licenses for tools that provide session pooling. Do we want 3 developers at an end-user site to consume three more DBMS licenses in order to use VSCode? Personally I think not. So whatever pooling tool they have I'm hoping we can accommodate it with a simple Settings option.
    MVDBMS Solutions
    @MVDBMS-Solutions
    Working on D3 language details, almost entirely just removal of all of the stuff supported by MVON and not by D3. Getting a little envious of the broad scope of MVON BASIC features. Real education.
    Hmm, I copied this from Universe. For whomever modified the UniVerseLanguage.json, did you leave in MVON stuff? I'm seeing a lot in here about PI/Open, type 1/19 files, tc.
    MVDBMS-Solutions @MVDBMS-Solutions is now using the Gitter Windows app for desktop/tray notifications.
    Mike Wright
    @itsxallwater
    @JeffTeter ping on that
    See the question above on the UniVerse language mods when you have a moment :)
    Charles Barouch
    @CharlesBarouch
    Are we meeting today? I'd like to get the doc conversation rolling. I sent invites.
    Mike Wright
    @itsxallwater
    believe so, would be good to confirm moving the call time going forward as well if people still wanted to do that
    Charles Barouch
    @CharlesBarouch
    Happy to do that. works better for me.
    Charles Barouch
    @CharlesBarouch
    Anyone else doing hacktoberfest.digitalocean.com?
    Dick Thiot
    @dthiot
    I am good to move the meeting. I am traveling and will be available for a few minutes at the start of the meeting to be on the call before my flight boards. As for the docs, I have a basic conversation to Markup but hadn't worked on it enough time to get it truly converted to Markup.
    Charles Barouch
    @CharlesBarouch
    You can send me the partial and the original. I can pick up on it.
    Dick Thiot
    @dthiot
    Email on markdown version of documentation sent.
    MVDBMS Solutions
    @MVDBMS-Solutions
    I recommend developing habits for a more modern, distributed-colaborative workflow. That would involve forking, , commiting changes into a work branch, collaborating on a common dataset, getting some eyes on the final branch, then doing a PR into the core. This is the way this stuff all works now. I understand that email is the way it's been done in mvLand since the 90's. But I have never heard of people working in Github and emailing assets to one another. HTH
    Dick Thiot
    @dthiot
    While you are correct as usual Tony, I was traveling last week and sent that as a quick way to get it to him. I had done an initial conversion from Word to Markdown but had not committed my updates.
    Mike Wright
    @itsxallwater
    FYI, got a bit of time in on #14 today as described https://github.com/mvextensions/mvbasic/issues/14#issuecomment-558802665. If you run with that branch you get a new extension config that'll allow you to swap the language definitions. Syntax highlighting and snippets still to come.
    Mike Wright
    @itsxallwater
    FYI we've published v2.0.4 and you can see the latest docs at https://github.com/mvextensions/mvbasic/blob/master/doc/Extension%20Guide.md.