« first day (232 days earlier)      last day (2948 days later) » 

00:10
Lol... Eh. No one will ever see that post again anyway.
 
13 hours later…
12:47
> extracted import/export ext methods; closes #153; closes #154
 
3 hours later…
15:26
@Mat'sMug here's something interesting. A raw user form file outside the IDE.
VERSION 5.00
Begin {C62A69F0-16DC-11CE-9E98-00AA00574A4F} UserForm1
   Caption         =   "UserForm1"
   ClientHeight    =   3165
   ClientLeft      =   45
   ClientTop       =   390
   ClientWidth     =   4710
   OleObjectBlob   =   "UserForm1.frx":0000
   StartUpPosition =   1  'CenterOwner
End
Attribute VB_Name = "UserForm1"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = False
Option Explicit
I can see that breaking the parser if we pass a plain file to it.
15:56
> fixed export bug
16:52
@RubberDuck Nope. ANTLR takes anything you throw at it. There would just be a few ErrorNodes instead of the module header stuff. Or the grammar can be adjusted pretty easily to pick it up ;)
17:23
Oh yeah? That's pretty cool.
17:37
@RubberDuck Is that from Access?
No @Mat'sMug. That's a regular old UserForm.
Bah, we don't really care about the module header stuff do we?
I'm trying to decide what to do with document modules. (ThisWorkbook, Sheet1, etc). You can't import them the same as .cls and .bas files. Can't decide if I want to try to copy/paste the code or just exclude them entirely.
No. I don't think we care about headers, but I'm sure we'll want to look at attributes.
There's no problem with the attributes, they look standard
@RubberDuck Excluding them would be bad. I think we can use that VBE method to replace the code in a module, instead of importing these files
Oh. Yeah. Yeah. You're right. I was just wasn't sure if Attribute is in the keywords or whatever. (I don't know as much as I should about your parser)
17:46
I don't know as much as I should either ;)
Yeah. You've got a point there.
So, the question is... Do I export it all or write the file myself? I write the file myself so I don't have to deal with the header. Yeah. That will work best I think.
It also means procedre attributes can only apply to .bas and .cls modules
I can live with that I think
That's already true though.
So, yeah. That'll work. (I think)
> Rubberduck best practices: don't implement your logic in a worksheet event handler. Write a class, test it, and instantiate it in the worksheet code / call that object's public methods.
Yes. Which is why I was considering not exporting document modules at all, but you're right. That code should still be exportable.
17:53
Mostly for version control
It occurred to me that, once all inspections are implemented, ....we could revive Clippy! .. or have an actual rubber duck that pops up and says "it looks like you are declaring a variable."
^^ NOT!!!
We'd need to be able to detect changes in the code pane for that :(
18:12
That's a bit more than we can do I think. I don't know. I haven't figured out how to get a handle on the window yet. If I can get a handle on the window, we can key log.
Which is on the roadmap for snippets.
But no. No Clippy...
 
2 hours later…
19:46
> Importing Works
19:59
nice!
20:14
@RubberDuck (not VBA) question here
20:55
I saw that earlier, but your answer has made me reconsider my stance on spreadsheet formulas being off topic...
 
1 hour later…
22:11
@RubberDuck It felt more like spreadsheet review though
22:29
Yeah... Idk. Perhaps leave your thoughts on that meta you mentioned @Mat'sMug.
I was convinced by the whole "Just because we don't know how to review it doesn't mean it's off topic@ thing.
@RubberDuck Me too :)

« first day (232 days earlier)      last day (2948 days later) »